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

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 in the Start search and open it. Expand Data Collector Sets > Event Trace Sessions . Locate WindowsUpdateTracelog in the list.

Upon restart, Windows will notice the registry key is missing and recreate it from scratch, effectively resetting the "active" status and resolving the conflict.

Have you noticed any accompanying this issue? Share public link

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

Below is a comprehensive guide to understanding this error and the exact step-by-step methods required to resolve it. Understanding the Error Components

Re-register the primary system performance infrastructure by running: lodctr /r Use code with caution.

If your system is running fine and updates are installing correctly, you can safely stop the error from being logged. This doesn't fix the underlying cause but prevents it from cluttering your Event Viewer. Expand Data Collector Sets > Event Trace Sessions

Alternatively, if you do not want to delete it, double-click the DWORD value inside that folder and change its value data from 1 (Enabled) to 0 (Disabled). Close the Registry Editor and reboot your system. 3. Run SFC and DISM Repairs

The 0xc0000035 error when starting the WindowsUpdateTraceLog session is exclusively a namespace collision issue within the ETW subsystem. It does not affect Windows Update functionality for downloading or installing updates, but it degrades diagnostic logging capability. The recommended resolution is to delete the orphaned AutoLogger registry entry and reboot, allowing Windows to reconstruct the session correctly. System administrators should avoid manually creating ETW sessions that conflict with Microsoft’s reserved AutoLogger names.

Temporarily disable any third-party real-time protection shields. Have you noticed any accompanying this issue

Delete the file. Windows will safely regenerate a clean, non-conflicting file upon normal reboot. Conclusion

Did the error start appearing after a ?

These built‑in tools scan for and repair corrupted system files.