DISM fix for recent Windows Update/WindowsDefender Platform corruption

Brink said:

It won't hurt anything to run SFC regularly if you like.

I just run them maybe weekly to make sure system files are perfect. Unless you run sfc scan you don't always know. Then I create a system restore point. Its just an extra safeguard really. My thinking might be totally wrong but Im hoping that if I pick a problem up early with sfc and fix it..it might stop the problem getting any worse where it gets to a point where it cant be fixed by sfc or dism. Im probably being over cautious

sportsfan148 said:

I just run them maybe weekly...

I run sfc /scannow nightly.

It's how I found this issue with the Defender Powershell hashes before Tuesday's 1903 .239 CU. and for me, the knowlege eliminated the CU as the culprit early on in this mystery. I also check nightly for Defender Platform changes.

sfc /scannow failing after this latest Defender Platfom update.

Running multiple Macrium backups every week, it's just common sense to know as early as possile when any corruption occurs, so when I do need to restore an image, I can be confident that I'm not bringing a hidden corruption problem along with it.

After using DISM to fix the recent Windows Defender Platform corruption found when running an sfc scan. Tonight Windows Update has installed the latest version of the Windows Antivirus Defender Antimalware Platform KB405263 version 4.18.1907.4 and to check if it was still OK... I ran SFC/ Scannow again. Unbelievably the corruption is back! I now don't have a clue whether to leave it alone or fix it again

Farvatten said:

I run sfc /scannow nightly.

It's how I found this issue with the Defender Powershell hashes before Tuesday's 1903 .239 CU. and for me, the knowlege eliminated the CU as the culprit early on in this mystery. I also check nightly for Defender Platform changes.

sfc /scannow failing after this latest Defender Platfom update.

Running multiple Macrium backups every week, it's just common sense to know as early as possile when any corruption occurs, so when I do need to restore an image, I can be confident that I'm not bringing a hidden corruption problem along with it.

Has Windows Update installed the latest Windows Defender Antimalware update on your PC yet?
Its just been installed on my PC about an hour ago. I fixed everything with DISM a few days ago. With the latest update the SFC corruption is back again!

f14tomcat said:

Still have this. Your other thread (now gone), showed .1907?

My message was merged into this thread. After the update the latest Antimalware Client Version is 4.18.1907.4. This new windows update has corrupted the sfc scan again

sportsfan148 said:

Has Windows Update installed the latest Windows Defender Antimalware update on your PC yet?

I'm also still on 4.18.1906.3-0

But thanks for the heads up!

Farvatten said:

I'm also still on 4.18.1906.3-0

But thanks for the heads up!

I wish I was!! lol
Trying to decide now whether to fix it again or just leave well alone this time. The only trouble is even if you leave well alone. It means not running an sfc scan again. So If there are any other issues with system files you aren't going to know and if you run sfc scannow again ..its gonna get fixed again anyway lol