SFCFix version 3.0.2.1 by niemiro.
Start time: 2024-04-18 21:22:22.158
Microsoft Windows 10 Build 22631 - amd64
Using .txt script file at C:\Users\thana\Desktop\SFCFixScript.txt [0]
RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{0823B6F8-F499-4d5e-B885-EA9CB4F43B24}\LocalServer32.
Successfully took ownership and permissions for registry key HKEY_CLASSES_ROOT\CLSID\{0823B6F8-F499-4d5e-B885-EA9CB4F43B24}\LocalServer32.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{0823B6F8-F499-4d5e-B885-EA9CB4F43B24}\LocalServer32.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{0823B6F8-F499-4d5e-B885-EA9CB4F43B24}\LocalServer32.
Successfully imported registry key HKEY_CLASSES_ROOT\CLSID\{0823B6F8-F499-4d5e-B885-EA9CB4F43B24}\LocalServer32.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{0823B6F8-F499-4d5e-B885-EA9CB4F43B24}\LocalServer32.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{0823B6F8-F499-4d5e-B885-EA9CB4F43B24}\LocalServer32.
Successfully restored ownership and permissions for registry key HKEY_CLASSES_ROOT\CLSID\{0823B6F8-F499-4d5e-B885-EA9CB4F43B24}\LocalServer32.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Classes\WOW6432Node\CLSID\{0823B6F8-F499-4d5e-B885-EA9CB4F43B24}\LocalServer32.
RegistryScript:: directive completed successfully.
Successfully processed all directives.
Failed to generate a complete zip file. Upload aborted.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 3 datablocks.
Finish time: 2024-04-18 21:23:50.414
Script hash: 6Y/I0XvZbie9UnZFIkH0voUaRAQe0OdX9DpERfIt14o=
----------------------EOF-----------------------
support.microsoft.com
It was the SFCFix version which worked, both fixes were the exact same but SFCFix handles the permissions differently to FRST as shown in the SFCFix completion log. I'm glad I managed to save you from doing a complete clean install.
The permissions were fine, they were set to their default, FRST just couldn't update them because it wasn't running with the right access token so I used SFCFix instead to overcome that issue.
That's pretty much it really - a version mismatch in some registry values which was likely caused by something interrupting a servicing stack update at some point. If you ever have an issue with running DISM, SFC or installing an update, then consult the CBS logs because they will usually immediately tell you what the problem is and most of the issues are very simple to fix once you know how.
And the registry key which we were fixing was related to a CBS worker:
Yeah I remember him, he used to fix lots of activation issues as well from what I remember?
Well, those 3 registry subkeys which I fixed. Honestly, I've done fixes which just involved deleting one registry value.
It could be anything, programs which do registry / file system monitoring e.g. antivirus programs or anything which attempts to block certain updates. I've seen a couple of Windows Update blocker tools achieve their "blocks" by deliberately breaking parts of the component store or turning off certain services without actually informing the user of what changes they're making in the background.
