Session Windowsupdatetracelog Failed To Start With The Following Error 0xc0000035 Repack [ 99% PROVEN ]

The error 0xc0000035 is a Kernel Event Tracing issue that occurs when Windows attempts to start a logging session (like WindowsUpdateTraceLog or RUXIMLog) but fails because an object with the same name already exists. In technical terms, it is a STATUS_OBJECT_NAME_COLLISION.

: In most cases, if your computer is receiving and installing updates normally, this error in the Event Viewer can be safely ignored as it is a logging-related conflict rather than a system failure. Microsoft Learn Recommended Troubleshooting Steps

Warning: Back up your registry before making manual changes. Kernel-EventTracing - Microsoft Q&A The error 0xc0000035 is a Kernel Event Tracing

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old ren C:\Windows\System32\catroot2 catroot2.old Restart the services: net start wuauserv net start bits net start cryptSvc Microsoft Learn 3. Adjust Registry (For Persistent Log Flooding)

wevtutil im C:\Windows\System32\winevt\Logs\Microsoft-Windows-WindowsUpdateClient%4Operational.man

often note that these log entries are common during normal operations and do not necessarily indicate a critical system failure. Microsoft Learn How to Fix It often note that these log entries are common

Last tested: March 2025 – Works on Windows 11 24H2 and Windows Server 2022.

Are you experiencing any specific performance issues like slow boot times or failed updates alongside this error? an in-place component repair is essential:

Step 6: Repair Windows Image (DISM)

For repack images, an in-place component repair is essential: