Session Windowsupdatetracelog Failed To Start With The Following Error 0xc0000035 | Repack

This paper analyzes the Windows event indicating "Session WindowsUpdateTraceLog failed to start with the following error 0xc0000035 repack". It examines root causes, diagnostic steps, and remediation approaches, and provides a reproducible troubleshooting workflow and preventive recommendations.

Alex opened Command Prompt as Administrator and ran:

logman query

Right there, under "Data Collector Sets", was WindowsUpdateTraceLog – stuck in a "Running" state, even though no updates were active. This paper analyzes the Windows event indicating "Session

The error means the WindowsUpdateTraceLog session already exists. Use logman (Windows built-in trace manager) to delete and recreate it.

logman stop WindowsUpdateTraceLog -ets
logman delete WindowsUpdateTraceLog -ets

Then reboot – the trace session should be recreated automatically when needed. Then reboot – the trace session should be

If WindowsUpdateTraceLog keeps getting stuck, Alex learned to:

But in most cases, simply stopping the old session fixed it forever. leftover state from previous tracing sessions

The Windows Event error 0xc0000035 typically denotes STATUS_OBJECT_NAME_COLLISION — an attempt to create an object (file, named pipe, event, session, or registry key) which already exists. When observed for the WindowsUpdateTraceLog session (part of Windows Event Tracing for Windows, ETW), the error prevents trace collection for Windows Update diagnostics and may indicate resource/name collisions, leftover state from previous tracing sessions, improper shutdown, or interfering third‑party software.