Hello, and welcome to Sysnative!
Ended up reading more related issues on this site and found one very quickly that enabled me to run Windows Update again...
Fingers crossed that everything is ok after it finishes installing the 60 updates it found...
What I actually did:
- Opened Registry, clicked HKLM and went to File > Load Hive the loaded c:\windows\system32\config\components with the Key name Components and noticed it was empty
- Did the same on another computer with the same OS and exported the Components folder...
- Merged that export to my PC then selected Components and went to File > Unload Hive
Now up to update 58 of 60... I'll let you know how it goes...
Unfortunately, that user posted terrible advice. I will endeavour to get it removed as soon as possible. Every single system has a completely different state of Windows Update. No matter how similar the PCs appear, even different install orders, and different installed programs (each of which require different internal Windows components enabled or disabled), varies the state of Windows Update. All of this state information is held in the COMPONENTS hive, and merging the two machine's components hives together completely trashes the state information on this machine to an unfixable level. I hate to break this to you, but this machine is no longer fixable by myself or anyone I know
(you've probably seen all the errors in your CheckSUR.log, you initially only had one, the first run after COMPONENTS import had thousands, and then there are hundreds. This is simply SURT seeing mismatches between the COMPONENTS hive from the other machine and other errors or the registry. It tried to fix them, but that has, in all honesty, only made the problem worse as now the differences exist throughout the registry and file system, not just in the COMPONENTS hive).
I think you can see where this is going, I'm afraid there is absolutely nothing I can do
However, it's not all bad news. You might be able to perform an In-Place upgrade now: https://www.sysnative.com/forums/wi...-install-windows-windows-7-windows-vista.html
Try that, it's your last resort, and the absolute best of luck to you.
P.S. The BSOD may be caused by bad RAM, and I guess there's no harm in checking, but there are also a whole load of other causes for that particular BSOD. Do not think that it *has* to be RAM. Please see here and made a separate thread in BSOD section to find out: https://www.sysnative.com/forums/bs...ctions-windows-8-1-8-7-and-windows-vista.html
Tell them you might soon be reinstalling due to WU, and you just want to know whether it looks hardware related first.
And please, not more following instructions on the internet just yet!