{"id":11196,"date":"2019-09-18T20:27:38","date_gmt":"2019-09-18T18:27:38","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=11196"},"modified":"2019-09-19T05:06:40","modified_gmt":"2019-09-19T03:06:40","slug":"scan-issues-with-msd-defender-antimalware-version-4-18-1908-7","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2019\/09\/18\/scan-issues-with-msd-defender-antimalware-version-4-18-1908-7\/","title":{"rendered":"Scan issues with MSD\/Defender Antimalware version 4.18.1908.7"},"content":{"rendered":"

[German<\/a>]A brief notification to Windows users (Windows 7, Windows 8.1 and Windows 10): Microsoft released this week the anti-malware version 4.18.1908.7, which is used in Windows Defender and Microsoft Security Essentials (MSE). The update of the anti-malware module should fix the issue when running the command sfc \/scannow in Windows 10. But the update has broken the ability to Microsoft's antivirus solution, to scan files. A quick scan is now really quick \u2013 it ends after seconds and scans just five to 64 files. Addendum:<\/strong> Microsoft has fixed the issue (partially) with an update – see inside.<\/p>\n

<\/p>\n

Some Background: The Defender Antimalware-Update<\/h2>\n

\"\"Earlier this week Microsoft released a silent update of the Defender antimalware engine to version 4.18.1908.7. The update had been expected by me for a long time to fix the issues in the system file check caused by July 2019 updates.<\/p>\n

I had reported in the mid of August in the article Microsoft fixes the Windows Defender sfc bug (August 2019)<\/a> that Microsoft intends to fix this issue by updating Windows Defender to version 4.18.1908. At the beginning of this week (6 weeks after Microsoft's announcement) Redmond started silently the distribution of anti-malware module version 4.18.1908.7. I had reported about this in the blog post Defender Antimalware Version 4.18.1908.7 released<\/a>. On September 16, 2019, Microsoft released update KB4052623<\/a> with anti-malware module version 4.18.1908.7 for all Windows versions in the Microsoft Update Catalog.<\/p>\n

MSE\/Defender scan finished after a few seconds<\/h2>\n

Microsoft has smuggled a friendly bug onto the system. If you use Windows Security in Windows 10 (or Microsoft Security Essentials in Windows 7 SP1) and start an antivirus scan, this process ends after a few seconds. Between five and 64 files (depending on your system) will be checked. I just tested it in Windows 10 using the following steps (the screenshots are obtained from my German Windows 10 V1903 system).<\/p>\n

1. Open the settings<\/em> page via start menu and go to Windows Security <\/em>category. Select the button Open Windows Security<\/em>.<\/p>\n

2. In Windows Security <\/em>window, select the Quick Scan button (see the next but one figure below) to initiate a scan of the system.<\/p>\n

\"Windows<\/p>\n

Windows Security will show the estimated time and progress of the scan (see screenshot above). It should be about 37 minutes for the quick scan on my test system.<\/p>\n

\"Bug<\/p>\n

But in the screenshot above you can see that this check is finished after a few seconds and a scan of five files. After updating the Defender antimalware engine to version 4.18.1908.7, Defender simply has a bug. The scan will stop on my system after five files have been scanned. Other users found out, that the scan ends after 14 up to 64 files scanned. The antimalware engine isn't able to provide a full scan of the files located on the system drive.<\/p>\n

After publishing the German edition of this article, I received confirmation<\/a> from my blog readers. Also here<\/a> is an independent post on a German forum, and German site deskmodder.de has an article<\/a> about that too. Since I've published the article, I got feedback<\/a>, that also Windows Server 2016, Windows 7 SP1<\/a> (with MSE) and Windows 8.1<\/a> is affected. At askwoody.com Woody Leonhard cited a Windows 7 SP1<\/a> user, commented on his forum as:<\/p>\n

I'm running Win 7 Pro, SP1, x64. I just updated (actually about an hour ago by now) the definitions in MS Security Essentials to 1.301.1608.0. I tried a Full Scan and it quit scanning after 29 files. Tried a Quick Scan and it also stopped after 29 files. It's not throwing any error codes and says that no threats were found after scanning 29 files. Gives me the big green checkmark. So, it looks just like a normal Full Scan except it only scans 29 files.<\/p>\n

I shut down the computer, restarted and attempted another definition update but was told I was already up to date. Tried another Full Scan with the same results as above.<\/p><\/blockquote>\n

At Microsoft Answers forum there are reports for Windows 7<\/a>, Windows 10 (V1809)<\/a>\u00a0 and here<\/a>. Also MVP colleague Lawrence Abrams from Bleeping Computer mentioned here<\/a> reports [reddit.com<\/a>, reddit.com<\/a>, reddit.com<\/a>, MS Answers<\/a>, MS Answers<\/a>, MS Answers<\/a>] dealing with the scan issues.<\/p>\n

My colleague at German site deskmodder.de, who also stumbled uppon this bug<\/a>, proposed a workaround. Instead of using a Quick Scan or a Full Scan, just use a user defined scan.<\/p>\n

\"Windows<\/p>\n

1. Select the hyperlink Scan options <\/em>in Windows Security <\/em>window and then check the option Custom scan <\/em>in the following page.<\/p>\n

2. Then scroll down, click the Check Now<\/em> button, and select a drive or folder from the dialog box that appears.<\/p>\n

Then Defender starts a scan of the selected file object (drive, folder) and checks all the files found there. There I immediately see the found files and the scan of the files runs very fast (several hundred per minute) – and not only 5 files in about 20 seconds.<\/p>\n

There is a fix – partially<\/h2>\n

On Twitter a user sent me the information that the issues has been fixed with the antivirus definition version 1.301.1684.0.<\/p>\n

\n

Fixed with Antivirus definition version 1.301.1684.0<\/p>\n

\u2014 Bruce Roberts (@BAR01474) September 18, 2019<\/a><\/p><\/blockquote>\n