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

The error code 0xC0000035 (technically defined as STATUS_OBJECT_NAME_COLLISION) typically occurs in the Windows Event Viewer when a specific logging session, such as WindowsUpdateTraceLog, attempts to start but finds a session with the same name already active or an object already exists. In most cases, this message is benign and does not impact system performance or the ability to receive updates. 1. Root Causes

Understanding error code 0xc0000035 is the first step toward a permanent fix. In this article, we will dissect the root cause, explore why it happens, and provide step-by-step solutions for Windows 10 and Windows 11. Windows 10/11: Go to Settings > System >

If the status is "Running," the error was likely just a harmless conflict during startup when the system tried to start a session that had already initialized. 2. Modify the Autologger Registry Keys Restart the services in the Command Prompt: net

Method 3: The Nuclear Option (Reset Windows Update Components)

If the ETW session cannot be stopped because it is in a "zombie" state (linked to a dead process), you may need to reset all Windows Update components. This is a broader fix, but it will clear the trace collision. Windows 10/11: Go to Settings &gt

  1. Windows 10/11: Go to Settings > System > Troubleshoot > Other troubleshooters.
  2. Select Windows Update > Run.
  3. Follow the prompts. If it finds “Windows Update components must be repaired” or “Service registration is missing or corrupt,” allow it to fix.
  4. Reboot and retry updates.

Restart the services in the Command Prompt:net start wuauservnet start bits 4. Registry Fix (For Advanced Users)

Before diving into settings, perform a full restart. Not a "Shutdown" (which often uses Fast Startup and saves the kernel state), but a Restart. This forces Windows to kill all active tracing sessions and start fresh. 2. Flush the ETW Logs

Corrupted system files are a common culprit for event tracing conflicts. Use the built-in repair tools in an elevated Command Prompt: