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

Troubleshooting: "session windowsupdatetracelog failed to start with the following error 0xc0000035"

This document explains what the error means, why it happens, and gives a clear, step-by-step plan to fix it. It’s written for Windows system administrators and power users who want a fast, practical resolution with optional diagnostics and prevention tips.

• PowerShell:

  wevtutil.exe enum-logs
  

  or

  logman query providers
  wevtutil el
  

• Using logman to list sessions:

  logman query -ets
  

If you see "WindowsUpdateTraceLog" in the list, stop it by typing:logman stop "WindowsUpdateTraceLog" -ets. PowerShell: wevtutil

Registry check

$path = "HKLM:\SYSTEM\CurrentControlSet\Control\WMI\AutoLogger\WindowsUpdateTraceLog" if (Test-Path $path) Write-Host "AutoLogger exists" -ForegroundColor Yellow or logman query providers wevtutil el

7. Related Error Codes

| Error Code | Meaning | Typical Cause | |------------|---------|----------------| | 0xc0000034 | STATUS_OBJECT_NAME_NOT_FOUND | Missing AutoLogger registry key | | 0xc0000035 | STATUS_OBJECT_NAME_COLLISION | Duplicate session name | | 0xc0000022 | STATUS_ACCESS_DENIED | Insufficient permissions for ETW | Reboot after completion.

logman stop <SessionName> -ets

wevtutil.exe stop <ChannelName>

If you want, I can:

• Open elevated PowerShell or CMD:

  sfc /scannow
  DISM /Online /Cleanup-Image /RestoreHealth
  

• Reboot after completion.