= STATUS_OBJECT_NAME_COLLISION ), meaning the session name already exists or the log file is being accessed simultaneously by another process.
The WindowsUpdateTraceLog error with code 0xC0000035 is a solvable system glitch. By methodically working through the fixes—starting with the DISM/SFC repair and moving to the targeted registry cleanup—you can eliminate the error messages from your Event Viewer. In many cases, a simple restart or running the Windows Update troubleshooter is all that's needed. If you encounter the error after a recent OS update, rest assured that Microsoft has provided official registry fixes that can swiftly resolve the conflict and restore normal functionality.
In plain English, this means that the operating system tried to create a new session, task, or file with a specific name, but another active session or file was already using that exact same name. Because two things cannot occupy the exact same space in the system's registry or memory under the same identifier, the system fails to start the new session and throws this error. In many cases, a simple restart or running
| Method | Difficulty | Time | Primary Benefit | | :--- | :--- | :--- | :--- | | | Low | 10-20 min | Repairs corrupted system files | | DISM RestoreHealth | Medium | 20-30 min | Repairs the underlying system image | | Reset Windows Update | Low | 10 min | Clears corrupted update caches | | logman command | High | 5-10 min | Directly deletes problematic ETW sessions | | Registry Key Modification | High | 5 min | Stops the specific error from being logged | | In-Place Upgrade | High | 1-2 hours | Repairs deep system corruption |
) typically means that Windows tried to start a logging session with a name that was already in use by an existing session. In most cases, this error is harmless and occurs during a normal reboot or update process when a previous session didn't shut down cleanly before a new one tried to start. Microsoft Learn Because two things cannot occupy the exact same
Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\AutoLogger\EventLog-System . Locate the and EnableProperty keys. Double-click each and change the Value Data from 1 to 0 . Restart your computer for changes to take effect. 3. Reset Windows Update Components
For a stable system, it is highly recommended to use a clean install of Windows from official sources. This is the most common fix
This is the most common fix, which stops the system from trying to launch the failing logger session. Press Win + R , type regedit , and hit Enter.
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
The error code is formally defined as STATUS_OBJECT_NAME_COLLISION , which indicates that a logging session or file name that Windows tried to create already exists . In the context of WindowsUpdateTracelog (or related logs like RUXIMLog ), this usually occurs during a system restart when Windows attempts to start a diagnostic trace that didn't shut down or clean up properly in the previous session.
