Skip to content Repair corrupted system files that may be causing session conflicts.
net start wuauserv net start cryptSvc net start bits net start msiserver Use code with caution. Conclusion
Incorrect parameters inside the Windows Management Instrumentation (WMI) Autologger registry keys can cause the system to spin up duplicate tracing tasks at startup.
Restarting the core update infrastructure clears out cached handles and frees up stuck session names. Press Windows Key + R , type services.msc , and press . Locate Windows Update in the list. Right-click it and select Stop .
After completing these steps and rebooting your machine, open the ( eventvwr.msc ). Navigate to Windows Logs > System and clear the current log. Monitor your system over the next 24 to 48 hours. The WindowsUpdateTracelog (0xc0000035) error should no longer populate your feed, and your Windows Update delivery system will run cleanly in the background. To help tailor this guide further, let me know: Repair corrupted system files that may be causing
: Leftover temporary files confuse the tracking system.
, 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
If the tracing log continues to fail, the entire Windows Update engine might be caught in a loop. Resetting the update components clears out corrupt update states. Open .
Run the Deployment Image Servicing and Management (DISM) tool first to repair the system image: DISM.exe /Online /Cleanup-image /Restorehealth Use code with caution. Restarting the core update infrastructure clears out cached
Outdated network drivers, particularly for Intel Wi-Fi adapters, are known to conflict with kernel processes and cause this error.
For most commands below, you will need to open Command Prompt, PowerShell, or Windows Terminal as an administrator. To do this, press the Windows key, type cmd , right-click on "Command Prompt", and select Run as administrator .
Press Windows Key + R , type , and press Enter to open the Performance Monitor. In the left panel, expand Data Collector Sets . Click on Event Trace Sessions .
This is always a good first step. It can automatically detect and resolve common issues with Windows Update components. Right-click it and select Stop
In the object names box, type NT AUTHORITY\SYSTEM and click . Click OK to save.
Flooded temporary files frequently cause name collisions. Clearing the SoftwareDistribution folder resets the update environment.
: 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
Here is a comprehensive guide to understanding why this error happens and how to fix it permanently. Understanding the Error: What is 0xc0000035?
Corrupted temporary update files frequently cause the tracking logger to glitch. Resetting the update components clears out these stuck processes.
Stale files in the Performance Monitor prevent new sessions from initiating.
