Session Windowsupdatetracelog Failed To Start With The Following Error 0xc0000035 Repack
If logman fails, reset ETW via WPR:
To fix a problem, you must first understand it. The code 0xC0000035 is a hexadecimal (computer-readable) error code. When translated, it corresponds to STATUS_OBJECT_NAME_NOT_FOUND . In plain English, this means that a specific program or process (in this case, the Windows Update tracing service) attempted to access a data object—like a system file, a registry key, or a configuration setting—but the system could not locate it.
In simple terms, the system is attempting to start a background telemetry trace log that is or was not properly closed during a previous user session or reboot. While this Event ID 2 error looks alarming, it rarely impacts day-to-day PC performance or stops updates from downloading. However, it can clutter logs and occasionally signal hidden file corruption. What Causes Error 0xc0000035? If logman fails, reset ETW via WPR: To
This paper analyzes the Windows event indicating "Session WindowsUpdateTraceLog failed to start with the following error 0xc0000035 repack". It examines root causes, diagnostic steps, and remediation approaches, and provides a reproducible troubleshooting workflow and preventive recommendations.
Press Windows Key + R , type cmd , and press Ctrl + Shift + Enter to open an . In plain English, this means that a specific
Often, a simple service restart clears stale log sessions.
net start wuauserv net start cryptSvc net start bits net start msiserver However, it can clutter logs and occasionally signal
Before diving into complex procedures, perform these quick checks as they might instantly resolve the issue:
Use from Sysinternals (Microsoft) to see if another process holds the trace session:
Then rebuild the ETW manifest:
This error typically appears in or during system repairs (e.g., using DISM or SFC), especially after a Windows update fails or a system image corruption occurs. The error code 0xc0000035 means STATUS_OBJECT_NAME_COLLISION – essentially, a duplicate object name exists (e.g., two processes trying to use the same log session name).










