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

Alex opened Command Prompt as Administrator and ran:

logman query

Right there, under "Data Collector Sets", was WindowsUpdateTraceLog – stuck in a "Running" state, even though no updates were active.

"Repackaging" inherently involves monitoring file and registry changes. Some third-party monitoring tools (legacy App-V sequencers or specific antivirus software) may hook into ETW providers. If the repackaging tool attempts to capture all system activity, it may clash with the Windows Update service's attempt to write to its own log file (WindowsUpdateTraceLog.etl), resulting in a handle collision.

The word "repack" in the error text is just internal Windows jargon. It doesn’t mean you need to reinstall Windows or repack anything manually. It simply means Windows tried to restart an existing trace session but found a duplicate name.

Think of it like trying to park two cars in the same reserved spot – the second car gets the error, not the parking lot. Alex opened Command Prompt as Administrator and ran:

The error code 0xc0000035 is technically defined as STATUS_OBJECT_NAME_COLLISION, which indicates that a tracking session or logger is attempting to start using a name that is already in use by the system. In the context of "WindowsUpdateTracelog," this often occurs during routine background maintenance or updates and is generally considered benign unless you are experiencing active system instability or update failures. Understanding the Error

When Windows Update or performance diagnostic tools attempt to initiate a Kernel Event Tracing session, they may encounter this collision if a previous session didn't close properly or if multiple services are requesting the same log name simultaneously. Recommended Solutions

If this error is cluttering your Event Viewer or causing noticeable performance dips, you can resolve it through several standard Windows repair methods:

Run Built-in Troubleshooters: The first step should be the Windows Update Troubleshooter, which can automatically detect and clear common logging collisions. The error code 0xc0000035 is technically defined as

Repair System Files: Use the System File Checker (SFC) and Deployment Image Servicing and Management (DISM) tools to repair corrupted registry keys or system files that might be triggering the collision: Open Command Prompt as an Administrator. Run sfc /scannow.

Once complete, run DISM /Online /Cleanup-Image /RestoreHealth.

Reset Update Cache: If the collision persists, clearing the update cache can force a "clean" restart of the logging session. This is done by stopping the Windows Update service and clearing the C:\Windows\SoftwareDistribution folder.

Registry Modification (Advanced): Some users resolve the persistent trace log error by navigating to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\AutoLogger\EventLog-System and setting the Enabled and EnableProperty values to 0. Note: Always back up your registry before making changes. under "Data Collector Sets"

If your system is otherwise stable and updates are installing successfully, many Microsoft Community Experts suggest that this specific log error can be safely ignored.

Are you experiencing any specific performance issues like slow boot times or failed updates alongside this error?

To update drivers:

Sometimes the error is not the session object, but the physical log file (WindowsUpdateTraceLog.etl) being locked.

Alex took a deep breath and followed three simple steps: