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

net start wuauserv net start cryptSvc net start bits net start msiserver

You must have Administrator privileges . Log in as an administrator or right-click Command Prompt/PowerShell > "Run as administrator." Method 1: Using Logman (The Official ETW Controller) logman is a built-in Windows command-line tool designed to manage ETW sessions. This is the most surgical and effective method. net start wuauserv net start cryptSvc net start

logman stop "WindowsUpdateTraceLog" -ets The -ets flag tells logman to talk directly to the Event Tracing subsystem. logman stop "WindowsUpdateTraceLog" -ets The -ets flag tells

Query existing trace sessions to confirm the collision. Type the following command: Run schtasks

net stop wuauserv net stop cryptSvc net stop bits net stop msiserver ren C:\Windows\System32\catroot2 catroot2.old ren C:\Windows\SoftwareDistribution SoftwareDistribution.old

A: This indicates a persistent scheduler or task is trying to start the trace session twice. Run schtasks.exe and look for any custom update-related tasks. Also, check for remnants of older Windows Update agents in C:\ProgramData\Microsoft\Diagnosis\ETLLogs . Conclusion The error "Session WindowsUpdateTraceLog failed to start with the following error 0xc0000035" is fundamentally a communication breakdown within Windows' own logging infrastructure. While the cryptic error code suggests a deep registry failure, the reality is far more manageable.