{"id":14131,"date":"2020-04-17T00:52:25","date_gmt":"2020-04-16T22:52:25","guid":{"rendered":"http:\/\/159.69.82.204\/win\/?p=14131"},"modified":"2020-04-17T08:40:40","modified_gmt":"2020-04-17T06:40:40","slug":"scep-mse-defender-broken-signatureupdate-kills-microsoft-antivirus-04-16-2020","status":"publish","type":"post","link":"https:\/\/borncity.com\/win\/2020\/04\/17\/scep-mse-defender-broken-signatureupdate-kills-microsoft-antivirus-04-16-2020\/","title":{"rendered":"SCEP\/MSE\/Defender: Broken Signatureupdate kills Microsoft Antivirus (04\/16\/2020)"},"content":{"rendered":"

[German<\/a>]An update, which may contain a broken signature file, has bricked all Microsoft virus scanners (Windows Defender, Microsoft Security Essential, and System Center Endpoint Protection (SCEP)) since April 16, 2020. The service for performing the virus scan simply crashes. A new signature file with a fix has been released.<\/p>\n

<\/p>\n

All Microsoft Antivirus scan engines bricked<\/h2>\n

\"\"The problem described one year ago in the blog post SCEP\/MSE\/Defender failed worldwide for hours due to a bad signatur file v1.289.1521.0 (03\/19\/2019)<\/a>,\u00a0 that a signature update bricked all Microsoft virus scanners, is back since April 16, 2020. I've been contacted an April 16, 2020 at 09:17 a.m. (CET) by German blog reader Michael, reporting issues with System Center Endpoint Protection (SCEP):<\/p>\n

Good morning.
\nMS has just distributed (08:39 in our case) updates for SCEP.
\nHere is an update : KB2461484 (Version 1.313.1638.0)
\nAs soon as a scan of any action is executed the Endpoint Protection crashes.<\/p><\/blockquote>\n

At that time I couldn't find other hits searching the Internet. Shortly after, Michael told me, that he has 400 systems with SCEP, that was affected. Later I received two comments to my blog post SCEP\/MSE\/Defender failed worldwide for hours due to a bad signatur file v1.289.1521.0 (03\/19\/2019)<\/a>, reporting the same issues for Windows Server 2012 R2 and Windows 7.<\/p>\n

Windows Defender and MSE also affected<\/h3>\n

At the same time I received a similar comment<\/a> from German blog reader Dekre, reporting, that Windows Defender stalls under Windows 10 Version 1909. Dekre reportet the following versions that causes issues:<\/p>\n

Antimalware version: 4.18.2003.8
\nModule: 1.1.6900.4
\nAV-Version: 1.313.1666.0
\nAntispyware-Version 1.313.1666.0<\/p>\n

Dekre pointet also to the German Microsoft Answers forum with this thread<\/a> dealing with the same effect. A user wrote:<\/p>\n

Windows Defender Antivirus does not start<\/p>\n

Hello, when I start my PC, the message always comes: \"The virus protection is disabled. Tap or click here to turn on Windows Defender Antivirus.\"<\/p>\n

When I click on it, it says: \"Page not available. Your administrator has restricted access to some areas of this app. The resource you're trying to access is unavailable. Contact the helpdesk for more information:\"<\/p><\/blockquote>\n

It is specified that the Security Intelligence Update for Windows Defender Antivirus – KB2267602 (version 1.313.1594.0) contains the error 0x80070643.<\/p>\n

\"Defender-Dienst<\/p>\n

Within this comment<\/a> another German blog reader reported issues with a stalling Defender service (see the German screenshot above). Other readers has contacted my via e-mail reporting the same, and the editors of German IT site heise has send me similar reader feedback.<\/p>\n

I just checked the Microsoft Security Essentials (MSE) on my Windows 7. The MSE reported that the last scan was a long time ago. When I started a quick scan, everything looked fine. But a short time later I got the following message that the service was stopped.<\/p>\n

\"Microsoft<\/p>\n

And next to the notification area of the taskbar the following toast notification of the MSE was displayed.<\/p>\n

<\/p>\n

The virus protection of the Microsoft Security Essentials (MSE) are therefore also completely paralysed. In the meantime, I have also read such a message at askwoody.com<\/a>.<\/p>\n

A Fix for the issue<\/h2>\n

The reason for the scan engine crashes is a bug that takes effect when a file has two dots before the file name extension (e.g. Test..exe, see also this reddit.com thread<\/a>). Lawrence Abrams did an analysis at Bleeping Computer in this article<\/a>. My German MVP colleague Ingo B\u00f6ttcher has written this forum post<\/a> in Microsoft Answers:<\/p>\n

The problem was fixed with the signature update 1.313.1687.0. Via Windows Update or the update search of Defender itself this signature version is distributed since tonight.<\/p><\/blockquote>\n

You can manually check for updates. In Windows 10, open the Windows Security<\/em> window, go to Virus & threat protection<\/em> and select the Check for Updates <\/em>hyperlink under Virus & Threat Protection Updates<\/em>. Then the new signature file should be installed by update. For MSE, you should have Windows Update check for updates. After a long search I was offered update KB2310138 with the above signature. After installing this update the error in the MSE seems to be fixed.<\/p>\n

Addendum: <\/strong>On April 17, 2020, Microsoft published another signature update<\/a> to version 1.313.1721.0. My editor from news magazine heise told me that everything is working again on her Windows 10 computer. Interesting observation from her was that the above approach via the Security Center did not work for her because the hyperlink Check for Updates<\/em> was missing. The reason might be that the threat protection service could not be restarted on her computer. She then manually triggered the Windows Update search, which resulted in the signature update. Even without a subsequent restart, the threat protection service was then up and running again.<\/p>\n","protected":false},"excerpt":{"rendered":"

[German]An update, which may contain a broken signature file, has bricked all Microsoft virus scanners (Windows Defender, Microsoft Security Essential, and System Center Endpoint Protection (SCEP)) since April 16, 2020. The service for performing the virus scan simply crashes. A … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[463,580,2],"tags":[646,773,47,2393,194],"class_list":["post-14131","post","type-post","status-publish","format-standard","hentry","category-issue","category-security","category-windows","tag-antivirus","tag-defender","tag-issue","tag-scep","tag-windows"],"_links":{"self":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/14131","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/comments?post=14131"}],"version-history":[{"count":0,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/posts\/14131\/revisions"}],"wp:attachment":[{"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/media?parent=14131"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/categories?post=14131"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/borncity.com\/win\/wp-json\/wp\/v2\/tags?post=14131"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}