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

The SFC scan checks and repairs corrupted system files.

Follow these steps carefully. They are ordered from least to most invasive.

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. The SFC scan checks and repairs corrupted system files

Think of it like trying to park two cars in the same reserved spot – the second car gets the error, not the parking lot.


Once upon a time, in a small IT department, there was a Windows Server named LogiCorp-SRV02. Every morning, the admin, Alex, checked the System Event Log for clues about the server’s health. Once upon a time , in a small

One Tuesday, Alex saw a strange yellow warning:

"Session 'WindowsUpdateTraceLog' failed to start with the following error: 0xc0000035. Repack." Repair image and system files:

Alex frowned. “What’s a ‘repack’? And why can’t a trace log start?”


Background software can lock trace sessions.

Often, a simple service restart clears stale log sessions.

  • Stop a session:
  • Check autologger registry (PowerShell):
  • Repair image and system files: