Here’s what’s likely happening and how to fix it: The Windows Update trace log session is already running, or its log file is locked/in use, or there’s a leftover registry entry from a previous session. How to fix: 1. Stop the existing trace session (Run as Administrator) logman stop windowsupdate_trace_log 2. Delete the trace session (if it exists) logman delete windowsupdate_trace_log 3. Clear Windows Update logs net stop wuauserv net stop bits del /f /q %SystemRoot%\Logs\WindowsUpdate\*.etl del /f /q %SystemRoot%\Logs\WindowsUpdate\*.old net start bits net start wuauserv 4. Check for orphaned registry entries Navigate to:
However, for a failing to start, 0xc0000035 often corresponds to STATUS_OBJECT_NAME_COLLISION (from NTSTATUS.h) – which means "Object name already exists" (a duplicate name). Here’s what’s likely happening and how to fix
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger Look for any entry named windowsupdate_trace_log and delete it (backup first). Alternative: Reset Windows Update components completely If the above doesn’t help, run: Delete the trace session (if it exists) logman
The error 0xc0000035 in Windows, particularly when related to windowsupdate_trace_log or Windows Update components, typically means or "The network response was not in the expected format" or sometimes "The path was not found" depending on context. run: The error 0xc0000035 in Windows
sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth Would you like help determining why that trace log is being started (e.g., is something trying to enable diagnostic logging automatically)?