|19 Mar 2010||#1|
| || |
MSE OOBE Event Error - Fixed- NOT
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.
|My System Specs|
|Similar help and support threads for2: MSE OOBE Event Error - Fixed|
|"Microsoft Security Client OOBE" stopped due to error: 0xC000000D||General Discussion|
|Can a S.M.A.R.T. 301 error be fixed with software?||Hardware & Devices|
|Event Viewer error iaStor Event 9||Drivers|
|"Microsoft Security Essentials OOBE" stopped (...) error 0xC000000D||BSOD Help and Support|
|Event Viewer Error Message Event ID11 - How do I get rid of this to?||BSOD Help and Support|
|Event Viewer Error Message Event ID10 - How to get rid of it?||BSOD Help and Support|
|Event 18 WHEA-Logger Error in Event Viewer||Hardware & Devices|
|Our Sites ||Site Links ||About Us ||Find Us |
© Designer Media Ltd
All times are GMT -5. The time now is 10:35 AM.