: Antivirus software or outdated network drivers may block trace session initiation. Step-by-Step Solutions 1. Terminate Existing Trace Sessions
| Measure | Implementation | |---------|----------------| | Avoid manual ETW sessions with reserved names | Do not use WindowsUpdateTraceLog for custom logging | | Properly stop tracing before service shutdown | In scripts, always call logman stop | | Monitor AutoLogger registry for corruption | Use Group Policy to enforce baseline of WMI/AutoLogger keys | | Deploy Windows updates regularly | Microsoft has fixed related ETW race conditions in KB5008212 and later |
If you are inspecting the Windows Event Viewer and notice a recurring Error Event ID 2 stating that the session "WindowsUpdateTracelog" failed to start with the following error: 0xc0000035 , you are encountering a common Windows operating system conflict. : Antivirus software or outdated network drivers may
Right-click it, select , and ensure you have administrative permissions to view it.
In the left sidebar, expand > Local Users and Groups > Groups . Right-click it, select , and ensure you have
Follow these troubleshooting steps in order to resolve the object collision and clean up your system logs. Step 1: Clear the Windows Update Cache
Once complete, the terminal will indicate whether it found and successfully repaired damaged system files. Restart your PC if prompted. Step 4: Reset Performance Counters Step 1: Clear the Windows Update Cache Once
0xc0000035 rarely indicates a broken Windows installation. It’s usually a harmless collision , not a corruption error.
Press Windows Key + S , type , right-click Command Prompt , and select Run as administrator .