Session Windowsupdatetracelog Failed To Start With The Following Error 0xc0000035 May 2026

Observed Error Message:
Session "WindowsUpdateTraceLog" failed to start with the following error 0xc0000035

Hexadecimal Code: 0xc0000035
NTSTATUS Equivalent: STATUS_OBJECT_NAME_COLLISION
Human-Readable Meaning: "A file, registry key, or object with the same name already exists."

Corrupt system files—especially those related to ETW (Event Tracing for Windows)—can cause this error. Check for duplicate ETW sessions (see Diagnostics below)


A: No. Methods 1, 2, 4, 5, 6, and 7 preserve update history. Method 3 (renaming SoftwareDistribution) resets history, but your installed updates remain intact.

The hexadecimal code 0xc0000035 translates to STATUS_OBJECT_NAME_COLLISION. A: No. Methods 1

In plain English, this means the system tried to create or start an object (in this case, a log file or a trace session), but an object with that name already exists, or the system believes it is already active. It is the computer equivalent of trying to create a new folder named "New Folder" when a folder with that exact name is already sitting right there on your desktop.

Microsoft includes a built-in troubleshooter that can diagnose and fix ETW session failures. Check for duplicate ETW sessions (see Diagnostics below)


  • Check for duplicate ETW sessions (see Diagnostics below) and stop the offending session.
  • Open Command Prompt as Administrator and run:

    net stop wuauserv
    net stop bits
    net stop dosvc
    

    logman stop "Windows Update Trace Log" -ets

    net start wuauserv net start bits net start dosvc