Error 0xc0000035 for WindowsUpdateTracelog is an operational technicality caused by name collisions within the ETW architecture. Clearing the update cache or configuring the Autologger registry flags will stop the system from generating duplicate logging instances, keeping your Windows Event Logs clean and free of unnecessary warning flags. To help find the most effective path forward, please share:
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.
However, if you're experiencing actual issues with updates or performance, here is how to resolve it. 1. Verify if the Logger is Already Running When the Windows Update service attempts to start
Right-click the key in the left folder tree.
Internal system file mismatches can corrupt structural components of the Windows Management Instrumentation (WMI) infrastructure, triggering tracing errors. Open Command Prompt as an . Run the deployment image repair tool first: DISM.exe /Online /Cleanup-image /Restorehealth Use code with caution. Allow the verification percentage to hit 100%. Run the System File Checker tool directly after: sfc /scannow Use code with caution. Restart your system once the verification finishes. Verifying the Fix triggering tracing errors.
Open an and run:
net stop wuauserv net stop cryptSvc net stop bits net stop msiserver Use code with caution. Restart the services by running: here is how to resolve it.
Think of it like starting two applications that both want to use the exact same name tag. The second one fails because the name is already taken. This conflict is why the trace log fails to initialize.
Autologger configuration files ( .etl ) in the system directory become unreadable or locked.
tool to stop any "ghost" sessions that might be causing the collision. Microsoft Learn In an elevated Command Prompt, type: logman query Look for any session named WindowsUpdateTraceLog or similar. If found, stop it by typing: logman stop "WindowsUpdateTraceLog" -ets 4. Check for Update Health Tool Conflicts Sometimes, a specific tool called Microsoft Update Health Tools causes this specific logging error. Microsoft Learn Installed Apps Search for Microsoft Update Health Tools If it exists, you can try Uninstalling
Since the error stems directly from the Windows Update tracing mechanism, purging the update cache usually clears the conflict.
