[SOLVED] Windows Server 2016 - Windows Update broken for years on domain controller

[Durando]

Farbar Recovery Scan Tool appeared to finish successfully. See attachment "Fixlog.txt".

ComponentsScanner run found a sequence mismatch, 1 corrupted key, and 48 inconsistencies/warnings. See attachment "ComponentsScanner-2023-08-27.txt".

 

[Maxstar]

Hmm still the same error about the corrupt value, please provide a new copy of the COMPONENTS hive.

 

[Durando]

As of right now the Components hive is in use and I will need to restart the server to free it, which can't be done until after close of business.

 

[Maxstar]

Okay, since the COMPONENTS hive is still loaded please check the following.

Open an elevated command prompt and run the following command and copy and paste the result in your next post.

reg query HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-s..settingshandlers-nt_31bf3856ad364e35_10.0.14393.0_none_ab5af94c69ca09f3

I expect the (default) value is still present as an REG_DWORD type instead of REG_SZ with the value not set.

    (Default)    REG_DWORD    0x46

 

[Durando]

Here is the output:

Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\Users\Administrator.SAWING_SHEARING>reg query HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-s..settingshandlers-nt_31bf3856ad364e35_10.0.14393.0_none_ab5af94c69ca09f3

HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-s..settingshandlers-nt_31bf3856ad364e35_10.0.14393.0_none_ab5af94c69ca09f3
    S256H    REG_BINARY    0E588F59C16B8303D5BFE3032CB948606E0CC49D59B3E1AEF0A39E21D8494CCD
    identity    REG_BINARY    4D6963726F736F66742D57696E646F77732D53797374656D53657474696E67732D53657474696E677348616E646C6572732D6E742C2043756C747572653D6E65757472616C2C2056657273696F6E3D31302E302E31343339332E302C205075626C69634B6579546F6B656E3D333162663338353661643336346533352C2050726F636573736F724172636869746563747572653D616D6436342C2076657273696F6E53636F70653D4E6F6E537853
    c!microsoft-w..-deployment_31bf3856ad364e35_10.0.14393.0_2b4dbbb4ebd28514    REG_BINARY
    f!settingshandlers_nt.dll_12a469feb9b70f0d    REG_DWORD    0x3
    f!windows.ui.settingshandle_acb75aecda89b471    REG_DWORD    0x3
    CF    REG_DWORD    0x0
    CTS    REG_DWORD    0x48bf0912

 

[Maxstar]

Thanks, please open regedit and navigate to the same key and take a screenshot of this screen and post it here.

HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-s..settingshandlers-nt_31bf3856ad364e35_10.0.14393.0_none_ab5af94c69ca09f3

 

[Durando]

EDIT: Never Mind - New Post Coming Later

 

[Durando]

Screenshot:

 

[Maxstar]

This looks good, please run ComponentsScanner again it should no longer report the corrupted value!

Run

ComponentsScanner again.

• Right-click ComponentsScanner.exe and select "Run as administrator", click Yes on the UAC (User Account Control) prompt which appears.
• Follow the on-screen instructions.
• Once complete, a report will be saved to your desktop called ComponentsScanner.txt.
• Post the logfile ComponentsScanner.txt as attachment into your next reply.

 

[Durando]

As predicted, no corrupted keys were found. See attachment.

 

[Maxstar]

This looks good to me! We can ignore the warnings since you were able to install the latest LCU. Are there any remaining issues or is everything up and running again?

 

[Durando]

Everything's fine on this domain controller, but I'll likely be posting another thread for another server in the same organization.

 

[Durando]

And thank you very much for your help, too, Maxstar.

 

[Maxstar]

You're welcome. Please start a new thread for the other server, then I will mark this thread as solved.