CBS registry key missing after failed update - Windows 2016 Server

SeekingTruth 191 Reputation points
2021-07-08T09:12:43.213+00:00

I had a failed Windows update on a Windows 2016 Server. Now every time I run the Windows update it say there are no update.

After doing some research I found that a number of registry keys are missing from "Component Based Servicing". These are the keys available on the server at the moment.

112973-image.png

Comparing this to another server which is working I can see the the keys ComponentDetect, Notifications, PackageDetect, UpdateDetect and Version are missing.

112962-image.png

This explains why the server can not display and Roles or Features as well as not finding any updates.

I would like to add these reg keys by importing from a operational server which is at the same patch level and install software as this faulty one. Unfortunately it doesn't let me as I don't have the correct permissions. It will not even allow me to change the permission for the administrator.

Can anyone assist? I really don't want to rebuild the server which is a DC.

Thanks

Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,371 questions
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,127 questions
Active Directory
Active Directory
A set of directory-based technologies included in Windows Server.
5,854 questions

6 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Dave Patrick 426.1K Reputation points MVP
    2021-07-08T12:30:32.563+00:00

    The simplest and much safer solution is to stand up a new one for replacement.

    I'd use dcdiag / repadmin tools to verify health correcting all errors found before starting any operations. Then stand up the new one, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health, when all is good you can decommission / demote old one.

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    0 comments
  2. Adam J. Marshall 8,626 Reputation points MVP
    2021-07-08T12:44:30.197+00:00

    First: Try repairing the CBS: 

    DISM /Online /Cleanup-Image /RestoreHealth
SFC /scannow

    Alternatively, (something to try that may or may not work)

    Take a backup of this key first via an export of the registry.

    Take ownership of the key root [Component Based Servicing] and replace ownership to inherited items. Then go back into the permissions and give authenticated users full rights to this key. Then take a backup of this key by exporting it from the registry.

    Then delete the key from the system

    Then run 

    DISM /Online /Cleanup-Image /RestoreHealth
SFC /scannow
    0 comments
  3. SeekingTruth 191 Reputation points
    2021-07-09T01:14:37.57+00:00

    Thanks AJTek-Adam-J-Marshall.

    I have run "DISM /Online /Cleanup-Image /ScanHealth" and it tells me that the component store is repairable.

    The /RestoreHealth failed and suggested that I use the SOURCE option.

    I just need to create a ISO from the provided Microsoft download that contains multiple editions of Windows 2016 server. Managed to extract the one I wanted as a WIM file. Trying to see how to create the ISO from this if possible.

    Any thoughts?

    0 comments
  4. Adam J. Marshall 8,626 Reputation points MVP
    2021-07-09T01:24:27.987+00:00
    0 comments
  5. Dave Patrick 426.1K Reputation points MVP
    2021-07-15T12:31:03.367+00:00

    Just checking if there's any progress or updates?

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    0 comments