Session Windowsupdatetracelog Failed To Start With The Following Error 0xc0000035 [verified] -

If system files responsible for Event Tracing are corrupted, Windows will continually mismanage session states. Use the deployment imaging tools to patch them. Open .

The Event Viewer error is a common Windows administrative log entry. It indicates that the operating system tried to start a trace logging session for Windows Update, but failed because a session with the exact same name or identifier was already running.

Repair corrupted system files that may be causing session conflicts.

Press Windows Key + R to open the Run dialog box. Type and press Enter to open the Registry Editor.

Restart your system if the utility repairs any corrupted components. Step 4: Manually Clear the Event Log Directory If system files responsible for Event Tracing are

Minimize the Command Prompt window. Open File Explorer and navigate to the following folder: C:\Windows\SoftwareDistribution

Select all files and folders inside this directory ( Ctrl + A ) and them. (If any file is locked, skip it).

Correcting the Autologger flags prevents the system from forcing a duplicate initialization of the tracing provider on startup.

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 The Event Viewer error is a common Windows

Again, I get this only when I logoff/logon during s session. I've tried every suggestion mentioned in many forums, including this, Experts Exchange Startup Error in Event Viewer - Microsoft Q&A

Temporarily disable third-party monitoring/security agents

A noteworthy wave of these errors occurred around August 2025, specifically with Windows 11 24H2 cumulative update . Users across both consumer Windows Update and enterprise WSUS platforms reported installation failures with error code 0x80240069, accompanied by the kernel-eventtracing error 0xc0000035.

Allow the progress bar to reach 100% (this may take several minutes). Next, execute the System File Checker scan: sfc /scannow Use code with caution. Press Windows Key + R to open the Run dialog box

Run the following commands one by one to stop and restart the update components: net stop wuauserv net stop bits net start bits net start wuauserv Microsoft Learn 3. Repair System Files

He realized then that the "error" wasn't a bug; it was a footprint. Someone—or something—had hijacked the trace session to mask their movement, leaving a lingering shadow that blocked the system’s own diagnostic eyes.

This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later.

After updating, restart your computer and monitor the Event Viewer for the error.

Manually terminating the stuck event trace session clears the object collision in the system memory.

Administrator privileges, registry backup performed.