Fix Microsoft Security Client OOBE Stopped Due to 0xC000000D

Microsoft Security Client OOBE Stopped Due to Error 0xC000000D

Microsoft Security Essentials (MSE) can scan your system for malware and external attacks. It is easy-to-use and comes preinstalled on your computer. The program works quietly and efficiently in the background to protect your system all the time.

Security Essentials and Windows Defender Problem in Win7/8/8.1

Reportedly, Windows Security Essentials and Windows Defender crash with 0x800106ba error on Windows 7, 8 and 8.1. Read this post to learn more.

Read More

Nevertheless, sometimes it gives you the Microsoft Security Client OOBE stopped error. When you go to the Event Viewer, you see the Event ID 3 Kernel-EventTracing window, saying Session “Microsoft Security Essentials OOBE” stopped due to the following error: 0xC000000D.

This error may also cause a blue screen of death (BSoD) error. So, it is necessary to fix this issue as soon as possible so as to keep your Windows system secure.

How to Fix Microsoft Security Client Error Code 0xC000000D

Delete the EppOobe.etl File

Some users said deleting the EppOobe.el file of Microsoft Security Essentials could be helpful to fix session “Microsoft Security Client OOBE” stopped error 0xC000000D. This file can be regenerated automatically when 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 choose Delete.
3. Restart your computer to see if the MSE error code 0xC000000D is fixed.

Run an SFC Scan

The OOBE issue may be caused by corrupted system files. To fix it, you can try 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 hit Enter.
3. Windows will perform a system scan and fix damaged system files.

Disable Program Compatibility Assistant Service

The issue – session “Microsoft Security Essentials OOBE” stopped due to the following error: 0xC000000D might be caused by incompatibility between OOBE and Program Compatibility Assistant Service. To fix this issue, you should disable this service.

Follow the guide below:

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

Turn off OOBE in Computer Management

If the settings in the OOBE item are not correct, you may encounter the Microsoft Security Client error. OOBE isn’t related to key functions of MSE but other services and progresses. So, you can try disabling this item to the Microsoft Security Client OOBE stopped error, which won’t impact MSE.

1. Right-click on Computer to choose 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 choose Properties.
4. Under the Trace Session tab, uncheck the box of Enabled.
5. Save the change.

Restart your PC to check if the OOBE issue is fixed. If not, try another method.

Uninstall Microsoft Security Essentials Completely

Here is what you should do:

1. Open Control Panel to show items by Category.

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

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

4. After that, you need to remove some leftovers to thoroughly delete the software.

The End

Has been bothered by the issue – session “Microsoft Security Client OOBE” stopped due to the following error: 0xc000000D? Now, it is your turn to follow these methods above to fix it.