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

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old ren C:\Windows\System32\catroot2 catroot2.old Use code with caution. Restart the core services:

However, for users running heavily modified "repack" versions of Windows, the issue may be systemic. If the Windows Update binaries themselves have been stripped from the OS to save space, the error will recur indefinitely because the system is trying to perform a function (tracing updates) that the operating system is no longer capable of supporting due to missing components. In such cases, the only true remediation is the restoration of the missing system files via a System File Checker ( sfc /scannow ) or, more drastically, a reinstallation of a complete, unmodified version of Windows.

Go to > Troubleshoot (on Windows 11) or Update & Security > Troubleshoot (on Windows 10). Click on Other troubleshooters (if applicable). ren C:\Windows\SoftwareDistribution SoftwareDistribution

This error typically appears in the Windows Event Viewer as a event (ID 2), indicating that a specific logging session failed to initialize because of a naming conflict or missing configuration. In the context of "WindowsUpdateTraceLog," this usually means the system tried to start a trace session that was already active or whose temporary log file was locked. What Error 0xc0000035 Means

If you are seeing this error frequently in your Event Viewer logs, this comprehensive guide will explain what causes it and how to fix it permanently. What is Error 0xc0000035? In such cases, the only true remediation is

When the Operating System attempts to start a specific logging session—in this case, the WindowsUpdateTracelog —it tries to register a unique security identifier (SID), naming context, or memory allocation block. If another active process or a previously orphaned session is already using that exact resource name, a collision occurs. The system enters a deadlock for that specific logging thread, terminates the startup sequence, and records the failure in your Event Viewer. Common Causes of the Tracelog Failure

If the above fails, the collision might be in the global ETW controller. Use this PowerShell script to list and force-remove any duplicate sessions: This error typically appears in the Windows Event

The error "Session Windows Update Trace Log failed to start with the following error 0xc0000035" can be a challenging issue to resolve. However, by following the troubleshooting steps and repacking methods outlined in this article, you should be able to resolve the issue and get your Windows updates back on track. If you are still experiencing issues, you may need to seek further assistance from Microsoft Support or a qualified IT professional.

A service, specifically WindowsUpdateTraceLog or a similar tracing session (like Microsoft-Windows-Remediation or PerfDiag Logger ), is trying to start, but the kernel detects that the name of that logger session is already active or used by another service.

Double-click the DWORD value and also set its Value Data to 0 . Close the editor and Restart your PC. 2. Terminate Conflicting ETW Sessions via Command Prompt