So I have been stuck on the current windows version for over 2 years. Just haven't got around to trying to really fix it. When I started I had a bunch of corrupted CBS and CSI manifests and 14 CSI Payload corruptions. I was able to download the individual msu updates and clear all the corrupted manifests. Now however I have listed 105 corrupted payloads.
Windows update - fails.
DISM /restorehealth - fails.
SFC /scannow won't run at all - Windows Resource Protection could not start the repair service.
In place Windows 10 upgrade - fails.
Through specifying source directories of downloaded MSU files and running DISM /restorehealth commands I finally got the computer to recognize the SSU.
I have attached a CBS log with having only run DISM /online /cleanup-image /checkhealth followed by /ScanHealth as well as a separate CBS log for /RepairHealth
If you haven't already, please review the posting instructions here, and attach the requested log files. Without log files, our helpers will not be able to assist, and this will slow down fixing your machine.
If logs have been already been provided, our team of volunteers will analyse the provided log files to build a fix for your system. Please be aware that this may take several days from your initial post, due to the high volume of threads that we receive.
You sir truly are a Jedi Master. Ran the SFCfix, completed successfully all commands. Ran the DISM showed no corruption. Rebooted just to make sure and reran dism /scanhealth, still all good.
Windows update shows pending install now on a few patches, first time in 3 years. Still downloading 22H2.
Tentatively I would say you have fixed it. I'll repost to confirm once the updates go through.
May I ask, do you just have some extremely large archive of dll files with checksums saved for your quick reference? Or is there an easy way if something similar happened that I would be able to find the correct versions of the dlls that were corrupted? I tried checking prior to your reply for the correct hashed versions of the files after downloading all 93 listed windows updates for Windows 10 21H1 and extracting the cabs then ran a simple export to a csv through powershell and didn't have a single match on the one I had checked (had just grabbed the hash on the smiengine.dll form the CBS log).
And one more quick question - do you have any suspicions as to what causes these corruptions that seem to be far too common for a lot of users? Wondering if there is any way to avoid similar situations.
Thank you! To find all those correct versions of the corrupted dll files would have taken me.... well, maybe forever.
The service you and the rest of the team on these forums provide is beyond measure. I've learned more in the last few days about windows update then I think I would ever want to know. How you keep track of and do it all is truly amazing.
You're welcome. Glad to hear this system is up-to-date now...
Yes, I have a large repository of files as well as dozens of VM's (with snapshots of specific build) which I can use as source.
Such corruptions may occur, for example, after a power outage, system crash etc. So it's always recommended to make regular backups (images) of the system drive.
