Reports of Windows Security (nee Microsoft Security Essentials) crashing after installing this morning’s definition updates

Topic

New Reply

This is quite rare, in my experience, but it looks like we got a bad Windows Defender definition update this morning. Poster Mike Reynard on the Windo
[See the full post at: Reports of Windows Security (nee Microsoft Security Essentials) crashing after installing this morning’s definition updates]

2 users thanked author for this post.

Elly, jburk07

Reply | Quote

Replies

My about screen looks identical (except dark theme). No issue.
Maybe there’s a simple setting that differs in the cases with issues.

Byte me!

1 user thanked author for this post.

woody

Reply | Quote

Could be. I’m hoping we get enough reports to be able to narrow it down.

Both of my production machines are working fine, with the same Antivirus version.

Reply | Quote

[Carl0s_H]

Can confirm I’ve seen this on two of our production servers running Windows Defender:

AntispywareSignatureVersion : 1.313.1638.0
AntivirusSignatureVersion : 1.313.1638.0
NISSignatureVersion : 1.313.1638.0

Windefend service stopped in both cases. Had to restart services twice on one of them, and only once on the other. Will update again if I see more/if the two already affected keep stopping.

Edit: Had to restart the services twice on both. Both seem to be stable at the moment.

• This reply was modified 4 years, 12 months ago by Carl0s_H. Reason: Situation changed

1 user thanked author for this post.

woody

Reply | Quote

Got the exact same version etc as Mike Reynard. No problems at all.

1 user thanked author for this post.

woody

Reply | Quote

AntispywareSignatureVersion : 1.313.1638.0
AntivirusSignatureVersion : 1.313.1638.0
NISSignatureVersion : 1.313.1638.0

windows 10 home and havent seen this,tried a few restarts just to check

1 user thanked author for this post.

woody

Reply | Quote

Same problem, same definition version.  Had to reboot. Win 1909.

1 user thanked author for this post.

woody

Reply | Quote

I didn’t get 1.313.1638.0. The one that installed today is 1.313.1666.0.

Reply | Quote

Bingo.

Looks like MS just released a new update.

1.313.1666.0  4/16/2020 11:46:11 AM

Not sure which time zone they’re using….

2 users thanked author for this post.

Elly, jburk07

Reply | Quote

I’m still waiting for yesterday’s version to be updated – and no, I’m not checking manually for an update in the light of this development! Thanks for the info Woody, and those responding.

1 user thanked author for this post.

woody

Reply | Quote

I didn’t observe it myself, but a colleague informed me about a crash he noticed on a Win2012R2 server.

System Center Endpoint Protection with:
Antimalware Client Version: 4.10.209.0
Engine Version: 1.1.16900.4
Antivirus definition: 1.313.1638.0
Antispyware definition: 1.313.1638.0

An error was logged in the Application log:

Faulting application name: MsMpEng.exe, version: 4.10.209.0, time stamp: 0x582a94a1
Faulting module name: mpengine.dll, version: 1.1.16900.4, time stamp: 0x5e70249a
Exception code: 0xc0000005
Fault offset: 0x00000000001d00cf
Faulting process id: 0xde8
Faulting application start time: 0x01d613c2a85bd437
Faulting application path: c:\Program Files\Microsoft Security Client\MsMpEng.exe
Faulting module path: C:\ProgramData\Microsoft\Microsoft Antimalware\Definition Updates\{1E974FAE-75D8-4963-B3FB-1FE387245A66}\mpengine.dll

2 users thanked author for this post.

satrow, woody

Reply | Quote

The update may have been pulled. I just manually checked for an update. See here:

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

1 user thanked author for this post.

woody

Reply | Quote

“Superseded” is probably a better term. MS releases new signature files several times a day.

I wonder if 1.313.1666.0 has the same bug(s)?

3 users thanked author for this post.

Elly, satrow, geekdom

Reply | Quote

Windows ran an auto scan about 10.33 GMT, no issues reported.

Checked security after seeing this thread – service had stopped. Service restart crashed so did system restart then ran a manual scan. No issues and service still running as I write.

Update list shows defender update 1.313.1638.0 was downloaded and installed before morning  scan, but I’m now also seeing 1.313.1666.0 installed at 13.31 i.e. immediately before latest scan.

1638 was the year of the Great Thunderstorm in Devon, England

1666 was the year of the Great Plague and the Great Fire of London !!!

Win10 22H2 Pro, MBAM Premium, Firefox, OpenOffice, Sumatra PDF.

2 users thanked author for this post.

Seff, woody

Reply | Quote

Just got a tweet from Lars Knudsen, who says the bug is still present in 1.313.1666.0

https://twitter.com/lars_tvis/status/1250772458304688129

3 users thanked author for this post.

jburk07, Carl0s_H, geekdom

Reply | Quote

Has anyone who has a problem filed a report with Microsoft?

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

Reply | Quote

[Grond]

Mine crashed about 1:30? AM CDT; I had manually updated to v1.313.1663? about 30 minutes prior. I’ve rebooted several times, no joy, haven’t tried the v1.313.1666 update yet.
Here’s a screengrab from just now. Hmm. Won’t let me attach the .jpg.

Windows 10 Pro x64 v1909 Desktop PC

• This reply was modified 4 years, 12 months ago by Grond.

Reply | Quote

My apologies for self-replying, but the edit timer ran out. My WinDefend service is stopped, will not restart, and the About info is as follows:

Antimalware Client Version: 4.18.2003.8
Engine Version: 0.0.0.0
Antivirus definition: 0.0.0.0
Antispyware definition: 0.0.0.0

I have MBAM Premium v4.1.0.56 as supplemental security to Defender. It is not “registered” with Win10.

Windows 10 Pro x64 v1909 Desktop PC

2 users thanked author for this post.

jburk07, woody

Reply | Quote

[Carl0s_H]

Carl0s_H wrote:

Can confirm I’ve seen this on two of our production servers running Windows Defender:

AntispywareSignatureVersion : 1.313.1638.0
AntivirusSignatureVersion : 1.313.1638.0
NISSignatureVersion : 1.313.1638.0

Windefend service stopped in both cases. Had to restart services twice on one of them, and only once on the other. Will update again if I see more/if the two already affected keep stopping.

Edit: Had to restart the services twice on both. Both seem to be stable at the moment.

• This reply was modified 4 years, 12 months ago by Carl0s_H. Reason: Situation changed

Update: We now have 6 servers reporting this issue. Our central update server has picked up definitions 1666.0, going to test and see if Lars’s tweet is true.

1 user thanked author for this post.

woody

Reply | Quote

[Carl0s_H]

Carl0s_H wrote:

Carl0s_H wrote:

Can confirm I’ve seen this on two of our production servers running Windows Defender:

AntispywareSignatureVersion : 1.313.1638.0
AntivirusSignatureVersion : 1.313.1638.0
NISSignatureVersion : 1.313.1638.0

Windefend service stopped in both cases. Had to restart services twice on one of them, and only once on the other. Will update again if I see more/if the two already affected keep stopping.

Edit: Had to restart the services twice on both. Both seem to be stable at the moment.

• This reply was modified 4 years, 12 months ago by Carl0s_H. Reason: Situation changed

Update: We now have 6 servers reporting this issue. Our central update server has picked up definitions 1666.0, going to test and see if Lars’s tweet is true.

Can confirm that we are still seeing this issue with definition version 1.313.1666.0. Application event log shows following error:

Faulting application name: MsMpEng.exe, version: 4.18.1911.3, time stamp: 0x2c9b5e9d
Faulting module name: mpengine.dll, version: 1.1.16900.4, time stamp: 0x5e70249a
Exception code: 0xc0000005
Fault offset: 0x00000000001d00cf
Faulting process id: 0xd38
Faulting application start time: 0x01d613f7e3bb86f8
Faulting application path: C:\ProgramData\Microsoft\Windows Defender\platform\4.18.1911.3-0\MsMpEng.exe
Faulting module path: C:\ProgramData\Microsoft\Windows Defender\Definition Updates\{95F4B139-ECBA-4749-B9FC-AF6C1C635CFA}\mpengine.dll
Report Id: 343ac0a7-18a9-434c-8077-56a20b2e9efe
Faulting package full name:
Faulting package-relative application ID:

For reference this is on Server 2016 LTSC (1607 Build 14393.0).

2 users thanked author for this post.

jburk07, woody

Reply | Quote

Windows 7 Pro,

Antimalware Client Version: 4.8.204.0
Engine Version: 1.1.16900.4
Antivirus definition: 1.313.1666.0
Antispyware definition: 1.313.1666.0
Network Inspection System Engine Version: 2.1.14600.4
Network Inspection System Definition Version: 119.0.0.0

I woke up and system showed the service stopped. I started it (took about a minute to start), started a quick scan, and it crashed in less than a 30 seconds. Tried to do an update, everything looked good, started a full scan, crashed in less than a 30 secons.

So I came here to Woody to check if there were any issues…sure enough, there are.

2 users thanked author for this post.

jburk07, woody

Reply | Quote

Win7 Pro

So far no issues with version 1.313.1666.0

Antimalware Client Version: 4.10.209.0
Engine Version: 1.1.16900.4
Antivirus definition: 1.313.1666.0
Antispyware definition: 1.313.1666.0
Network Inspection System Engine Version: 2.1.14600.4
Network Inspection System Definition Version: 119.0.0.0

=================

The  version 1.313.1638.0 was causing issues.

AntispywareSignatureVersion : 1.313.1638.0
AntivirusSignatureVersion : 1.313.1638.0
NISSignatureVersion : 1.313.1638.0

=================

Also, checked event viewer to find that antimalware was having an issue with a known good URL.

Microsoft Antimalware engine has been terminated due to an unexpected error.
Failure Type: Crash
Exception code: 0xc0000005
Resource: file:C:\Users\XXXXXXX\Favorites\100Lb. Gas Stainless Steel Smokehouse – The Sausage Maker, Inc..url

 

2 users thanked author for this post.

jburk07, woody

Reply | Quote

Nothing out of the ordinary on my desktop or NAS.  Systems nominal.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

2 users thanked author for this post.

jburk07, woody

Reply | Quote

Have you tried running a Full Scan? Lawrence Abrams could trigger the crash on two out of three PCs, using the latest version 1.313.1666.0.

1 user thanked author for this post.

TonyS

Reply | Quote

Worked fine until I tried running a full scan, it died. The Restart button did nothing.

Faulting application name: MsMpEng.exe, version: 4.18.2003.8, time stamp: 0x7be0fdee
Faulting module name: mpengine.dll, version: 1.1.16900.4, time stamp: 0x5e70249a
Exception code: 0xc0000005
Fault offset: 0x00000000001d00cf
Faulting process id: 0x1078
Faulting application start time: 0x01d612cff6343637
Faulting application path: C:\ProgramData\Microsoft\Windows Defender\platform\4.18.2003.8-0\MsMpEng.exe
Faulting module path: C:\ProgramData\Microsoft\Windows Defender\Definition Updates\{52FB5464-4DA2-473D-B213-2CC5356BD68D}\mpengine.dll
Report Id: 1fd93ea0-c80e-4db2-9e04-16377d26574d

Now I have 100’s of these errors showing up:

The Windows Defender Antivirus Service service terminated with the following error:
General access denied error.

If at first you don’t succeed, reboot!

 

2 users thanked author for this post.

woody, jburk07

Reply | Quote

Just looked at the 2019 server essentials server and defender stopped on it at 10:32 am.

Reply | Quote

Woody, I did a Quick Scan only and it worked fine with the latest version 1.313.1666.0.

2 users thanked author for this post.

woody, jburk07

Reply | Quote

FWIW:  Win8.1×64 KB2267602

version 1.313.1585.0 installed ok. 2.5 hours ago

version 1.313.1668.0 installed o.k. just now. latest version update gave me.

No problems with Windows Defender updates for last 4 years.

2 users thanked author for this post.

woody, jburk07

Reply | Quote

That’s why this is so odd. There must be something fundamentally wrong with the latest signature updates if they cause Defender to crash.

Reply | Quote

I’ve seen this once before on our server estate, mid January this year – literally all 188 2016 servers had bad definitions installed overnight and were showing as “service down” on our monitoring system. Had to manually roll back the definitions on each server, took me close to 6 hours. I’ve tried rolling back the definitions this time, but it hasn’t helped.

Reply | Quote

[HiFlyer]

Re: 224218

 

spoke too soon.  after 1668 installed quick scan wasgood.  full scan crashed.  had to manually restart win defender, then another ok quick scan.  Then another crashed full scan.  Restarted pc.  Started full scan which crashed after 30 minutes scanning (790,000 items)

Just installed 1687 ok.  Quick scan ran ok.

Just started full scan still running at 100,000 items checked (12 minutes)

• This reply was modified 4 years, 12 months ago by HiFlyer.

1 user thanked author for this post.

woody

Reply | Quote

Keep us posted…

Reply | Quote

re:  2242503

excelsior!  finally  Full Scan successful.

Reply | Quote

Same experience here, I just had to manually start Security Essentials on the first two machines I looked at this morning. The April 16th update that came in overnight seems to be the culprit

Reply | Quote

Win 7 Home Premium,   MSE,  no problem.

Reply | Quote

[TonyS]

Just done full scan with v.1666 – Yes it’s crashed, about to reboot.

 

Rebooted. Same v.1666 signatures. Service running. Smart scan finished ok, normal (?) service resumed (for the time being).

Win10 22H2 Pro, MBAM Premium, Firefox, OpenOffice, Sumatra PDF.

• This reply was modified 4 years, 12 months ago by TonyS.

1 user thanked author for this post.

jburk07

Reply | Quote

I let it update when it needs to and only do quick scans when it needs to as I don’t go trolling the Internet.  I just checked and my antivirus definition is:  1.313.1607.0   So it looks like it has not updated to the problematic version.  I’m not about to tell it to update; I’ll let MSFT figure this out.

Reply | Quote

agoldhammer wrote:

I let it update when it needs to and only do quick scans when it needs to as I don’t go trolling the Internet.  I just checked and my antivirus definition is:  1.313.1607.0   So it looks like it has not updated to the problematic version.  I’m not about to tell it to update; I’ll let MSFT figure this out.

Likewise, mine’s set to quick scan as standard. Looks like MS may have done half a job going from 1638 to 1666?

Win10 22H2 Pro, MBAM Premium, Firefox, OpenOffice, Sumatra PDF.

Reply | Quote

Just now received 1668 so evidently they are trying to pump out a fix. Haven’t attempted a full scan. This morning I got the 1666 but nothing scanned.

Don't take yourself so seriously, no one else does 🙂
All W10 Pro at 22H2,(2 Desktops, 1 Laptop).

1 user thanked author for this post.

TonyS

Reply | Quote

AntispywareSignatureVersion : 1.313.1666.0
AntivirusSignatureVersion : 1.313.1666.0

SmartScan crashed at about 8500 files.

Event Log for defender shows that all crashes happen when scanning .LNK or .URL files, like WildChild reported above.

When defender does not run, my PulseSecure vpn client rates the machine as unsafe and terminates the vpn connection.

Just wrote me a small “WindowsDefenderRestarter.exe” program to automatically restart the antivir service when it crashed. McGyver approach…

And just now updated to 1.313.1666.0, let’s see what happens…

Reply | Quote

There now seems to be a newer version 1.313.1668.0

2 users thanked author for this post.

woody, jburk07

Reply | Quote

[NetDef]

1.313.1668.0

. . . has just been released.

If the client did not do a scan, automatically or manual, they likely never noticed a problem during the two bad signature releases between yesterday and just now.

 

Edit:  Just completed (on three machines) a “fingers crossed test scan” using the 1668 update.  No crashes on all three.  YMMV.

 

~ Group "Weekend" ~

• This reply was modified 4 years, 12 months ago by NetDef.

3 users thanked author for this post.

Elly, woody, jburk07

Reply | Quote

Same here, just received 1668 too, and the bug is still here even after reboot.

After some investigation, I noticed that any attempt to scan a file with a filename ending with a point (ie : my_file_ends_with_a_point..avi) ends with a service crash.

2 users thanked author for this post.

woody, jburk07

Reply | Quote

Hi,

same here, on Windows 7, 64-bit, but MSE crashes also after the latest today’s update ( 1.313.1668.0).

The only pattern I was able to discern so far was me using the Executor launcher. I.e. if I start a program from Start menu, everything is OK. If I start it via Executor, MSE crashes. Also if I only invoke Executor and then ESC to close it (without running any program), MSE will crash.

 

Reply | Quote

I have 1687 (brand new?) installed, and fully up to date client 4.18.2003.8 on 1909 patched to March 2020. I first followed the Reddit post here: https://www.reddit.com/r/Windows10/comments/g29z46/windows_defender_now_longer_working_after/fnku3cq/, and found that the installed PeaZip had created a bunch of files (noted from event viewer) that had appended multiple dots to the filenames. I clean uninstalled PeaZip with RevoUninstaller, removing all the cruft, rebooted, ran Quick Scan, and it performed without issue.

Just ran another Quick Scan here while typing this, no issues. I cannot tell you with certainty whether it was the removal of the offending software filenames that contained multiple dots, or the new definitions file 1687 that fixed it for my system.

Reply | Quote

I ran a quick scan without difficulty, but I’ve been running quick scans without difficulty regardless of version.

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

Reply | Quote

I just now manually started (not restarted) the WinDefend service from Task Manager/Services, updated the definition files from “Virus & threat protection updates” inside Windows Security, and ran a Full Scan. Zero threats detected.

The update went to v1.313.1687.0, timestamped 11:04AM, and the About section reads:

Antimalware Client Version: 4.18.2003.8
Engine Version: 1.1.16900.4
Antivirus Version: 1.313.1687.0
Antispyware Version: 1.313.1687.0

Windows 10 Pro x64 v1909 Desktop PC

Reply | Quote

Grond wrote:

I just now manually started (not restarted) the WinDefend service from Task Manager/Services, updated the definition files from “Virus & threat protection updates” inside Windows Security

Pls see my problem and request for help further below.  Pls explain in detail what you did to get the definition Update button to appear in the Virus & threat protection screen.

Did you restart your computer?

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

[Karlston]

According to the Bleeping Computer article, the cause is the scanning of files with two periods in the name, eg start..exe, bones..ttf etc. Probably, multiple periods (more than one) is the cause.

So, those folks not having problems may simply not have any files with the double/multiple period in the name?

Hanlon's Razor: Never attribute to malice that which can be adequately explained by stupidity.

• This reply was modified 4 years, 12 months ago by Karlston.

1 user thanked author for this post.

woody

Reply | Quote

Quite possible. But I’m not sure that’s the only source of problems……

Reply | Quote

I think it was. The Defender log can be checked to locate such files:

Event Viewer, navigate to Applications and Services logs > Microsoft > Windows > Windows Defender > Operational.
Look there for error and you’ll find something like “crash exception code 0xc00000005 ” and it includes the name of the file with two dots. To resolve the issue, remove the extra dot or delete the file.
Windows 10’s Defender fails with threat service has stopped error

4 users thanked author for this post.

HiFlyer, Tex265, satrow, woody

Reply | Quote

Thanks b,

Followed your link, found I had 1 old website link in my Internet 11 Favorite file with a ..url

Deleted, started Defender in Services.  This allowed the Definitions Update button to reappear on the Virus and Threat protection screen and could then update to 1.313.1687.0

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

2 users thanked author for this post.

satrow, b

Reply | Quote

Looks like 1.313.1687.0 fixes the problem….

Note “313”not “303.”

2 users thanked author for this post.

NetDef, Carl0s_H

Reply | Quote

OK, I recently logged on computer and have the Windows Restart Now problem with a red X.

Windows 10 Pro v1909 had updated to 1.313.1666.0.

Showhide program shows I have 1.313.1687.0 waiting for next download (using Group Policy setting of 2)

Due to the red X, Virus and threat protection screen only shows a Restart Now button which does nothing.  The screen does not offer the manual definition download/update button.

How do I get past this?

Windows 10 Pro x64 v22H2 and Windows 7 Pro SP1 x64 (RIP)

Reply | Quote

Windows Update Manager might provide a means to download and install the latest virus definition:

https://github.com/DavidXanatos/wumgr

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

1 user thanked author for this post.

woody

Reply | Quote

Has there been any confirmation on what was wrong with earlier virus definitions and under what circumstances?

On permanent hiatus {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.1265 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1992 x64 i5-9400 RAM16GB HDD Firefox116.0b3 MicrosoftDefender

Reply | Quote

Choking on double-dot filenames, I believe: #2242546

Reply | Quote

The broken signature file affected not only Windows Defender. Microsoft Security Essentials (MSE) and also System Center Endpoint Protection (SCEP) has been bricked too. We have had a similar thing in March 2019 …

SCEP/MSE/Defender: Broken Signatureupdate kills Microsoft Antivirus (04/16/2020)

Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author

https://www.borncity.com/win/

1 user thanked author for this post.

Carl0s_H

Reply | Quote

Until a couple of hours ago I was running Windows Defender KB 226702, Version 1.313.1607.0 and all was well; thought I’d keep my head down. Then it tried to carry out an automatic scan and of course Win. Def. turned itself off – I had the dickens of a job turning it on again. It has since updated spontaneously to KB 226702, Version 1.313.1687.0 but I don’t feel inclined to attempt a scan in case it turns off my real-time protection again. I’m scanning with Malwarebytes Free on a regular basis and will continue to do so until M/S sorts this one out. Please let me know when the bug has gone for sure…………………….Many thanks.

Reply | Quote

woody wrote:

Right now, for those of us who don’t pay extra for Microsoft security, the politically correct names are “Windows Defender Security Center” for the suite of protection products and “Windows Defender Antivirus” for the antivirus component. But inside Windows, the product is known as “Windows Security” (see screenshot) and “Antivirus” is an engine in Windows Security.

Got that?

For the next few weeks. 👍

Next month, in Windows 10 Version 2004, Windows Defender is renamed to Microsoft Defender in at least three places within Windows Security. 🙄

Microsoft Renames Windows 10 Antivirus to Microsoft Defender
The change will become official in Windows 10 20H1
https://news.softpedia.com/news/microsoft-renames-windows-10-antivirus-to-microsoft-defender-526767.shtml

Microsoft renames Windows Defender on Windows 10
In Windows 10 May 2020 Update, Microsoft has quietly updated Windows Security app to replace mentions of Windows Defender with Microsoft Defender.

For example, the tech giant has renamed ‘Windows Defender Offline Scan’ to ‘Microsoft Defender Offline Scan. Even the other parts of Windows Security app has been updated to remove all mentions of ‘Windows Defender’.
…
In Protection update page, Microsoft has also replaced Windows Defender with Microsoft Defender.

In places like the Group Policy editor, Microsoft has inserted mentions of Microsoft Defender, Microsoft Defender Antivirus, Microsoft Defender Exploit Guard, etc.
https://www.windowslatest.com/2020/04/12/microsoft-renames-windows-defender-on-windows-10

Reply | Quote

@born writes:

The broken signature file affected not only Windows Defender. Microsoft Security Essentials (MSE) and also System Center Endpoint Protection (SCEP) has been bricked too. We have had a similar thing in March 2019 …

SCEP/MSE/Defender: Broken Signatureupdate kills Microsoft Antivirus (04/16/2020)

1 user thanked author for this post.

Carl0s_H

Reply | Quote

woody wrote:

Looks like 1.313.1687.0 fixes the problem….

Note “313”not “303.”

Yes, I can confirm this worked in our environment. Manually updated the group of failed servers yesterday evening, and they all quick/full scan successfully without killing the service.

2 users thanked author for this post.

The Surfing Pensioner, woody

Reply | Quote

Woody said “politically correct names are …”.  That moniker, politically correct, is one of the most overused & incorrectly applied terms out there.  In this case, it might be more correct to maybe use the term corporate correct name.

Reply | Quote

b wrote:

Windows Defender is renamed to Microsoft Defender in at least three places within Windows Security.

What about firewall?

Reply | Quote

carpintero wrote:

b wrote:

Windows Defender is renamed to Microsoft Defender in at least three places within Windows Security.

What about firewall?

“Microsoft Defender Firewall” when switching off/on under a network profile in Windows Security/Firewall & network protection, and in documentation:

Turn Microsoft Defender Firewall on or off
Applies to: Windows Defender, Windows 10

(But also still “Windows Defender Firewall” in the Start menu under Windows Administrative Tools.)

Reply | Quote

[carpintero]

Also, Woody posted “Office 365 becomes Microsoft 365”.

To those who saw “Being John Malkovich”, recall the restaurant menu, envision “Microsoft”.

• This reply was modified 4 years, 12 months ago by carpintero.
• This reply was modified 4 years, 12 months ago by carpintero.

1 user thanked author for this post.

Cybertooth

Reply | Quote

FWIW, early this morning after they booted, I ran Windows Update and then a full Windows Defender scan on two Win10H machines without any trouble.

Reply | Quote

I would have expected the double dot problem to be rare, but I’ve just scanned my system looking to see if I have any. It turns out that Microsoft Visual Studio creates hundreds of them. For eample “C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\Common7\IDE\ItemTemplates\Microsoft.VisualStudio.Community.Item..vstman”

How Microsofts testing could miss this in their testing (of either product) escapes me. Oh, wait. Microsoft and testing. Two words which should never be in the same sentence these days.

2 users thanked author for this post.

SueW, Cybertooth

Reply | Quote

Replying to myself because ‘edit’ isn’t working. Missed some words there. Visual Studio does create them, but the hundreds are in C:\Windows subdirectories, many in \WinSxS.

Reply | Quote