Reading over the Windows news this morning, I learned from WindowsLatest that some users are reporting issues when trying to run the DISM /cleanup-image commands on their brand-new 2004 upgrades. I’ve got 5 machines running that release here, but am unable to replicate those difficulties on any of my 2004 PCs. Thus I can only repeat the advice included in their story entitled Windows 10 major update is causing issues with DISM tool. Here’s the problem description and the related repair prescription they provide, quoted verbatim:
Windows 10 version 2004 appears to break the DISM tool and we’ve been able to verify issues with the command-line based program on our device. In May 2020 Update, DISM command tool might report incorrect corruption status. For example, you might receive a report from the DISM tool that corruption is still present even when it has been repaired.
To fix the issues with DISM, you can run the same command multiple times until it renders the correct status. You can also verify that DISM has fixed issues with Windows 10 by using /ScanHealth command.
If I understand what WindowsLatest is saying, this means keep running the restorehealth option on DISM until the output for the scanhealth or checkhealth options read No component store corruption detected. The operation completed successfully. Here’s an extended illustration (warning: this whole sequence will take some time to complete; on my older, slower Lenovo T520 laptop, it took over 5 minutes, even with no errors detected or reported):
Syntax for the potentially faulty DISM commands is shown (but I can’t reproduce the errors that WindowsLatest reports).
[Click image for full-sized view.]
According to the same story, Microsoft is aware of the issue and plans to address it in the upcoming Patch Tuesday release (June 9, if I’m figuring dates correctly). We’ll just have to see how widespread the issue may be in the meantime. But if you find errors popping up with DISM, you can try repeating the commands an additional two or three times to see if that fixes things. If not, you’ll just have to wait for the upcoming update — and hope it fixes the issue(s).
Author: Ed Tittel
Ed Tittel is a 30-plus-year computer industry veteran. He’s a Princeton and multiple University of Texas graduate who’s worked in IT since 1981 when he started his first programming job. Over the past three decades he’s also worked as a manager, technical evangelist, consultant, trainer, and an expert witness. See his professional bio for all the details.