Question
  • This thread is locked from future replies
203 views

MSE Update Failure Fail

Mr. Soda asked on

This title may sound like a typo or bad grammar but it's exactly what I'm experiencing. Occasionally, sometimes only once a week or so; my clean install of MSE will claim to have failed to update it's definitions. The download begins, moves towards installation, then right when it's about done I get the following error I'll attach below. However if I close this error & check for definition updates again it says all is fine & that they did in-fact update. It should also be noted that I've been experiencing this for a few weeks now, even prior to my clean install of the latest version as I was running a very slightly out-of-date one prior. I've run various other Malware scanners including Malwarebytes plus ESET & Bitdefender's online scanners which all report I'm clean. What should I do about this error or is it in Microsoft's hands?

$ Ø Ð Å
6 people had this question

Abuse history


The answered status icon Answer

See this thread:

https://answers.microsoft.com/en-us/protect/forum/protect_defender-protect_updating/windows-10-windows-defender-not-update-with-error/d992150e-656b-4263-a743-9cebaedfa02b

Although this thread addresses Windows Defender, the concept applies to Microsoft Security Essentials too. You don't have to worry about anything, if this does not start occurring every time you update.

Prashant Kumar

Please come back with the results.
Please mark replies as helpful/answer if they are.
3 people found this helpful

Abuse history


The answered status icon Answer

See this thread:

https://answers.microsoft.com/en-us/protect/forum/protect_defender-protect_updating/windows-10-windows-defender-not-update-with-error/d992150e-656b-4263-a743-9cebaedfa02b

Although this thread addresses Windows Defender, the concept applies to Microsoft Security Essentials too. You don't have to worry about anything, if this does not start occurring every time you update.

Prashant Kumar

Thanks, it hasn't so far so I'll just ignore it.

Mr. Soda,

We all are individual volunteers here, we are not employed by Microsoft. Another volunteer here have asked you bunch of questions about your system, he is experienced contributor here and know what he is asking. Feel free to answer them.

But, according to me, pain of answering all those questions is not worth taking. I analysed this error code myself in the thread I mentioned. I presented my analysis in that thread, with logs. To verify this yourself, go to C:\Windows\Temp. There you will find MpSigStub.log. Open it and scroll down to the bottom. You will find entries like these there:

----------------------------------------------------------------------------------
Command:    MpSigStub.exe /program WD /q
Running as administrator: yes
Start time: 03-01-2017 12:15 (version 1.1.13251.0)

=================================== ProductSearch ==================================

                 Windows Defender:
         Status: Active           
        Product: 4.10.14393.0     
         Engine: 1.1.13303.0      
     Signatures: 1.233.3739.0     
     NIS Engine: 2.1.12706.0      
 NIS Signatures: 116.72.0.0       

================================ PackageDiscovery ================================

Package files discovered:
C:\WINDOWS\Temp\79D79B24-BA26-4B8E-A112-89698B723365-Sigs\1.233.3739.0_TO_1.233.3766.0_MPASDLTA.VDM._P (?.?.?.?)
C:\WINDOWS\Temp\79D79B24-BA26-4B8E-A112-89698B723365-Sigs\1.233.3739.0_TO_1.233.3766.0_MPAVDLTA.VDM._P (?.?.?.?)

               AM BDD:     
       Engine: Not included
  AS base VDM: Not included
  AV base VDM: Not included
 AS delta VDM: 1.233.3766.0
 AV delta VDM: 1.233.3766.0

================================ PatchApplication ================================

Patched mpasdlta.vdm to 1.233.3766.0
Patched mpavdlta.vdm to 1.233.3766.0

================================= MpUpdateEngine =================================

Package files for the engine update:
C:\WINDOWS\Temp\79D79B24-BA26-4B8E-A112-89698B723365-Sigs\1.233.3739.0_TO_1.233.3766.0_MPASDLTA.VDM._P (?.?.?.?)
C:\WINDOWS\Temp\79D79B24-BA26-4B8E-A112-89698B723365-Sigs\1.233.3739.0_TO_1.233.3766.0_MPAVDLTA.VDM._P (?.?.?.?)
C:\WINDOWS\Temp\79D79B24-BA26-4B8E-A112-89698B723365-Sigs\mpasdlta.vdm (1.233.3766.0)
C:\WINDOWS\Temp\79D79B24-BA26-4B8E-A112-89698B723365-Sigs\mpavdlta.vdm (1.233.3766.0)

Updated from C:\WINDOWS\Temp\79D79B24-BA26-4B8E-A112-89698B723365-Sigs (0x0)

================================= ValidateUpdate =================================

MpSigStub successfully updated Windows Defender using the AM BDD package.

               Original:     Updated to: 
 AS delta VDM: 1.233.3739.0  1.233.3766.0
 AV delta VDM: 1.233.3739.0  1.233.3766.0

Deleted C:\WINDOWS\Temp\79D79B24-BA26-4B8E-A112-89698B723365-Sigs\1.233.3739.0_TO_1.233.3766.0_MPASDLTA.VDM._P
Deleted C:\WINDOWS\Temp\79D79B24-BA26-4B8E-A112-89698B723365-Sigs\1.233.3739.0_TO_1.233.3766.0_MPAVDLTA.VDM._P
End time: 03-01-2017 12:16
----------------------------------------------------------------------------------

Bolded are two lines that you need to focus on- the time and message of successful update. After scrolling down to bottom of the log, start scrolling up and note these two lines in recent entries. You will find MSE is indeed getting updated successfully frequently. This is clear indication that MSE is working and updating normally. If you find this log filled with errors then it is a sign of worry. But successful updates in regular intervals clearly show how well MSE is updating and there is no need to worry about it.

But, again, this is my own suggestion. If you are still not satisfied with my answer, feel free to unmark my reply and continue with answering those many questions, I won't interfere.

Prashant Kumar

Please come back with the results.
Please mark replies as helpful/answer if they are.
1 person found this helpful

Abuse history


progress