Session Windowsupdatetracelog Failed To Start With: The Following Error 0xc0000035

To confirm that the error is resolved, clear your Event Viewer custom logs, initiate a manual check for updates via , and review your Administrative Events log after 10 to 15 minutes of operation. The Event ID 2 collision warning should no longer populate. To help tailor the best next steps, tell me:

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

If you are digging through your Windows Event Viewer and spot Event ID 2 or Event ID 7000 paired with Error 0xc0000035 , you are not alone. This specific error translates to STATUS_OBJECT_NAME_COLLISION . It means that the Windows Event Tracing (ETW) system tried to start a logging session named "WindowsUpdateTracelog," but a session with that exact name or security identifier was already running.

This specific error points to a conflict within the Windows Event Tracing (ETW) system. While it rarely causes immediate system crashes, ignoring it can prevent Windows Update from properly logging its activities, making future update failures much harder to diagnose. To confirm that the error is resolved, clear

Corrupt Event Trace Log ( .etl ) files can cause persistent object name collisions. Removing them forces Windows to rebuild fresh tracking templates. Boot your PC into .

If you have followed the steps above, your Event Viewer should be clean, and your system running smoothly once again! If the error persists after all these steps, it might be worth checking your hard drive health (using chkdsk ) to ensure no physical sectors are failing on your drive.

Open and run:

Which (Windows 10 or Windows 11) are you running?

If the status is "Running," the error was likely just a harmless conflict during startup when the system tried to start a session that had already initialized. 2. Modify the Autologger Registry Keys

The most common reason for the 0xc0000035 error is that the Windows Registry has a "stuck" entry telling the system the log session is already running. We need to delete this entry so Windows can create a fresh one. (If any file is locked, skip it)

You can manually manage active ETW sessions using the Windows Performance Monitor to stop the collision from recurring. Press Windows Key + R , type perfmon , and hit . In the left pane, expand Data Collector Sets . Click on Startup Event Trace Sessions .

Often, simply forcing the trace log session to stop and restart will resolve the conflict.

This is a specific "Event Tracing Session." Windows uses these sessions to log activities in the background. As the name suggests, this specific session is designed to log details about how Windows Update behaves. It means that the Windows Event Tracing (ETW)

Older Intel storage drivers occasionally conflict with Windows event tracing allocations.