Server 2019 (17763.379) - very behind on updates, won't install latest cumulative update - error 0x80070103 - SFCFix finds no corruption

jonwill

jonwill

Member
Joined
Apr 19, 2024
Posts
7
Thank you for volunteering, this site is amazing!

My goal here is to get this system up to date to avoid migrating its roles to a new VM.

Windows update says "A current driver on your PC may be better than the driver we're trying to install. We'll keep trying to install"

Dism restorehealth comes back successful
sfc finds and fixes problems (but says that every time I run it)
SFCFix finds no corruption
Windows update troubleshooter finds nothing.
have run scripts for stopping wuauserv, bits, etc, clearing softwaredistribution and catroot2.
Tried WSUS Offline Update. It mentions "not applicable" several times, and didn't seem to install any updates.

Have tried in-place upgrade installs with
SW_DVD9_Win_Server_STD_CORE_2019_1809.18_64Bit_English_DC_STD_MLF_X22-74330.ISO
SW_DVD9_Win_Server_STD_CORE_2019_1809.19_64Bit_English_DC_STD_MLF_X23-31944.ISO
SW_DVD9_Win_Server_STD_CORE_2019_1809.1_64Bit_English_DC_STD_MLF_X22-02970.ISO
SW_DVD9_Win_Server_STD_CORE_2022_2108.31_64Bit_English_DC_STD_MLF_X23-71666.ISO
Server 2022 doesn't really give me an error message, just that the install failed.
2019 upgrade installs give "Failed in SAFE_OS phase with an error during REPLICATE_OC operation"
with or without network adapter enabled.

I've tried installing standalone updates. Especially recent Service Stack Updates and Cumulative Updates for server 2019 1809, and much older ones, just a bit newer than my current OS build.

These are the all the standalone updates I've tried. All of them report "The update is not applicable to your computer"

windows10.0-kb4598480-x64_0b0c7a9e6fb982e698647a3c06068fc8a69ea8db.msu
windows10.0-kb5037425-x64_41cda5553d76768e7bbf158dcf40690fe25cd870.msu
windows10.0-kb4490481-x64_a07dfdc8de3f0c2f590c950410a8a40522cd07dd.msu
windows10.0-kb4493510-x64_f692d391a4869d910c754895169dbd0d237a86da.msu
windows10.0-kb4499728-x64_36248692f756ec842e644b8b79fb7e1c0d64085d (1).msu
windows10.0-kb4499728-x64_36248692f756ec842e644b8b79fb7e1c0d64085d.msu
windows10.0-kb4523204-x64_57098d9954748b2d7d767f73f60493bc592ff286.msu
windows10.0-kb5003711-x64_577dc9cfe2e84d23b193aae2678b12e777fc7e55.msu
windows10.0-kb5005112-x64_81d09dc6978520e1a6d44b3b15567667f83eba2c (1).msu
windows10.0-kb5005112-x64_81d09dc6978520e1a6d44b3b15567667f83eba2c.msu
windows10.0-kb5034624-x64-ndp48_9aaf1ded061cdc7fd9107501a2a590835f33540d.msu
windows10.0-kb5034768-x64_04b794598371fdc01bb5840c68487388ca029ad5.msu
windows10.0-kb5036896-x64_57eaad3d6f3738831f3f8c6bdf7a77df618429c2.msu

Attaching log files. Thanks again!
 

Attachments

Last edited:
ComponentsScanner.exe found no corruptions.

Noticing you are after the whole CBS folder. Here you are, attached:
 

Attachments

Hi and welcome to Sysnative,

Export CBS (Component Based Servicing) hive
  • Click on the Start button and type regedit
  • When you see regedit on the list, right-click on it and select Run as administrator.
  • When regedit opens, using the left pane, navigate to the following registry key and select it by clicking on it once.
    Code: 
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
  • Once selected, click File > Export....
  • Change the Save as type: to Registry Hive Files (*.*).

    622dbef75cd3a-Export-CBS-hive.png

  • Name this file ComponentBasedServicing (with no file extension) and save it to your Desktop.
  • Right-click on the saved file and choose Send > Compressed (zipped) Folder.
  • Attach the .ZIP file to your next post.
  • If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.
 
Please post the reg export as hive file (as mentioned in the screenshot) not as *.reg file.
 
I have some bad news, this CBS hive is missing multiple keys including all their subkeys. Do you have recent backups before the issue started?
 
I expect this machine may have never updated properly. Installed in 2019. I don't have backups that go back years, no. Not for OS files.
I do have its hyper-v host running more updated 2019. I do have backups of its OS from April 2022. I don't suppose that helps.
 
Then I'm afraid there is nothing else left than rebuilding this VM server from scratch. Sorry!
 
Thinking out loud... I have original install media. Can I get what I need from that? Maybe if I install that on a new VM, export the hive?
Build 379 (what I'm running) is what the original install media is.
 
I am not a fan of such 'MacGyver' fixes because it may cause many other issues, especially since such a hive file from a 'spare' VM' will not match with other essentials registry hives like the COMPONENTS hive. And more importantly there's no guarantee this will result in a stable server.

So personally, I never recommend such solutions. But if you want to try this way of fixing, then I recommend to clone the problematic server and import the CBS hive from a very similar system (patch level) and then perform an in-place upgrade. Note: this is definitely not most recommended way to solve such issues, and rebuilding from scratch is more reliable.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top