[SOLVED] Widows Server 2019 Standard can't install updates 0x800f081f

AlconX

Contributor
Joined
Jun 14, 2024
Posts
6
Hello!

I have Widows Server 2019 Standard where I cannot install updates. I get 0x800f081f error (updates are installing and rolling back after restart).

I started from DISM:
Code:
DISM /Online /Cleanup-Image /RestoreHealth
What I got:
Code:
Deployment Image Servicing and Management tool

Version: 10.0.17763.1697

Image Version: 10.0.17763.2565

[===========================97.9%========================  ]
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

I check dism.log, but only error I see is in CBS.log:
Code:
2024-06-14 10:51:47, Info                  CBS    Repr: CSI Store check completes
2024-06-14 10:51:47, Info                  CBS    Exec: Not able to find amd64_dual_prnms003.inf_31bf3856ad364e35_10.0.17763.2686_none_640a716a1446731e\Amd64\unishare-pipelineconfig.xml from directory local source
2024-06-14 10:51:47, Info                  CBS    Exec: Not able to find WinSxS\amd64_dual_prnms003.inf_31bf3856ad364e35_10.0.17763.2686_none_640a716a1446731e\Amd64\unishare-pipelineconfig.xml from directory local source
2024-06-14 10:51:47, Info                  CBS    Repr: Not able to find replacement file for component amd64_dual_prnms003.inf_31bf3856ad364e35_10.0.17763.2686_none_640a716a1446731e, file Amd64\unishare-pipelineconfig.xml from any local source
2024-06-14 10:51:47, Info                  CBS    Exec: Download qualification evaluation, business scenario: Manual Corruption Repair
2024-06-14 10:51:47, Info                  CBS    Exec: Clients specified using local source only.
2024-06-14 10:51:47, Info                  CBS    Repr: The system configuration is not qualified for Windows Update download, skip WU.
2024-06-14 10:51:47, Info                  CBS    Failed to collect payload and there is nothing to repair. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2024-06-14 10:51:47, Info                  CBS    Failed to repair store. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2024-06-14 10:51:47, Info                  CBS   
2024-06-14 10:51:47, Info                  CBS    =================================
2024-06-14 10:51:47, Info                  CBS    Checking System Update Readiness.
2024-06-14 10:51:47, Info                  CBS   
2024-06-14 10:51:47, Info                  CBS    (p)    CSI Payload Corrupt    (n)            amd64_dual_prnms003.inf_31bf3856ad364e35_10.0.17763.2686_none_640a716a1446731e\Amd64\unishare-pipelineconfig.xml
2024-06-14 10:51:47, Info                  CBS    Repair failed: Missing replacement payload.
2024-06-14 10:51:47, Info                  CBS   
2024-06-14 10:51:47, Info                  CBS    Summary:
2024-06-14 10:51:47, Info                  CBS    Operation: Detect and Repair
2024-06-14 10:51:47, Info                  CBS    Operation result: 0x800f081f

I tried DISM with source install.wim from iso file and Windows folder of another WS2019 where updates works. Same error message.

Could you please help me fix this?
 
I was able to overcome DISM problem and now goes succesfully. SCF /scannow reports no problems, ComponentsScanner no problems too.

WU error now changed to 0x800703f1. Please find attached CBS.log - WU starts installation of KB5039217 and KB5038283 and then after restart is rolling back :(

Any help would be much appreciated.
 

Attachments

Hi and welcome to Sysnative,

Upload your DRIVERS Hive
  • Navigate to C:\Windows\System32\config and locate the DRIVERS 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 DRIVERS.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.
 
Replace Drivers Hive Manually

Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
  1. Download DRIVERS.ZIP and save to your desktop.
  2. Right-click on it and select Extract all.... Make sure the "Show extracted files when complete" is checked and click Extract.
  3. Now we have the DRIVERS file that we will be using to replace your current one.
  4. Navigate to C:\Windows\System32\config
  5. Right-click on the current DRIVERS file and select rename. Rename it to DRIVERS.bad.
    Note: If you get an error that the file is in use, reboot your computer and then try again.
  6. Take the file from the Drivers folder on your desktop and paste it into C:\Windows\System32\config

Reboot the server and attempt to update if it fails attach a new copy of the CBS logs as well as a copy of the following logfile.

Upload the setupapi.dev.log file
  • Open Windows Explorer and browse to the C:\Windows\INF folder.
  • Right-click on the file setupapi.dev.log 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.
657716925b62b-setup-api-dev-folder.png

  • Attach the file setupapi.dev.zip in your next reply.
 

Attachments

Download
6530fbb0f4101-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.
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.

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

Attachments

Here's the next fix, it seems we'll need to restore multiple drivers.

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.

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

Attachments

Updates installed successfully :) Thank you for your help and patience! I just made a donation for sysnative forums.
 
You're welcome. Glad to hear the updates installed successfully after the last fix, and thanks for your donation to Sysnative... (y)
I will mark this thread as solved.
 

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

Back
Top