[SOLVED] [7SP1 x64] update fails on configuring after reboot

I have not yet released January updates. December update is currently hidden on this system to prevent it from constantly applying, failing, restarting, etc.
I can check online for the January update, have been holding off waiting for everyone to get their Meltdown/Spectre acts coordinated. This system is from 2012 and I don't want to mess it up any worse than it already is.
Do you want me to go ahead and check online and attempt January update?
 
Can I just unhide the already-downloaded December update and apply? Or do you want a fresh copy downloaded from MS?
 
Downloaded KB4054518 from MS website, standalone installer. Applied update, again failed at 7% during configuring stage. setupapi.dev.log zip attached.
 

Attachments

Can you right-click on the following files, go to the security tab, and verify that both SYSTEM and Administrators have Full permission?
c:\windows\inf\Usbstor.inf
c:\windows\inf\Usbstor.pnf
c:\windows\inf\Usb.inf
c:\windows\inf\Usb.pnf
c:\windows\inf\Usbport.inf
c:\windows\inf\Usbport.pnf
 
Both SYSTEM and Administrators have Full permissions to all of those files. I also verified that the domain relationship is still in effect, local Administrator group still shows domain members as it should.
 
Please do the following so I can gather more info.

FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop (you may use the one you already have downloaded).
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

Fix result of Farbar Recovery Scan Tool (x64) Version: 27.01.2018
Ran by networkadmin (29-01-2018 12:36:16) Run:8
Running from C:\Users\networkadmin\Desktop
Loaded Profiles: networkadmin & andy (Available Profiles: User1 & hal & networkadmin & lynn & andy)
Boot Mode: Normal
==============================================
fixlist content:
*****************
cmd: icacls c:\windows\inf\Usbstor.inf
cmd: icacls c:\windows\inf\Usbstor.pnf
cmd: icacls c:\windows\inf\Usb.inf
cmd: icacls c:\windows\inf\Usb.pnf
cmd: icacls c:\windows\inf\Usbport.inf
cmd: icacls c:\windows\inf\Usbport.pnf
*****************

========= icacls c:\windows\inf\Usbstor.inf =========
c:\windows\inf\Usbstor.inf NT AUTHORITY\SYSTEM:(I)(F)
BUILTIN\Administrators:(I)(F)
BUILTIN\Users:(I)(RX)
Successfully processed 1 files; Failed processing 0 files
========= End of CMD: =========

========= icacls c:\windows\inf\Usbstor.pnf =========
c:\windows\inf\Usbstor.pnf NT AUTHORITY\SYSTEM:(I)(F)
BUILTIN\Administrators:(I)(F)
BUILTIN\Users:(I)(RX)
Successfully processed 1 files; Failed processing 0 files
========= End of CMD: =========

========= icacls c:\windows\inf\Usb.inf =========
c:\windows\inf\Usb.inf NT AUTHORITY\SYSTEM:(I)(F)
BUILTIN\Administrators:(I)(F)
BUILTIN\Users:(I)(RX)
Successfully processed 1 files; Failed processing 0 files
========= End of CMD: =========

========= icacls c:\windows\inf\Usb.pnf =========
c:\windows\inf\Usb.pnf NT AUTHORITY\SYSTEM:(I)(F)
BUILTIN\Administrators:(I)(F)
BUILTIN\Users:(I)(RX)
Successfully processed 1 files; Failed processing 0 files
========= End of CMD: =========

========= icacls c:\windows\inf\Usbport.inf =========
c:\windows\inf\Usbport.inf NT AUTHORITY\SYSTEM:(I)(F)
BUILTIN\Administrators:(I)(F)
BUILTIN\Users:(I)(RX)
Successfully processed 1 files; Failed processing 0 files
========= End of CMD: =========

========= icacls c:\windows\inf\Usbport.pnf =========
c:\windows\inf\Usbport.pnf NT AUTHORITY\SYSTEM:(I)(F)
BUILTIN\Administrators:(I)(F)
BUILTIN\Users:(I)(RX)
Successfully processed 1 files; Failed processing 0 files
========= End of CMD: =========

==== End of Fixlog 12:36:17 ====
 
Please do the following so I can gather more info. Note the addition of step#6.

FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop (you may use the one you already have downloaded).
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
6. Also, please attach the file named perms that is located on your desktop.
 

Attachments

Fix result of Farbar Recovery Scan Tool (x64) Version: 27.01.2018
Ran by networkadmin (29-01-2018 14:13:24) Run:9
Running from C:\Users\networkadmin\Desktop
Loaded Profiles: networkadmin & andy (Available Profiles: User1 & hal & networkadmin & lynn & andy)
Boot Mode: Normal
==============================================
fixlist content:
*****************
cmd: icacls c:\windows\inf /save %userprofile%\desktop\perms
*****************

========= icacls c:\windows\inf /save %userprofile%\desktop\perms =========
processed file: c:\windows\inf
Successfully processed 1 files; Failed processing 0 files
========= End of CMD: =========


Had to save perms as perms.txt before I could attach, let me know if that messed anything up.

==== End of Fixlog 14:13:24 ====
 

Attachments

OK, I have an idea. Please repeat the following.

1. Download this file: http://live.sysinternals.com/procmon.exe
2. Run ProcMon.exe
3. Go to the Options menu, and click Enable Boot Logging and then close Procmon.
4. Create a folder on your Desktop in which you'll save the logs.
5. Try installing the failing update as you usually would.
6. Reboot your computer when requested.
7. Relaunch ProcMon. A dialogue box will appear asking if you wish to save the collected data. Please click Yes.
8. Save the file in the default format (.PML)
9. Save the file in a folder on your Desktop that you have created in Step 4.
10. Close ProcMon.
11. Zip up the entire folder containing ProcMon logs and upload to a filesharing service for me to review.
12. Please also zip up your entire c:\windows\logs\cbs folder and zip/upload to a filesharing service for me to review.
 
Do the following with the new local administrative user that you created.

Please check the following.
1. Sign back in to the computer with your new administrative local user account.
2. Navigate to c:\windows\inf and find usb.inf
3. Right-click on usb.inf and choose Properties
4. Click the Security Tab.
5. Click the Advanced button and verify it looks like the following.


6. Click the Owner tab and verify that the current owner is SYSTEM. If it is, please continue.
7. Click the Edit button, select the new local administrative user in the "Change owner to" listbox.
8. Click OK to the Windows Security alert that comes up. Click OK again....and then again to get out of all the dialog boxes.
9. Right-click on usb.inf and choose Properties
10. Click the Security tab. Click the Edit... button. Click Add.
11. Change the Locations...to the local machine.
12. Type in the name of the new local administrative user and click Check Names button.
13. Click OK. Ensure it is selected in the "Group or user names:" list box. Check the Allow Full control checkbox.
14. Click OK. Answer Yes to the Windows Security warning. Click OK again to exit the dialogs.

Thanks.
 
Well, it appears we have reached the end of our road. The office where that laptop lives was in was broken into last night, laptop was stolen. Powers that be have never seen a need to purchase tracking software for our few laptops. On a brighter note, I forgot to hide the December update after the last failure, so IF whoever has it manages to get in, they will be totally frustrated with constant restarts until/unless they wipe the OS and start over.

Sure wish we could have solved it - I wanted to know where the problem was! I read through part of one of the files I posted to you and was going to check permissions on the C:\Windows\System32\DriverStore folder, see if that might be the problem. Now we'll never know.

Thank you for all your help with this, you've been incredibly helpful and patient.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top