Check the logs again. Open Event Viewer ( eventvwr.msc ), navigate to Applications and Services Logs > Microsoft > Windows > WindowsUpdateClient > Operational . Re-run Windows Update. The 0xc0000035 error should no longer appear.
The error 0xc0000035 occurs when the ETW session tries to start but discovers that a session with the exact same name ( WindowsUpdateTraceLog ) is or has been orphaned by a previous process that crashed without cleaning up.
HKLM\SYSTEM\CurrentControlSet\Control\WMI\AutoLogger\WindowsUpdateTraceLog
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. Check the logs again
If the error persists, the Autologger registry key for the specific session may need deletion.
Again, I get this only when I logoff/logon during s session. I've tried every suggestion mentioned in many forums, including this, Experts Exchange Startup Error in Event Viewer - Microsoft Q&A
Alex led John on a wild goose chase through various system logs, device drivers, and even a detour into the Windows registry. Along the way, they discovered that the laptop had been used by a graphics designer, who had installed a custom graphics driver that was interfering with the Windows Update service. The 0xc0000035 error should no longer appear
Troubleshooting "Session WindowsUpdateTraceLog Failed to Start" (Error 0xC0000035)
Some Microsoft documentation states that 0xc0000035 corresponds to , meaning the system cannot locate necessary configuration or registration information related to the event-tracking session. When Windows Update attempts to start its logging mechanism but cannot find the required registry keys or session objects, this error triggers. In the context of Windows 11 24H2 cumulative updates, the error indicates that the system could not find the necessary registry entries when starting the event-tracking session.
Session "WindowsUpdateTraceLog" failed to start with the following error 0xc0000035 While it looks intimidating, it is often a
has been identified as a conflict source:
One of the most confusing aspects of error 0xc0000035 is that technical sources offer two different interpretations. Understanding both helps pinpoint the actual cause.
Navigate to the following system path: C:\Windows\System32\LogFiles\WMI
Security software interfering with the ETW (Event Tracing for Windows) system.
In the registry address bar, navigate to the following path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\WindowsUpdateTracelog Look for a DWORD value named in the right-hand pane.