Windows Server 2022 update error 0x800f081f on KB 5010354 (and KB5010421)

Question

I have a Windows Server 2022 that has been giving the error 0x800f081f when trying to install KB5010354 and KB5010421.

Have tried the following but no luck...

• DISM.exe /Online /Cleanup-image /Restorehealth
• sfc /scannow

Have tried both running the updates from Windows update and manually downloading.

In the CBS.log and this seems to be the first sign of a problem...
2022-03-03 21:55:03, Info CBS Exec: Warning - Manifest doesn't exist for: \?\C:\WINDOWS\SoftwareDistribution\Download\0a240c064e2e4090368304b772279c66\inst_Windows10.0-KB5010354-x64.cab_\amd64_microsoft-windows-n..troller-diagnostics_31bf3856ad364e35_10.0.20348.1_none_773e8bc973bca46e.manifest

Suggestions on what else I can try?

Answer 1

Hi MikeCisar,

According to your description, we could try to clear Windows Update Cache & components:

Run Command Prompt as Administrator and enter the commands below:

Net Stop bits
Net Stop wuauserv
Net Stop appidsvc
Net Stop cryptsvc
Ren %systemroot%SoftwareDistribution SoftwareDistribution.bak
Ren %systemroot%system32catroot2 catroot2.bak
Net Start bits
Net Start wuauserv
Net Start appidsvc
Net Start cryptsvc

If the issue still insists, try to download the update from Microsoft Catalog webiste.

https://www.catalog.update.microsoft.com/Home.aspx

Then try to install it with dism command.

1. Create the folder C:\temp\cab
2. Download the update patch from http://catalog.update.microsoft.com to C:/temp
3. Expand the .msu file to extract the .cab file by running the following command as administrator in CMD.
   expand -F:* C:\temp{.msu filename and extension}C:\temp\cab
4. Then use the following DISM command to add the patch package
   Dism /online /add-package /packagepath:c:\temp\cab{.cab file extension}
5. Reboot

https://pureinfotech.com/install-cab-file-windows-10/

Best Regards,

Carl

Answer 2

If you're able to perform an in place upgrade repair it typically is the most efficient method for troubleshooting 0x800f081f.

https://www.tenforums.com/tutorials/16397-repair-install-windows-10-place-upgrade.html

https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-2022

When performing an in place upgrade repair there are options to accept or not accept updates at the time of the in place upgrade repair.

Select no updates during the repair.

If the repair is successful then perform updates.

.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post there is /\ with a number: click = a helpful post
.
.
.
.
.

Answer 3

I have the same problem.

I tried a manual installation with the same result.

SFC repair and restorehealth commands don't seem to help.

In place upgrade solves the problem, but as more and more cases are popping up, it might be better for microsoft to fix this problem anyway.Problem also seems to occur only on virtual servers

2023-02-02 09:09:50, Info CBS Exec: Warning - Manifest doesn't exist for: ?\C:\WINDOWS\CbsTemp\31012573_977870743\Windows10.0-KB5022291-x64.cab\amd64_microsoft-windows-slb-mux-perfcounters_31bf3856ad364e35_10.0.20348.1_none_1da2555dd5ebeb46.manifest

2023-02-02 09:09:50, Info CBS Component Identity: Microsoft-Windows-Slb-Mux-PerfCounters, Culture=neutral, Version=10.0.20348.1, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS

2023-02-02 09:09:50, Info CBS Exec: Warning - Manifest doesn't exist for: ?\C:\WINDOWS\CbsTemp\31012573_977870743\Windows10.0-KB5022291-x64.cab\msil_microsoft-windows-slbmux-events_31bf3856ad364e35_10.0.20348.1_none_48fc7f53590719a7.manifest

Answer 4

I was able to resolve this problem. It was a long story but finally resolved. It is hard work but possible to do.

Answer 5

HI @Carl Fan

Thanks for your suggestions, unfortunately still a no-go. FWIW the first two cumulative updates that were having problems installing are now superceded by KB5011497 so its now failing with the same error code instead of the other two.

The DISM run failed at 3.9%... here's the last bit of the DISM log, if that helps...

DISM Package Manager: PID=8900 TID=9144 CBS is being initialized for online use. More information about CBS actions can be located at: %windir%\logs\cbs\cbs.log - CDISMPackageManager::Initialize
DISM Package Manager: PID=8900 TID=9144 Loaded servicing stack for online use only. - CDISMPackageManager::CreateCbsSession
DISM Package Manager: PID=8900 TID=9144 Processing the top level command token(add-package). - CPackageManagerCLIHandler::Private_ValidateCmdLine
DISM Package Manager: PID=8900 TID=9144 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
DISM Package Manager: PID=8900 TID=9144 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
DISM Package Manager: PID=8900 TID=9144 Encountered the option "packagepath" with value "c:\temp\cab\Windows10.0-KB5011497-x64.cab" - CPackageManagerCLIHandler::Private_GetPackagesFromCommandLine
DISM Package Manager: PID=8900 TID=9144 Package Multiple_Packages~~~~0.0.0.0 with CBS state 0(CbsInstallStateAbsent) being mapped to dism state 1(DISM_INSTALL_STATE_NOTPRESENT) - CDISMPackage::LogInstallStateMapping
DISM Package Manager: PID=8900 TID=9144 Initiating Changes on Package with values: 4, 7 - CDISMPackage::Internal_ChangePackageState
DISM Package Manager: PID=8900 TID=9144 CBS session options=0x100! - CDISMPackageManager::Internal_Finalize
DISM Package Manager: PID=8900 TID=8552 Error in operation: source for package or file not found, ResolveSource() unsuccessful. (CBS HRESULT=0x800f081f) - CCbsConUIHandler::Error
DISM Package Manager: PID=8900 TID=9144 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f081f)
DISM Package Manager: PID=8900 TID=9144 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg
DISM Package Manager: PID=8900 TID=9144 Failed processing package changes - CDISMPackageManager::ProcessChanges(hr:0x800f081f)
DISM Package Manager: PID=8900 TID=9144 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg
DISM Package Manager: PID=8900 TID=9144 Loaded servicing stack for online use only. - CDISMPackageManager::CreateCbsSession
DISM Package Manager: PID=8900 TID=9144 Failed while processing command add-package. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)
DISM Package Manager: PID=8900 TID=9144 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800F081F
DISM Package Manager: PID=8900 TID=9144 Finalizing CBS core. - CDISMPackageManager::Finalize
DISM Manager: PID=5828 TID=1384 Closing session event handle 0x208 - CDISMManager::CleanupImageSessionEntry
DISM.EXE: Image session has been closed. Reboot required=no.
DISM.EXE:
DISM.EXE: <----- Ending Dism.exe session ----->
DISM.EXE: