SEARCH

The How-To Geek Forums Have Migrated to Discourse

How-To Geek Forums / Windows 7

(Solved) - Microsoft Security Client OOBE" stopped due to the following error: 0xC000000D

(6 posts)
  • Started 2 years ago by raphoenix
  • Latest reply from raphoenix
  • Topic Viewed 28255 times

raphoenix
Posts: 14920

This Error in Windows 7 has never been fixed by MS.

It comes and goes with my systems all the time.

Has continued on for years now if you search on solutions.

However it does not pose any danger from what I can tell.

Asssume Win8 will fix the isssue.

Rick P.

Posted 2 years ago
Top
 
raphoenix
Posts: 14920

The error cleared up mysteriously on it's own about 4 months ago.

Now it's back in the logs again on both systems starting 08/05/2012.

There are Thousands of postings on the net concerning this error over the years yet no one has ever solved the issue including MS.

My guess is that it's a Registry Entry which is incorrect but how could one ever find it in the Registry ????

MSE is still operating perfectly so is hard to understand.

Is a strange situation for sure.

Rick P.

Posted 2 years ago
Top
 
GuiltySpark
Posts: 4024

Rick,

Do you mean the oobeldr ?

Posted 2 years ago
Top
 
raphoenix
Posts: 14920

OOBE

Something MS calls "Out Of The Box Experience".

Like WOW, Windows is so great to do things on without having to configure anything or know anything about computers !!!!

=================================================================

Log Name: Microsoft-Windows-Kernel-EventTracing/Admin
Source: Microsoft-Windows-Kernel-EventTracing
Date: 8/8/2012 16:51:56
Event ID: 3
Task Category: Session
Level: Error
Keywords: Session
User: SYSTEM
Computer: ASUS20
Description:
Session "Microsoft Security Client OOBE" stopped due to the following error: 0xC000000D
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-EventTracing" Guid="{B675EC37-BDB6-4648-BC92-F3FDC74D3CA2}" />
<EventID>3</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>2</Task>
<Opcode>14</Opcode>
<Keywords>0x8000000000000010</Keywords>
<TimeCreated SystemTime="2012-08-08T21:51:56.822805800Z" />
<EventRecordID>101</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="172" />
<Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel>
<Computer>ASUS20</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="SessionName">Microsoft Security Client OOBE</Data>
<Data Name="FileName">C:\ProgramData\Microsoft\Microsoft Security Client\Support\EppOobe.etl</Data>
<Data Name="ErrorCode">3221225485</Data>
<Data Name="LoggingMode">5</Data>
</EventData>
</Event>

Posted 2 years ago
Top
 
GuiltySpark
Posts: 4024

I just asked because there is an oobeldr in the Registry.

Posted 2 years ago
Top
 
raphoenix
Posts: 14920

This procedure appears to solve the issue.

It MUST be done Exactly by the Steps.

1. DISABLE the Microsoft Antimalware Service

2. REBOOT the machine

3. DELELETE the EppOobe.etl File
(Reference Path) C:\ProgramData\Microsoft\Microsoft Security Client\Support\EppOobe.etl

4. REBOOT the machine

5. ENABLE the Microsoft Antimalware Service

6. REBOOT the machine

7. Frequently CHECK the Administrative Events Log under Custom Views to ensure the error does not reappear.

NOTE: Just Deleting the EppOobe.etl file and Rebooting will NOT work.

Rick P.

Accepted Answer · Posted 2 years ago
Top
 



Topic Closed

This topic has been closed to new replies.