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

Click , close the Registry Editor, and restart your computer. Method 3: Run SFC and DISM Repairs

In the Windows subsystem, the hex code 0xc0000035 translates directly to STATUS_OBJECT_NAME_COLLISION .

Repairing corrupted system files often clears up logging conflicts. Microsoft Learn Command Prompt as an Administrator. Run the System File Checker: sfc /scannow Once finished, run the Deployment Image tool: DISM /Online /Cleanup-Image /RestoreHealth 2. Reset Windows Update Components Click , close the Registry Editor, and restart your computer

Navigate to the following path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger

$sessionName = "WindowsUpdateTraceLog" $sessions = logman query -ets | Select-String $sessionName -Context 0,2 Microsoft Learn Command Prompt as an Administrator

Corrupted system files are a primary suspect. Use the Deployment Imaging and Service Management (DISM) tool and the System File Checker (SFC) to repair them.

How to Fix Session WindowsUpdateTracelog Failed to Start with Error 0xc0000035 Use the Deployment Imaging and Service Management (DISM)

If you would like to pinpoint the exact root cause on your machine, please let me know: Which are you currently running?

Error 0xc0000035 for WindowsUpdateTraceLog signals a name collision—commonly a stale or duplicate ETW session. Resolution focuses on identifying and removing the conflicting session or registry entries, restarting services (or the system), repairing system components, and capturing diagnostics if the cause remains unclear.