If you’d like me to provide instructions for specific tools like Event Viewer to confirm the fix, or walk through these steps via a remote session, just let me know!
The 0xC0000035 error code, also known as STATUS_OBJECT_NAME_COLLISION , indicates that the tracing session WindowsUpdateTraceLog is trying to start, but the system believes it is already running. This typically happens due to:
Query existing trace sessions to confirm the collision. Type the following command:
In the context of WindowsUpdateTraceLog , Windows tries to start an event‑tracking session for update diagnostics, but that session (or a component with the same name) is already active. The collision prevents the second instance from starting, but the first one continues running normally, so the overall health of your system remains unaffected. If you’d like me to provide instructions for
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\WindowsUpdateTracelog Use code with caution. Look for a DWORD value named in the right pane.
If other solutions fail, you can use the logman command to manually manage ETW sessions.
: Type DISM /Online /Cleanup-Image /RestoreHealth and press Enter to repair the Windows system image. 2. Reset Windows Update Components Type the following command: In the context of
Since the error indicates a naming collision, it often happens because the session is already active. Open (search for it in the Start menu). Navigate to Data Collector Sets > Event Trace Sessions .
– Security suites, driver management tools, and other background applications can sometimes block Windows Update components from starting properly.
net start wuauserv net start cryptSvc net start bits net start msiserver net start EventLog Look for a DWORD value named in the right pane
Did this error start appearing after a ? Are you comfortable using the Windows Registry Editor ? Share public link
If third-party antivirus software or monitoring tools are hooking into the Windows Update Tracelog API, they can cause object name collisions. A clean boot helps isolate this. Press , type msconfig , and click OK .
Stop the update services by entering these commands one by one: net stop wuauserv net stop cryptSvc net stop bits net stop msiserver Rename the cache folders:
Again, I get this only when I logoff/logon during s session. I've tried every suggestion mentioned in many forums, including this, Experts Exchange Startup Error in Event Viewer - Microsoft Q&A