Delivering across India
Fast dispatch from trusted warehouses, every day

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

Press Windows Key + X and select or Command Prompt (Admin) .

Corrupt system files—especially those related to ETW (Event Tracing for Windows)—can cause this error.

Close Task Manager, click and OK in the System Configuration window, and restart your computer.

: This specific hexadecimal code translates to STATUS_OBJECT_NAME_COLLISION . In simple terms, Windows is trying to create a logging object or session that already exists in the system memory. Method 1: Delete the Overlapping Performance Logs Press Windows Key + X and select or Command Prompt (Admin)

“Session 'WindowsUpdateTracelog' failed to start with the following error: 0xc0000035”

A: Microsoft's documentation and support forums contain references to both interpretations. For practical purposes, both point toward the same underlying issue: a mismatch between what the Windows Update trace service expects and what actually exists in the system configuration.

Open and navigate to: C:\Windows\System32\LogFiles\WMI Locate the folder named RtBackup . For practical purposes, both point toward the same

If the error is flooding your Event Viewer and you want to stop it specifically:

The 0xC0000035 error, while annoying to see in the Event Viewer, is often a harmless log entry caused by a simple name conflict within Windows' system tracing. For many users, the error can be safely ignored.

This is always a good first step. It can automatically detect and resolve common issues with Windows Update components. to see if the error persists.

This is a nuclear but highly effective option. It resets the Windows Update client to a clean state.

Editing the registry can be risky. Always back up your registry or create a system restore point before proceeding.

An explanation and guide for resolving the "Session 'WindowsUpdateTracelog' failed to start with the following error: 0xC0000035" system event. Understanding the Error

After running both, to see if the error persists.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\AutoLogger