Solved Report On Multiple Windows Update Failures from Dec 2018 On

[malletKATman]

Did you change the Windows Update from "Never.." back to the normal setting.

No, I have always configured Windows Update as "Check for updates but let me choose whether to download and install them", for the 9+ years I have used this box. Now I have the process set to "Never..." because to do otherwise interferes with the Shutdown process.

When I want to test an candidate install I go to the Microsoft Update Catalog, search for the update, and manually download the MSU file for it. Then I shutdown the Windows Update service with "services.msc", end the TrustedUpdater.exe process with the Task Manager (required to break locks on the Update log files), delete the Install logs (%WinDir%\WindowsUpdate.log and %WinDir%\Logs\CBS\CBS.log, restart the Windows Update service, and click on the downloaded MSU to run the install. (I was advised in this thread that I could operate that way.) Proceeding thusly creates as lean, isolated and small a set of log files as is possible which is desirable because all these forums have a strict size limit on uploadable ZIP files, and I don't want to clutter my dropbox if I don't have to (the alternate way to "upload" a big file: place it in my dropbox, request a URL for the file from Dropbox, and post that URL in my forum thread.)

 

[malletKATman]

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.
=============================
View attachment 02-20 2nd SURT & SFCFix Run Logs.zip

 

[Snick]

SFCFix.exe fixed 16321 orphaned components. With SFCFix.exe, you have to have a script written to specifically address some of your other issues. There are specific directives/commands you use to tell the program what to do and what to repair or replace something with. Quite often base16/hexidecimal notation is used in the scripts. SFCFix.exe run by itself is slightly better than sfc /scannow, but the real power is using it to repair or replace using SFCScript.txt.

Another program, FRST has similar features, you prepare a script from the results of a scan or scans, prepare the fix or fixes, then run it through the run fix button on the GUI.


I have a program I wrote that automates some of the search, copy, paste function, and I have a library of 400K+ cat/mum, primary, and manifest files which makes it easier for me to locate and provide those replacements then most people. Original Poster is (OP). I'll leave speculation to your helper(s) at Sysnative. They are prompt in responding to your request, surgical in their repair process and the most knowledgeable with Windows Update. That's why I am training there.


From your CBS.log it appears you have a problem with first update that won't install, it looks like it is corrupt, then systemic failure of the others as a result. Yep, they'll help with that too.

 

[wither 2]

No, I have always configured Windows Update as "Check for updates but let me choose whether to download and install them", for the 9+ years I have used this box. Now I have the process set to "Never..." because to do otherwise interferes with the Shutdown process.

When I want to test an candidate install I go to the Microsoft Update Catalog, search for the update, and manually download the MSU file for it. Then I shutdown the Windows Update service with "services.msc", end the TrustedUpdater.exe process with the Task Manager (required to break locks on the Update log files), delete the Install logs (%WinDir%\WindowsUpdate.log and %WinDir%\Logs\CBS\CBS.log, restart the Windows Update service, and click on the downloaded MSU to run the install. (I was advised in this thread that I could operate that way.) Proceeding thusly creates as lean, isolated and small a set of log files as is possible which is desirable because all these forums have a strict size limit on uploadable ZIP files, and I don't want to clutter my dropbox if I don't have to (the alternate way to "upload" a big file: place it in my dropbox, request a URL for the file from Dropbox, and post that URL in my forum thread.)

I just thought I'd mention that I asked you to set it to "Never" and reboot before trying to install the download from Microsoft Update Catalog to prevent Windows Update from searching for updates during the install. Some of the downloaded updates won't install with it running because there would be more than one Windows Installer running and that's not allowed.

 

[malletKATman]

I just thought I'd mention that I asked you to set it to "Never" and reboot before trying to install the download from Microsoft Update Catalog to prevent Windows Update from searching for updates during the install. Some of the downloaded updates won't install with it running because there would be more than one Windows Installer running and that's not allowed.

I always have "Never" set when I make those Microsoft Update Catalog downloads. The only difference is that I haven't rebooted before manually installing. But I have stopped the Windows Update Service and killed the TrustedUpdater.exe process before starting each run. Once the service is restarted with the "Never.." option, Windows Update never shows any updates ready for installing for the life of the session. That's necessary now to allow a regular shutdown from the "Start" icon (prevents Windows Update from attempting to install all the available Important updates before really shutting down). Otherwise I would have to Run a "shutdown /s /t 00" command.

 

[malletKATman]

SFCFix.exe fixed 16321 orphaned components. With SFCFix.exe, you have to have a script written to specifically address some of your other issues. There are specific directives/commands you use to tell the program what to do and what to repair or replace something with. Quite often base16/hexidecimal notation is used in the scripts. SFCFix.exe run by itself is slightly better than sfc /scannow, but the real power is using it to repair or replace using SFCScript.txt.

Another program, FRST has similar features, you prepare a script from the results of a scan or scans, prepare the fix or fixes, then run it through the run fix button on the GUI.

I have a program I wrote that automates some of the search, copy, paste function, and I have a library of 400K+ cat/mum, primary, and manifest files which makes it easier for me to locate and provide those replacements then most people. Original Poster is (OP). I'll leave speculation to your helper(s) at Sysnative. They are prompt in responding to your request, surgical in their repair process and the most knowledgeable with Windows Update. That's why I am training there.

From your CBS.log it appears you have a problem with first update that won't install, it looks like it is corrupt, then systemic failure of the others as a result. Yep, they'll help with that too.

In the description of SFCFix as part of the posting requirements for the Sysnative Windows Update forum they make no mention of how to run SFCFix with a script. If that is necessary, I hope they include instructions.

I just got my first response from my posting on that forum: to wit.

"Hello and welcome to Sysnative!

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."
​

This from "softwaremaniac", a moderator of another forum and a Windows Update instructor. I guess he doesn't think SFC, CHKDSK and SFCFix are adequate to prove that there is nothing wrong with the [FONT=&quot]architectural [/FONT]structure of my Windows partition. Oh well, I guess I'll try to humor him.

 

[Snick]

Softwaremaniac is excellent at fixing your Windows Update issues. May be something in the log you provided that info is needed from crystaldisk. Everyone that responds at Sysnative is trained or in training, the latter with direct supervision of an instruction with expert knowledge of the subject-matter. If you have a question or concern, address it to them in your posts.

 

[malletKATman]

Softwaremaniac is excellent at fixing your Windows Update issues. May be something in the log you provided that info is needed from crystaldisk. Everyone that responds at Sysnative is trained or in training, the latter with direct supervision of an instruction with expert knowledge of the subject-matter. If you have a question or concern, address it to them in your posts.

I appreciate the recommendation for softwaremaniac. He wanted the CrystalDiskInfo report on the health of my new C: SSD. That report is similar to that from Samsung Magician provided with the new disk that I use regularly. I provided softwaremaniac with both reports, in which it is quite clear that my disk is healthy. I also pointed out that the disk was installed just 6 weeks ago, and that any file corruption from faulty disk I/O is likely old and caused by the previous C: 80BG SSD that ran for 9 years before being replaced by, and the entire Windows partition copied to, the new drive with the Samsung Data Migration tool.

Now softwaremaniac wants to look at my Registry exported as a hive file, starting at the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing node. I'm glad he's digging into this problem and I thank you for steering me to Sysnative.

 

[Snick]

Was checking the SSD for bad sectors. Yes new SSDs do fail. Component hive corruption as I thought!

 

[malletKATman]

Was checking the SSD for bad sectors. Yes new SSDs do fail. Component hive corruption as I thought!

However, this problem started before I installed the new SSD so it was not the cause of any hive corruption.

Meanwhile, softwaremaniac had me install the Farber Recovery Scan Tool (FRST64.exe), load the Components registry hive (with the "Turn Windows features on and off" option in Control Panel->Programs and Features and leaving the dialog open on the screen, and make a Search Registry run in FRST64.exe searching for KB4284826;KB4338818;KB4343900. I posted the resulting SearchReg.txt run log file. He responded with a fixlist.txt file to repair the Components registry hive with a FRST64.exe Fix option run. This ran successfully. I followed with another SURT run which came up with a new set of errors, to wit:
===============================
Summary:
Seconds executed: 306
Found 14206 errors
CSI Missing Deployment Key Total count: 2053
CBS Watchlist Component Missing Total count: 12153
===============================
I posted the Fix run Fixlog.txt and the new SURT CheckSUR.log for softwaremaniac to examine.

I can upload a ZIP file to this thread with SearchReg.txt, fixlist.txt, Fixlog.txt and the new CheckSUR.log if you would like to examine the evidence all this produced.

 

[Snick]

Not needed, I'm following your thread on Sysnative as it progresses, via the link you provided in my PM. Thank you for that! Here, just let us know the outcome. Play by play is unnecessary but thank you for your diligence.

 

[Snick]

However, this problem started before I installed the new SSD so it was not the cause of any hive corruption.

Yes, as CrystalDiskInfo also indicates not the cause. All this was transferred from your other drive obviously.

When dealing with computer issues, everyone has a different level of tech savviness. Quite often the Original Poster (OP) doesn't understand why a helper determines a particular test, scan, or log is necessary in the troubleshooting process.

If an OP has numerous errors, especially all zero errors, (the file is empty) check for a failing HDD or SSD is high on the troubleshooting agenda. (usually first). If the drive is failing, repair/replacement of files/folders will not correct the underlying issue, the drive is bad.

FRST is being used for a registry search to find registry (hive) corruptions. Softwaremaniac (SM) is searching for specific KB registry entries, i.e. your failed updates. When FRST creates the log, then a fix script will be created to address (remove) those entries from the registry. At the beginning of the script is an entry to create a restore point (very, very important) followed by a DeleteValue: entry for the appropriate registry entries. If you peruse the log FRST created when you run the FIX, you will see that most, if not all, say "successful". You can peruse a tutorial on FRST if you wish here:
FRST Tutorial - How to use Farbar Recovery Scan Tool - Malware

 

[malletKATman]

Not needed, I'm following your thread on Sysnative as it progresses, via the link you provided in my PM. Thank you for that! Here, just let us know the outcome. Play by play is unnecessary but thank you for your diligence.

Roger, Wilco. Thank's for the tutorial on Windows Update problem analysis and FRST in particular.

 

[malletKATman]

FRST is being used for a registry search to find registry (hive) corruptions. Softwaremaniac (SM) is searching for specific KB registry entries, i.e. your failed updates. When FRST creates the log, then a fix script will be created to address (remove) those entries from the registry. At the beginning of the script is an entry to create a restore point (very, very important) followed by a DeleteValue: entry for the appropriate registry entries. If you peruse the log FRST created when you run the FIX, you will see that most, if not all, say "successful". You can peruse a tutorial on FRST if you wish here:
FRST Tutorial - How to use Farbar Recovery Scan Tool - Malware

A first read of the tutorial indicates that FRST should be approached with great caution, else the "Sorcerer's Apprentice" scene from Walt Disney's famous Fantasia movie would be reproduced live on your monitor.

 

[Snick]

No problem, always glad to help or attempt to explain something. Backups are always appropriate when attempting to correct computer issues, as well as regular scheduled backups. (my footer says it all)

When/if I get my nervous system/sleep problem under control, I'll be back in Sysnative Windows Update Academy.

If you have any more questions, please feel free to present them. If I don't know the answer, I'll attempt to locate an acceptable response.

 

[malletKATman]

I promised long ago that I would report progress and the ultimate solution to this thread that I conducted on the Systnative.com website’s Windows Update forum, as recommended by Snick. That problem was “solved” in a long and laborious thread on that forum (there are still 719 missing “dead Key” nodes (without values) in my Components registry hive) which appear not to cause any problem. My Windows 7 system is now up to date with MS W.U. releases. You can view this SOLVED thread at Windows 7 PRO SP1 64-Bit Multiple Windows Update Failures from Dec 2018 On at that website.

 

[Snick]

My professors!

 

[malletKATman]

My thanks to Snick and others to contributing to the process by which my problems were solved elsewhere.