Solved Event ID: 3002

[Pawl]

MSSE is giving me an Event ID: 3002 on every reboot anyone know why?

Here's info...
Microsoft Antimalware Real-Time Protection feature has encountered an error and failed.
Feature: Behavior Monitoring
Error Code: 0x80004005
Error description: Unspecified error
Reason: The filter driver requires an up-to-date engine in order to function. You must install the latest definition updates in order to enable real-time protection.

I've cleared the C:\ProgramData\Microsoft\Microsoft Security Essentials\Support\MSSEOOBE.etl still get the event. :sarc:

 

[TOMMY2252]

an uninstall and reinstall should do the trick have you try that? i'm been using MSSE as-well never had any problem.

 

[Pawl]

Yeap tried that...no joy

 

[Borg 386]

I have had the following error with the file you're referring to:

Administrative Event Viewer Error - Session "Microsoft Security Essentials OOBE" stopped due to the following error: 0xC000000D

The fix for that is to delete the file(MSSEOOBE.etl), and the file is rebuilt during the next reboot.

Another option you could try is going to MS and downloading the full definitions pack. This might correct any corruptions

Install the latest Microsoft Security Essentials definition updates - Get the latest definitions - Microsoft Malware Protection Center

I also have this link for troubleshooting: MSE Solution Center

Microsoft Security Essentials Solution Center

I did have something like that happen a long while back, I d/led the full definitions, it kept giving me the error similar to yours for about a day or two, and then the errors stopped.

Here is another link for you to look at:

http://social.answers.microsoft.com...t/thread/22732d11-a83e-4106-b5de-24736b3cbf61

Another thought, make sure Windows Defender is disabled (MSE should disable it automatically). If it's not, you may have to disable it manually

 

[Pawl]

Yeap defender is disabled I did the def download thing as for the .etl file see 1st post.

 

[Phone Man]

I had the same problem back in March. After MS worked on my system for 4 hrs the fix was to remove the etl file that you have already done. It cleared for a week and then came back and I was unable to get it to work right so I dumped MSE and never looked back. Now use NIS2011.

Jim

 

[Pawl]

Norton is resource hog from my experience and misses to many virii.

 

[Borg 386]

MSE did it on my system for a little bit, and I notice someone else had the same experience I did quite some time back on the last link.

Their experience ended the same way as mine, it just started working correctly after 2 or 3 days.

When I was getting the problem you're having, I couldn't use the update button on MSE, the same thing would happen. I was however, able to update the defs using windows updater. After using that for d/l ing the defs, some time after that I clicked on the update button, and to my surprise, it was working again.

 

[Phone Man]

Norton is resource hog from my experience and misses to many virii.

Since 2009 Norton has been great. Low resource usage and rated near the top. They saw the light and got it going.

Jim

 

[Jacee]

Go here and click on 'validate your Windows Software'
Know The Facts

This may help with getting automatic definition/updates.

 

[Pawl]

Got it solved here's what I did...
set windows update to recieve updates for windows and other products it updated MSSE then deleted the etl file then ran MSSE update and rebooted.
Seems to have fixed it as I rebooted 3-4 times and no more events.
Thanks for everyones help...I guess everyones tips all rolled into one gave me the help.

 

[Jacee]

Thanks for letting us know!

 

[Borg 386]

Glad to hear it's sorted. Now that you mention it, I believe that is exactly what happened to me. After getting the defs from the MS Updater, it corrected itself and functioned normally.