Windows 10: DISM, once over...

Windows version: 21H1 (OS Build 19043.1165) In this thread, the issue with DISM just recently had been resolved. The system had a BSOD today due to "MEMORY_MANAGEMENT, according to the BlueScreenView app. The actual BSOD screen stated something about critical system files, but it had not been recorded. Running the commands of "scf and dism..." gave some interesting results: The "/CheckHealth and /ScanHealth" disagree on the status of the component store; shouldn't they be the same? Running the the DISM command with "/RestoreHealth" option finishes normally. After reboot, checked the component store again with "/CheckHealth and /ScanHealth". The results were the same as in the image above. What is the reason for the difference and how can it be remediated? TIA...

:)

 

Programs not working

In post 26 there were steps listed to fix the operating system corruption.
Are you able to follow them?
In post 29 was the suggested dism repair command.

 

How to get damn DISM to work?

Thx guys, I'll compress this data into a blog post. For all the so called guides I've read, not a single one mentioned it has to be WIM file (some listed even ESD which clearly doesn't work) or that certain ISO images don't work with DISM.

After I've done DISM thingie, SFC also managed to repair stuff. Which is what I've needed here.

 

DISM - Parameter "Cleanup-Image" is not known (error 87)

Hello Eric,

To troubleshoot your concern, we suggest that you run DISM Restore Health command. Refer to the steps provided below:

• Open Command Prompt (Administrator).
• Type the following command:

DISM /Online /Cleanup-Image /RestoreHealth

3. Press Enter.

Let us know how it goes.

Thank you.