Session "microsoft security client oobe" stopped due to the following error: 0xc000000d

Question

Problem :

Currently I am using Windows Server 2008 R2. I usually connect the server by remote desktop connection. But nowadays my server disconnects my remote desktop session randomly and also all my application running during the session are closed. My issue is the remote desktop connection is forcibly logged off by Windows Server 2008 R2.
After reconnecting when I try to open the event viewer I often see the following error:

session ‘microsoft security client’ oobe stopped due to the following error: 0xC000000D

Why my Windows Server 2008 R2 behaving like that?

Answer 1

OOBE problem Solution as follows :

You must shutdown the security counter.

Everyone says to delete the following but don’t delete C:\ProgramData\Microsoft\Microsoft Security Client\Support\EppOobe.etl file. Generally file is used and created by this counter.

Please DON'T DELETE THE EppOobe.etl file instead

Please go into Computer Management by following below steps :

-> control panel -> administrative tools -> computer management and drill down into:

System Tools -> Performance -> Data Collector Sets -> Startup Event Tracing Sessions

Then please select the Microsoft Security Client OOBE and just right click on it and select Properties.

After that Click on the tab Trace Session and

Just DISABLE it  by unchecking the Enabled box Then, you please select OK.

This will resolve your issue.

Answer 2

Delete the EppOobe.etl File

Few users told deleting the EppOobe.el file of Microsoft Security Essentials could be useful to solve session “Microsoft Security Client OOBE” stopped error 0xC000000D. This file can be regenerated automatically at the time you install MSE.

1. Go to Windows Explorer and navigate to C:\ProgramData\Microsoft\Microsoft Security Client\Support\EppOobe.etl.
2. Delete it by right-clicking it to select Delete.
3. Restart your computer to view in case the MSE error code 0xC000000D is solved.

Run an SFC Scan

The OOBE problem may be caused by corrupted system files. To solve it, you can attempt System File Checker to scan for your system and repair the system corruption.

1. Run Command Prompt with administrative rights.
2. Type sfc /scannow in the pop-up window and press Enter.
3. Windows will make a system scan and fix damaged system files.

Disable Program Compatibility Assistant Service

The problem - session “Microsoft Security Essentials OOBE” stopped due to the pursuing error: 0xC000000D might be caused by incompatibility between OOBE and Program Compatibility Assistant Service. To solve this problem, you must disable this service.

Pursue the guide below:

1. Hit Win + R, input services.msc to the Run box and click OK.
2. Trace Program Compatibility Assistant Service from the services list, double-click it, choose Disabled from Startup type and click Stop.
3. Lastly, save the changes by clicking Apply and OK.

Turn off OOBE in Computer Management

In case the settings in the OOBE item are not right, you may encounter the Microsoft Security Client error. OOBE isn’t connected to key functions of MSE however other services and progresses. Hence, you can attempt disabling this item to the Microsoft Security Client OOBE stopped error, which won’t impact MSE.

1. Right-click on Computer to select Manage.
2. Navigate to Computer Management > System Tools > Performance > Data Collector Sets > Startup Event Trace Sessions.
3. Right-click the Microsoft Security OOBE item to select Properties.
4. Under the Trace Session tab, uncheck the box of Enabled.
5. Save the change.

Restart your PC to inspect in case the OOBE problem is solved. In case not, attempt another method.

Uninstall Microsoft Security Essentials fully

Here is what you must do:

1. Open Control Panel to display items by Category.

2. Click the Uninstall a program connect from the Programs section.

3. Select Microsoft Security Essentials and click Uninstall to remove it.

4. Afterwards, you require to remove few leftovers to thoroughly delete the software.