Reply to thread

I've made a small amount of progress with the win10 disk, but I just need a bit of help running the /restorehealth command.


I've so far been focusing on the win11 disk, but I recently tried to repair the image of the win10 disk. I ran /restorehealth on it without specifying a source and it detected 10 CSI Payload Corruptions and fixed 2 of them. I then ran sfc scannow which fixed 3 files but failed to fix 7 others. I attempted to boot into the OS and it got a little further than last time. It loaded extremely slowly but over the course of an hour I was able to get to the win10 logon screen, login to a black screen, briefly see some adobe update screen, saw my screensaver appear, was able to activate the ctrl+alt+del display, selected task manager which took about 20min to load, a message about the page file configuration appeared, I was taken to the virtual memory options window and once task manager started I was able to see that the Windows Font Cache Service and Windows Error Reporting service were taking up a relatively high amount of system resources (2 of the corrupted files appeared to be related to these services). The system then sat like this for another couple of hours but didn't appear to make any more progress. I tried to logoff and enter the RE but it was responding too slowly so I just held the power button down.


I then tried to fix the remaining corrupted files by using as a DISM source, a Windows installer of the same Win10 version downloaded from UUP Dump, but after trying a few variations of the command it was unable to find the source files. When I previously restored the health of the win11 image, I had very little success using .wim files as sources and ended up resorting to installing the same version of win11 on a separate partition and then using it as a source. Surely there's a better way than that, so I was wondering if you could tell me what I'm doing wrong?



A summary of the file corruption repair process is below.


Windows 10 version: 10.0.19045.2965


The command syntax I used to repair the image.

  • dism  /image:f:\ /Cleanup-Image /Restorehealth /source:wim:g:\sources\install.wim:1 (I then tried: dism  /image:f:\ /Cleanup-Image /Restorehealth /source:g:\sources\install.wim /limitaccess)

  • f:\ is the win10 image.
  • g:\ was the drive letter given to the installer after double clicking on its ISO file. The wim file details are below.
    • Only one index, Index: 1 with the below details:
      • Index : 1
      • Name : Windows 10 Pro
      • Description : Windows 10 Pro
      • Size : 19,425,715,752 bytes
      • WIM Bootable : No
      • Architecture : x64
      • Hal : <undefined>
      • Version : 10.0.19045
      • ServicePack Build : 2965
      • ServicePack Level : 0
      • Edition : Professional
      • Installation : Client
      • ProductType : WinNT
      • ProductSuite : Terminal Server
      • System Root : WINDOWS
      • Directories : 32851
      • Files : 121637
      • Created : 31/03/2025 - 1:01:33 PM
      • Modified : 31/03/2025 - 1:08:41 PM
      • Languages :
                en-US (Default)


Files DISM was unable to repair:

  • amd64_microsoft-windows-errorreportingconsole_31bf3856ad364e35_10.0.19041.2546_none_cab0968ad830fc10\werconcpl.dll
  • amd64_microsoft-windows-magnify_31bf3856ad364e35_10.0.19041.1566_none_e2d33b2e4df989bf\Magnify.exe
  • amd64_microsoft-system-user-component_31bf3856ad364e35_10.0.19041.1741_none_d9c7f44bf0037320\UserMgrProxy.dll
  • amd64_microsoft-windows-settingsynchost_31bf3856ad364e35_10.0.19041.2193_none_f4b71718d84fd066\SettingSyncHost.exe
  • amd64_microsoft-windows-b..core-fonts-jpn-boot_31bf3856ad364e35_10.0.19041.1_none_3f0d37efc90f3433\meiryo_boot.ttf
  • amd64_microsoft-windows-clipboard-userservice_31bf3856ad364e35_10.0.19041.1503_none_6445ca7b1f9ae25e\CBDHSvc.dll
  • amd64_microsoft-windows-rasbase-rascustom_31bf3856ad364e35_10.0.19041.2193_none_6df16fe771dcec8c\rascustom.dll
  • x86_microsoft-windows-d..gement-winproviders_31bf3856ad364e35_10.0.19041.1741_none_cfbd5351a1e9dda0\f\OSProvider.dll

Files SFC was able to repair:

  • Wininit.exe
  • Bootmgr.exe.mui
  • mscormmc.dll

File SFC was unable to repair:

  • UserMgrProxy.dll
  • meiryo_boot.ttf
  • CBDHSvc.dll
  • Werconcpl.dll
  • Magnify.exe
  • Rascustom.dll
  • SettingSyncHost.exe


And also why not, the log files are attached too.


Back
Top