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
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. The error 0xc0000035 typically translates to a "Status
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
How to Fix "Session 'WindowsUpdateTracelog' failed to start with error 0xC0000035"
If you have encountered the error "Session 'WindowsUpdateTracelog' failed to start with the following error: 0xC0000035" in your Windows Event Viewer, you are not alone. This error code, 0xC0000035, translates to STATUS_OBJECT_NAME_COLLISION.
In plain English, this means a process (usually related to Windows Update or performance monitoring) tried to start a logging session using a name that was already in use by another active session. While it looks intimidating, it is often a benign "noise" entry that can be safely ignored if your system is otherwise running smoothly.
However, if you're experiencing actual issues with updates or performance, here is how to resolve it. 1. Verify if the Logger is Already Running
Since the error indicates a naming collision, it often happens because the session is already active. Open Performance Monitor (search for it in the Start menu). Navigate to Data Collector Sets > Event Trace Sessions.
Look for "WindowsUpdateTracelog" or "Circular Kernel Context Logger."
If the status is "Running," the error was likely just a harmless conflict during startup when the system tried to start a session that had already initialized. 2. Modify the Autologger Registry Keys
This is the most common permanent fix suggested by experts to stop the error from recurring in your logs. Press Win + R, type regedit, and press Enter.
Navigate to the following path:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-System
Inside this folder, you may see a subkey with a GUID name like b675ec37-bdb6-4648-bc92-f3fdc74d3ca2.
On the right panel, find the Enabled and EnableProperty DWORD values. Double-click each and change the Value data from 1 to 0. Restart your computer. 3. Clear the Windows Update Cache
If the error is accompanied by failed updates, clearing the cache can resolve conflicts with corrupted log files. Open Command Prompt as an Administrator.
Stop the update services by typing these commands one by one: net stop wuauserv net stop bits
Navigate to C:\Windows\SoftwareDistribution and delete all files and folders inside. Restart the services: net start wuauserv net start bits 4. Run System Repair Tools
Corruption in system files can sometimes trigger naming collisions in kernel tracing.
Run the System File Checker by typing sfc /scannow in an elevated Command Prompt. Title: Fix: "Session "Windows Update Trace Log" failed
If SFC doesn't fix it, use the DISM tool:DISM /Online /Cleanup-Image /RestoreHealth. 5. Disable IPv6 (If applicable)
In some specific environments, particularly those still using legacy features like Homegroup, the 0xC0000035 error is linked to internal networking conflicts.
Go to Control Panel > Network and Sharing Center > Change adapter settings.
Right-click your connection, select Properties, and uncheck Internet Protocol Version 6 (TCP/IPv6). Summary Table: Error Breakdown
Circular kernal context logger failed to start - Experts Exchange
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
An explanation and guide for resolving the "Session 'WindowsUpdateTracelog' failed to start with the following error: 0xC0000035" system event. Understanding the Error
The error 0xC0000035 is a standard Windows NT status code representing STATUS_OBJECT_NAME_COLLISION. In the context of the Event Viewer and the WindowsUpdateTracelog, this occurs when the operating system attempts to start a new event tracing session but discovers a session or object with the same name already exists. Essentially, the "WindowsUpdateTracelog" is trying to occupy a space that is already claimed by a duplicate process. Common Causes
Trace Session Overlap: An existing instance of the Windows Update trace logger did not shut down correctly.
Clogged Data Collector Sets: Stale files in the Performance Monitor prevent new sessions from initiating.
Non-Critical Conflict: In many cases, this error is a benign side effect of how Windows 10 and 11 handle background diagnostics during the update process. How to Resolve the Conflict 1. Clear the Tracelog Files
Manually clearing the existing log files often resolves the "Object Name Collision" by removing the duplicate entries.
Open File Explorer and navigate to: C:\Windows\System32\LogFiles\WMI Locate the folder named RtBackup.
Right-click it, select Properties, and ensure you have administrative permissions to view it.
Delete the files ending in .etl within this folder (specifically those related to Windows Update). Restart your computer. 2. Reset Windows Update Components
If the logger is failing due to a corrupted update state, resetting the service can clear the block. Open Command Prompt as an Administrator. Type the following commands, pressing Enter after each: net stop wuauserv net stop cryptSvc net stop bits net stop msiserver Rename the software distribution folders:
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old ren C:\Windows\System32\catroot2 catroot2.old Restart the services: net start wuauserv (and the others stopped above). 3. Manage via Performance Monitor Type Performance Monitor in the Start search and open it. Expand Data Collector Sets > Event Trace Sessions. Locate WindowsUpdateTracelog in the list.
If it shows as "Running" or "Stopped" with an error, right-click it and select Stop.
Restart your PC to allow Windows to re-initialize the session correctly. Is This Error Serious?
If your computer is otherwise performing well and Windows Updates are installing successfully, this error is typically informational. It indicates a brief conflict during background logging rather than a hardware failure or a critical system crash. You can safely ignore it unless you are experiencing "Blue Screen" errors or a total failure of the Windows Update service. AI responses may include mistakes. Learn more Session "Windows Update Trace Log" failed to start
Title: Fix: "Session "Windows Update Trace Log" failed to start with error 0xc0000035"
Body:
I ran into the following error while checking my Windows Update logs or using a diagnostic tool (like perfmon / Performance Monitor):
Session "Windows Update Trace Log" failed to start with the following error 0xc0000035
After some research, I found that error 0xc0000035 translates to ERROR_ALREADY_EXISTS — meaning the trace session is already running or another process has a conflicting handle.
Here is how I fixed it (and you can too):
A: No. Methods 1, 2, 4, 5, 6, and 7 preserve update history. Method 3 (renaming SoftwareDistribution) resets history, but your installed updates remain intact.
Here is what typically happens in the background:
WindowsUpdateTracelog session.Open Registry Editor and navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\AutoLogger
Check for the presence of the WindowsUpdateTraceLog key.
# Check for WindowsUpdateTraceLog session collisions
Get-WinEvent -LogName "Microsoft-Windows-EventTracing/Operational" | Where-Object $_.Id -eq 100 -and $_.Message -like "*0xc0000035*"
Summary
The 0xc0000035 error looks intimidating, but it is usually just a case of Windows tripping over its own feet.
- The Cause: A "Name Collision" (Object already exists).
- The Usual Suspect: A stuck Registry Key in the Autologger folder.
- The Fix: Delete the
WindowsUpdateTraceLog registry key and let Windows recreate it.
If you have followed the steps above, your Event Viewer should be clean, and your system running smoothly once again! If the error persists after all these steps, it might be worth checking your hard drive health (using chkdsk) to ensure no physical sectors are failing on your drive.
Cause: It occurs when an Autologger session tries to start but finds a duplicate object already active. Common triggers include update conflicts, outdated drivers (like network or graphics drivers), or corrupted system files.
Impact: Usually, this error does not indicate a critical failure. If your Windows Updates are installing correctly and your system is stable, it can often be safely ignored. Resolution Steps
If the error is accompanied by system crashes or update failures, follow these troubleshooting steps: 1. Run System Repair Tools
Repair corrupted system files that may be causing session conflicts.
How To Fix Kernel Event Tracing Error Code 0XC0000035 in Windows
Method 7: Restore CORRECT Registry Permissions
A less common but documented cause is incorrect permissions on the ETW session registry key.
- Press
Win + R, type regedit, and press Enter.
- Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger
- Look for a subkey named WindowsUpdateTraceLog.
- Right-click it → Permissions.
- Ensure
SYSTEM and Administrators have Full Control.
- If the key is missing, create a new key named exactly
WindowsUpdateTraceLog. (Do not add any default values—Windows will populate them on service restart.)
- Reboot.
2. Error Overview
Observed Error Message:
Session "WindowsUpdateTraceLog" failed to start with the following error 0xc0000035
Hexadecimal Code: 0xc0000035
NTSTATUS Equivalent: STATUS_OBJECT_NAME_COLLISION
Human-Readable Meaning: "A file, registry key, or object with the same name already exists."