[SOLVED] WS2019 - 0x800f0982 KB5028168

[kama]

Thank you for taking the next step.

 

[Maxstar]

Please post a new copy of the COMPONENTS and the Side By Side (SBS) hive as described in post #3.

 

[kama]

WeTransfer

 

[Maxstar]

Here's the next fix.

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 SFCFixScript.txt and save it to your desktop.
• Drag the SFCFixScript.txt 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.

Afterwards reboot the server and attempt to update again. If it fails attach a new copy of the CBS logs.

 

[kama]

Here are the next logs. I am happy that you are helping me.

 

[Maxstar]

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.

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 Files button.

SearchAll: msinfo32.exe.mui

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

 

[kama]

Hopefully I have done everything as requested. Further many thanks.

 

[Maxstar]

Please attempt to update again with Process Monitor running.

Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square (CTRL +E) on the toolbar as shown below.



4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up the LogFile.PML and upload it to WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free and provide the link as well as a new copy of the CBS logs.

 

[kama]

Log files are online. I sent the WeTransfer link via private message.

 

[Maxstar]

Thanks, here's the next fix.

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.

Afterwards attempt to update again. If it fails attach a new copy of the CBS logs.

 

[kama]

Thanks! Here is the next log.

 

[Maxstar]

2023-07-30 18:26:34, Error                 CSI    00000024 (F) Can not identify matching versions for component Microsoft-Windows-DirectoryServices-Domain-Tools-Command-ldp.Resources, version 10.0.17763.4377, arch x86, culture [l:5]'nl-NL', nonSxS, pkt {l:8 b:31bf3856ad364e35}.[gle=0x80004005]
2023-07-30 18:26:34, Error                 CSI    0000002a (F) Can not identify matching versions for component Microsoft-Windows-InetRes-Adm.Resources, version 11.0.17763.4492, arch amd64, culture [l:5]'nl-NL', nonSxS, pkt {l:8 b:31bf3856ad364e35}.[gle=0x80004005]
2023-07-30 18:26:36, Error                 CSI    00000033 (F) Can not identify matching versions for component machine.inf.Resources, version 10.0.17763.1971, arch amd64, culture [l:5]'nl-NL', nonSxS, pkt {l:8 b:31bf3856ad364e35}.[gle=0x80004005]
2023-07-30 18:26:36, Error                 CSI    00000043 (F) Can not identify matching versions for component Microsoft-Windows-VolumeEncryption-Adm.Resources, version 10.0.17763.404, arch amd64, culture [l:5]'nl-NL', nonSxS, pkt {l:8 b:31bf3856ad364e35}.[gle=0x80004005]
2023-07-30 18:26:36, Error                 CSI    00000047 (F) Can not identify matching versions for component Microsoft-Windows-DevInst-Adm.Resources, version 10.0.17763.2145, arch amd64, culture [l:5]'nl-NL', nonSxS, pkt {l:8 b:31bf3856ad364e35}.[gle=0x80004005]
2023-07-30 18:26:36, Error                 CSI    0000004b (F) Can not identify matching versions for component Microsoft-Windows-DataCollection-Adm.Resources, version 10.0.17763.2867, arch amd64, culture [l:5]'nl-NL', nonSxS, pkt {l:8 b:31bf3856ad364e35}.[gle=0x80004005]
2023-07-30 18:26:38, Error                 CSI    00000053 (F) Can not identify matching versions for component Microsoft.Windows.FileServer.Management.Plugin.UI.resources, version 10.0.17763.592, arch msil, culture [l:5]'nl-NL', nonSxS, pkt {l:8 b:31bf3856ad364e35}.[gle=0x80004005]
2023-07-30 18:26:38, Error                 CSI    00000057 (F) Can not identify matching versions for component Microsoft.Windows.FileServer.Management.Plugin.resources, version 10.0.17763.3650, arch msil, culture [l:5]'nl-NL', nonSxS, pkt {l:8 b:31bf3856ad364e35}.[gle=0x80004005]

Hi,

Here's the next fix.

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.

Afterwards attempt to update again. If it fails attach a new copy of the CBS logs.

 

[kama]

Thanks. I would like to send a better message, but I need to attach another CBS log.

 

[Maxstar]

Is this server a virtual machine or a physical server? Some new corruptions are automaticcaly repaired, and the latest log shows a bunch of issues we've fixed in previous posts.

 

[kama]

It is a physical server. Terminal Server services are enabled and in use. HyperV is enabled, but no virtual machine is running.

Edit: Over the weekend, only I was logged in as administrator via Terminal Services.

 

[kama]

Windows Server 2019 Remote Desktop Services are enabled without Domain. Currently two more users are logged in.
The old installation was very similar, but without Hyper-V enabled. This installation ran for several years without any problems with the updates.

 

[Maxstar]

Okay, please run the following command to look at the installed langauage packs.

DISM /online /get-intl > "%userprofile%\desktop\DISM-lang.txt"

 

[kama]

No language other than de-DE has ever been installed by me. Where it, fr, it, pl, ru or tr come from, I do not know. Also nl was never installed consciously by me.

 

[Maxstar]

This is a common issue (bug) on Windows Server 2019 systems. In the latest log a payload file for the Turkisch language pack was corrupted, and all the other issues has to due with the Dutch (NL) language pack. Are you able to clone this server to a virtual environment, so we can test some things safely?

 

[kama]

That should work, but I probably need at least 1 day. Do you have a suggestion with which tool I do best? I do not need instructions, a cue would be enough.