"Microsoft Security Client OOBE" stopped due to error: 0xC000000D

Layback Bear · 16 Feb 2013

Jacee said:

In the future, if anyone is still running MSE v.2 .... It should have been updated to version 4. This was available Client Update Package - Kb2691906.

Download Microsoft Security Essentials from Official Microsoft Download Center

How to upgrade to the latest version of Microsoft Security Essentials when you're running a beta

Jacee shouldn't Windows Updates with a proper COA automatically recommended that update to the newer version.

Jacee · 17 Feb 2013

That would have come with Windows automatic updates in February of 2012, if you had MSE version 2 running then. If the update wasn't checked to be downloaded and installed (as in my Step-Daughter's case) it wouldn't update.
I had to uninstall the old version 2 and install the RTM version 4 on her computer.

Layback Bear · 17 Feb 2013

So if I understand you correctly the update will be offered to all genuine systems (COA) but like other things one has to select it.

FloridaNative · 17 Feb 2013

Thanks, this is going to be such an amazing machine that I am totally pleased with the planned configuration. I am so looking forward to having Photoshop, Illustrator, InDesign and Lightroom open at the same time with no lagging. But I will definitely store your tip away for future reference, and future upgrades!

gregrocker · 11 Apr 2013

In addition to the steps given in this thread to unintall MSE when it errors as discussed, what finally ended the error for me recently was searching Registry for remainders shown in Microsoft Security Client OOBE stopped due to the following error: 0xC000000D

izkiel · 16 Jan 2014

The best way to get rid of this message/log after uninstalling MSE is to:

1. run regedit
2. go to HKLM\System\CurrentControlSet\Control\WMI\Autologger
3. find and delete Microsoft Security Client OOBE entry
4. reboot pc
5. go to C:\ProgramData\Microsoft\
6. delete Microsoft Security Essentials folder
7. reboot again

That will get rid of it. :)

Dragonchaser · 25 Oct 2014

Hi,

For what it's worth here is a fix that worked for me:

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.