While often benign in a standard user session, this error can cause repackaging jobs to fail, hang, or produce "dirty" packages with conflicting log file handles.
If the troubleshooter does not resolve the issue, you can try manually repacking the Windows Update component. To do this:
The error message is a common issue found inside the Windows Event Viewer. It typically falls under the Kernel-EventTracing category with an Event ID of 2. This error signifies that Windows tried to launch a background diagnostic logging session for Windows Update, but encountered a system conflict.
If the SFC scan finds corrupted files but fails to fix them, you can use the Deployment Image Servicing and Management tool (DISM) to restore the health of your Windows image.
Error 0xc0000035 for WindowsUpdateTraceLog signals a name collision—commonly a stale or duplicate ETW session. Resolution focuses on identifying and removing the conflicting session or registry entries, restarting services (or the system), repairing system components, and capturing diagnostics if the cause remains unclear. While often benign in a standard user session,
The system attempts to start a logging session that is already running, resulting in a naming collision.
Follow these structural solutions in sequence to resolve the resource conflict. 1. Modify the Autologger Registry Settings
Look for files with the .etl extension associated with Windows Update or Autologgers (such as RtBackup ).
Custom Windows images often have modified registry settings to streamline performance, which can cause conflicting logging services. Method 1: Fix Using Registry Editor (Most Effective) coffee in hand
Look for the folder associated with the error (e.g., EventLog-System or the specific update tracer subkey). On the right panel, find the or Enabled DWORD value. Double-click it and change the Value Data from 1 to 0 . Click OK , close the Registry Editor, and restart your PC. 3. Deploy DISM and SFC Repair Tools
Another Unit 035 was already sitting at the desk, coffee in hand, scribbling furiously.
If the error persists and floods your Event Viewer, you can disable the specific autologger that is failing:
Sometimes, third-party antivirus software treats ETW logs as suspicious, preventing them from starting. How to Fix 0xc0000035 in Event Viewer (Step-by-Step) close the Registry Editor
If you notice this error consistently popping up when you boot your PC, it is highly likely that a third-party startup program, antivirus, or background utility is clashing with the Windows Update logging service. Press , type msconfig , and hit Enter . Under the General tab, select Selective startup . Ensure Load startup items is unchecked.
Rename the software distribution folders to clear the cache:
Troubleshooting Session "WindowsUpdateTraceLog" Failed to Start (0xc0000035)