Session Windowsupdatetracelog Failed To Start With The Following Error 0xc0000035

Navigate to the following path using the left sidebar: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\WindowsUpdateTracelog Look for a DWORD value named in the right-hand pane.

Before investing time in troubleshooting, verify if the error is affecting system functionality:

Some antivirus programs (e.g., McAfee, Norton, Bitdefender, or even some VPN filters) hook into the ETW subsystem to monitor network and process activity. If they hold a lock on the trace log object, 0xc0000035 occurs.

Optional but recommended: Look for the or LogFileMode settings in the same folder. Ensure your user account has full permissions over this registry key by right-clicking the WindowsUpdateTracelog folder, selecting Permissions , and verifying SYSTEM and Administrators have Full Control. Close the Registry Editor and restart your computer. Navigate to the following path using the left

net start wuauserv net start cryptSvc net start bits net start msiserver Use code with caution. 2. Modify the Autologger Registry Settings

logman delete "SessionName"

Outdated network drivers, particularly for Intel Wi-Fi adapters, are known to conflict with kernel processes and cause this error. Optional but recommended: Look for the or LogFileMode

0xc0000035 (STATUS_OBJECT_NAME_COLLISION) occurs when the Windows Event Tracing (ETW) system attempts to start a logging session with a name that is already in use. For WindowsUpdateTracelog

John smiled, feeling grateful for the unexpected detour. He realized that sometimes, the most seemingly insurmountable errors require a dash of creativity and a pinch of whimsy to solve. And he made a mental note to keep Alex's number handy for the next time he encountered a mysterious error message.

If none of the above solutions work and the error is accompanied by system instability, an in‑place upgrade can refresh your Windows installation without deleting personal files. net start wuauserv net start cryptSvc net start

Windows attempts to write to a log file that is already locked or corrupted.

Third-party apps, especially security software, can interfere with Windows processes. Performing a clean boot starts Windows with a minimal set of drivers and startup programs, allowing you to see if the error is caused by a background application.

: This stops the specific logging but does not impact the actual delivery of updates. Troubleshoot problems updating Windows - Microsoft Support