scannow fails at 72%

Do the error mean Windows Defender isn't working right?

The computer had failed to upgrade from 1809 to 1903 to 1909 unless there were steps made to block upgrades.

Windows 10 version history - Wikipedia

https://docs.microsoft.com/en-us/win...0-version-1909
https://docs.microsoft.com/en-us/win...0-version-1903

The in place upgrade repair can be performed using any of these iso: 1909, 1903, 1809
The most up to date version is preferred.
If there is / are failures they can be troubleshooted.

Run setupdiag > post a share link into the thread using one drive, drop box, or google drive
https://docs.microsoft.com/en-us/win...rade/setupdiag

Ok, I will make the bootable USB drive per the instruction links. Once I do that how do I do the

in place upgrade repair

?

Thanks.

1) Download the Windows 10 iso to the desktop or to a flash drive (> or = 8 GB)

2) Open file explorer

3) Identify the iso

4) click on setup.exe and launch

5) Follow the text and images in this link:

Repair Install Windows 10 with an In-place Upgrade

Try3:

I don't have a WD icon in my systray. But if I go to "Control Panel\System and Security\Windows Defender Firewall" it shows Defender is On. Where can I find the version?

If I check Windows Update, I see the last update attempt for Quality was 1/16/20 which failed and it was:
"2020-01 Microsoft Edge Update for Windows 10 Version 1809 for x64-based Systems (KB4535547)"

Previous to that the last Quallty update was successful on 1/14/2020:
"2020-01 Cumulative Update for .NET Framework 3.5, 4.7.2 and 4.8 for Windows Version 1809 for x64 (KB4535101)"

The last Definition Update was:
2/10/2020, Successful: "Security Intelligence Update for Windows Defender Antivirus - KB2267602 (Version 1.309.663.0)"

All updates listed that failed were repeated and then were successful.

Also, Yes I was online when running the DISM commands.

The findings from scannow / restorehealth only indicate a mismatch.
They don't indicate malfunctioning Windows defender.

This is a known hash mismatch problem.

This is from a Microsoft link:


Cause

This is a known issue in Windows 10, version 1607 and later versions, and Windows Defender version 4.18.1906.3 and later versions up to version 4.8.1908.

The files for the Windows Defender PowerShell module that are located in %windir%\System32\WindowsPowerShell\v1.0\Modules\Defender ship as part of the Windows image. These files are catalog-signed. However, the manageability component of Windows Defender has a new out-of-band (OOB) update channel. This channel replaces the original files with updated versions that are signed by using a Microsoft certificate that the Windows operating system trusts. Because of this change, SFC flags the updated files as "Hashes for file member do not match."

Future releases of Windows will use the updated files in the Windows image. After this change is implemented, SFC will no longer flag the files.



The troubleshooting should fix the hash mismatch.

In case the in place upgrade fails it can be troubleshooted.

Ok, I ran the in place repair, and afterwards when I ran sfc /scannow it says it didn't find any integrity violations.

Here's the result up setupdiag: SetupDiagResults.log - Google Drive

I think I'm all set, Windows seems to be running much faster.

This is my WD info:
Antimalware Client Version: 4.18.2001.7
Engine Version: 1.1.16700.3
Antivirus Version: 1.309.747.0
Antispyware Version: 1.309.747.0

Thanks for your support.