Session Windowsupdatetracelog Failed To Start With The Following Error 0xc0000035

sc query wuauserv

"Object Name Already Exists," Elias whispered, the translation of the hex code bitter on his tongue.

At first glance, this looks like a critical system failure. You might worry that your Windows Update mechanism is broken or that your hard drive is failing. While those can be issues, this specific error is usually related to a configuration conflict within the Windows Event Tracing (ETW) system.

If your computer is otherwise updating and running normally, this error is often harmless and can be safely ignored sc query wuauserv "Object Name Already Exists," Elias

This means that the Kernel Event Tracer tried to spin up a new logging session using a specific name or identifier, but another active process or an orphaned registry key was already using that exact same name or memory space. Because two items cannot share the same identifier, the startup sequence fails and triggers the event log entry. Common Causes of the Error

If the error persists, aggressive heuristic engines in third-party antivirus suites may be holding onto the ETW handle for WindowsUpdateTracelog .

Corrupted system files can cause logging conflicts. You can fix them using the Command Prompt Right-click the button and select Command Prompt (Admin) Windows Terminal (Admin) sfc /scannow Once finished, type the following and press DISM /Online /Cleanup-Image /RestoreHealth 3. Clear the Windows Update Cache While those can be issues, this specific error

Press Windows Key + R , type regedit , and press to open the Registry Editor.

If third-party antivirus software or monitoring tools are hooking into the Windows Update Tracelog API, they can cause object name collisions. A clean boot helps isolate this. Press , type msconfig , and click OK .

Incorrect parameters inside the Windows Management Instrumentation (WMI) Autologger registry keys can cause the system to spin up duplicate tracing tasks at startup. Common Causes of the Error If the error

To solve the problem, we first need to understand the components involved.

This error is related to logging the update process, not the update process itself. Think of it like a flight recorder (black box) on an airplane. If the black box is broken, the flight recorder cannot start. However, the airplane can usually still fly just fine.