Windows 10: Unable to perform DISM /RestoreHealth remotely

Hi Team,I am experiencing an issue when trying to repair Windows Component using DISM /RestoreHealth remotely using Source as a SharedLocation :"dism /online /cleanup-image /Restorehealth /Source:\\ServerName /LimitAccess" When I run this command locally on machine in CMD with Admin - it works absolutely fine. However, If I push the same command as a package via SCCM, it doesn't work, it throws below error. Error: 0x800f081f The source files could not be found. Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on spec

:)

 

DISM command /RestoreHealth unable to find source files

I am unable to perform SFC Scan or DISM Restore Health Successfully.

Windows 10 Pro Version 21H1 Build 19043.1083.

• sfc /scannow finds corruption its unable to fix.
  
• DISM /Online /Cleanup-Image /CheckHealth
  
  • Results in "The component store is repairable
    
• DISM /Online /Cleanup-Image /ScanHealth
  
  • Results in "The component store is repairable"
    
• DISM /Online /Cleanup-Image /RestoreHealth
  
  • Results in "The Source files could not be found"
    

I've downloaded what I believe to be the correct .iso file for the version of Windows I am running/needing. See below:





Mounting the .iso file to F: and pointing DISM to use its install.wim file is also failing.

• DISM /Online /Cleanup-Image /RestoreHealth /Source:F:\Sources\install.wim
  
• Results in "The source files could not be found".
  

Could anyone help me decipher the log files?

Log File of DISM command without source specified:
Error

Log File of DISM command with source specified:

Error

 

How to get damn DISM to work?

Yes, I have the image mounted, the same bloody image I've used to install the OS I'm just using. This is absurd. I've tried this:

Dism /Online /Cleanup-Image /RestoreHealth /Source:E:\x64\sources\install.esd
Dism /Online /Cleanup-Image /RestoreHealth /Source:E:\x64\sources\install.esd:1
Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:E:\x64\sources\install.esd
Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:E:\x64\sources\install.esd /limitaccess
Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:E:\x64\sources\install.esd:1
Dism /Online /Cleanup-Image /RestoreHealth /Source:esd:E:\x64\sources\install.esd:1 /limitaccess

None of this crap works even though entire freaking internet is saying that this is the way to do it. Some even mention using quotas for the path which makes no difference (It doesn't need it anyway since there aren't any spaces anyway.

I just can't understand how can OS integrity check tool feature be dumber as years pass by instead of being smarter and more useful.

EDIT:
Redownloading 4 gigs of stupid image because the one I have apparently isn't good enough. *sigh*

 

Error DISM restorehealth


twp things..

Executing command line: Dism /Online /Cleanup-Image /RestoreHealth /Source:"D:\Users\Hali\Downloads\IMAGE_HEALTH\IMAGE_HEALTH_SXS\Temp\Mount\windows\winsxs" /LimitAccess

Place the "Image_health" folder on C - you are running the command 9 folders deep...
Place Image_health-sxs.cmd inside "image_health" folder
Image health sxs cmd was and is only a TEST cmd
Image-health is the normal cmd...

[removed]

"C:\Windows\Logs\CBS\CBS.log" post the CBS.log

Also dism /scanhealth gives a better file report in the dism.log

Your damaged files appear to be that from a windows update, as windows update files are not on setup media..

step 1 delete current dism and cbs log files
step 2 run Image_Health.cmd - option 1 = scanhealth
step 3 run Image health - option 2 = restorehealth
step 4 run image health - option 3 = restorehealth /source
step 5 post dism.log and cbs.log (note: you can post logs as .txt > cbs.txt dism.txt)