Press Windows Key + X and select or Command Prompt (Admin) .
The Windows Event error 0xc0000035 typically denotes STATUS_OBJECT_NAME_COLLISION — an attempt to create an object (file, named pipe, event, session, or registry key) which already exists. When observed for the WindowsUpdateTraceLog session (part of Windows Event Tracing for Windows, ETW), the error prevents trace collection for Windows Update diagnostics and may indicate resource/name collisions, leftover state from previous tracing sessions, improper shutdown, or interfering third‑party software.
When Windows attempts to call the missing logging structure, it triggers a collision or a failure to start. If the above methods do not resolve the issue on a repacked OS, you may need to switch to an official, unaltered Windows ISO from Microsoft to ensure system stability and proper update tracking. If you want to debug this further, please share:
The Windows Update Trace Log is a valuable tool for system administrators and power users to diagnose and troubleshoot issues related to Windows updates. However, sometimes this log may fail to start, hindering the troubleshooting process. One such error that users may encounter is "Session Windows Update Trace Log failed to start with the following error: 0xc0000035." In this article, we will explore the possible causes of this error and provide step-by-step solutions to resolve the issue, specifically focusing on the "repack" aspect.
If you see WindowsUpdateTracelog or similar listed, stop it by typing: logman stop "WindowsUpdateTracelog" -ets 2. Repair System Files Press Windows Key + X and select or Command Prompt (Admin)
Third-party repack scripts disable update services but leave autologger hooks active.
Here is a short story about a very confused robot named to help illustrate what’s happening inside your computer. The Tale of the Double-Booked Robot
Here are the step-by-step methods to resolve this error, ordered from the most effective and common fixes to advanced troubleshooting.
Residual log buffers can lock the ETW (Event Tracing for Windows) session names. Boot your PC into . Open File Explorer and navigate to: C:\Windows\System32\LogFiles\WMI Use code with caution. Locate the directory named RtBackup . When Windows attempts to call the missing logging
= STATUS_OBJECT_NAME_COLLISION ), meaning the session name already exists or the log file is being accessed simultaneously by another process.
If you are seeing this error on a custom Windows installation ("repack"), the creator of the ISO may have stripped out specific telemetry components, telemetry hosts, or altered user permissions to "debloat" the operating system.
If the error persists, you can disable this specific trace session from starting automatically. This will not stop Windows Updates from downloading; it only stops the diagnostic tracking log. Press Windows Key + R , type regedit , and hit Enter.
Save the file with a .reg extension, for example, fix-windows-update.reg . However, sometimes this log may fail to start,
Click , close the Registry Editor, and restart your computer. Method 3: Run SFC and DISM Repairs
Before diving into complex procedures, perform these quick checks as they might instantly resolve the issue:
Open .