Session Windowsupdatetracelog Failed To Start With The Following Error 0xc0000035 Hot! May 2026
0xc0000035 (STATUS_OBJECT_NAME_COLLISION) occurs when the system tries to start a logging session, but an object with that same name already exists or is still in use. For WindowsUpdateTraceLog , this usually means
- Corrupted Trace Files: The log file (
.etlfile) created during a previous session wasn't closed properly (perhaps during a crash or power loss), leaving it in a "locked" or corrupt state. - Antivirus Interference: Sometimes, over-protective antivirus software locks a log file to scan it and refuses to release it before Windows tries to write to it again.
- Leftover Registry Keys: The system registry believes the session is "active" even though it isn't, preventing a new start command from executing.
logman stop "Windows Update Trace Log" -ets Corrupted Trace Files: The log file (
5. Last resort — Reboot into Safe Mode
The neon hum of the server room was the only heartbeat in the building. Elias sat hunched over Terminal 4, his eyes reflecting a cascade of scrolling text. He was hunting a ghost in the machine, a silent killer of productivity that had paralyzed the regional grid. Then, it appeared in cold, unfeeling white text: logman stop "Windows Update Trace Log" -ets 5
Delete the contents of the RtBackup folder and restart your PC. Windows will recreate these files cleanly upon reboot. 3. Restart the Windows Update Services Sometimes the service responsible for the trace is hung. it appeared in cold