New
#11
There's a brand new Cumulative. Installed it and just for kicks tried the SFC. No CBS.log corruption.
There's a brand new Cumulative. Installed it and just for kicks tried the SFC. No CBS.log corruption.
It's the Windows Defender platform version that matters, not the Windows version.
Denis
Last edited by Try3; 14 Aug 2019 at 05:43.
Ya I think it`s been fixed, no more corrupt files for me for like 3 weeks now, after using the command Cliff gave me.
It's been my experience and others that it's the Defender Platform updates not the CU's or the Definition updates that create this sfc /scannow hash corruption. The Defender platform version hasn't change for me in 3 weeks and currently remains at: 4.18.1907.4-0 from July 25th, that was the last time I had to fix the corruption. These Defender platform changes occur about every month. My money is on seeing the same corruption again when this gets pushed in the next week or so.
Ways to check your current Defender Antimalware Platform Version
sfc /scannow failing after this latest Defender Platfom update.
Last edited by Farvatten; 14 Aug 2019 at 17:46.