You are checking the Event Viewer (Applications and Services Logs > Microsoft > Windows > WindowsUpdateClient > Operational) or running a system scan, and you see this error:
Session "WindowsUpdateTraceLog" failed to start with the following error 0xc0000035
This error indicates that the Event Tracing for Windows (ETW) session for Windows Update cannot start. Code 0xc0000035 translates to STATUS_OBJECT_NAME_COLLISION — meaning a session with that name already exists (orphaned or stuck).
When repacking, you might have:
On a clean boot, Windows attempts to start WindowsUpdateTraceLog but finds that another session (or a stale handle) is already using its GUID or name.
If you’re a repacker creating custom images, here’s how to avoid 0xc0000035 entirely:
To update drivers:
This error message typically appears in the Windows Event Viewer
when a background diagnostic logging session fails to initialize. In most cases, it is a benign system glitch that can be safely ignored unless you are experiencing severe performance issues or blue screens. Microsoft Learn What the Error Means 0xc0000035 : This code usually refers to STATUS_OBJECT_NAME_COLLISION
, meaning a logging session with that exact name was already running or a file with that name already exists. WindowsUpdateTraceLog
: 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
often note that these log entries are common during normal operations and do not necessarily indicate a critical system failure. Microsoft Learn How to Fix It
If you notice system slowdowns or want to clear the error, try these steps: Troubleshoot problems updating Windows - Microsoft Support You are checking the Event Viewer (Applications and
The error code 0xC0000035 is formally defined as STATUS_OBJECT_NAME_COLLISION, which indicates that a logging session or file name that Windows tried to create already exists. In the context of WindowsUpdateTracelog (or related logs like RUXIMLog), this usually occurs during a system restart when Windows attempts to start a diagnostic trace that didn't shut down or clean up properly in the previous session.
If your computer is otherwise updating and running normally, this error can typically be safely ignored. However, if you want to resolve it or are experiencing update issues, follow these steps: 1. Run Built-in Repair Tools
Use the Windows Update Troubleshooter to automatically identify and fix common configuration errors.
Go to Settings > System > Troubleshoot > Other troubleshooters. Select Windows Update and click Run. 2. Repair System Files
Corrupted system files can cause naming collisions in the kernel event tracing system. Use the following commands to repair them: Open Command Prompt as an Administrator.
Run the Deployment Image Servicing and Management (DISM) tool:DISM /Online /Cleanup-Image /RestoreHealth This error indicates that the Event Tracing for
Once finished, run the System File Checker (SFC):sfc /scannow 3. Clear Windows Update Cache
Deleting the temporary update files can resolve conflicts where the system tries to restart a trace based on outdated data. Open Command Prompt as Administrator. Stop the Update service: net stop wuauserv
Navigate to C:\Windows\SoftwareDistribution and delete all contents. Restart the service: net start wuauserv 4. Advanced: Registry Modification
If the error persists and floods your Event Viewer, you can disable the specific autologger that is failing:
Open Registry Editor (regedit) and navigate to:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-System
Look for the subkey associated with the trace log (often a GUID like b675ec37-...). Change the Enabled and EnableProperty values from 1 to 0. On a clean boot
Warning: Back up your registry before making manual changes. Kernel-EventTracing - Microsoft Q&A
The error 0xC0000035 (STATUS_OBJECT_NAME_COLLISION) during WindowsUpdateTraceLog indicates a benign name conflict, often ignorable if system updates function normally. Resolving this involves clearing the Windows Update cache via Command Prompt or disabling the specific autologger in the registry editor. For a detailed troubleshooting guide, visit Microsoft Q&A.