Member Avatar for DeanMSands3

I have my suspicions on how to fix this, I just want to make sure I'm right.

dism /image:C:\ /cleanup-image /restorehealth /scratchdir:C:\Scratch /Source:WIM:C:\Source\Install.wim:2

From my DISM log.

(p) CSI Manifest Corrupt            x86_microsoft-windows-c..dtc-runtime-cluster_31bf3856ad364e35_10.0.14393.953_none_7434ed91724916c9
Repair failed: Missing replacement manifest.
(p) CSI Payload Corrupt         amd64_microsoft-windows-c..sktop.appxmain.root_31bf3856ad364e35_10.0.14393.1358_none_50bc92cd091f5c0a\Cortana.LocalSearch.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt         amd64_microsoft-windows-c..sktop.appxmain.root_31bf3856ad364e35_10.0.14393.1358_none_50bc92cd091f5c0a\Cortana.IntentExtraction.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt         amd64_microsoft-windows-c..sktop.appxmain.root_31bf3856ad364e35_10.0.14393.1358_none_50bc92cd091f5c0a\Cortana.Dss.BackgroundTask.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt         amd64_microsoft-windows-c..sktop.appxmain.root_31bf3856ad364e35_10.0.14393.1358_none_50bc92cd091f5c0a\Cortana.Nodewinrtwrap.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt         amd64_microsoft-windows-n..orking-connectivity_31bf3856ad364e35_10.0.14393.1066_none_a8485c0b80ebb5de\OnDemandConnRouteHelper.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt         amd64_microsoft-windows-n..orking-connectivity_31bf3856ad364e35_10.0.14393.1066_none_a8485c0b80ebb5de\Windows.Networking.Connectivity.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt         amd64_microsoft-windows-classpnp-minwin_31bf3856ad364e35_10.0.14393.953_none_487cf0798b3b556f\Classpnp.sys
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt         amd64_microsoft-foundatio..ostics-errordetails_31bf3856ad364e35_10.0.14393.0_none_36927aa70a1e0894\ErrorDetailsUpdate.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt         amd64_microsoft-foundatio..ostics-errordetails_31bf3856ad364e35_10.0.14393.0_none_36927aa70a1e0894\ErrorDetails.dll
Repair failed: Missing replacement payload.
(p) CSI Payload Corrupt         amd64_microsoft-desktop-p..ioning-platform-uap_31bf3856ad364e35_10.0.14393.0_none_a641fa67da8fc706\countrytable.xml
Repair failed: Missing replacement payload.

C:\Source\Install.wim is a known good 14393 WIM from installation ISO. This is Home edition so I'm using Index:2.

My suspicion is that I should be able to patch the WIM with the MSU updates and try the DISM again. Any thoughts, DaniWeb?

Edited by DeanMSands3
  • 2 Contributors
  • 4 Replies
  • 2K Views
  • 3 Days Discussion Span
  • Latest Post Latest Post by DeanMSands3

Dani AI

Generated

Good instincts, . Those “Missing replacement manifest/payload” lines usually mean the repair source is older than the target OS (your log shows 14393.1358 components, while a vanilla 14393.0 ISO won’t have those files). Microsoft’s guidance is to use a repair source patched to at least the same CU level as the broken install. Also double‑check the WIM index really matches your edition before you start. (learn.microsoft.com)

From WinRE, this offline workflow is reliable and keeps CBS metadata happy (copying files by hand can mask problems but won’t fix the store):

:: 1) Confirm letters (WinRE often remaps)
dir D:\Windows

:: 2) Verify the correct edition index
dism /Get-ImageInfo /ImageFile:C:\Source\install.wim

:: 3) Mount that index
dism /Mount-Image /ImageFile:C:\Source\install.wim /Index:2 /MountDir:C:\Mount

:: 4) Slipstream updates into the WIM (SSU first, then LCU)
dism /Image:C:\Mount /Add-Package /PackagePath:C:\Updates\SSU.msu
dism /Image:C:\Mount /Add-Package /PackagePath:C:\Updates\LCU.msu

:: 5) Commit the image
dism /Unmount-Image /MountDir:C:\Mount /Commit

:: 6) Repair the offline OS using the updated WIM
dism /Image:D:\ /Cleanup-Image /RestoreHealth /Source:WIM:C:\Source\install.wim:2 /LimitAccess /ScratchDir:D:\Scratch

:: 7) Follow with an offline SFC
sfc /scannow /offbootdir=D:\ /offwindir=D:\Windows

Notes:

  • If you keep the image mounted, you can point RestoreHealth at the mounted Windows folder (for example, /Source:C:\Mount\Windows). (learn.microsoft.com)
  • Use SSU before LCU when servicing media for older builds like 1607; that ordering still matters when you are manually integrating packages. (support.microsoft.com)
  • If an in‑place upgrade (as suggested) later fails, clearing a stale $WINDOWS.~BT can help; use Disk Cleanup or remove it from an elevated prompt after taking ownership. ()

DISM/RestoreHealth source options, Add‑Package, and offline SFC switches are documented here if you want to dig deeper. (learn.microsoft.com)

Recommended Answers

All 4 Replies

Member Avatar for DeanMSands3

rproffitt: There are prior discussions about this. Example where they went with an in-place upgrade:
https://www.tenforums.com/performance-maintenance/23170-sfc-corrupt-files-2.html

Which is a great idea except I was stuck in the Recovery Console. I ended up copying some known good files from the WinSXS folder to clear up the CSI Payload Corrupt errors. Couldn't figure out the manifest errors.

For some reason the Windows Boot Manager wouldn't boot from a USB so I tried enabling it from BIOS. Hilariously, the USB didn't boot but Windows finally did.

I'm still wrestling with it. Now I'm trying to get the Creators Update, but it keeps failing. DISM and SFC both report success. The Update Troubleshooter reported success then failure. Now I'm going for an in-place upgrade.

Edited by DeanMSands3
commented: I'm staying tuned. +0
Member Avatar for DeanMSands3

Finally deleted $Windows.BT and the Creators Update went through. Laptop seems to be working fine now.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.