If you are using a modified Windows "repack," system binaries related to Event Tracing might be altered or broken. Open .
If you would like to pinpoint the exact root cause on your machine, please let me know: Which are you currently running?
Corrupted system files can prevent update services from initializing correctly. In the same administrator Command Prompt, run: sfc /scannow
Open File Explorer and navigate to: C:\Windows\System32\LogFiles\WMI If you are using a modified Windows "repack,"
: Use the Windows Services Manager ( services.msc ) to find the Windows Update service, right-click it, and select Restart .
Sometimes old log files get stuck. Navigate to C:\Windows\SoftwareDistribution and delete the contents of the DataStore and Download folders (you may need to stop the Windows Update service first) [2, 4].
Change their values from 1 to 0 . This prevents the system from attempting to start that specific trace session, which stops the error from logging in the Event Viewer. Corrupted system files can prevent update services from
If the error persists on every reboot, you can disable the specific "AutoLogger" that is failing.
Repackaged Windows ISOs often disable services like Microsoft.Windows.WindowsUpdate.RUXIMLog or WindowsUpdateTraceLog to stop telemetry data from being sent to Microsoft. If the logger is disabled or modified poorly, it throws this error.
If the error persists but your system updates are installing correctly, Microsoft support specialists often suggest it is a known timing issue that does not require further action. In plain terms
Method 4: Disable IPv6 (Workaround for Specific Network Collisions)
You are checking the Event Viewer (Applications and Services Logs > Microsoft > Windows > WindowsUpdateClient > Operational) or running a system scan, and you see this error:
The core of the issue lies in the hexadecimal status code: 0xc0000035 . In the Windows NT status code hierarchy, this specific code translates to STATUS_OBJECT_NAME_COLLISION . In plain terms, this error indicates that the operating system attempted to create or access a named object (in this case, a kernel session or a file mapping) that already exists.
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
The error code 0xc0000035 is a Windows error code that typically indicates a problem with the Windows registry or a failure to access a required system resource. In the context of the Windows Update Trace Log, this error may occur due to corrupted system files, registry entries, or issues with the Windows Update service.