Session Windowsupdatetracelog Failed To Start With The Following Error 0xc0000035 Access

This is a specific "Event Tracing Session." Windows uses these sessions to log activities in the background. As the name suggests, this specific session is designed to log details about how Windows Update behaves.

If your PC is running smoothly, you can this log entry.

# list active ETW sessions logman query -ets This is a specific "Event Tracing Session

Essentially, Windows is trying to launch the WindowsUpdateTraceLog session, but it thinks the session is already running or the file associated with it is locked. It sees a "collision," so it aborts the process.

This specific error occurs when the Windows Operating System attempts to start a diagnostic logging session that is already active, or when there is a naming collision in the kernel trace memory. The hex code 0xC0000035 translates directly to STATUS_OBJECT_NAME_COLLISION . # list active ETW sessions logman query -ets

Double-click and change its Value Data from 1 (Enabled) to 0 (Disabled). Click OK .

This comprehensive guide will explain what error 0xc0000035 means, why it appears, and provide step-by-step solutions to resolve it—from beginner‑friendly fixes to advanced troubleshooting for IT professionals. Run: sfc /scannow .

Before jumping into the fixes, it helps to understand the root causes:

Understanding the root cause can help you choose the most effective fix. The error can be triggered by several factors:

Select and run the Windows Update tool. 2. Repair System Files Corrupted system files can cause logging conflicts. Open Command Prompt as Administrator . Run: sfc /scannow .