Dism Repair / Windows Update Issues

Question

Trying to do updates to a Server 2019 Standard (Desktop Experience) VM, when doing so I keep receiving 0x800f081f. Followed a bunch of different forums for troubleshooting, including resetting windows update, running windows update troubleshooter, ensuring the server has network access, etc.

Decided it would be easier to just do a sfc /scannow and a dism's /restorehealth. Sfc finds corrupt files it cannot repair so I did a /checkhealth and /restorehealth, the /restorehealth gave me a 0x800f081f error so I downloaded the 1809 ISO (the server is 1809 currently), mounted it, checked the drive it mounted to (H:), verified it has the install.wim file in "sources", checked which index the "Standard (Desktop Experience)" is under (index 2) using DISM, and ran: DISM /Online /Cleanup-Image /RestoreHealth /Source:WIM:H:\sources\install.wim:2 /LimitAccess

When that finally completes I get 0x800f081f, which the only thing I can find online that I had not already tried/verified was permissions, so I moved the contents from the H:\ drive to a local folder, gave my user account full permissions to the folder and child objects, then tried running the /restorehealth for the new location, and still receive the same error.

After receiving the same error there, I went back to volume licensing center and downloaded the 1809 ISO assuming the one I received was corrupt in some way, nope, same error.

When peeking at the CBS log I notice this as the culprit (this is the same when running it local, through mounted ISO or online):

2022-02-02 08:57:31, Info CBS Checking System Update Readiness.
2022-02-02 08:57:31, Info CBS
2022-02-02 08:57:31, Info CBS (p) CSI Payload Corrupt (n) amd64_dual_ntprint.inf_31bf3856ad364e35_10.0.17763.1_none_d5e39b8fa1bd4175\Amd64\PJLMON.DLL
2022-02-02 08:57:31, Info CBS Repair failed: Missing replacement payload.

////EDIT: replaced it with another servers, still the same result//// Is it safe to copy pjlmon.dll from a working server to resolve this? When looking this DLL up online I can see it is a critical one for the machine to function, I do not want to break this server and don't trust the third party repair tools.

Here are the errors in the dism.log incase they help at all (this is the same when running it local, through mounted ISO or online):

2022-02-02 11:45:47, Info DISM DISM Package Manager: PID=18092 TID=5164 Error in operation: source for package or file not found, ResolveSource() unsuccessful. (CBS HRESULT=0x800f081f) - CCbsConUIHandler::Error
2022-02-02 11:45:47, Error DISM DISM Package Manager: PID=18092 TID=16824 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f081f)
2022-02-02 11:45:47, Error DISM DISM Package Manager: PID=18092 TID=16824 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg
2022-02-02 11:45:47, Error DISM DISM Package Manager: PID=18092 TID=16824 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f081f)
2022-02-02 11:45:47, Error DISM DISM Package Manager: PID=18092 TID=16824 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg
2022-02-02 11:45:47, Error DISM DISM Package Manager: PID=18092 TID=16824 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800f081f)
2022-02-02 11:45:47, Error DISM DISM Package Manager: PID=18092 TID=16824 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)
2022-02-02 11:45:47, Info DISM DISM Package Manager: PID=18092 TID=16824 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine

Any help appreciated!

Answer 1

Hello NateBreeden,

Thank you for your question and reaching out.

I can understand you are facing update error 0x800f081f.

This error message basically states that DISM was unable to find the files required to fix the online Windows image in their default location. To resolve this issue, you have to either run a component clean up and then an SFC Scan or provide DISM with a location that contains the files it needs to attempt the image repair. You can also fix this by upgrading Windows .iso then run the setup again to repair the files.

dism.exe /online /Cleanup-Image /StartComponentCleanup
sfc /scannow

Wait for these commands run and when they’re done, run:Dism /Online /Cleanup-Image /RestoreHealth
At this point, Dism /Online /Cleanup-Image /RestoreHealth should work again.

Please also disable or uninstall any Antivirus program you may have temporarily.

---

--If the reply is helpful, please Upvote and Accept as answer--

Answer 2

There might be hope but you'll need to find the KB number referenced to the "CSI Payload Corrupt"

Answer 3

The Jan11th update was replaced with this out of band.
https://www.catalog.update.microsoft.com/Search.aspx?q=KB5010791

--please don't forget to upvote and Accept as answer if the reply is helpful--