Session Windowsupdatetracelog Failed To Start With The Following Error 0xc0000035 ((top)) -

Windows operating systems use Event Viewer to track system health, software performance, and hardware alerts. Among the various logs, you might encounter a persistent error:

Execute the Deployment Image Servicing and Management tool first: DISM.exe /Online /Cleanup-image /Restorehealth Use code with caution. Once finished, run the System File Checker: sfc /scannow Use code with caution.

wevtutil el

Fixing Windows Error 0xC0000035: Session "WindowsUpdateTracelog" Failed to Start

Fixing Event ID 2: Session "WindowsUpdateTracelog" Failed to Start with Error 0xc0000035 Windows operating systems use Event Viewer to track

Stop the core update services by typing the following commands one by one, pressing after each: net stop wuauserv net stop bits net stop cryptsvc Use code with caution.

The WindowsUpdateTracelog is an Event Tracing for Windows (ETW) session. Windows uses it to monitor, log, and debug the background activities of the Windows Update service.

Press Windows Key + S , type , right-click Command Prompt , and select Run as administrator .

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". Press Windows Key + S , type ,

This lists all active trace sessions. Look for any session that might conflict with WindowsUpdateTraceLog .

Use the Deployment Imaging Service and Management (DISM) and System File Checker (SFC) tools to repair corruption. Open as an administrator. Run the following commands one at a time: DISM /Online /Cleanup-Image /RestoreHealth sfc /scannow

Clean ETW/Registry leftovers (advanced; back up registry first)

Error 0xC0000035 regarding WindowsUpdateTracelog is fundamentally an internal housekeeping error where Windows bumps into its own data trails. Clearing out your temporary update files or adjusting the Autologger status in the registry will stop the collision loop, clean up your Event Viewer, and keep your operating system running smoothly. To help narrow down the best next step, please let me know: clean up your Event Viewer

Allow the progress bar to reach 100% (this may take several minutes). Run the System File Checker tool next: sfc /scannow Use code with caution. Restart your computer once the verification finishes. Verifying the Resolution

The primary driver behind this error is a tracking conflict within the Event Trace Sessions.

This specific error occurs when the Windows Operating System attempts to start a diagnostic logging session that is already active, or when there is a naming collision in the kernel trace memory. The hex code 0xC0000035 translates directly to STATUS_OBJECT_NAME_COLLISION .

Open the (search for it in the Start menu). Navigate to Data Collector Sets > Event Trace Sessions .