[SOLVED] Windows 2022 fails WU -- metadata corruption

Elvenite · Saturday at 4:37 AM

Hi,

Since some time before summer I haven't been able to install any Windows Updates in one of my Windows 2022 Standard servers.
It's a DB server that can only be taken down for short periods during weekends.
sfc doesn't detect any errors, neither does dism but the CBS log claims I have a metadata corruption.
I've downloaded KB5036909, unpacked everything (twice) and tried to run dism using these files as source, didn't help.
I've also tried to install KB5036909 directly, same error as always (file not found).
I've failed to perform an in-place upgrade of Windows as none of the ISO's I've tried (the original evaluation version and the one that can be downloaded from MS) allows me to keep applications and settings.
Any help is greatly appreciated!

Elvenite · Saturday at 4:38 AM

I couldn't find a way to attach the log files to the original message, so there they come instead:

Elvenite · Saturday at 8:09 AM

I'll add yet another csb.log, this one was created when I tried to run Windows Update. It contains more data, maybe even a hint about what to fix.

Maxstar · Saturday at 8:43 AM

Rich (BB code):

2025-01-04 10:06:27, Info                  CBS    (w)	CBS Package Index Package Missing	0x80070490	Package_for_RollupFix~31bf3856ad364e35~amd64~~0.0.0.0	Package_for_RollupFix~31bf3856ad364e35~amd64~~20348.2402.1.11

Hi and welcome to Sysnative,

I only see the above warning in the first log, so please do the following.

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 (*.*).
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.

Elvenite · Saturday at 8:52 AM

Thanks for the quick reply!
Please find the requested file attached to this message.

Maxstar · Saturday at 9:01 AM

Please do the following.

Step 1. Download

SFCFix and save it to your desktop.

Warning: This fix was written specifically for this system. Do not run this fix on another system.

Save any work you have open, and close all programs.
Download the attachment SFCFix.zip and save it to your desktop.
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.
Post the logfile (SFCFix.txt) as attachment in your next reply.

Step 2. Run the following DISM command and post the result. If it fails attach a new copy of the CBS log.

Code:

DISM /online /cleanup-image /RestoreHealth

Elvenite · Saturday at 9:24 AM

Thanks.
I've attached the logs here.
(WU still didn't run through, but I guess you can tell from the logs)

Maxstar · Saturday at 9:30 AM

The CBS shows the same warning, so please do the following.

Follow these instructions to remove an update.

Open the Start menu of Windows and type the command CMD
When you see Command Prompt on the list, right-click on it and select Run as administrator.
When command prompt opens, copy and paste the following command into it, then press enter.

Code:

wusa /uninstall /KB:5036909

Let me know if it says it was successful or you get the message: The update KB5036909 is not installed on this computer.

Elvenite · Saturday at 9:31 AM

It failed. "The update KB5036909 is not installed on this computer".

Maxstar · Saturday at 9:34 AM

Download the

Farbar Recovery Scan Tool and save it to your Desktop:

Download the 64 bit version: - Farbar Recovery Scan Tool Link

Open the startmenu and type the command cmd.
After you find the Command Prompt, right click on it and select Run as Administrator.
Copy and paste the following into the Command Prompt and press enter.

Code:

reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS

Right-click on the file FRST64.exe and choose Run as administrator.

Copy and paste the following (code) into the Search box and click the Search Registry button.

Code:

KB5036909

When the scan is complete, a message will display that SearchReg.txt is saved in the same folder FRST was started from.
Post the logfile SearchReg.txt as attachment in your next reply.

Elvenite · Saturday at 9:35 AM

Forget the last message. Apparently I have once removed some reg keys while troubleshooting the issue, when I restored them the command ran. It still failed, though: "Installed encountered an error: 0x800f0905."

Maxstar · Saturday at 9:36 AM

Which registry keys have you removed from the registry?

Elvenite · Saturday at 9:39 AM

These, but I restored them when I found them on the desktop and then tried to uninstall the KB using your command.
Do you still want me to scan the registry for it?

Maxstar · Saturday at 9:41 AM

Please readd that key into the registry and perform the FRST REG Search.

Elvenite · Saturday at 9:48 AM

Thanks again for your rapid responses.
Here is the result of the scan

Maxstar · Saturday at 9:53 AM

Step 1. Start the

Farbar Recovery Scan Tool again.

Warning: This script was written specifically for this system. Do not run this script on another system.

Download the attachment fixlist.txt and save it to your desktop.
Right-click on FRST.exe and select "Run as administrator".
Press the Fix button.
If for some reason the tool needs a restart, please make sure you let the system restart normally.
When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
Post the logfile Fixlog.txt as attachment in your next reply.

Step 2. Run the following DISM command and attach a new copy of the CBS log.

Code:

DISM /online /cleanup-image /RestoreHealth

Elvenite · Saturday at 10:06 AM

Done.

Maxstar · Saturday at 10:08 AM

Here's the next fix.

Step 1. Start the

Farbar Recovery Scan Tool again.

Warning: This script was written specifically for this system. Do not run this script on another system.

Download the attachment fixlist.txt and save it to your desktop.
Right-click on FRST.exe and select "Run as administrator".
Press the Fix button.
If for some reason the tool needs a restart, please make sure you let the system restart normally.
When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
Post the logfile Fixlog.txt as attachment in your next reply.

Step 2. Run the following DISM command and attach a new copy of the CBS log.

Code:

DISM /online /cleanup-image /RestoreHealth

Elvenite · Saturday at 10:18 AM

Please find the latest logs attached.
I've noticed that I no longer can run Notepad, it simply doesn't launch. A reboot didn't help.
I guess once we've got WU to work, it will reappear?

Maxstar · Saturday at 10:20 AM

Please try to update and post the result, now there are no warnings anymore in the CBS log.

[SOLVED] Windows 2022 fails WU -- metadata corruption

Member

Member

Attachments

Member

Attachments

Moderator, Windows Update Expert, Security Analyst

Member

Attachments

Moderator, Windows Update Expert, Security Analyst

Attachments

Member

Attachments

Moderator, Windows Update Expert, Security Analyst

Member

Moderator, Windows Update Expert, Security Analyst

Member

Moderator, Windows Update Expert, Security Analyst

Member

Attachments

Moderator, Windows Update Expert, Security Analyst

Member

Attachments

Moderator, Windows Update Expert, Security Analyst

Attachments

Member

Attachments

Moderator, Windows Update Expert, Security Analyst

Attachments

Member

Attachments

Moderator, Windows Update Expert, Security Analyst