Cumulative Update KB4507453 Windows 10 v1903 build 18362.239 - July 9 Win Update

Ztruker · 14 Jul 2019

Try3 said:

If your Windows defender, Settings, About shows Antimalware client version 4.18.1906.3 or greater then you have avoided the SFC problem.

Where do I find Windows defender, Settings, About?

Try3 · 14 Jul 2019

Rich,

Open your Windows defender window

Cumulative Update KB4507453 Windows 10 v1903 build 18362.239 - July 9-wd-ui.png

Click on Settings

Cumulative Update KB4507453 Windows 10 v1903 build 18362.239 - July 9-wd-settings.png

Click on About

Cumulative Update KB4507453 Windows 10 v1903 build 18362.239 - July 9-wd-settings-about.png

Denis

Farvatten · 14 Jul 2019

Ztruker said:

Where do I find Windows defender, Settings, About?

Also worth noting, whenever there's a Window Defender Antimalware client update there's a new version platform folder created under:

C:/ProgramData/Microsoft/Windows Defender/Platform/

It seems to hold on to the last two versions and this helps to see the folder dates of when the installs have taken place. It's how I was alerted to this change to 4.18.1906.3-0 the morning of 07/09

Cumulative Update KB4507453 Windows 10 v1903 build 18362.239 - July 9-windowsdefenderplatformfolders.jpg

Ztruker · 14 Jul 2019

Thanks Denis, I couldn't find Settings

All set now.

Farvatten, looks like I got the update on 7/8/2019 which lines up with this:

Cumulative Update KB4507453 Windows 10 v1903 build 18362.239 - July 9-image.png

Ztruker · 14 Jul 2019

Just ran DISM and SFC, all clean and green:

Code:

C:\Users\ztruk>dismandsfc
07/14/2019
03:03 PM
Dism /Online /Cleanup-Image /StartComponentCleanup

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.239

[===========                20.0%                          ]
The operation completed successfully.
...
07/14/2019
03:03 PM
Dism /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1

Image Version: 10.0.18362.239

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
...
07/14/2019
03:04 PM
SFC /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.
07/14/2019
03:38 PM

khanmein · 14 Jul 2019

sportsfan148 said:

Hi Ed, Ive just completed a full clean install, deleted all partitions etc. After setting things up, getting all windows updates and latest drivers etc. I ran sfc scannow and those errors related to Windows Defender are there for me too in the CBS logs file. Im undecided whether to fix it or leave well alone and wait and hope that Microsoft produces a fix for it

Same here. The solution is I ran DISM /Online /Cleanup-Image /RestoreHealth then reboot and ran sfc /scannow. If you didn't reboot, the error is still there.

sportsfan148 · 15 Jul 2019

Try3 said:

Ed,

If your Windows defender, Settings, About shows Antimalware client version 4.18.1906.3 or greater then you have avoided the SFC problem.

[For those of use who were afflicted, the problem appeared after updating from 4.18.1905.4 to 4.18.1906.3]

Denis

After completing my clean installation of Windows 10 1903, Windows Defender shows I have Antimalware client version 4.18.1906.3 and I have those errors after an SFC scan. The anti malware update was unavoidable. After the OS clean install Windows Update updated the Anti Malware along with all other available Windows Updates.

sportsfan148 · 15 Jul 2019

Farvatten said:

I hadn't though of that, avoiding the problem if your latest Defender Platform updated from 4.18.1905.4-0 to 4.18.1906.3-0 AFTER .this 239 CU

Ed, I first saw the Defender Powershell hash problem appear in my sfc /scannow checks the night BEFORE this .239 CU when my Defender Platform updated from 4.18.1905.4-0 to 4.18.1906.3-0.

sfc /scannow failing after this latest Defender Platfom update.

After a clean install two days ago both the Anti Malware client version and the 239 Cumulative Update were installed automatically by Windows Update. I have the errors when I run SFC scan. No other issues at all with the PC. Everything is running perfectly well. I am undecided whether to run DISM and SFC scan or just leave well alone to see if Microsoft fixes the issue through Windows Update.

CountMike · 15 Jul 2019

Darn it, you guys hexed me. One of first things I do after large updates is to run sfc /scannow and it came clean. after other adjustments and cleanup I run dism /online /cleanup-image /startcomponentcleanup /ResetBase
I checked again just before making full backup and sfc finished 100% but with errors and that dism comes to 20% and says it finished.
I tried several times and same happens.

sportsfan148 · 15 Jul 2019

CountMike said:

Darn it, you guys hexed me. One of first things I do after large updates is to run sfc /scannow and it came clean. after other adjustments and cleanup I run dism /online /cleanup-image /startcomponentcleanup /ResetBase
I checked again just before making full backup and sfc finished 100% but with errors and that dism comes to 20% and says it finished.
I tried several times and same happens.

Hi Mike, Im the same as you. I always run an sfc scan after Windows Updates. Thats why I immediately ran sfc scannow after the clean OS installation because quite a few windows updates were installed. . That's how I stumbled across the issue.
The only dism command Ive run in the past is dism /online /cleanup-image /restorehealth to fix sfc scan problems.
What is dism /online /cleanup-image /startcomponentcleanup /ResetBase? Im unfamiliar with that.
Is it a necessary command or is dism /online /cleanup-image /restorehealth sufficient?
I know dism also has the /checkhealth and /scanhealth switches...but in my experience they seem to be a bit of a waste of time. Ive always just used the /restorehealth switch straight away.
Any feedback/advice on the best way to use DISM would be much appreciated