[SOLVED] Windows Cumulative Updates end with Error 0x800f0982 (Windows 10 Enterprise 64bit LTSC 1809 Build 17763.5696)

Tessar

Member
Joined
Feb 1, 2025
Posts
19
Location
Germany
Hello Forum,

all installation attempts of any cumulative updates fail with error 0x800f0982. Language Pack is not installed. A restoration was unsuccessful.

The results

1# sfc /scannow

result: Windows Resource Protection did not find any integrity violations


2# Run SURT/DISM
Dism /Online /Cleanup-Image /RestoreHealth

result :
[===========================85.5%================= ]
Error: 0x800f081f
The source files were not found.


3# Run ComponentsScanner


Result : No corruptions were detected, but 3 warnings were found in the COMPONENTS hive.

If anyone can help, that would be great.

Tessar
 

Attachments

Hi @Tessar,

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
 
Rich (BB code):
2025-02-07 21:29:29, Info                  CSI    00000007 Hashes for file member [l:35]'WindowsDefenderApplicationGuard.wim' do not match.
 Expected: {l:32 ml:4096 b:c52addbd5f6c743ad95072bc8fd346e306a7e4f58e46742baddb038ac474035b}.
 Actual: {l:32 b:36273bd2950de5c613bec7c4560fc62c2807014c7616bef95e8a013675cf50c1}.
2025-02-07 21:29:29, Info                  CSI    00000008 Warning: Unable to repair payload file ([l:35]'WindowsDefenderApplicationGuard.wim') for component ([l:91 ml:140]'amd64_microsoft-windows-dynamic-image_31bf3856ad364e35_10.0.17763.316_none_b52ad881bae51f4e') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2025-02-07 21:31:29, Warning               CBS    Current tick count: 800 lower than last tick count: 941. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]

Hi and welcome to Sysnative,


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.
 
Hi,

Step 1. Download
67139f7e69a58-SFCFix-ico.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.
67139f52b3c1e-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.


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
 

Attachments

Hello Maxstar,
here comes the log file, the DISM command was completed as follows (successful) :
100 %
The restore operation was completed successfully.
The operation was completed successfully.
 

Attachments

Great, please attempt to update the latest update is from April last year as it seems. If it fails attach a new copy of the CBS logs.
 
Sorry, I don't want to make a mistake:
Yes, correct, the last working update was in April, can I now try to update to the latest CU (2-2025 / KB5052000)?
 
Yes, all the monthly updates are cumulative so when KB5052000 is offered there's no need to install the previous updates first.
 
Unfortunately, the installation failed again with error 0x800f0982. Attached is the CBS log. But However, I was unable to complete the step (sfc /scannnow) successfully because the report says that a restart is still pending (Message: A system repair is pending and requires a restart to complete.")
 

Attachments

Rich (BB code):
2025-02-15 13:46:33, Error                 CSI    00000015 (F) Can not identify matching versions for component Microsoft-Windows-DirectoryServices-Domain-Tools-CommandLine-NetDom.Resources, version 10.0.17763.5830, arch amd64, culture [l:5]'en-US', nonSxS, pkt {l:8 b:31bf3856ad364e35}.[gle=0x80004005]
2025-02-15 13:46:33, Error                 CSI    00000016@2025/2/15:12:46:33.850 (F) Attempting to mark store corrupt with category [l:21 ml:22]'CorruptComponentValue'[gle=0x80004005]
2025-02-15 13:46:33, Error                 CSI    00000017@2025/2/15:12:46:33.850 (F) onecore\base\wcp\componentstore\storelayout.cpp(2264): Error 800f0982 [Warning,Facility=15 (0x000f),Code=2434 (0x0982)] originated in function ComponentStore::CRawStoreLayout::AddComponentFile expression: ((SCODE) (((unsigned long)(1)<<31) | ((unsigned long)(15)<<16) | ((unsigned long)(0x982))) )
[gle=0x80004005]

Please provide a new copy of the COMPONENTS hive.
 
Here's the next fix.

Step 1.
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.
650c22f99662d-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.


Step 2. Run the System File Checker and post the result. If it fails attach a new copy of the CBS log.
Code:
SFC /Scannow
 

Attachments

For the next fix I'll need to rebuild an VM with the German language pack and some older updates, so this may take some time.
 

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

Back
Top