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

Open an administrative Command Prompt and run logman query -ets . If you see a WindowsUpdateTraceLog session in a “Running” or stale state, stop it immediately. Then, smile — you’ve just fixed the problem.

Sometimes, the simplest fix is to reset the logging infrastructure. This can clear out temporary "ghost" sessions. Open an administrative Command Prompt and run logman

When the Windows Update service attempts to start a new trace log session (specifically the "WindowsUpdateTraceLog" Event Tracing for Windows (ETW) session), it tries to create a unique object name. The error occurs when that name already exists in the system’s object namespace but is in a stalled, dead, or inaccessible state. Sometimes, the simplest fix is to reset the

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old ren C:\Windows\System32\catroot2 catroot2.old Restart the services: net start wuauserv net start cryptSvc 3. Repair System Image & Files The error occurs when that name already exists

Are you experiencing any with updates failing to install, or are you just seeing this error in your Event Viewer ?

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