ETW is a high-performance logging mechanism built into the operating system. It allows services like Windows Update to log diagnostic data without slowing down the system.
Introduction Windows Update is the lifeblood of system security and feature stability on Microsoft operating systems. However, it is also notoriously sensitive to corruption, misconfigurations, and resource conflicts. One of the more cryptic errors that administrators and users encounter when digging into the WindowsUpdate.log or the Event Viewer is: "Session "WindowsUpdateTraceLog" failed to start with the following error 0xc0000035." At first glance, this error looks like a critical system failure. The hexadecimal code 0xc0000035 can be intimidating, but it is a well-known status code in the Windows kernel: STATUS_OBJECT_NAME_COLLISION . In plain English, this means "a file, registry key, or object with that name already exists."
net start wuauserv net start cryptSvc net start bits net start msiserver ETW is a high-performance logging mechanism built into
Stop the offending session. If you see WindowsUpdateTraceLog listed, stop it with:
By using the logman tool to manually stop the duplicated ETW session, you can resolve the collision in under 30 seconds. Windows Update will immediately regain its ability to download and install updates. However, it is also notoriously sensitive to corruption,
A: No. If you ignore it, Windows Update will remain in a degraded state. You won't receive security patches, leaving your system vulnerable.
Query existing trace sessions to confirm the collision. Type the following command: In plain English, this means "a file, registry
Open an elevated Command Prompt. Press Win + X , then select "Terminal (Admin)" or "Command Prompt (Admin)."