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.
This lists all registered event logs. To clear a specific log:
Corrupted temporary update files frequently trigger tracking collisions when the Windows Update agent continuously loops or fails to register completed actions. Clearing the cache resets this behavior.
This error typically triggers due to one of the following underlying issues:
If a reboot is not feasible:
"Session 'WindowsUpdateTraceLog' failed to start with the following error: 0xC0000035" typically appears in the Windows Event Viewer under the Kernel-EventTracing
If underlying system files related to Windows Event Tracing are corrupted, the built-in deployment image tools can repair them. Open .
The error code translates directly to STATUS_OBJECT_NAME_COLLISION . While this error looks alarming, it rarely causes system crashes or stops Windows Update from working. However, it can clutter your Event Viewer and indicate minor sync issues within the Windows Management Instrumentation (WMI) or Event Trace Log (ETL) subsystems. What Causes Error 0xc0000035?
In the Windows subsystem, the hexadecimal code 0xc0000035 translates specifically to STATUS_OBJECT_NAME_COLLISION .