Minimize the command window. Open File Explorer and navigate to: C:\Windows\SoftwareDistribution
This specific error occurs when the Windows Operating System attempts to start a diagnostic logging session that is already active, or when there is a naming collision in the kernel trace memory. The hex code 0xC0000035 translates directly to STATUS_OBJECT_NAME_COLLISION .
⚠️ : Registry editing carries risks. Always back up the registry before making changes.
If the error persists and updates are failing, clearing the update cache can resolve naming collisions: Open as an administrator. Minimize the command window
If you are experiencing system slowdowns or Windows Update failures, you can address the error using the following methods: 1. Run Standard System Repairs
System file corruption is a common culprit for tracing errors. The System File Checker (SFC) and Deployment Image Servicing and Management (DISM) tools can automatically repair these issues. Open .
Navigate to C:\Windows\SoftwareDistribution and inside. ⚠️ : Registry editing carries risks
Navigate to the SoftwareDistribution folder: cd %systemroot%\SoftwareDistribution
Open File Explorer and navigate to C:\Windows\System32\LogFiles\WMI . Locate the file named WindowsUpdateTraceLog.etl . it to WindowsUpdateTraceLog.etl.old . Restart your computer . Method 3: Run SFC and DISM Tools
Since the error stems directly from the Windows Update tracing mechanism, purging the update cache usually clears the conflict. If you are experiencing system slowdowns or Windows
Press Windows Key + S , type , right-click Command Prompt , and select Run as administrator .
The same underlying problem can appear in Event Viewer with different session names. Here are the most frequent variants you might encounter:
Corrupted system files can trigger collision errors during startup. Open as an Administrator.
If system file checks find no issues, reset the Windows Update components manually: