[Server2012R2Upd3 x64] WU error 80073712 (Store Corruption)

[BrianDrab]

OK, looks like some corrupt xml files. Please do the following so I can validate which ones.

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Select the Options....Enable Boot Logging option. A Enable Boot Logging dialog will come up. Just click OK.
3. Create a folder on your desktop named BootLog.
4. Attempt to install KB4056898 just like you have in the past. Let the machine reboot and revert just like it has in the past.
5. After the machine has rebooted and come back up to the desktop, open Process Monitor again. A message box will come up telling you that a log of boot-time activity was created and ask if you wish to save it. Click Yes and save to the BootLog folder on your desktop.
6. This may take some time as it converts the boot-time data. Allow it to finish.
7. Zip up the entire BootLog folder on your desktop and upload to SendSpace and provide a link for me to download.
8. Also zip and upload your entire CBS folder.

Thank you.

 

[scs1]

Ok, so this was a little unexpected.


Having arranged a time when I can reboot and be available immediately afterwards to gather the log..


- I ran the KB4056898 installation again and it ran for something like 2 mins than finished. No error, no reboot request. I checked Windows Update History and it confirmed a successful install!
- So, I then ran the current security-only monthly update from 2018-02 (KB4074597) and that installed cleanly with no issues after reboot.


So that's good news - we can still get security-only rollups applied.


- Lastly I ran the current full monthly rollup (KB4074594) which failed - probably with the same IE-related issue we're trying to fix.


Here's a link to the CBS log folder, taken a few mins after the failure of KB4074594.


Download CBS.zip from Sendspace.com - send big files the easy way

 

[BrianDrab]

Interesting indeed. OK, please do the following.

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Select the Options....Enable Boot Logging option. A Enable Boot Logging dialog will come up. Just click OK.
3. Create a folder on your desktop named BootLog.
4. Attempt to install KB4074594 just like you have in the past. Let the machine reboot and revert just like it has in the past.
5. After the machine has rebooted and come back up to the desktop, open Process Monitor again. A message box will come up telling you that a log of boot-time activity was created and ask if you wish to save it. Click Yes and save to the BootLog folder on your desktop.
6. This may take some time as it converts the boot-time data. Allow it to finish.
7. Zip up the entire BootLog folder on your desktop and upload to SendSpace and provide a link for me to download.
8. Also zip and upload your entire CBS folder.

Thank you.

 

[scs1]

Hi,

Just to check we're on the same page...

KB4074594 fails before asking for a reboot - it doesn't reboot and revert.

Simon

 

[BrianDrab]

Ahhh, thank you. Please adjust the instructions as follows.

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Open an elevated Command Prompt and attempt to install KB4074594 just like you have in the past.
3. Stop Process Monitor as soon as KB4074594 fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.

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.