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

The ETW subsystem maintains a namespace for active trace sessions and AutoLogger sessions (sessions configured to start at boot). The error 0xc0000035 occurs when:

To solve the problem, we first need to understand the components involved.

1. WindowsUpdateTraceLog: 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.

2. The Error Code 0xc0000035: In Windows hexadecimal error codes, 0xc0000035 translates to STATUS_OBJECT_NAME_COLLISION. The ETW subsystem maintains a namespace for active

Translation: "I tried to start a new logging session, but an object with that name already exists."

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.

  • Monitor for recurring failures—if frequent, escalate to Microsoft support with ETL captures and logs.

    • Corrupt system files—especially those related to ETW (Event Tracing for Windows)—can cause this error. At first glance

    Windows Update is the lifeblood of system security and feature stability on Microsoft operating systems. However, it is also notoriously sensitive to corruption, misconfigurations, and resource conflicts. One of the more cryptic errors that administrators and users encounter when digging into the WindowsUpdate.log or the Event Viewer is:

    "Session "WindowsUpdateTraceLog" failed to start with the following error 0xc0000035."

    At first glance, this error looks like a critical system failure. The hexadecimal code 0xc0000035 can be intimidating, but it is a well-known status code in the Windows kernel: STATUS_OBJECT_NAME_COLLISION. In plain English, this means "a file, registry key, or object with that name already exists." this means "a file

    This article will dissect exactly what this error means, why it prevents Windows Update from functioning correctly, and provide a step-by-step guide to resolving it permanently.

    To fix the problem, we must first understand what the components of this error message actually mean.