Session Windowsupdatetracelog Failed To Start With The Following Error 0xc0000035 — Fix

Troubleshooting "Session WindowsUpdateTraceLog Failed to Start with Error 0xc0000035"

Registry check

$path = "HKLM:\SYSTEM\CurrentControlSet\Control\WMI\AutoLogger\WindowsUpdateTraceLog" if (Test-Path $path) Write-Host "AutoLogger exists" -ForegroundColor Yellow

Disclaimer: This paper is for educational and diagnostic purposes. Always test changes in a non-production environment first. Microsoft product names and error codes are property of Microsoft Corporation.

0xc0000035 (STATUS_OBJECT_NAME_COLLISION) occurs when the Windows Event Tracing (ETW) system attempts to start a logging session with a name that is already in use. For WindowsUpdateTracelog

, this often means a previous update session didn't shut down correctly, leaving an orphaned entry that blocks new logs from starting.

While typically benign and safe to ignore if updates are still installing correctly, you can resolve it using the following methods: 1. Clear Orphaned Tracing Sessions

If a session is stuck, you can manually stop it to resolve the naming collision. Identify Sessions : Open Command Prompt as Administrator and run logman query to list active ETW sessions. Stop the Conflict : If you see WindowsUpdateTracelog or a similar name, run: logman stop "WindowsUpdateTracelog" -ets 2. Reset Windows Update Components

This clears the update cache and restarts the related services, which often fixes registration errors.

Open an elevated Command Prompt and run these commands sequentially:

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 Restart the services: net start wuauserv net start cryptSvc 3. Repair System Image & Files

Corrupted system files can prevent logging services from initializing properly. System File Checker sfc /scannow Run the DISM tool for deeper repairs: DISM /Online /Cleanup-Image /RestoreHealth 4. Adjust Logging Registry (Advanced)

If the error persists every boot, you may need to disable the specific autologger that is failing. Navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\WindowsUpdateTracelog DWORD and set its value to

: This stops the specific logging but does not impact the actual delivery of updates. Troubleshoot problems updating Windows - Microsoft Support Disclaimer: This paper is for educational and diagnostic

Run the Windows Update troubleshooter: Select Start > Settings > System > Troubleshoot > Other troubleshooters. Microsoft Support Startup Error in Event Viewer - Microsoft Q&A

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:

  1. Run the System File Checker (SFC) tool: The SFC tool scans and replaces corrupted system files, which can resolve issues related to system file corruption.
  2. Check and update registry entries: Manually checking and updating registry entries related to the Windows Update service can resolve issues related to registry corruption.
  3. Run a full system scan with an anti-virus program: Malware infections can be detected and removed with a full system scan, which can resolve issues related to malware.
  4. Disable conflicting software or third-party applications: Disabling or uninstalling conflicting software or third-party applications can resolve issues related to software conflicts.
  5. Reset Windows Update components: Resetting Windows Update components, such as the Windows Update cache, can resolve issues related to corrupted Windows Update data.

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. Run the System File Checker (SFC) tool :

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:

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?

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 Press Win + R

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?

Part 3: Solutions to Fix the Error

The following solutions are ordered from the easiest (non-invasive) to the more advanced (registry modifications).

Method 2: Using Performance Monitor (Graphical Alternative)

For administrators who prefer a GUI over command lines:

  1. Press Win + R, type perfmon.msc, and press Enter.
  2. In the left pane, expand Data Collector Sets > Event Trace Sessions.
  3. Look for WindowsUpdateTraceLog in the list.
  4. Right-click it and select Stop.
  5. Wait 10 seconds, then right-click and select Delete.
  6. Restart the Windows Update service as shown in Method 1.

Appendix A: Sample Registry Export (Healthy)

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\AutoLogger\WindowsUpdateTraceLog]
"GUID"="C5B6F0A4-8C9E-4A2B-9F7D-1E3A5B7C9D0E"
"Start"=dword:00000001
"FileName"="%SystemRoot%\System32\LogFiles\WU\TraceLog.etl"
"MaxFileSize"=dword:00000032
"Status"=dword:00000000