Session Windowsupdatetracelog Failed To Start With The Following Error 0xc0000035 【99% LEGIT】

System changes awaiting a full system initialization cause token registration overlaps. Step-by-Step Solutions to Resolve the Error

: It occurs when an Autologger session tries to start but finds a duplicate object already active. Common triggers include update conflicts, outdated drivers (like network or graphics drivers), or corrupted system files.

If you are auditing your Windows Event Viewer and notice a recurring Error ID 2 from the Kernel-EventTracing source, you are not alone. The error message typically reads:

If clearing the cache fails, the conflict is likely hardcoded into your startup configuration registry. Removing or modifying the duplicate entry forces Windows to recreate it correctly. Press Windows Key + R , type regedit , and press Enter . System changes awaiting a full system initialization cause

If the tracing log continues to fail, the entire Windows Update engine might be caught in a loop. Resetting the update components clears out corrupt update states. Open .

However, if you are experiencing actual Windows Update failures, system stutters, or crashes, you should follow the troubleshooting steps below. How to Fix Error 0xC0000035 1. Run the Windows Update Troubleshooter

Are your background , or are they failing too? If you are auditing your Windows Event Viewer

Wait for the process to reach 100%, then run the System File Checker (SFC) tool: sfc /scannow Use code with caution.

The error occurs when the Windows Operating System attempts to start a logging session for the Windows Update Trace log, but the session identifier (GUID) or naming convention conflicts with an already active session. The Significance of Error Code 0xc0000035

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\WindowsUpdateTracelog Use code with caution. In the right pane, locate the DWORD value named . Press Windows Key + R , type regedit , and press Enter

Stop the core update services by typing the following commands and hitting Enter after each: net stop wuauserv net stop bits Use code with caution.

Some antivirus programs (e.g., McAfee, Norton, Bitdefender, or even some VPN filters) hook into the ETW subsystem to monitor network and process activity. If they hold a lock on the trace log object, 0xc0000035 occurs.

This can help remove a corrupted log that may be causing the collision.

You can stop the naming collision by manually stopping the conflicting trace session through the Performance Monitor. Press Win + R , type , and hit Enter . In the left pane, expand Data Collector Sets . Click on Startup Event Trace Sessions . Locate WindowsUpdateTracelog in the center list. Right-click it and select Properties . Switch to the Trace Session tab. Uncheck the Enabled box. Click Apply and OK . Restart your computer.