Windows 10: DISM fails when /Image: switch used ...

Good day all !Looks like a bug ?????I have a non working VMware VM virtual machine.I loaded Windows 21H2 on a 2nd VM and set it to see the 1st non-working VM hard drive as E:\I then runISM /Image:E:\ /Cleanup-Image /RestoreHealthI get:Error: 605An error occurred accessing the temporary folder C:\Users\user\AppData\Local\Temp\B4D55BBB-E86F-4B51-AF5F-C94DBDD0DC70. Ensure that the path to the temporary folder exists and that you have Read/Write permissions on the folder.... then I runISM /Image:E:\ /Cleanup-Image /RestoreHealthI get:Error: 605 An error occurred accessing

:)

 

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.

 

Source to use for DISM on Windows 10

This is not completely true. The suggestion is to download the Techbench version and use DISM to apply to install.wim directly. However, you can also use the version download from MCT except it will involve an extra step as follows:

1. Use the latest version of 7-Zip to extract the content of install.esd. For example: to a folder xxx on the desktop
2. From Admin command prompt:
   Dism /Online /Cleanup-Image /RestoreHealth /Source:%USERPROFILE%\Desktop\xxx\windows /LimitAccess

See screen shot, the contents of install.wim and install.esd are exactly the same.

 

Use DISM to Repair Windows 10 Image  


Even doing a clean install of Windows 10 gives corrupt files. Dism seems useless in Windows 10 or in it's current build. I've tried all suggested steps and doing a clean install as a last resort and still get Error: 0x800f081f.

So if the official ISO and upgrade from Microsoft is corrupted, how would someone fix this issue? The reason for me using Dism was because I was getting errors using Windows image backup and powershell giving errors, not sure if there's any other issues.