Windows Server 2019 cannot update since 17763.2028, Error 0x800f0988

SFD136

Member
Joined
Nov 30, 2022
Posts
14
Hello, I was left with a Windows Server 2019 Domain Controller with Exchange 2019 on it, failing to install every CU with an error 0x800f0988. Previously the server was left without installing CUs. However, the client received E-Mail Alerts of not being able to install latest Sophos Endpoint. As the server does not meet the requirement of Azure Code Signing (17763.2210), I have no other choices but to make the Windows Update work again.

Step #1 - Run SFC Scan
Windows Resource Protection did not find any integrity violations.

Step #2 - Run SURT/DISM
[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

Step #3 / Step #4
See the attachment.

Thanks for the generous help.
 

Attachments

Hi and welcome to Sysnative,

Step 1. Upload your COMPONENTS hive.
  • Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
  • Please copy this file to your desktop.
  • Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
  • Right-click on this file on your desktop and select Send To > Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
  • If the file is too large to upload here, upload the file to www.wetransfer.com and post the link in your next reply.

Step 2. Download the
577bf0efb8088-FRST.png
Farbar Recovery Scan Tool and save it to your Desktop:

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.
Code:
samsrv.dll.mui
  • When the scan is complete, a message will display that 'Search.txt' is saved in the same folder FRST was started from. Notepad will open this file also.
  • Post the logfile Search.txt as attachment in your next reply.
 
Please open an elevated command prompt, run the following command and post the result.
Rich (BB code):
certutil -hashfile %systemroot%\WinSxS\amd64_microsoft-windows-d..vices-sam.resources_31bf3856ad364e35_10.0.17763.1_en-us_0546285497a0e2e9\samsrv.dll.mui SHA256
 
Please open an elevated command prompt, run the following command and post the result.
Rich (BB code):
certutil -hashfile %systemroot%\WinSxS\amd64_microsoft-windows-d..vices-sam.resources_31bf3856ad364e35_10.0.17763.1_en-us_0546285497a0e2e9\samsrv.dll.mui SHA256

CertUtil: -hashfile command FAILED: 0x80070002 (WIN32: 2 ERROR_FILE_NOT_FOUND)
CertUtil: The system cannot find the file specified.

FYI
_31bf3856ad364e35_10.0.17763.1_.png
%systemroot%\WinSxS\amd64_microsoft-windows-d..vices-sam.resources_31bf3856ad364e35_10.0.17763.1_en-us_0546285497a0e2e9
No such directory, only variants of other languages exist.
 
Here's the first fix.

Download
56f31e53c97da-SFCFix.PNG
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.
6190d993a26f3-SFCFix-Zip-Eng.gif

  • 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.
 

Attachments

Here's the first fix.

Download
56f31e53c97da-SFCFix.PNG
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.
6190d993a26f3-SFCFix-Zip-Eng.gif

  • 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.

Please check the output of SFCFix while I try to install the update again.

SFCFix version 3.0.2.1 by niemiro.
Start time: 2023-08-20 22:36:21.817
Microsoft Windows Server 10 Build 17763 - amd64
Using .zip script file at C:\Users\Administrator\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\WinSxS

Successfully created directory tree \\?\C:\Windows\WinSxS\amd64_microsoft-windows-d..vices-sam.resources_31bf3856ad364e35_10.0.17763.1_en-us_0546285497a0e2e9.

Successfully copied file C:\Users\Administrator\AppData\Local\niemiro\Archive\WinSxS\amd64_microsoft-windows-d..vices-sam.resources_31bf3856ad364e35_10.0.17763.1_en-us_0546285497a0e2e9\samsrv.dll.mui to C:\Windows\WinSxS\amd64_microsoft-windows-d..vices-sam.resources_31bf3856ad364e35_10.0.17763.1_en-us_0546285497a0e2e9\samsrv.dll.mui.

Successfully restored ownership for C:\Windows\WinSxS
Successfully restored permissions on C:\Windows\WinSxS
PowerCopy:: directive completed successfully.




RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-d..vices-sam.resources_31bf3856ad364e35_10.0.17763.1_en-us_0546285497a0e2e9.

Successfully imported registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-d..vices-sam.resources_31bf3856ad364e35_10.0.17763.1_en-us_0546285497a0e2e9.

Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-d..vices-sam.resources_31bf3856ad364e35_10.0.17763.1_en-us_0546285497a0e2e9.
RegistryScript:: directive completed successfully.




Successfully processed all directives.



Failed to generate a complete zip file. Upload aborted.


SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 2 datablocks.
Finish time: 2023-08-20 22:41:06.469
Script hash: DDh3ZBDTDDf+aQN6FpVzkd8uI2hGCIkqogeQYQgAF18=
----------------------EOF-----------------------
 
Here's the first fix.

Download
56f31e53c97da-SFCFix.PNG
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.
6190d993a26f3-SFCFix-Zip-Eng.gif

  • 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.

Same Error Code of 0x800f0988, latest CBS log attached.
 

Attachments

Just my 2 cents while waiting, the samsrv.dll.mui version 10.0.17763.1 all went missing except the en-us one we just placed into WinSXS, while version 10.0.17763.1790 have 7 language variants. I wonder if the one installed the server used a multiple language installation disk and hence if we need to place all 7 variants of version 10.0.17763.1 before it works.
 

Attachments

  • 1 vs 1790.png
    1 vs 1790.png
    586.6 KB · Views: 7
I'll think we need to replace this package for several other language packs as well. Please provide a new copy of the COMPONENTS hive, then I can setup a VM with all the language packs to provide a new fix.
 
I'll think we need to replace this package for several other language packs as well. Please provide a new copy of the COMPONENTS hive, then I can setup a VM with all the language packs to provide a new fix.

Just chatting with friends on Telegram...Sorry for keeping you waiting.

Involved Languages includes:
de-de
en-us
es-es
fr-fr
it-it
ko-kr
pl-pl
 

Attachments

Last edited:
Hi,

If some language packs are not in use, I would suggest to remove them first.
Any ideas to remove them properly via DISM or any other ways? I never use languages other than en-us.
Actually I have never seen a Server with so many languages pre-installed. When I checked WinSXS on a properly updated WS2019 from the same site, I found even the 8th language - ja-jp. I suspect the ISO image that the guy used to install these bunch of VMs came from an OEM like HPE or DELL, where they always bundle multiple languages into one single DVD for easier distribution.

1692604476197.png

In contrast, the WS2019 in my home lab only have 2 samsrv.dll.mui, all in en-us.

1692604761003.png
 
You can remove the additional language packs through Settings > Time & Language > Language > Select Language and click remove.
 
You can remove the additional language packs through Settings > Time & Language > Language > Select Language and click remove.
1692605673437.png

No such dummy languages...should I try to install the affected languages one by one and then remove them again, hoping the action will get rid of the dummy languages?
 
Please run the following command and attach Packages.txt to your next post.
Code:
DISM /online /get-packages /format:table > "%userprofile%\desktop\Packages.txt"
 
Hmm, let's try the following command:
Code:
DISM /online /get-intl > "%userprofile%\desktop\DISM-intl.txt"
 

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

Back
Top