This is the most direct fix for 0xc0000035. The error indicates a naming collision, meaning an old trace log session is still registered but not active.
Outcome: After this, trigger a manual update check. The trace log should now start successfully.
Error 0xC0000035 (STATUS_OBJECT_NAME_COLLISION) means a named kernel or user-mode object (event, mutex, semaphore, registry key, ETW session name, or file) already exists with that name, preventing the logging/tracing session from creating it.
In Event Viewer, navigate to:
Applications and Services Logs → Microsoft → Windows → EventTracing → Operational
Look for Event ID 100 (Session initialization failure) with error code 0xc0000035.
Before attempting any fixes, it is crucial to understand the underlying mechanism. When Windows Update (via the wuaueng.dll or the Update Orchestrator Service) initializes, it attempts to create an Event Tracing for Windows (ETW) session named WindowsUpdateTraceLog.
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.
The error 0xc0000035 occurs when the ETW session tries to start but discovers that a session with the exact same name (WindowsUpdateTraceLog) is already running or has been orphaned by a previous process that crashed without cleaning up.
The error "Session WindowsUpdateTraceLog failed to start with the following error 0xc0000035" is fundamentally a communication breakdown within Windows' own logging infrastructure. While the cryptic error code suggests a deep registry failure, the reality is far more manageable.
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.
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 in-place upgrade (installing Windows from a USB drive while keeping apps and data) is the recommended final step before a clean installation.
Remember: In Windows, 0xc0000035 isn't a death sentence—it's just a collision. Clear the road, and updates will flow again.
The neon hum of the server room was the only heartbeat in the building. Elias sat hunched over Terminal 4, his eyes reflecting a cascade of scrolling text. He was hunting a ghost in the machine, a silent killer of productivity that had paralyzed the regional grid. Then, it appeared in cold, unfeeling white text: This is the most direct fix for 0xc0000035
session windowsupdatetracelog failed to start with the following error 0xc0000035
"Object Name Already Exists," Elias whispered, the translation of the hex code bitter on his tongue.
It wasn't a simple crash. The system was trying to birth a process into a space already occupied by a phantom. Two realities were fighting for the same memory address. Every time the update service tried to log its progress, it slammed into a mirror image of itself—a digital doppelgänger that shouldn't have been there.
He realized then that the "error" wasn't a bug; it was a footprint. Someone—or something—had hijacked the trace session to mask their movement, leaving a lingering shadow that blocked the system’s own diagnostic eyes.
As he reached for the kill command, the screen flickered. The error message didn't disappear. It multiplied, filling the monitor until the hex code was all he could see. The ghost wasn't just in the machine; it was in control. for this specific error or continue the to see what Elias finds?
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
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. Outcome: After this, trigger a manual update check
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. In Event Viewer
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?
Understanding and Fixing Error 0xC0000035 in Windows The error message
"Session 'WindowsUpdateTraceLog' failed to start with the following error: 0xC0000035" typically appears in the Windows Event Viewer under the Kernel-EventTracing
source. While it may look alarming, it is often a benign event that does not impact your computer's performance or ability to update. What Does Error 0xC0000035 Mean? In technical terms, the error code 0xC0000035 translates to STATUS_OBJECT_NAME_COLLISION
. This indicates that Windows tried to start a new logging session using a name that was already in use by another active session or a session that didn't shut down properly. Because the name "collides" with an existing one, the second attempt fails, and Windows logs the error. Should You Worry? In most cases,
. Microsoft support specialists and community experts often classify this as a "benign" error that can be safely ignored if your system is otherwise operating normally. It is frequently just a timing issue during the startup or shutdown process.
However, if you are experiencing actual Windows Update failures, system stutters, or crashes, you should follow the troubleshooting steps below. How to Fix Error 0xC0000035 1. Run the Windows Update Troubleshooter
Start with the built-in automated tool to identify and fix common configuration issues. Update & Security Troubleshoot Additional troubleshooters Other troubleshooters Windows Update and select Run the troubleshooter 2. Repair System Files (SFC and DISM)
Corrupted system files can cause logging conflicts. You can fix them using the Command Prompt Right-click the button and select Command Prompt (Admin) Windows Terminal (Admin) sfc /scannow Once finished, type the following and press DISM /Online /Cleanup-Image /RestoreHealth 3. Clear the Windows Update Cache
The following solutions are ordered from the easiest (non-invasive) to the more advanced (registry modifications).