Session Windowsupdatetracelog Failed To Start With The Following Error 0xc0000035 Repack ((new))
FIXED: Session "WindowsUpdateTraceLog" Failed to Start with Error 0xc0000035
Applies to: Windows 10, Windows 11, Windows Server 2016/2019/2022
- Open
regedit
- Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger
- Look for a child key named WindowsUpdateTraceLog. If it exists, delete it.
- Also check:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\... for orphaned update channels (less common, but delete if present).
Since this is a naming collision error during the boot-up or startup trace logging, disabling or resetting the specific autologger session in the Windows Registry is often the most direct fix. Press the Windows Key + R to open the Run dialog box. Type regedit and press Enter to open the Registry Editor. Since this is a naming collision error during
- Get-ChildItem 'HKLM:\SYSTEM\CurrentControlSet\Control\WMI\Autologger'
What Causes This Error?
- A corrupted Windows Update trace log session.
- Previous Windows Update or servicing stack repairs left orphaned log session handles.
- Using deployment tools (DISM, SFC) while Windows Update is in a conflicted state.
- Third-party software interfering with Windows trace logging (e.g., antivirus, performance monitors).
