Session Windowsupdatetracelog Failed To Start With The Following Error 0xc0000035 Direct

The error is a "Status Object Name Collision" . It typically means the Windows Update Trace Logger tried to start, but a session with that same name was already running. Is this serious? In most cases, no .

logman is a built-in Windows command-line tool designed to manage ETW sessions. This is the most surgical and effective method.

If you are auditing your Windows Event Viewer logs, you might frequently encounter a critical or error-level log entry under Event ID 2. The error message reads: . The error is a "Status Object Name Collision"

Purging the update cache removes corrupted files that might be forcing the tracing tool into a collision state.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\WindowsUpdateTracelog Use code with caution. In the right pane, locate the DWORD value named . In most cases, no

For persistent cases, use a tool like or Sysinternals WinObj to inspect the \KernelObjects\ namespace for a stale WindowsUpdateTraceLog event handle. No public tool directly deletes these; a reboot is the cleanest solution.

Select all files and folders inside this directory ( Ctrl + A ) and delete them. Return to your command window and restart the services: net start wuauserv net start bits Use code with caution. Step 2: Modify the Autologger Registry Settings If you are auditing your Windows Event Viewer

Here is how I fixed it (and you can too):

Once complete, read the command prompt output to verify if corruption was found and repaired, then reboot your PC. Method 4: Clean Boot Troubleshooting