This document explains what the error means, why it happens, and gives a clear, step-by-step plan to fix it. It’s written for Windows system administrators and power users who want a fast, practical resolution with optional diagnostics and prevention tips.
For administrators who prefer a GUI over command lines:
Win + R, type perfmon.msc, and press Enter.WindowsUpdateTraceLog in the list.You are most likely to see this error if:
The error 0xc0000035 associated with the failure to start the WindowsUpdateTraceLog session indicates a specific naming conflict within the Windows Event Tracing for Windows (ETW) subsystem. When the Windows Update service attempts to start an ETW trace session for diagnostic logging, it fails because an AutoLogger session with the same name is already registered in the registry but not active, or a stale session entry exists. This paper details the root cause, diagnostic steps, and resolution methods for this error.
If you want, I can provide exact commands for your Windows version (Windows 10, 11, Server) and a ready-to-run PowerShell script to automate the diagnostics and common fixes — tell me which OS you’re on.
Introduction
The "Session WindowsUpdateTrackLog failed to start with the following error 0xc0000035" error is a frustrating issue that can occur on Windows operating systems. This error is related to the Windows Update service, which is responsible for keeping the operating system and installed software up-to-date with the latest security patches and features. In this essay, we will explore the causes and potential solutions to this error, as well as discuss the implications of this issue on system performance and security.
Understanding the Error
The error code 0xc0000035 is a Windows error code that indicates a STATUS_ACCESS_DENIED exception. This means that the Windows Update service is unable to access a required resource or registry key, preventing it from starting the WindowsUpdateTrackLog session. The WindowsUpdateTrackLog session is responsible for tracking and logging Windows updates, which is essential for troubleshooting and debugging purposes.
Causes of the Error
Several factors can contribute to the occurrence of this error. One possible cause is corrupted registry entries or missing registry keys required by the Windows Update service. Malware infections or viruses can also cause this error by modifying system files and registry entries. Additionally, issues with system files, such as corrupted or missing files, can prevent the Windows Update service from functioning correctly. Conflicting software or third-party applications can also interfere with the Windows Update service, leading to this error.
Solutions to the Error
Fortunately, there are several potential solutions to resolve the "Session WindowsUpdateTrackLog failed to start with the following error 0xc0000035" error. Here are a few:
Implications of the Error
The "Session WindowsUpdateTrackLog failed to start with the following error 0xc0000035" error can have significant implications on system performance and security. Without a functioning Windows Update service, the operating system and installed software may not receive important security patches and updates, leaving the system vulnerable to security threats. Additionally, the error can cause system instability, crashes, and freezes, which can impact productivity and overall system performance.
Conclusion
In conclusion, the "Session WindowsUpdateTrackLog failed to start with the following error 0xc0000035" error is a frustrating issue that can occur on Windows operating systems. Understanding the causes and potential solutions to this error is essential for resolving the issue and maintaining system performance and security. By applying the solutions outlined in this essay, users can resolve the error and ensure that their system remains up-to-date and secure. Regular system maintenance, such as running disk cleanups and virus scans, can also help prevent this error from occurring in the future.
0xc0000035 (STATUS_OBJECT_NAME_COLLISION) occurs when the system tries to start a logging session, but an object with that same name already exists or is still in use. For WindowsUpdateTraceLog , this usually means
a previous session didn't close properly or a background process is conflicting with it Microsoft Learn
If your computer is otherwise updating and running normally, this error is often harmless and can be safely ignored
. However, if you want to clear it from your Event Viewer or if updates are failing, try the following steps: Microsoft Learn 1. Run Windows Update Troubleshooting Press Win + R , type perfmon
The built-in troubleshooter can reset many components that cause this conflict. Troubleshoot Other troubleshooters Windows Update Microsoft Learn 2. Reset Windows Update Components
Clearing the update cache forces the system to re-initialize its logging and update files. Command Prompt as an administrator. Type these commands one by one, pressing Enter after each:
net stop wuauserv net stop cryptSvc net stop bits net stop msiserver Use code with caution. Copied to clipboard Rename the cache folders:
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old ren C:\Windows\System32\catroot2 catroot2.old Use code with caution. Copied to clipboard Restart the services:
net start wuauserv net start cryptSvc net start bits net start msiserver Use code with caution. Copied to clipboard Microsoft Learn 3. Clear Orphaned Logging Sessions
tool to stop any "ghost" sessions that might be causing the collision. Microsoft Learn In an elevated Command Prompt, type: logman query Look for any session named WindowsUpdateTraceLog or similar. If found, stop it by typing: logman stop "WindowsUpdateTraceLog" -ets 4. Check for Update Health Tool Conflicts Sometimes, a specific tool called Microsoft Update Health Tools causes this specific logging error. Microsoft Learn Installed Apps Search for Microsoft Update Health Tools If it exists, you can try Uninstalling
it. Windows will reinstall a fresh version if needed during the next update cycle. Microsoft Learn 5. Repair System Files
If the above steps don't work, ensure your core system files aren't corrupted. Microsoft Learn sfc /scannow in an elevated Command Prompt. Follow up with DISM /Online /Cleanup-Image /RestoreHealth Are you currently having trouble installing a specific update , or did you just notice this error while browsing the Event Viewer
Fix “Error Code: 0XC0000035” Kernel event tracing on Windows
The error code 0xC0000035 translates to STATUS_OBJECT_NAME_COLLISION, which essentially means Windows tried to start a logging session (like WindowsUpdateTraceLog) that was already running or has a naming conflict with an existing object.
In most cases, this error is harmless and can be ignored if your Windows Updates are otherwise installing correctly. However, if you want to resolve it or are facing update issues, follow these steps: 1. Run the Windows Update Troubleshooter This is the fastest way to reset minor update glitches. Go to Settings > System > Troubleshoot.
Select Other troubleshooters and click Run next to Windows Update. 2. Repair System Files (SFC & DISM)
Corrupted system files can trigger collision errors during startup. Open Command Prompt as an Administrator.
Run the following commands one by one, allowing each to finish: sfc /scannow DISM /Online /Cleanup-Image /RestoreHealth 3. Clear the Windows Update Cache
If the logger is stuck because of old data, clearing the cache can force a fresh start.
Open an elevated Command Prompt and stop the services:net stop wuauservnet stop bits
Navigate to C:\Windows\SoftwareDistribution and delete all files inside.
Restart the services in the Command Prompt:net start wuauservnet start bits 4. Registry Fix (For Advanced Users)
If the error persists in your Event Viewer every reboot, you can disable the specific Autologger that is failing.
Open Regedit and navigate to:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-System Common Scenarios Where This Error Appears You are
Locate the subkey mentioned in your error (or look for Enabled keys in this folder). Change the value of Enabled from 1 to 0. Restart your computer.
Note: Only use the registry fix if you specifically want to stop the error from appearing in your logs and are confident your system is otherwise healthy.
Are you experiencing any specific issues with updates failing to install, or are you just seeing this error in your Event Viewer?
It was a typical Monday morning for John, a IT specialist at a large corporation. He arrived at his desk, sipped his coffee, and began to tackle the day's tasks. One of his colleagues had reported an issue with the Windows Update service on one of the company's laptops, and John had volunteered to take a look.
As he opened the Event Viewer on the laptop, he noticed a peculiar error message: "session windowsupdatetracelog failed to start with the following error 0xc0000035". John's curiosity was piqued. He had seen some weird errors in his time, but this one was new.
Determined to get to the bottom of the issue, John started digging deeper. He checked the Windows Update settings, ran a few troubleshooting tools, and even attempted to manually update the system. But no matter what he tried, the error persisted.
As the day wore on, John became increasingly frustrated. He had never seen an error like this before, and his usual troubleshooting techniques weren't yielding any results. He decided to take a break and clear his head.
As he walked to the company cafeteria, John stumbled upon a quirky coworker, Alex, who was known for his unorthodox problem-solving skills. Alex was a self-proclaimed "tech whisperer" who often approached problems from unusual angles.
John shared the error message with Alex, who raised an eyebrow. "0xc0000035, eh? That's a nasty one," Alex said, stroking his chin. "I've seen that error before, but only in the most...creative of circumstances."
Alex led John on a wild goose chase through various system logs, device drivers, and even a detour into the Windows registry. Along the way, they discovered that the laptop had been used by a graphics designer, who had installed a custom graphics driver that was interfering with the Windows Update service.
As they dug deeper, Alex regaled John with tales of his own troubleshooting adventures, including a legendary fix for a printer that had been possessed by a mischievous spirit (or so Alex claimed). John's skepticism was tempered by a growing sense of wonder.
Finally, after what seemed like an eternity, Alex declared, "I think I see the problem!" With a flourish, he adjusted a registry setting, and the Windows Update service sprang to life.
The error message "session windowsupdatetracelog failed to start with the following error 0xc0000035" disappeared, replaced by a triumphant "Windows Update: Up to date". John breathed a sigh of relief as he and Alex high-fived.
As they walked back to their desks, John turned to Alex and asked, "How did you do that?" Alex grinned. "It's all about thinking outside the box...or in this case, the Windows Update box."
John smiled, feeling grateful for the unexpected detour. He realized that sometimes, the most seemingly insurmountable errors require a dash of creativity and a pinch of whimsy to solve. And he made a mental note to keep Alex's number handy for the next time he encountered a mysterious error message.
The error 0xc0000035 typically translates to a "Status Object Name Collision," which essentially means a system log or process tried to start while another with the same name was already running. In most cases, if your computer is otherwise performing well and receiving updates, this error is benign and can be safely ignored.
If you are experiencing system slowdowns or Windows Update failures, you can address the error using the following methods: 1. Run Standard System Repairs
Corrupted system files are a common culprit for event tracing conflicts. Use the built-in repair tools in an elevated Command Prompt:
SFC Scan: Type sfc /scannow and press Enter to repair core system files.
DISM Tool: Type DISM /Online /Cleanup-Image /RestoreHealth and press Enter to repair the Windows system image. 2. Reset Windows Update Components the error can cause system instability
If the error persists and updates are failing, clearing the update cache can resolve naming collisions: Open Command Prompt as an administrator.
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:
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old ren C:\Windows\System32\catroot2 Catroot2.old
Restart the services using the net start command followed by the service names above. 3. Disable the Log (Advanced)
If the error is flooding your Event Viewer and you want to stop it specifically:
Open the Performance Monitor (search for it in the Start menu). Navigate to Data Collector Sets > Event Trace Sessions.
Find the session causing the error (e.g., WindowsUpdateTraceLog or PerfDiag Logger), right-click it, and select Properties.
Under the Stop Condition tab, you can set a Maximum Size (e.g., 100 MB) to prevent it from failing due to overflow, or simply stop the session if it's not needed for active debugging.
Are you currently seeing this error alongside any specific system issues, like failed updates or blue screens?
The error code 0xC0000035 (technically defined as STATUS_OBJECT_NAME_COLLISION) typically occurs in the Windows Event Viewer when a specific logging session, such as WindowsUpdateTraceLog, attempts to start but finds a session with the same name already active or an object already exists. In most cases, this message is benign and does not impact system performance or the ability to receive updates. 1. Root Causes
Naming Collision: A process tries to initiate a logging session already in use by another process or a previous session that wasn't properly closed.
System File Corruption: Damaged system files or registry entries can cause session failures.
Third-Party Interference: Some antivirus software may block or conflict with Event Tracing for Windows (ETW) sessions.
Driver Issues: Outdated network or chipset drivers can sometimes trigger kernel-level tracing conflicts. 2. Troubleshooting and Solutions
If the error is accompanied by actual performance issues or update failures, follow these steps: Step 1: Run Windows Update Troubleshooter
This is the first line of defense for any update-related logging errors.
Go to Settings > System > Troubleshoot (or Update & Security > Troubleshoot on Windows 10).
Select Other troubleshooters and click Run next to Windows Update. Step 2: Repair System Files
Use the Deployment Imaging Service and Management (DISM) and System File Checker (SFC) tools to repair corruption. Open Command Prompt as an administrator. Run the following commands one at a time: DISM /Online /Cleanup-Image /RestoreHealth sfc /scannow
Fix “Error Code: 0XC0000035” Kernel event tracing on Windows