A second attempt to create the same session (either manually or by another service) triggers a name collision.
Open the , type cmd , right-click on Command Prompt , and select Run as Administrator .
System changes awaiting a full system initialization cause token registration overlaps. Step-by-Step Solutions to Resolve the Error A second attempt to create the same session
This error, which translates to a conflict where a resource already exists, can lead to cluttered logs and, in some cases, performance degradation or issues with Windows Updates.
At first glance, this looks like a critical system failure. You might worry that your Windows Update mechanism is broken or that your hard drive is failing. While those can be issues, this specific error is usually related to a configuration conflict within the Windows Event Tracing (ETW) system. Step-by-Step Solutions to Resolve the Error This error,
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.
If resetting the session doesn't work, the log file itself might be corrupted. Renaming it forces Windows to create a new, healthy file. While those can be issues, this specific error
Press Windows Key + R , type regedit , and press to open the Registry Editor.
Locate the DWORD value in the same key. Set its Value data to 0 . Exit the Registry Editor and restart your machine. Method 3: Reset Performance Counters and Log Infrastructure
When the Windows Update service attempts to start a new trace log session (specifically the "WindowsUpdateTraceLog" Event Tracing for Windows (ETW) session), it tries to create a unique object name. The error occurs when that name already exists in the system’s object namespace but is in a stalled, dead, or inaccessible state.
Before investing time in troubleshooting, verify if the error is affecting system functionality: