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

By stopping the conflicting trace session, cleaning autologger registry keys, resetting Windows Update components, and reapplying the correct ETW manifests, you can resolve the error permanently. For repack builders, prevention is best: avoid gutting ETW providers and clean your registry before image capture.

When you see 0xc0000035 with "WindowsUpdateTraceLog", don’t panic – just stop the ghost session and move on. No repacking needed. No repacking needed

The scenario unfolds as follows: The repack script initiates a process that calls for the tracing session. Simultaneously, or perhaps due to a previous failed check, the system believes the session is already active. Because the repack environment modifies standard system behaviors, the normal "stop and restart" logic for these services fails. The result is the STATUS_OBJECT_NAME_COLLISION . The repack script tries to open a door that the system believes is already open, or worse, it tries to create a door where one already stands. To understand why this error occurs

To understand why this error occurs, one must first understand the component at the heart of the message: WindowsUpdateTracelog . The Windows operating system utilizes a high-performance tracing architecture known as Event Tracing for Windows (ETW). ETW allows for the logging of kernel and application events in real-time, providing developers and system engineers with a granular view of system performance and behavior. By stopping the conflicting trace session

⚠️ Do not delete other AutoLogger keys unless you know their purpose.

Open ( services.msc ) and Stop the "Windows Update" service.