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

Whether you are using any ? Share public link

Temporarily disable any third-party real-time protection shields.

In plain English, this means a process (usually related to Windows Update or performance monitoring) tried to start a logging session using a name that was already in use by another active session. While it looks intimidating, it is often a benign "noise" entry that can be safely ignored if your system is otherwise running smoothly. Whether you are using any

For persistent cases, use a tool like or Sysinternals WinObj to inspect the \KernelObjects\ namespace for a stale WindowsUpdateTraceLog event handle. No public tool directly deletes these; a reboot is the cleanest solution.

Look for any session named WindowsUpdateTraceLog . If present but not functioning, it may be a stale session. While it looks intimidating, it is often a

Session "WindowsUpdateTraceLog" failed to start with the following error 0xc0000035

Minimize the Command Prompt window and open ( Windows Key + E ). Look for any session named WindowsUpdateTraceLog

Are you seeing this error alongside , or is it just appearing in your Event Viewer ?

If you are encountering other issues alongside this error, please share if your , if you are experiencing system slowdowns , or if you noticed this error after installing specific third-party software . Share public link

Administrator privileges, registry backup performed.

Since the error is caused by an object name collision, deleting the old log files forces Windows to create fresh ones without any conflicts. Press Windows Key + R to open the dialog box.