Open an administrative Command Prompt and run logman query -ets . If you see a WindowsUpdateTraceLog session in a “Running” or stale state, stop it immediately. Then, smile — you’ve just fixed the problem.
If the error persists in your Event Viewer every reboot, you can disable the specific Autologger that is failing.
The "Session WindowsUpdateTraceLog failed to start with error 0xc0000035" is a frustrating but solvable Windows Update issue. At its core, it is a — often an orphaned session that never released its object name. Open an administrative Command Prompt and run logman
"Session 'WindowsUpdateTraceLog' failed to start with the following error: 0xC0000035" typically appears in the Windows Event Viewer under the Kernel-EventTracing
At its core, the 0xC0000035 error code corresponds to STATUS_OBJECT_NAME_COLLISION . This is a technical way of saying there's a . The Event Tracing for Windows (ETW) system tried to start a new trace session (like WindowsUpdate_trace_log ), but it found that a session with the same name was already running or that its configuration files were corrupted. If the error persists in your Event Viewer
The error code translates to STATUS_OBJECT_NAME_COLLISION , which essentially means Windows tried to start a logging session (like WindowsUpdateTraceLog ) that was already running or has a naming conflict with an existing object.
A simple restart often clears stuck trace sessions. After rebooting, retry the operation that caused the error. The error code translates to STATUS_OBJECT_NAME_COLLISION
with the following commands (run as Administrator):