[SOLVED] [7SP1 x64] Monthly Quality Rollup failures - KB4041681, KB4054518, and KB4056894

Hopefully I've managed to follow your directions accurately. Awaiting your next directions...

Code:
SFCFix version 3.0.0.0 by niemiro.
Start time: 2018-01-28 15:39:19.968
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at C:\Users\Dennis\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-m..ents-mdac-ado15-dll_31bf3856ad364e35_6.1.7600.21227_none_68f23680a34301a2

Successfully copied file C:\Users\Dennis\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-m..ents-mdac-ado15-dll_31bf3856ad364e35_6.1.7600.21227_none_68f23680a34301a2\msado15.dll to C:\Windows\winsxs\amd64_microsoft-windows-m..ents-mdac-ado15-dll_31bf3856ad364e35_6.1.7600.21227_none_68f23680a34301a2\msado15.dll.

Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-m..ents-mdac-ado15-dll_31bf3856ad364e35_6.1.7600.21227_none_68f23680a34301a2
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-m..ents-mdac-ado15-dll_31bf3856ad364e35_6.1.7600.21227_none_68f23680a34301a2
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2018-01-28 15:39:22.058
Script hash: sxdsYAwR3+Uk7fEtsrrIKO2ZK34iC+mIE97MY6SS0TI=
----------------------EOF-----------------------

The scan done by scannow reported "Windows Resource Protection did not find any integrity violations."; I've attached the resultant cbs.txt.

View attachment cbs.txt
 
Windows Update currently shows KB4056894 needs to be installed (pre-checked by Windows for downloading & installation), and KB4033342 is queued up to be installed after KB4056894 is successfully installed (box is unchecked).
Note that I thought we were in the home stretch, and didn't quite read & follow your directions accurately. Initially I actually went through a manual installation, in which KB915597 and KB4055532 were successfully installed, and KB4056894 failed after reaching 98%, with the message "Failure Configuring Windows Updates" "Reverting Changes..."
 
Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Install KB4056894 just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
11908d1430506241-windows-updates-fail-repeatedly-stop-jpg


4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and attach the LogFile.PML file as well as your CBS.log
 
Last edited:
I'm good with all the above directions - except installing KB4056894 from an elevated command prompt. How do I install an update after opening a command prompt as an administrator? Lastly, do you want the LogFile.PMI and the CBS.log zipped as separate files or as a single file (or does it matter)?

Thanks - Dennis
 
CBS.zip: Dropbox - CBS.zip
Log point.zip: Dropbox - Log point.zip

Hopefully this is helpful, but please note that I tried several schemes yesterday to get copies of Logfile.PML and the CBS folder at the point of failure, but I was unable to get procmon.exe to continue recording through the manual & automatic reboots at the time the update failed. The failure flow follows:

Control Panel -> Windows Update -> select only KB4056894 & click install -> download, create Restore Point -> "The updates were successfully installed", at which time a manual reboot is required. This is the point I grabbed the linked zip files above. The screen shot below shows the state of the system when I grabbed the files.

Continuing the update process, I reboot the machine, the update installation fails (typically at 98% complete), and the system automatically rolls itself back. A second (automatic) reboot ensues, and a second message appears indicating the update failed and the system is rolling itself back. Once that's complete I'm taken to the login screen (there is no third reboot). The procmon.exe logging process does not survive the reboots.

log_point.JPG
 
Ah, yes, failure upon reboot. Do 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 only KB4056894 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 along with your CBS.log.
 
Dropbox - Logs.zip

Excellent - the new CBS folder and the Bootlog files were huge (4.82GB), but when zipped they're 'only' 438MB. I hope you have a tool that sorts things out quickly in your analysis!
 
I'd love to - but I'm trying to keep this machine alive to keep a licensed seat of SolidWorks 2008 functioning. The license is machine specific, and it would cost thousands to transfer it - if it would work on a Windows 10 machine at all. It's a bit of a drag. If money were no object, I'd upgrade both the machine and the CAD software, but... <sigh>
 
Understood. I just asked in case you weren't aware of the possibility.

Step#1 - FRST Scan
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Right click to run as administrator. When the tool opens click Yes to disclaimer.
3. Please ensure you place a check mark in the Addition.txt check box at the bottom of the form before running (if not already).
4. Press Scan button.
5. It will produce a log called FRST.txt in the same directory the tool is run from (which should now be the desktop)
6. Please copy and paste log back here.
7. Another log (Addition.txt - also located in the same directory as FRST64.exe) will be generated Please also paste that along with the FRST.txt into your reply.
 
The two files ran on for a total of about 2000 lines, so I attached them rather than copy/paste them. Hopefully this isn't an issue. (??)
 

Attachments

This is an interesting experience - I knew nothing of the existence of CheckSUR.log this morning, and here I've attached it to a message on a forum I knew nothing about just a short while ago. The depth of my inexperience is astounding!
 

Attachments

The computer has an Asus P6T Deluxe motherboard, and is hardwired from a port on the board to a Linksys WRT54GS wireless router, which is hardwired to an ARRIS SURFboard (SB6141) - and connected to a 30Mb/s WOW cable account. There is one other computer hardwired to the router - an HP5710 thinclient which is left on all the time to handle VoIP calls. There is also a Mac laptop (OSx 10.9.5) connected wirelessly to the router. The only other addition to the mix is a Canon MB5320 Printer, which handles printing and scanning via wireless connection to the router.
That's it - our home / office network - in all it's glory.
 
Apologies - there's 3 other bits on the network that were under my radar. There's an 8TB WD My Book Live Duo backup drive hardwired to the router through a Linksys SE3005 switch, a Sony DVD player with a wireless connection to the router, and a Powerly energy bridge that the local utility company uses in conjunction with a smart meter to optimize power usage.
Sooo... that's it. There ain't no more to the network.
 
Hi,
please zip up and attach the following file:

C:\Windows\winsxs\poqexec.log

Also, can you check if the "Remote Access Connection Manager" service is disabled? Do the same for this service "Routing and Remote Access".
 

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

Back
Top