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

Rename the temporary update folders to force Windows to create fresh, clean ones. Type these commands:

Run the System File Checker by typing sfc /scannow in an elevated Command Prompt.

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old ren C:\Windows\System32\catroot2 Catroot2.old

Minimize the Command Prompt window. Open File Explorer and navigate to the following folder: C:\Windows\SoftwareDistribution Rename the temporary update folders to force Windows

tool to stop any "ghost" sessions that might be causing the collision. Microsoft Learn In an elevated Command Prompt, type: logman query Look for any session named WindowsUpdateTraceLog or similar. If found, stop it by typing: logman stop "WindowsUpdateTraceLog" -ets 4. Check for Update Health Tool Conflicts Sometimes, a specific tool called Microsoft Update Health Tools causes this specific logging error. Microsoft Learn Installed Apps Search for Microsoft Update Health Tools If it exists, you can try Uninstalling

Fixing Error 0xc0000035: Session "WindowsUpdateTracelog" Failed to Start

Minimize the command window. Open File Explorer and navigate to: C:\Windows\SoftwareDistribution Open File Explorer and navigate to the following

Allow the scan to reach 100% completion. If it reports finding and repairing corrupted files, restart the system immediately. Method 4: Re-evaluate Third-Party Security Software

If you are auditing your Windows Event Viewer logs, you might frequently encounter a critical or error-level log entry under Event ID 2. The error message reads: .

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\WindowsUpdateTracelog Use code with caution. In the right pane, locate the DWORD value named . Check for Update Health Tool Conflicts Sometimes, a

Run the following commands one by one to stop and restart the update components: net stop wuauserv net stop bits net start bits net start wuauserv Microsoft Learn 3. Repair System Files

When your system boots or triggers an update cycle, the Autologger mechanism attempts to spin up this trace session. If a previous instance of the log did not close properly, or if another system process has already claimed that specific logging handle, Windows throws the 0xC0000035 collision error. Step 1: Clear the Windows Update Cache

– Faulty Wi‑Fi or Ethernet drivers may prevent the necessary logging session from initialising, especially if the error is related to network‑aware components.

Fixing Event ID 2: "Session WindowsUpdateTracelog failed to start with the following error: 0xc0000035"

In the object names box, type NT AUTHORITY\SYSTEM and click . Click OK to save.