Session Windowsupdatetracelog Failed To Start With The Following Error 0xc0000035 |top| Jun 2026

Under the tab, you can set a Maximum Size (e.g., 100 MB) to prevent it from failing due to overflow, or simply stop the session if it's not needed for active debugging.

When your system boots or triggers an update cycle, the Autologger mechanism attempts to spin up this trace session. If a previous instance of the log did not close properly, or if another system process has already claimed that specific logging handle, Windows throws the 0xC0000035 collision error. Step 1: Clear the Windows Update Cache

Editing the registry can be risky. Always back up your registry or create a system restore point before proceeding. Under the tab, you can set a Maximum Size (e

Click , close the Registry Editor, and restart your computer .

In the architecture of Windows Management Instrumentation (WMI) and Event Tracing for Windows (ETW), every logging session must maintain a unique identity. When the Windows Update service or a related telemetry component attempts to spawn the WindowsUpdateTracelog kernel trace session, it checks the internal registry of active trace providers. If a duplicate context structure or an identical name string is already registered within the kernel, the subsystem rejects the initialization request and records this collision error. Step 1: Clear the Windows Update Cache Editing

For most commands below, you will need to open Command Prompt, PowerShell, or Windows Terminal as an administrator. To do this, press the Windows key, type cmd , right-click on "Command Prompt", and select Run as administrator .

0xc0000035 rarely indicates a broken Windows installation. It’s usually a harmless collision , not a corruption error. Expand the Network adapters section.

Because WindowsUpdateTracelog interfaces with your network stack, resolving driver conflicts often mitigates ETW object collisions. Right-click the Start menu and select . Expand the Network adapters section.