DISM reports corruption, repair-windowsimage states HEALTHY

I have been working a several Windows 8.1 systems regarding issues. Some state out of memory (which it does not have), just black screen when sitting for a while. I have run dism /online /cleanup-image /restorehealth which consistently states it fixed "component store corruption was repaired" but never does. The powershell cousin to the command (repair-windowsimage) states "Image Health State" is HEALTHY. I know the commands have very minimal differences and believe they execute the same exe but runs just a bit different.

HELP!

January 30th, 2015 1:55am

consistently states it fixed "component store corruption was repaired" but never does.

What modules are being "repaired" then?  E.g. as seen in CBS.log.  You could run ProcMon to try to understand why DISM would think that a repair had worked but hadn't.  Sounds like a permissions issue or interference by a security product.  ProcMon might help expose either case.

 

HTH

Free Windows Admin Tool Kit Click here and download it now
January 31st, 2015 1:30am

Hi willrow,

Basically the Repair-WindowsImage command is under DISM Cmdlets so there is no difference.

I think you might have little misunderstand about dism /online /cleanup-image /restorehealth

This is a command which perform a whole system components repair but not a health checking.

The health checking command is dism /online /cleanup-image /checkhealth and I think it will give same result with PowerShell.

Regards

February 1st, 2015 8:21pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics