Session Windowsupdatetracelog Failed To Start With The | Following Error 0xc0000035 Repack
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.
“Repack”
In the context of this error, “repack” refers to a custom Windows image — for example, a modified .wim or .esd file created with tools like NTLite, MSMG Toolkit, or DISM. Repacking often involves removing components, integrating updates, or altering services. This process commonly triggers the error. The error 0xc0000035 is a Kernel Event Tracing
To troubleshoot and resolve the "Session Windows Update Trace Log failed to start with the following error: 0xc0000035" issue, follow these steps: WindowsUpdateTraceLog: This is a specific Event Tracing for
Here’s a detailed guide to understanding and resolving the error: “Session WindowsUpdateTraceLog failed to start with the following error 0xc0000035 repack”. Step 2: Stop the Ghost Session logman stop
Since this error usually just means a duplicate process is trying to run, it’s often harmless. However, if it’s cluttering your Event Viewer, you can "clear the office" by following these steps:
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old ren C:\Windows\System32\catroot2 Catroot2.old Restart the services: net start wuauserv net start bits 3. Modify the Registry (For Advanced Users)
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(orERROR_ALREADY_EXISTSin Win32 API terms). This means the system attempted to create an object (a trace session) that already exists.
Step 2: Stop the Ghost Session
logman stop WindowsUpdateTraceLog -ets