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

The error "" is a common, often benign, notification found within the Windows Event Viewer, frequently occurring on Windows 10 and 11 systems. When this error is associated with a "repack" (a modified, re-packaged version of Windows, often used for unauthorized activation or customization), it typically indicates that the Windows Update/Event Tracking subsystems have been altered or disabled to prevent activation checks or telemetry tracking.

Corrupted update caches often trigger duplicate logging loops. Clearing these components resets the session state.

For a user encountering this, the implications are twofold:

⚠️ Do not delete other AutoLogger keys unless you know their purpose. The error "" is a common, often benign,

While the core issue is always a name collision, several underlying factors can trigger this specific event:

If the Event Viewer continues to generate hundreds of these log errors every minute, you can explicitly disable the redundant logging parameters within the Windows Registry. Press Win + R , type , and hit Enter .

To fix the problem, you must first decode the message. Clearing these components resets the session state

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

This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later.

: The first step should be the Windows Update Troubleshooter, which can automatically detect and clear common logging collisions. Press Win + R , type , and hit Enter

WindowsUpdateTracelog is a specific ETW session dedicated to monitoring the Windows Update process. It acts as a diagnostic conduit, capturing data regarding how the system checks for updates, downloads them, and installs them. Under normal circumstances, this session is initiated by the operating system on-demand or during specific maintenance windows. The system requires exclusive access to the specific log files and buffers associated with this session to ensure data integrity. When the operating system—or a third-party application—attempts to start this tracing session, it calls upon the underlying kernel subsystems to reserve the necessary resources.

Type regedit and press (or click OK) to open the Registry Editor.