Microsoft mitigates Windows 10 2004 known issue impacting DISM
by Sergiu Gatlan
Microsoft acknowledged and mitigated a new Windows 10 known issue affecting the Deployment Image Servicing and Management (DISM) tool used to service Windows images prior to deployment.
DISM can be used to prepare images in the Windows image (.wim) or a virtual hard disk (.vhd or .vhdx) formats for Windows PE, Windows Recovery Environment (Windows RE), and Windows Setup.
The issue is present on both client (Windows 10, version 2004) and server (Windows Server, version 2004) platforms, and it leads to DISM inaccurately reporting that images are corrupted even after they are successfully repaired.
Workaround available
"After using the Deployment Image Servicing and Management (DISM.exe) command /restorehealth to detect and correct system corruption, you might receive a report from the tool that corruption is still present," the issue's Windows 10 health dashboard's entry says.
As Microsoft further explains this can happen even when the scanned Windows image has been repaired using the /RestoreHealth command:
DISM.exe /Online /Cleanup-image /Restorehealth
Redmond says that subsequent scans of apparently corrupted Windows images using DISM will show the true state of the corruption.
To make sure that DISM has indeed fixed them, you can either rerun your previous command or use the /ScanHealth command like this:
DISM.exe /Online /Cleanup-Image /ScanHealth
The company says that a resolution for this DISM known issue is in development, with a solution to be released during mid-June.
New compatibility hold
Microsoft today has also added an additional compatibility hold on top of the nine Windows 10 May 2020 Update safeguard holds applied the day Windows 10 2004 started publicly rolling out.
This new upgrade block prevents Windows 10 devices with old drivers and Memory Integrity enabled from installing the Windows 10 May 2020 Update until the display drivers on those systems are updated.
Microsoft recommends users not to attempt to manually update via the Update now button or the Media Creation Tool until the issues behind currently applied safeguard holds are resolved.