Session Windowsupdatetracelog Failed To Start With The Following Error 0xc0000035 Work ✰

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

Which (e.g., Windows 11 23H2) are you currently running?

, this often means a previous update session didn't shut down correctly, leaving an orphaned entry that blocks new logs from starting. Click , close the Registry Editor, and restart your computer

0xc0000035 (STATUS_OBJECT_NAME_COLLISION) occurs when the Windows Event Tracing (ETW) system attempts to start a logging session with a name that is already in use. For WindowsUpdateTracelog

Follow these troubleshooting methods in order, starting with the simplest system resets and moving toward registry configurations. 1. Clear the Windows Update Cache Clear the Windows Update Cache To fix the

To fix the issue, it helps to understand what the error code actually means:

logman stop "Windows Update Trace Log" -ets In Windows hexadecimal error mapping

: Antivirus software or outdated network drivers may block trace session initiation. Step-by-Step Solutions 1. Terminate Existing Trace Sessions

If corrupted temporary update files are holding the trace token open, purging the SoftwareDistribution directory will force Windows to generate clean logging environments.

In Windows hexadecimal error mapping, 0xc0000035 translates directly to STATUS_OBJECT_NAME_COLLISION . This means the system tried to create a tracking object or session name that already exists in memory. Because two diagnostic sessions cannot share the exact same namespace simultaneously, the secondary request fails and logs Event ID 2. Common Triggers