[SOLVED] Windows Server 2019 - Unable To Install Updates - 0x800f081f

S

SecOpsSierra

Member
Joined
Feb 25, 2025
Posts
8
Hello all! I'm attempting to install updates on my Windows Server 2019 VM and I'm getting 0x800f0983.
I've done what most others have starting with:

SFC Completes OK:
Code: 
C:\windows\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.
Click to expand...


DISM fails
Code: 
C:\windows\system32>DISM.exe /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.17763.5830

Image Version: 10.0.17763.6775

[==========================100.0%==========================]
Error: 0x800f081f

The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

The DISM log file can be found at C:\windows\Logs\DISM\dism.log

DISM logs points to CBS log which shows:

Code: 
2025-02-26 00:09:34, Info                  CBS    =================================
2025-02-26 00:09:34, Info                  CBS    Checking System Update Readiness.
2025-02-26 00:09:34, Info                  CBS   
2025-02-26 00:09:34, Info                  CBS    (p)    CSI Payload Corrupt    (n)            wow64_microsoft-windows-security-schannel_31bf3856ad364e35_10.0.17763.6414_none_79edd7a95b7b05f2\r\schannel.dll
2025-02-26 00:09:34, Info                  CBS    Repair failed: Missing replacement payload.
2025-02-26 00:09:34, Info                  CBS   
2025-02-26 00:09:34, Info                  CBS    Summary:
2025-02-26 00:09:34, Info                  CBS    Operation: Detect and Repair
2025-02-26 00:09:34, Info                  CBS    Operation result: 0x800f081f
2025-02-26 00:09:34, Info                  CBS    Last Successful Step: Entire operation completes.
2025-02-26 00:09:34, Info                  CBS    Total Detected Corruption:    1
2025-02-26 00:09:34, Info                  CBS        CBS Manifest Corruption:    0
2025-02-26 00:09:34, Info                  CBS        CBS Metadata Corruption:    0
2025-02-26 00:09:34, Info                  CBS        CSI Manifest Corruption:    0
2025-02-26 00:09:34, Info                  CBS        CSI Metadata Corruption:    0
2025-02-26 00:09:34, Info                  CBS        CSI Payload Corruption:    1
2025-02-26 00:09:34, Info                  CBS    Total Repaired Corruption:    0
2025-02-26 00:09:34, Info                  CBS        CBS Manifest Repaired:    0
2025-02-26 00:09:34, Info                  CBS        CSI Manifest Repaired:    0
2025-02-26 00:09:34, Info                  CBS        CSI Payload Repaired:    0
2025-02-26 00:09:34, Info                  CBS        CSI Store Metadata refreshed:    True
2025-02-26 00:09:34, Info                  CBS   
2025-02-26 00:09:34, Info                  CBS    Total Operation Time: 599 seconds.

Any help would be greatly appreciated!
 
Hi @SecOpsSierra,

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
 
Hi and welcome to Sysnative,

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

Thanks Maxstar. Ran SFCFix process and DISM. No errors listed. Going to reboot and try Windows Update again, will report back shortly.
 
Great, let me know the result and attach the latest CBS logs when it fails.
 
Please provide the COMPONENTS hive.

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,

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.

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

Attachments

Rich (BB code): 
2025-02-28 13:38:47, Error                 CSI    000000a7@2025/2/28:13:38:47.490 (F) onecore\base\wcp\componentstore\csd_winners.cpp(1279): Error STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE originated in function OriginateFilesMissingError expression: (null)
[gle=0x80004005]

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

    652ff1dfded79-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.
 
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.
650ef5dbdfd06-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 attempt to update. If it fails attach a new copy of the CBS logs.
 

Attachments

You must log in or register to reply here.

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

Back
Top