Bad Updates

Status
Not open for further replies.
A

avastalicious

New Member
Thread author
Verified
Jan 30, 2013
75
0
8
36
So I used Windows Defender on Windows 8 for a while. I liked the experience with it until today.

Today a new definition update came, version 1.145.1429.0. I was surprised to find Windows Defender with a big red interface, stating that it's services are off and I need to restart them.
I restart the services, try to run a quick scan and after 20 seconds the Windows Defender services crash again.

Next I run the "mpcmdrun -removedefinitions" command in command prompt and revert the definitions to 1.145.1385.0. Quick Scan works now and the program is stable.

When I update to 1.145.1429.0 Quick Scan crashes the services.
I just tought it was reliable until today. What if a normal user got infected because of these broken signatures? :s

I can reproduce the issue over and over again, by updating and then reverting to the last known good definitions.
 
Yeah, like they tested these updates:

http://news.softpedia.com/news/Windows-7-Update-Causes-Blue-Screen-of-Death-Some-Users-Report-334329.shtml


Anyone else having problems with 1.145.1429.0 definitions?
 
avastalicious said:
Yeah, like they tested these updates:

http://news.softpedia.com/news/Windows-7-Update-Causes-Blue-Screen-of-Death-Some-Users-Report-334329.shtml


Anyone else having problems with 1.145.1429.0 definitions?
Click to expand...

Yes exactly the same issue on my 3 pcs
 
You need to open a command prompt window by typing "command prompt" in the start screen.
Then right click it and choose "Run as administrator". Type these lines in the command prompt window and press enter after each one:
cd /d C:\Program Files\Windows Defender
then
mpcmdrun -removedefinitions

This is it, you should be reverted to 1.145.1385.0. This is for Windows 8, mind you. The directory name is different with Microsoft Security Essentials on Windows 7.
By the way, another update came, 1.145.1455.0. The issue is still present, 1.145.1385.0 being the only stable definition.
 
http://www.eightforums.com/system-security/21764-windows-defender-0x800106ba-error.html
http://www.overclock.net/t/1369292/windows-defender-problem-with-windows-8

These are from today, we're not alone. :)
Microsoft, wtf?
 
avastalicious said:
You need to open a command prompt window by typing "command prompt" in the start screen.
Then right click it and choose "Run as administrator". Type these lines in the command prompt window and press enter after each one:
cd /d C:\Program Files\Windows Defender
then
mpcmdrun -removedefinitions

This is it, you should be reverted to 1.145.1385.0. This is for Windows 8, mind you. The directory name is different with Microsoft Security Essentials on Windows 7.
By the way, another update came, 1.145.1455.0. The issue is still present, 1.145.1385.0 being the only stable definition.
Click to expand...

Yes im using win 8, It worked a treat thanks
 
is there a command to roll back two definitions as i updated my laptop to 1.145.1455.0. in the hope it would resolve the problem
 
It is not resolved. I restarted a couple of times, even reverted definition to stock (mpcmdrun -removedefinitions -all) then updated to 1.145.1470.0.

Quick Scan still crashes Defender services.
 
avastalicious said:
It is not resolved. I restarted a couple of times, even reverted definition to stock (mpcmdrun -removedefinitions -all) then updated to 1.145.1470.0.

Quick Scan still crashes Defender services.
Click to expand...

I don't know what to tell you.
It is working fine on my laptop after updating and rebooting I was able to complete Quick Scan without errors.

Thanks.:D
 
@Littlebits
It's not just the quick scan, it will turn itself off randomly. Yesterday I didn't quick scan, I just launched Defender and found the services turned off, then I discovered that quick scan crashes it too.
 
still not fixed here, random shutdowns of defender and still wont complete a quick scan
 
I will post an update when it gets fixed. A MVP of Microsoft forums acknowledged the issue and has reported it to a contact in MSFT.
 
I didn't even experience it, as I disable WD daily and also on that day I switched to Avast. I missed the WD catastrophe.

KelvinW4 said:
Wow guys I thought it was just me, but oh well I went to comodo again :(
Click to expand...
 
Good news, everyone! (Futurama reference) :)

Users on Microsoft forums reported that 1.145.1493.0 fixed the issue. I confirm it, ran a couple of scans and it's stable now.

You need to download the definitions manually though, it seems the update in the Defender GUI downloads an older version at the moment.
Grab 'em here:
http://www.microsoft.com/security/portal/definitions/adl.aspx
 
Status
Not open for further replies.

You may also like...