Simpler solution may be to not specify a source
dism /online /cleanup-image /restorehealth
Corrupted Windows Server 2016 installation - Issues running DISM
I've got a HyperV Virtual Machine with a Windows Server 2016 installation which appears to have become corrupted. I'm trying to get it back up running (I'd rather do that than rebuild the whole server), however DISM is being... difficult.
I'm using the command dism /image:f:\ /cleanup-image /restorehealth /source:wim:g:\sources\install.wim:2 where G:\ is a mounted Windows Server 2016 ISO (from what I've checked index 2 is Windows Server 2016 Standard Desktop Experience) and F: is the mounted virtual machine VHDX with the corrupted Windows installation.
Unfortunately, the dism command ultimately fails:
Error: 0x800f081f
The source files could not be found.
Looking over the provided DISM.log file I can see that the ISO appears to be missing some files...
=================================
Checking System Update Readiness.(p) CSI Payload Corrupt amd64_microsoft-windows-shell32_31bf3856ad364e35_10.0.14393.1794_none_e1adcedb6cb8eae3\apps.inf
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_microsoft-windows-apisetschema-server_31bf3856ad364e35_10.0.14393.1715_none_61379ad2ce2e3654\apisetschema.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt amd64_microsoft-windows-pnpsysprep_31bf3856ad364e35_10.0.14393.479_none_7b790dc55511835d\sppnp.dll
Repair failed: Missing replacement payload.
What should I do?
Windows for business | Windows Server | User experience | Other
2 answers
Sort by: Most helpful
-
Anonymous
2022-07-26T16:43:09.46+00:00 -
Drew Frampton 0 Reputation points
2023-08-30T02:07:52.2033333+00:00 Can I please check:
Your server is 2016. Does it matter which index you use for your 2016 dism command?
Ie., I saw you used 2. Would it matter if you used the non desktop experience version, ie index 1?