The core of the issue lies in the status code .
If the above doesn’t help, run:
In the context of an ETW session (specifically WindowsUpdate_trace_log ), this error does not imply that two sessions have the same "Friendly Name," but rather that the specified for the trace (e.g., WindowsUpdate_trace_log.etl ) is currently locked by a system process or was not properly cleaned up during a previous session crash. The core of the issue lies in the status code
If the error persists but your updates are working fine, you can stop the specific trace session from attempting to start at boot. Press Win + R , type regedit , and hit Enter.
Would you like help determining why that trace log is being started (e.g., is something trying to enable diagnostic logging automatically)? Press Win + R , type regedit , and hit Enter
Here’s what’s likely happening and how to fix it:
If the logging session is stuck because the update service is confused, a full reset often clears the "collision." Open as Administrator. Stop the services by typing: net stop wuauserv net stop cryptSvc net stop bits net stop msiserver Stop the services by typing: net stop wuauserv
ETW sessions are managed by the kernel and require specific file handles and memory buffers to operate. If a session is requested with a file path that is currently inaccessible or locked by another process, the Session Manager cannot initialize the logger.
The error 0xc0000035 in Windows, particularly when related to windowsupdate_trace_log or Windows Update components, typically means or "The network response was not in the expected format" or sometimes "The path was not found" depending on context.
Navigate to: