Running DISM Command Still shows Nothing fixed after repair in Windows 10, Version 2004? [ Here is why you don't need to worry!]

DISM command not working or does your Windows 10, 2004 both client and server edition shows corrupted files even after running DISM DISM.exe /Online /Cleanup-image /Restorehealth ? then i hope this guide might be helpful for you...

                            Its been so long, since i wrote a post about Windows 10 (if you are a regular reader of our site, then you might even say its been so long, since you actually wrote a post buddy!, got you as well😁😁 ) here is a post i decided to write it because i guess most of you might have already upgraded your Windows 10,Version 1909 to Version 2004 and Might search for a solution for one of the most serious issue which we doesn't need to worry about when occurs. 

If you haven't already upgraded, then its a good news for you, because users who installed this Windows 10, version 2004 are facing a couple of issues, one of them is their DISM command which was believed to repair your PC has actually being corrupt!.

What is the exact issue ?

If you are a intermediate user or advanced user then you might have well known this command " DISM.exe /Online /Cleanup-image /Restorehealth" and  DISM.exe /Online /Cleanup-image /ScanHealth

this command which will fix your corrupted files, will now show your files are corrupted even after fixing the files in background!

Which means you won't know whether the file is actually corrupted or just got fixed :( 

So, what is the solution? why i don't need to worry?

Microsoft says, this is a known issue and they are actually working on a possible fix and we can expect a fix in the next one or two weeks.. until then if your PC is having problems, then Microsoft asks you to do one small thing, run the same command again! I'm not kidding, that was the actual temporary fix that was suggested by Microsoft.

Here is What Microsoft Says from the Official site...

DISM might incorrectly report corruption is still present after repair

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. This can occur even when it has been repaired. An example for using the /restorehealth command is: DISM.exe /Online /Cleanup-image /Restorehealth

Affected platforms:

Client: Windows 10, version 2004

Server: Windows Server, version 2004

 

Workaround: If you receive reports that there is still corruption, subsequent scans should indicate the true state of the corruption. You can verify that DISM has fixed it by rerunning the same command or by using the /ScanHealth command. An example using the /ScanHealth command is: DISM.exe /Online /Cleanup-Image /ScanHealth

Just reran the command and find your true state of files whether it was fixed or not, until Microsoft fixes the issue..

Keep breaking:)