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

The Windows Performance Library or diagnostic tools may attempt to launch duplicate instances of the same log.

If you installed a modified Windows ISO (repack), the creator may have disabled or stripped certain telemetry components.

if ($sessions) Write-Host "Found conflicting session – removing..." logman stop $sessionName -ets logman delete $sessionName -ets

If the error persists, you can disable this specific trace session from starting automatically. This will not stop Windows Updates from downloading; it only stops the diagnostic tracking log. Press Windows Key + R , type regedit , and hit Enter. Click , close the Registry Editor, and restart your computer

This means that the Event Trace Session manager tried to create a new logging session using a specific name or memory allocation, but an existing session or temporary file was already using that exact identity. Because two things cannot occupy the same namespace simultaneously, the system aborts the process and logs the error.

The most immediate fix is to prevent the service from starting during the capture. Before starting your repackaging tool:

If you’re a repacker creating custom images, here’s how to avoid 0xc0000035 entirely:

: This built-in tool can reset common update components automatically. Find it in Settings > Update & Security > Troubleshoot > Additional troubleshooters . This means that the Event Trace Session manager

If you notice this error consistently popping up when you boot your PC, it is highly likely that a third-party startup program, antivirus, or background utility is clashing with the Windows Update logging service. Press , type msconfig , and hit Enter . Under the General tab, select Selective startup . Ensure Load startup items is unchecked.

The most direct way to solve this is to disable the specific logging session that is causing the collision.

When you see 0xc0000035 with "WindowsUpdateTraceLog", don’t panic – just stop the ghost session and move on. No repacking needed.

If your system is experiencing slowdowns, frozen updates, or repetitive log bloat, follow these step-by-step methods to resolve the naming collision. 1. Clear the Windows Update Cache locate the Start DWORD value.

For a repack, you want to clean without breaking customizations. Run these commands in an admin CMD:

The error 0xc0000035 during a repack indicates a conflict over the WindowsUpdateTraceLog ETW session. It is rarely

Then checked the event log again – no more 0xc0000035 errors. The log session started cleanly.

Navigate to the following registry path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\WindowsUpdateTracelog In the right pane, locate the Start DWORD value.