It was a typical Monday morning for John, a IT specialist at a large corporation. He arrived at his desk, sipped his coffee, and began to tackle the day's tasks. One of his colleagues had reported an issue with the Windows Update service on one of the company's laptops, and John had volunteered to take a look.
A: Technically, yes—by disabling Autologger for that session. But that would cripple diagnostic capabilities. It’s better to fix the root cause.
How to Fix "Session 'WindowsUpdateTracelog' failed to start with error 0xC0000035" It was a typical Monday morning for John,
Manually clearing the existing log files often resolves the "Object Name Collision" by removing the duplicate entries.
Type the following commands one by one, hitting Enter after each: net stop wuauserv net stop bits Wait a few seconds, then restart them: net start wuauserv net start bits 4. Check for Circular Logging Conflicts If you are tech-savvy, you can manage the session directly: How to Fix "Session 'WindowsUpdateTracelog' failed to start
If your computer is otherwise performing well and Windows Updates are installing successfully, this error is typically . It indicates a brief conflict during background logging rather than a hardware failure or a critical system crash. You can safely ignore it unless you are experiencing "Blue Screen" errors or a total failure of the Windows Update service. AI responses may include mistakes. Learn more
Corrupt system files—especially those related to ETW (Event Tracing for Windows)—can cause this error. Clear the Update Cache
After that completes, run the DISM repair tool to fix the system image: DISM /Online /Cleanup-Image /RestoreHealth Microsoft Learn 4. Clear the Update Cache