Microsoft has finally released Windows Defender Antimalware Version 4.18.1908.7. SFC /Scannow problem running since the middle of July this year is supposed to come to end after this update.
Even Redmondians has confirmed this bug in the Windows 10 versions and promised an improvement with the Defender Antimalware version 4.18.1908.7. The new update has now been installed via Windows Update or Microsoft Security Center.
Windows Defender Antimalware Version 4.18.1908.7
However, the update brings some improvements it has also known issues –
The update replaced the ps1 and xml files located at
% Windir%\System32\Windows PowerShell\v1.0\Modules\Defender
Known issues –
After the change, several downloads may get blocked when AppLocker is enabled.
- To settle this issue, open Group Policy, and then change the setting to Allow for the following path –
%OSDrive%\ProgramData\Microsoft\Windows Defender\Platform\*
One can only hope that the bug is fixed and SFC / Scannow now goes through without first having to work with the DISM commands, which then restored the older files.
But there is also a known bug that Microsoft still describes for 4.18.1901.7:
Some devices running Windows 10 will not start if Secure Boot is turned on after getting 4.18.1908.7. Microsoft is working on this problem and plans to find a solution in a future update. To work around this problem in the meantime, follow these steps –
- Start the device and access UEFI (BIOS).
- Disable Secure Boot and then restart.
- In the command prompt with administrative privilege, run the following command –
"%programdata%\Microsoft\Windows Defender\Platform\4.18.1901-7\MpCmdRun.exe" -revertplatformWait a minute and then do the following –
- Run “sc query windefend” (without quotes) to make sure the Windows Defender service is running.
- Ti the same way, run “sc qc windefend” to verify that the Windows Defender binary no longer points to version 4.18.1901.7.
- Restart the device, re-enter the BIOS, and then turn on Secure Boot.
Source – Release note.