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

After deployment, Windows will re-create the trace session automatically when Windows Update runs.

So the message means: Windows tried to start the ETW session for logging Windows Updates, but another session or system component already holds that resource. After deployment, Windows will re-create the trace session

Alex took a deep breath and followed three simple steps: Locate the and EnableProperty keys

Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\AutoLogger\EventLog-System . Locate the and EnableProperty keys. Double-click each and change the Value Data from 1 to 0 . Restart your computer for changes to take effect. 3. Reset Windows Update Components The error you're encountering

The Windows Event error 0xc0000035 typically denotes STATUS_OBJECT_NAME_COLLISION — an attempt to create an object (file, named pipe, event, session, or registry key) which already exists. When observed for the WindowsUpdateTraceLog session (part of Windows Event Tracing for Windows, ETW), the error prevents trace collection for Windows Update diagnostics and may indicate resource/name collisions, leftover state from previous tracing sessions, improper shutdown, or interfering third‑party software.

The error you're encountering, Kernel-EventTracing Event ID 2 with the message "Session 'SensorFramework-{d61722cd-d3ce-0897-1694- Microsoft Learn

The Windows Update Trace Log is a valuable tool for system administrators and power users to diagnose and troubleshoot issues related to Windows updates. However, sometimes this log may fail to start, hindering the troubleshooting process. One such error that users may encounter is "Session Windows Update Trace Log failed to start with the following error: 0xc0000035." In this article, we will explore the possible causes of this error and provide step-by-step solutions to resolve the issue, specifically focusing on the "repack" aspect.