Session Windowsupdatetracelog Failed To Start With The Following Error 0xc0000035 Repack Link

The error 0xc0000035 is a Kernel Event Tracing issue that occurs when Windows attempts to start a logging session (like WindowsUpdateTraceLog or RUXIMLog) but fails because an object with the same name already exists. In technical terms, it is a STATUS_OBJECT_NAME_COLLISION.

Below is a blog-style guide on understanding and resolving this issue. The error 0xc0000035 is a Kernel Event Tracing

Step 6: Repair Windows Image (DISM)

For repack images, an in-place component repair is essential: WindowsUpdateTraceLog: This is a specific Event Tracing for

References and Further Reading

(Normative references typically include Microsoft Docs on ETW, logman, wevtutil, Autologger registry keys, DISM/SFC, and Windows Update troubleshooting.) Wait for the scan to finish

2. Error Breakdown

The Components

• WindowsUpdateTraceLog: This is a specific Event Tracing for Windows (ETW) session used by the Windows Update Agent to log diagnostic information.
• Error Code 0xC0000035: Translated from Hexadecimal, this corresponds to STATUS_OBJECT_NAME_COLLISION (or ERROR_ALREADY_EXISTS in Win32 API terms). This means the system attempted to create an object (a trace session) that already exists.

Wait for the scan to finish. If it repairs files, restart your PC.