[SOLVED] Windows 7 PRO SP1 64-Bit Multiple Windows Update Failures from Dec 2018 On

malletKATman

malletKATman

Contributor
Joined
Feb 19, 2019
Posts
134
My Windows 7 PRO SP-1 64-Bit system has been running for nine years on my custom-built PC. My system now has a 1TB System C: SSD with only the system and application installations and one minor user whose User Profile (the base of all user libraries and other files) is entirely on the C: drive, and two “regular users” whose User Profiles are defined on a 1TB Winchester E: drive. This configuration was chosen in part because nine years ago SSD drives were small and very expensive. I had only an 80GB Windows partition on my original system which could not accommodate regular users’ storage requirements. (On Jan 10 2019 I replaced it with a new 1TB SSD, which necessitated running as the one “C: Only” user to perform the Windows Partition copy.)

On or about December 2018 Windows Update, which had been functioning essentially perfectly up to that point, began to fail on almost every update with various reported hexadecimal codes including: 8050800C, 80073701, 80070002, 80246007, 80600C00, 800F0902 and finally 64C. Usually these would fail in the initial update staging process, but one, the 2019-02 Windows 64-Bit Quality Rollup, failed later after the reboot when attempting to “Configure the Update” during startup.

I have a thread on the SevenForums.com “Windows Updates & Activation” forum detailing the entire history of this problem at the following URL: Report On Multiple Windows Update Failures from Dec 2018 On - Windows 7 Help Forums , so I will not repeat that information here. A senior member of that forum, Nickname “Snick”, has investigated my problem and recommended I present this problem to this forum and post the logs for my last System Update Readiness Tool (SURT) run (shows 55362 errors) and a failed Windows Update run.

Note I cannot upgrade to a newer Windows release because I run a vital database application on the Windows XP Mode hardware-assisted virtual machine, which does not run on Windows 8 or 10, and is no longer supported by Microsoft.

SFC /SCANNOW or SFC /VERIFYONLY report no errors; CHDSK /F of my Windows partition shows no errors. I have posted the results of my last SURT run, and the CBS.log and WindowsUpdate.log for one manually selected (from Microsoft Update Catalog) failed update run, in separate attached ZIP files.

I will appreciate any help I can get.
 

Attachments

Last edited:
I ran niemiro's SFCFix last night after rerunning the SURT "install" tool again for fresh data. It's interesting that the SFCFix description in the pre-posting instructions for this forum states that SFCFix running time "can be upwards of 15 minutes depending....". The run was almost 4.5 hours. The attachment is the ZIP file of CBS.log (probably reset by this morning's startup), the CheckSUR.log from the immediately preceding SURT run, the latest WindowsUpdate.log, and the SFCFix.txt file that logged SFCFix's actions.

Here is the action summary from the end of SFCFix.txt

====================================
SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 0
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 54976
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 55072
AutoAnalysis:: directive completed successfully.

Successfully processed all directives.
SFCFix version 3.0.1.0 by niemiro has completed.
Currently storing 2662 datablocks.
================================

Important question: are these fixes sufficient that I should try to install one of the failing updates again?
 

Attachments

I reran the combined SURT & SFCFix mashup to see if cascading such runs would fix more problems. It's unlikely that is the case as you can see from the CheckSUR.log and the SFCFix.txt files in the ZIP file. This time SFCFix ran in only 8 minutes; it clearly found a lot fewer things to work on.

=============================
SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 0
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 17617
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 16321
AutoAnalysis:: directive completed successfully.

Successfully processed all directives.
SFCFix version 42.32768.0.0 by niemiro has completed.
Currently storing 2662 datablocks.
=============================
 

Attachments

"Hello and welcome to Sysnative! (from softwaremaniac)

As this is an extreme number of corruptions, I would ask you that you first download a utility like CrystalDiskInfo, so I could verify there are no issues with the drive.

Thank you."

I installed CrystalDiskMark 6.0.2 x64 and ran the entire benchmark with 3 test runs. Here are the benchmark results.
========================================
  • MB/s = 1,000,000 bytes/s [SATA/600 = 600,000,000 bytes/s]
  • KB = 1000 bytes, KiB = 1024 bytes

Sequential Read (Q= 32,T= 1) : 389.823 MB/s
Sequential Write (Q= 32,T= 1) : 388.169 MB/s
Random Read 4KiB (Q= 8,T= 8) : 32.377 MB/s [ 7904.5 IOPS]
Random Write 4KiB (Q= 8,T= 8) : 101.528 MB/s [ 24787.1 IOPS]
Random Read 4KiB (Q= 32,T= 1) : 32.768 MB/s [ 8000.0 IOPS]
Random Write 4KiB (Q= 32,T= 1) : 98.058 MB/s [ 23939.9 IOPS]
Random Read 4KiB (Q= 1,T= 1) : 26.898 MB/s [ 6566.9 IOPS]
Random Write 4KiB (Q= 1,T= 1) : 66.357 MB/s [ 16200.4 IOPS]

Test : 1024 MiB [C: 9.5% (79.3/838.3 GiB)] (x3) [Interval=5 sec]
Date : 2019/02/20 23:32:20
OS : Windows 7 Professional SP1 [6.1 Build 7601] (x64)
======================================

I hope this is satisfactory. I regularly use Samsung's Magician tool to measure the health of my C: SSD drive. This is what it says about my drive status as of this moment.

44017
 
This C: SSD was installed about 6 weeks ago; it's highly unlikely it's causing any file corruption. Prior to this I had a 180GB SSD that ran for 9+ years with only an 80GB Windows partition. If there was any file corruption due to C: disk I/O, it almost certainly happened years ago with the original SSD, not this drive.
 
Step#1 - Export registry as hive


  • Click on the Start button and in the search box, type regedit
  • When you see regedit on the list, right-click on it and select Run as administrator.
  • When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
  • Once selected, click File > Export....
  • Change the Save as type: to Registry Hive Files (.).
  • Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
  • Right-click on the saved file and choose Send To -> Compressed (zipped) Folder.
  • Attach the .ZIP file to your next post.
  • If the file is too large to upload here, upload to SendSpace and just provide the link here.
 
Right-clicking on the ComponentBasedServicing output file does not offer a Send To -> Compressed (zipped) Folder option on my system. (Sorry, I can't capture a screen image to prove it.) I use Bitzipper to process ZIP (as well as tar and zipx files), which provides extremely strong compression into standard ZIP archives. It won't allow an insert of an extensionless file name into a ZIP file, so I renamed the file ComponentBasedServicing.xxx and inserted it into the ZIP file. You can restore the extensionless file name when you extract it if you wish. It was exported as a "Registry Hive Files" type as you requested. (BTW: regedit refused to export the file to my Desktop, so I exported it into a folder instead: a trivial deviation from your instructions.)

Do you recommend any Registry cleaning products or consider them too dangerous?

Thank you for your support.
 

Attachments

Hi! Thank you for your patience.

Please do the following:

FRST Registry Search
1. Click your Start button and choose Control Panel.
2. In the upper right corner ensure the View by: is set to Category.
3. Select the Programs group.
4. Click the Turn Windows features on or off link. This will bring up the Windows Features dialog. Wait until this dialog populates with information. If this does not happen for some reason, please continue with the steps anyway.
Note: This loads your components hive which is what we want. Please keep this dialog open while you perform the remaining steps.
5. 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.
6. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
7. Copy and paste KB4284826;KB4338818;KB4343900 into the Search box and click the Search Registry button.
8. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt.
9. You may close any remaining open windows now.
 
Thank you.

Step#1 - 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.
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.

Afterwards, please run SURT again and attach CheckSUR.log.
 

Attachments

Both tasks were done in sequence. The FRST64 fix run completed successfully. The SURT run still found errors, to wit:
===============================
Summary:
Seconds executed: 306
Found 14206 errors
CSI Missing Deployment Key Total count: 2053
CBS Watchlist Component Missing Total count: 12153
===============================

Both the Fixlog.txt and CheckSUR.log are in the attached 02-23 FRST64 Fixlog.txt and SURT CheckSur.log.ZIP file.
 

Attachments

Thank you. This will take multiple rounds of fixes. I am going to sleep now, so good night.

FRST Registry Search
1. Click your Start button and choose Control Panel.
2. In the upper right corner ensure the View by: is set to Category.
3. Select the Programs group.
4. Click the Turn Windows features on or off link. This will bring up the Windows Features dialog. Wait until this dialog populates with information. If this does not happen for some reason, please continue with the steps anyway.
Note: This loads your components hive which is what we want. Please keep this dialog open while you perform the remaining steps.
5. 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.
6. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
7. Copy and paste KB3022345;KB4457144;KB4462923;KB3146706;KB3161608 into the Search box and click the Search Registry button.
8. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt.
9. You may close any remaining open windows now.
 
Thank you. Now do the following:

Step#1 - 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.
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. Run SURT again and attach CheckSUR.log.
 

Attachments

Both tasks were done in sequence. The SURT run still found errors, to wit:
===============================
Summary:
Seconds executed: 309
Found 7948 errors
CSI Missing Deployment Key Total count: 2053
CBS Watchlist Component Missing Total count: 5895
===============================

Both the Fixlog.txt and CheckSUR.log are in the attached 02-23 No. 2 FRST Run Fixlog.txt and SURT CheckSur.log.ZIP file. It looks like this iterative process is converging.
 

Attachments

Thank you. Yes. We still have many more iterations to go, but we'll get there:

FRST Registry Search
1. Click your Start button and choose Control Panel.
2. In the upper right corner ensure the View by: is set to Category.
3. Select the Programs group.
4. Click the Turn Windows features on or off link. This will bring up the Windows Features dialog. Wait until this dialog populates with information. If this does not happen for some reason, please continue with the steps anyway.
Note: This loads your components hive which is what we want. Please keep this dialog open while you perform the remaining steps.
5. 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.
6. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
7. Copy and paste KB4459934;KB4344152;KB4338423;KB4095874;KB4054998;KB4033996;KB4014596 into the Search box and click the Search Registry button.
8. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt.
9. You may close any remaining open windows now.
 
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