The 0xC0000035 error code, also known as STATUS_OBJECT_NAME_COLLISION , indicates that the tracing session WindowsUpdateTraceLog is trying to start, but the system believes it is already running. This typically happens due to:
Follow these troubleshooting methods in sequence to clear the log collision. 1. Perform a Clean Boot and Restart Windows Update Services
If you identify an offending session, delete it with: Perform a Clean Boot and Restart Windows Update
If the status is "Running," the error was likely just a harmless conflict during startup when the system tried to start a session that had already initialized. 2. Modify the Autologger Registry Keys
Purging the update cache removes corrupted files that might be forcing the tracing tool into a collision state. Press Windows Key + R , type ,
Press Windows Key + R , type , and hit Enter to open the Registry Editor.
Restart the services in the Command Prompt: net start wuauserv net start bits 4. Registry Fix (For Advanced Users) why it appears
Execute the Deployment Image Servicing and Management tool first: DISM.exe /Online /Cleanup-image /Restorehealth Use code with caution.
The system registry forcing a duplicate startup trace.
This comprehensive guide will explain what error 0xc0000035 means, why it appears, and provide step-by-step solutions to resolve it—from beginner‑friendly fixes to advanced troubleshooting for IT professionals.
Note: Disabling this specific trace log will stop the Event Viewer error without impacting your system's ability to download or install regular Windows updates. Step 3: Run SFC and DISM Repairs