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.
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."
For persistent cases, use a tool like LiveKd or Sysinternals WinObj to inspect the \KernelObjects\ namespace for a stale WindowsUpdateTraceLog event handle. No public tool directly deletes these; a reboot is the cleanest solution. Run the System File Checker (SFC) tool :
If you are a Windows administrator or a power user who frequently checks Event Viewer, you may have encountered a persistent and annoying entry in your system logs. It usually appears as a warning, distinct from the critical errors that crash systems, but consistent enough to raise alarms.
The error reads: "Session WindowsUpdateTracelog failed to start with the following error: 0xc0000035"
While this error rarely causes your computer to crash or prevents you from working, it indicates a breakdown in the communication between your operating system and its diagnostic tools. It suggests that Windows is trying to log update activities but failing to write the necessary data. Over time, this can clutter your logs, mask other serious issues, and interfere with Windows Update troubleshooting.
In this comprehensive guide, we will dissect this specific error code, explore why the WindowsUpdateTracelog session is failing, and provide step-by-step methods to resolve it permanently.
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.
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 you want
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
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) sipped his coffee
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
Run the Windows Update troubleshooter: Select Start > Settings > System > Troubleshoot > Other troubleshooters. Microsoft Support Startup Error in Event Viewer - Microsoft Q&A
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.