Create a batch script or run these commands sequentially in an elevated Command Prompt:
Stop the offending session. If you see WindowsUpdateTraceLog listed, stop it with: Create a batch script or run these commands
net stop wuauserv net stop cryptSvc net stop bits net stop msiserver ren C:\Windows\System32\catroot2 catroot2.old ren C:\Windows\SoftwareDistribution SoftwareDistribution.old Introduction Windows Update is the lifeblood of system
If the problem persists after following all three methods in this guide, the issue may be a corrupted Windows Imaging Component (WIC) or a failing storage drive. At that point, running an (installing Windows from a USB drive while keeping apps and data) is the recommended final step before a clean installation. The hexadecimal code 0xc0000035 can be intimidating, but
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."
You must have Administrator privileges . Log in as an administrator or right-click Command Prompt/PowerShell > "Run as administrator." Method 1: Using Logman (The Official ETW Controller) logman is a built-in Windows command-line tool designed to manage ETW sessions. This is the most surgical and effective method.