Server 2016 updates failing, DISM /restorehealth gives error 1734

[mpupdates]

I've been fighting with a Server 2016 system that refuses to install the latest (Jan 2025) cumulative update. I've tried the usual sfc/dism to check things out. DISM "restorehealth" gives me an error 1734 "The array bounds are invalid". The Windows update troubleshooter says the database is bad but was unable to fix it. I tried the manual steps of removing the SoftwareDistribution and Catroot2 folders, etc but these issues are persisting.

The CBS.LOG file indicates a series of errors, all involving KB5044293 which I think was from Oct 2024, and they all look similar to this (different package #'s for each of the 30-40 entries):
Mark store corruption flag because of package: Package_3077_for_KB5044293~31bf3856ad364e35~amd64~~10.0.1.7. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]

At this point I'm stuck because I don't know how to resolve that. I see the registry is littered with references to these things, especially ones in areas like:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\

But those are set with permissions that only TrustedInstaller can modify and I wouldn't be comfortable trying to take ownership of those and removing them anyway for fear of making things worse.

I'm unfamiliar with how these Sysnative tools work exactly that I've seen so much of when other people have random issues, but I figured it's worth a shot.

The ComponentScanner didn't find any errors / corruption, but I did run a fresh DISM /restorehealth and am including that CBS.zip file plus the component scanner log just to confirm it didn't find anything.

 

[Windows Update Bot]

Hi @mpupdates,

Welcome to Sysnative Forums!

If you haven't already, please review the posting instructions here, and attach the requested log files. Without log files, our helpers will not be able to assist, and this will slow down fixing your machine.

If logs have been already been provided, our team of volunteers will analyse the provided log files to build a fix for your system. Please be aware that this may take several days from your initial post, due to the high volume of threads that we receive.


- Sysnative Windows Update Team

 

[PeterJ]

Hello and welcome,

Follow the instructions below please.

Step 1:
WARNING! The following fix is specific to the user's system in this thread only. No one else should follow these instructions, as it could damage your system.

• Download
  
  SFCFix and move the executable to your desktop.
• Download the attachment SFCFix.zip and save it on your desktop.
• Save any work you have open, and close all programs.
• Drag the SFCFix.zip file over the SFCFix.exe executable and release it.
  
  
• SFCFix will launch, let it complete.
• Once done, a file will appear on your desktop, called SFCFix.txt.
• Attach that file to your next reply.

Step 2:
Restart the machine.
Run the command sfc /scannow in an elevated commandprompt and report the result.
If it fails, copy the file C:\Windows\Logs\CBS\cbs.log to your desktop.
Zip the copied file and attach the zipped cbs.log to your next reply.

 

[mpupdates]

I don't know how these things happen, but to get around this DISM restorehealth error, I ended up copying over the missing cat/mum files in the %systemroot%\Servicing\Packages directory. Why they disappeared from this particular server, no clue. Probably some failure doing a "StartComponentCleanup" at some point?

I'm still getting errors trying to install the latest 2025-01 server 2016 cumulative update (the latest servicing stack is already installed, of course). KB5049993 ... takes a good long time and then gives me an error (I used the wusa.exe /log option) "The referenced assembly could not be found". I wish it told me which referenced assembly that was... that would be helpful, Microsoft. I don't know why all of this has to be so cryptic on their part. Why can't they give us errors that contain enough info to figure out what the heck happened? :)

Anyway, using the Windows Update troubleshooting tool, it "helpfully" tells me about "potential Windows Update Database error detected" and then is unable to fix it. But as usual it doesn't tell you any info about why it came to that conclusion.

I guess maybe now that I've got past the issue with the component store and the DISM /restorehealth, maybe I can try clearing the update DB again (the SoftwareDistribution and catroot2 folders). I've done that already (several times now, with no change in being able to install that update), but not since restoring those missing cat/mum files.