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

Press Win + S , type , right-click Command Prompt , and choose Run as Administrator .

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\WindowsUpdateTraceLog Use code with caution. Locate the DWORD value in the right-hand pane.

No – both versions handle ETW sessions identically for Windows Update. The fix works across Windows 10/11 and Server 2019/2022. Press Win + S , type , right-click

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

In the context of the , the OS is attempting to start a diagnostic trace log to monitor Windows Update activities. Because a previous trace session failed to close properly, or a duplicate logging instance is already running, the system hits a naming collision and halts. Common Causes of the Error No – both versions handle ETW sessions identically

The term typically refers to custom, stripped-down, or pre-activated ISOs of Windows (such as "ghost" builds, gaming-optimized editions, or light repacks) distributed on forums.

Then restart the service:

: The log buffer allocation is too small to handle the stream of telemetry, causing it to crash and fail to reset cleanly upon reboot.

Press Windows + R , type eventvwr.msc , and press Enter. In the Event Viewer, expand Windows Logs and click on System . Then, click Filter Current Log... on the right side. In the filter dialog, set the Event IDs field to 2 and the Event sources field to Microsoft-Windows-Kernel-EventTracing and click OK . This will show you all relevant errors for this session. Because a previous trace session failed to close

The most direct way to resolve a name collision is to stop the existing session manually. Press Win + R , type perfmon , and hit Enter. Expand on the left sidebar. Click on Startup Event Trace Sessions . Locate WindowsUpdateTracelog in the list. Right-click it and select Stop .