Note: Disabling the tracer via 0 stops the diagnostic collision. Windows Update will still function normally and will automatically recreate or restart clean tracking logs when required. Step 3: Run SFC and DISM Repairs
The error 0xc0000035 associated with the failure to start the WindowsUpdateTraceLog session indicates a specific naming conflict within the Windows Event Tracing for Windows (ETW) subsystem. When the Windows Update service attempts to start an ETW trace session for diagnostic logging, it fails because an AutoLogger session with the same name is already registered in the registry but not active, or a stale session entry exists. This paper details the root cause, diagnostic steps, and resolution methods for this error.
You must have Administrator privileges . Log in as an administrator or right-click Command Prompt/PowerShell > "Run as administrator." Note: Disabling the tracer via 0 stops the
# Check for WindowsUpdateTraceLog session collisions Get-WinEvent -LogName "Microsoft-Windows-EventTracing/Operational" | Where-Object $_.Id -eq 100 -and $_.Message -like "*0xc0000035*"
Note: Disabling this specific trace log will stop the Event Viewer error without impacting your system's ability to download or install regular Windows updates. Step 3: Run SFC and DISM Repairs When the Windows Update service attempts to start
0xc0000035 NTSTATUS Equivalent: STATUS_OBJECT_NAME_COLLISION Human-Readable Meaning: "A file, registry key, or object with the same name already exists."
Only use the registry fix if you specifically want to stop the error from appearing in your logs and are confident your system is otherwise healthy. Log in as an administrator or right-click Command
Clearing the update cache forces the system to re-initialize its logging and update files. Command Prompt as an administrator. Type these commands one by one, pressing Enter after each:
