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

Fix: “Session WindowsUpdateTraceLog Failed to Start with Error 0xc0000035” (Repack Guide)

If you are a Windows system administrator, a PC technician, or an advanced user building custom images (repacks), you may have encountered a cryptic error message while inspecting the Event Viewer or during a sysprep process:

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

Step 3: Test & Verify

Alex reran the update check:

Look for any session named WindowsUpdateTraceLog or a session using GUID that looks update-related. If found, stop it:

Step 4: Reset Windows Update Components (Repack-Safe)

For a repack, you want to clean without breaking customizations. Run these commands in an admin CMD: If found, stop it: Step 4: Reset Windows

Step 5: Re-register the Windows Update ETW Provider

The WindowsUpdateTraceLog session depends on a specific ETW provider. Re-register it:

Method 1: Modify the Autologger Registry Key (Most Effective) Alex saved the logman command in a text

The Happy Ending

LogiCorp-SRV02 started logging Windows Update activity perfectly. Alex saved the logman command in a text file called fix_wutrace.txt, just in case.

Solutions to Resolve the Error