MSE OOBE Event Error - Fixed

Phone Man · 19 Mar 2010

For those that have upgraded MSE and have seen the following error on bootup in Event Viewer.

Session "Microsoft Security Essentials OOBE" stopped due to following error; 0xC000000D

here is the fix.

OK we have a fix. After MS worked on my PC for 4 hrs they got it fixed. Go to C:\ProgramData\Microsoft\Microsoft Security Essentials\Support and delete MSSEOOBE.etl and reboot. After reboot this file should be recreated and the error should be gone. I have found that when you delete MSE this folder remains and the files get updated when you run MSE. It looks like the one file was not updating properly and causing the failure. After it was working I did another test. I deleted MSE and also all the files in the Support directory. I then reinstalled MSE and everything is still fine. If you look at the error under Detail it will point to this file.

Jim

Phone Man · 27 Mar 2010

Well the error has returned. It worked great for a week then came back. Same fix will clear it but after a few boots it comes back. I have now dumped MSE and will wait for MS to produce a new version.

Jim

Dragonchaser · 25 Oct 2014

There is a thread here that has a fix.

1. First of all someone suggested to either rename the file EppOobe.etl (in C > ProgramData > Microsoft > Microsoft Security Client > Support) as EppOobe.etl.old, or delete it, and reboot, however, this did not work for me.

2. Then someone (grogramon) suggested:

i had similar problem...here's the solution that worked for me.
boot into safe mode if your system freezes after logging in (like mine was).
open a command line (win+r)
run 'services.msc' and hit enter (don't type the quotes)
scroll down to find 'program compatibility assistant service' (PcaSvc)
right-click and open the 'properties'
change the 'startup type' from 'automatic' to 'disabled'
save and reboot

That worked for me.

Hope this helps.

MSE OOBE Event Error - Fixed

MSE OOBE Event Error - Fixed- NOT