[SOLVED] Windows Server 2019 [ERROR 0x800f0982]

Argon

Member
Joined
Oct 15, 2022
Posts
93
Hi everybody and thank you for your precious help on my domain controller (sic ^_^; ), after different update problem I am definitely blocked.

sfc /scannow is ok
Dism /Online /Cleanup-Image /ScanHealth is ok
Dism /Online /Cleanup-Image /CheckHealth is ok
Dism /Online /Cleanup-Image /RestoreHealth is ok

But Error on KB5018419 (0x800f0982)

Components too big : components.zip

ComponentsScanner.exe is in progress but no longer seems to be progressing...


Loading registry hive from C:\Windows\System32\config\COMPONENTS
Parsing loaded hive, please wait...
Hive parsed successfully - found 389 707 keys and 1 204 587 values
Starting corruption scan
Performing regedit load test
Scanning CanonicalData\Catalog for corruptions
Scanning CanonicalData\Deployments for corruptions
Scanning DerivedData\Components for corruptions
Scanning VersionedIndex\...\ComponentFamilies for corruptions
Checking WinSxS catalogs against CanonicalData\Catalogs
Checking WinSxS components against DerivedData\Components
Checking f! marks
Checking manifests
Checking for malformed Deployment keys
Checking CatalogThumbprints & c! marks (in progress or stop ??)
 

Attachments

Hi and welcome to Sysnative,

Could you please provide a copy of the CBS folder with the previous log(s).
  • Open Windows Explorer and browse to the C:\Windows\Logs folder.
  • Right-click on the CBS folder and choose Send to > Compressed (zipped) folder.
  • Now the message will appear, "Windows cannot create the Compressed (zipped) Folder here. Do you want it to be placed on the desktop instead?"
  • Click on the Yes button here.
618e949e09fef-CBS-Folder.png

  • Attach the file CBS.zip to your next reply.
 
Please try to install KB5018419 again while Process Monitor is running. And attach the latest CBS log(s) and LogFile.pml to your next post.

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.
 
the update is taking so long to progress that Process Monitor closes itself, I have to restart it, is that good?
 
Hi,

Not really, but let's see if we can use the ProcMon trace when KB5018419 failed. Please attach the latest CBS log(s) as well.
 
it stayed about 1 hour on 20% and failed all of a sudden didn't have time to restart procman before. In CBS there are also two logs procman, hope that's enough for you :'(

CBS.zip
 
Hi,

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 SFCFixScript.txt and save it to your desktop.
  • Drag the SFCFixScript.txt file over the SFCFix.exe executable and release it.
62151e1bebac4-SFCFix-Txt-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. If it fails attach a new copy of the CBS log(s).
 

Attachments

Hello, it didn't work.
It takes about 39 minutes to go from 20% to 73%
Then 2, 3 minutes to go from 73% to 100% and fail.

I was able to capture Procmon a bit at the start and end when it's at 73%. So I I think managed to catch the ending error.

logfile : Logfile.zip
cbs : CBS.zip
 
Hi,

Export SBS (SideBySide) 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\SideBySide
  • Once selected, click File > Export....
  • Change the Save as type: to Registry Hive Files (*.*).

    622dbdc454cdb-Export-SBS-hive.png

  • Name this file SideBySide (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.
 
Rich (BB code):
9:42:17.8856276 AM    TiWorker.exe    8188    RegQueryValue    HKLM\COMPONENTS\DerivedData\Components\amd64_microsoft-windows-p..i-ntprint.resources_31bf3856ad364e35_10.0.17763.1971_ko-kr_928b259037af56c6\f!ntprint.dll.mui    NAME NOT FOUND    Length: 0
9:42:17.8872774 AM    TiWorker.exe    8188    RegOpenKey    HKLM\Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-p..i-ntprint.resources_31bf3856ad364e35_ko-kr_6254c8dd35b0f1e1    NAME NOT FOUND    Desired Access: Read

Hi,

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.
62151e1bebac4-SFCFix-Txt-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. If it fails attach a new copy of the CBS log(s).
 

Attachments

Hi,

It seems there is a problem with the Korean (ko-KR) language pack, I'll need to test some things and install an VM - with the necessary updates - to investigate this issue further.
 
Thank you very much, what's amazing is that there was never a Korean language installation, just French and English
 
Thanks for letting us know that the Korean language pack was never installed on this server.

Please run the following command in an elevated command prompt and attach "DISM-lang.txt" to your next post.
Code:
DISM /online /get-intl > "%USERPROFILE%\desktop\DISM-lang.txt"
 

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

Back
Top