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

Corrupted temporary update files frequently cause the tracking logger to glitch. Resetting the update components clears out these stuck processes.

"Object Name Already Exists," Elias whispered, the translation of the hex code bitter on his tongue.

The error 0xc0000035 appears in the under Microsoft-Windows-Kernel-EventTracing/Admin with Event ID 2 . The message indicates that the system's Windows Update event-tracing session failed to initialize properly. The error can involve several session names, including "WindowsUpdate_trace_log," "Microsoft.Windows.WindowsUpdate.RUXIMLog," "Circular Kernel Context Logger," and "Microsoft.Windows.Remediation". Reboot normally

Reboot normally.

Stale files in the Performance Monitor prevent new sessions from initiating. Here are a few:

Stop the core update services by typing the following commands one by one, pressing after each:

session windowsupdatetracelog failed to start with the following error 0xc0000035 " "Circular Kernel Context Logger

Fortunately, there are several potential solutions to resolve the "Session WindowsUpdateTrackLog failed to start with the following error 0xc0000035" error. Here are a few: