Session Windowsupdatetracelog Failed To Start With The Following Error 0xc0000035 -

0xc0000035 translates to STATUS_OBJECT_NAME_COLLISION , which indicates that Windows tried to start a logging session with a name that is already in use by another active session. In the context of WindowsUpdateTracelog

, this often means the Windows Update logging mechanism is already running or didn't shut down properly. Microsoft Learn 1. Check if the Session is Already Running

Since the error is a "collision," manually stopping any existing sessions with that name can clear the path for a clean start. Microsoft Learn Right-click and select Command Prompt (Admin) Terminal (Admin) logman query to see all active ETW (Event Tracing for Windows) sessions. If you see WindowsUpdateTracelog in the list, stop it by running: logman stop "WindowsUpdateTracelog" -ets Microsoft Learn 2. Restart Windows Update Services Restarting the core services can reset the logging state. Microsoft Learn Open an elevated Command Prompt.

Run the following commands one by one to stop and restart the update components: net stop wuauserv net stop bits net start bits net start wuauserv Microsoft Learn 3. Repair System Files

Corruption in the Windows Update registration or system files can trigger this conflict. Microsoft Learn Open Command Prompt as an Administrator. Run the System File Checker: sfc /scannow

After that completes, run the DISM repair tool to fix the system image: DISM /Online /Cleanup-Image /RestoreHealth Microsoft Learn 4. Clear the Update Cache

Corrupted files in the update folder may cause persistent logging errors. Microsoft Learn Stop the Windows Update service: net stop wuauserv Navigate to C:\Windows\SoftwareDistribution and delete all files and folders inside. Restart the service: net start wuauserv Microsoft Learn Is this error critical?

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 Title: Fix: "Session "Windows Update Trace Log" failed

Repair corrupted system files that may be causing session conflicts.

How To Fix Kernel Event Tracing Error Code 0XC0000035 in Windows

Fix: Session "WindowsUpdateTracelog" failed to start with error 0xc0000035

If you are digging through your Windows Event Viewer and keep seeing Event ID 2 with the error message "Session 'WindowsUpdateTracelog' failed to start with the following error: 0xc0000035," you aren't alone.

This error is essentially a "traffic jam" in your system's logging department. Here’s a quick breakdown of why it happens and how to clear it up. What Does This Error Actually Mean?

The error code 0xc0000035 stands for STATUS_OBJECT_NAME_COLLISION.

In plain English: Windows is trying to start a tracing session (a log that tracks what Windows Update is doing), but it’s hitting a snag because a session with that same name or ID is already running or wasn't shut down properly. It’s like trying to save a file in a folder where a file with that exact name is already open. Is This Critical?

Usually, no. If your computer is running smoothly and Windows Updates are installing correctly, this is often just "log noise." However, if it’s cluttering your Event Viewer or you’re having trouble updating Windows, you should address it. How to Fix It 1. The "Clean Slate" Reboot

Before diving into settings, perform a full restart. Not a "Shutdown" (which often uses Fast Startup and saves the kernel state), but a Restart. This forces Windows to kill all active tracing sessions and start fresh. 2. Flush the ETW Logs Session "Windows Update Trace Log" failed to start

The most effective fix involves clearing the temporary files where these logs live. Press Windows Key + E to open File Explorer. Navigate to: C:\Windows\System32\LogFiles\WMI Look for a folder named RtBackup.

Note: You may need to take ownership of this folder to delete files inside it.

Delete the contents of the RtBackup folder and restart your PC. Windows will recreate these files cleanly upon reboot. 3. Restart the Windows Update Services Sometimes the service responsible for the trace is hung.

Type cmd in your Start menu, right-click it, and select Run as Administrator.

Type the following commands one by one, hitting Enter after each: net stop wuauserv net stop bits Wait a few seconds, then restart them: net start wuauserv net start bits 4. Check for Circular Logging Conflicts If you are tech-savvy, you can manage the session directly:

Search for Performance Monitor in the Start menu and open it. Expand Data Collector Sets on the left. Click on Startup Event Trace Sessions. Locate WindowsUpdateTracelog in the list. Right-click it and select Properties.

Under the Trace Session tab, ensure "Enabled" is checked, but if the error persists, try toggling the "Circular" log mode to help overwrite old data.

The 0xc0000035 error is rarely a "system killer." It’s a minor conflict in how Windows tracks its own update progress. By clearing the RtBackup folder or restarting the update services, you usually tell Windows to stop overthinking and start the log fresh.

Are you seeing this error alongside Windows Update failures, or is it just appearing in your Event Viewer? it is actively disrupting updates.

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):

Q: Is this error a sign of malware?

A: Unlikely. Malware rarely targets ETW trace session names in this way. It’s almost always a software collision or log corruption issue.

Troubleshooting: "session windowsupdatetracelog failed to start with the following error 0xc0000035"

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.

Q: Will I lose update history by fixing this error?

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.

Frequently Asked Questions

Step 1: Check Event Viewer

1. Press Win + X and select Event Viewer.
2. Navigate to: Applications and Services Logs > Microsoft > Windows > WindowsUpdateClient > Operational.
3. Look for Event ID 100 or Event ID 104 with the error text: "Session "WindowsUpdateTraceLog" failed to start with the following error 0xc0000035".
4. Check the timestamps. If the error appears repeatedly every few minutes, it is actively disrupting updates.