The error 0xC0000035 (technically STATUS_OBJECT_NAME_COLLISION) is a common "benign" error in the Windows Event Viewer. It typically occurs when a system component, like WindowsUpdateTracelog, tries to start a logging session that is already active or hasn't been properly closed from a previous run.
To resolve this issue, follow these steps in order.
This error typically appears in the Windows Event Viewer as a Kernel-EventTracing event (ID 2), indicating that a specific logging session failed to initialize because of a naming conflict or missing configuration. In the context of "WindowsUpdateTraceLog," this usually means the system tried to start a trace session that was already active or whose temporary log file was locked. What Error 0xc0000035 Means Resolution & Remediation Steps To resolve this issue,
If none of the above work:
When you are "repacking" (using tools like Microsoft App-V, VMware ThinApp, AdminStudio, or creating WIM images), the tool attempts to monitor system changes. If the Windows Update service attempts to start its diagnostic logging simultaneously—perhaps triggered by a background task or the startup of the Windows Update Agent—the repackaging tool detects a collision. The system cannot start a second instance of a trace session with the same name. What Error 0xc0000035 Means 7
: This is a specific event tracing session used by the operating system to track the health and activity of the Windows Update service. Benign Nature : Experts from Microsoft Community Support
Resolution and Remediation
If the trace definition is corrupted, you may need to reset the auto-logging registry keys.