Session Windowsupdatetracelog Failed To Start With The Following Error 0xc0000035 Repack -

  • Enumerate and stop conflicting sessions:
  • Remove stale Autologger registry entries (if present):
  • Check for third‑party interference:
  • Repair system components:
  • Recreate or reset ETW sessions:
  • Only perform provider unregister/register when corruption is confirmed.
  • If error occurs during an update/repackaging operation:
  • Collect diagnostic traces if issue persists:

    • During repacking, if you removed Windows Update components incorrectly (e.g., deleting wuauserv dependencies but keeping related ETW manifests), the tracing service attempts to start but fails due to mismatched internal references.

    The SFC scan checks and repairs corrupted system files.

    Corrupt update cache can trigger log session conflicts.

    net stop wuauserv
net stop bits
rd /s /q %systemroot%\SoftwareDistribution
net start wuauserv
net start bits

    If you are a Windows system administrator, a PC technician, or an advanced user building custom images (repacks), you may have encountered a cryptic error message while inspecting the Event Viewer or during a sysprep process:

    “Session ‘WindowsUpdateTraceLog’ failed to start with the following error 0xc0000035.”

    This error often appears alongside the keyword “repack” — referring to repackaged Windows installations, custom ISOs, or modified system images. It is frustrating because it doesn’t always crash the system visibly, but it can lead to update failures, performance degradation, and Sysprep errors.

    This article will explain exactly what this error means, why it happens during repacking, and how to resolve it permanently.

    The error “Session WindowsUpdateTraceLog failed to start with error 0xc0000035” is a classic ETW naming collision, often exposed during repacking. It doesn’t mean your Windows installation is broken, but it indicates a low-level mismatch that can disrupt updates and deployment tools like Sysprep.

    By stopping the conflicting trace session, cleaning autologger registry keys, resetting Windows Update components, and reapplying the correct ETW manifests, you can resolve the error permanently. For repack builders, prevention is best: avoid gutting ETW providers and clean your registry before image capture.

    If you’ve followed this guide, run logman query and check Event Viewer – you should see WindowsUpdateTraceLog running silently, and your repack will be ready for deployment without any 0xc0000035 shadow lurking in the logs.

    Need help with a specific repack tool or a stubborn Sysprep failure? Let us know in the comments below (or contact your system image provider).

    The error 0xC0000035 (STATUS_OBJECT_NAME_COLLISION) during WindowsUpdateTraceLog indicates a benign name conflict, often ignorable if system updates function normally. Resolving this involves clearing the Windows Update cache via Command Prompt or disabling the specific autologger in the registry editor. For a detailed troubleshooting guide, visit Microsoft Q&A.

    The error code 0xC0000035 is formally defined as STATUS_OBJECT_NAME_COLLISION, which indicates that a logging session or file name that Windows tried to create already exists. In the context of WindowsUpdateTracelog (or related logs like RUXIMLog), this usually occurs during a system restart when Windows attempts to start a diagnostic trace that didn't shut down or clean up properly in the previous session.

    If your computer is otherwise updating and running normally, this error can typically be safely ignored. However, if you want to resolve it or are experiencing update issues, follow these steps: 1. Run Built-in Repair Tools

    Use the Windows Update Troubleshooter to automatically identify and fix common configuration errors. Enumerate and stop conflicting sessions:

    Go to Settings > System > Troubleshoot > Other troubleshooters. Select Windows Update and click Run. 2. Repair System Files

    Corrupted system files can cause naming collisions in the kernel event tracing system. Use the following commands to repair them: Open Command Prompt as an Administrator.

    Run the Deployment Image Servicing and Management (DISM) tool:DISM /Online /Cleanup-Image /RestoreHealth

    Once finished, run the System File Checker (SFC):sfc /scannow 3. Clear Windows Update Cache

    Deleting the temporary update files can resolve conflicts where the system tries to restart a trace based on outdated data. Open Command Prompt as Administrator. Stop the Update service: net stop wuauserv

    Navigate to C:\Windows\SoftwareDistribution and delete all contents. Restart the service: net start wuauserv 4. Advanced: Registry Modification

    If the error persists and floods your Event Viewer, you can disable the specific autologger that is failing:

    Open Registry Editor (regedit) and navigate to:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-System

    Look for the subkey associated with the trace log (often a GUID like b675ec37-...). Change the Enabled and EnableProperty values from 1 to 0.

    Warning: Back up your registry before making manual changes. Kernel-EventTracing - Microsoft Q&A

    The error code 0xC0000035 typically indicates a STATUS_OBJECT_NAME_COLLISION, which means the WindowsUpdateTraceLog session failed to start because a logging session with that same name is already running or wasn't properly closed. In most cases, this error is benign and can be safely ignored unless you are experiencing actual failures with Windows Update. Recommended Troubleshooting Steps

    If you are seeing this error frequently or experiencing update issues, try the following solutions:

    Restart Windows Update Services: Use the Windows Services Manager (services.msc) to find the Windows Update service, right-click it, and select Restart.

    Run System Repairs: Open Command Prompt as an administrator and run these two commands to fix potential system file corruption: sfc /scannow DISM /Online /Cleanup-Image /RestoreHealth Remove stale Autologger registry entries (if present):

    Clear the Update Cache: Stop the Windows Update service, then navigate to C:\Windows\SoftwareDistribution and delete its contents. Restart the service afterward.

    Manage ETW Sessions: You can manually stop conflicting sessions using the logman command in an elevated Command Prompt: Type logman query -ets to find the active sessions.

    Use logman stop "WindowsUpdateTraceLog" -ets to force stop the conflicting session.

    Update Drivers: Outdated network or chipset drivers can sometimes cause timing issues that trigger these collisions. Use the Windows Device Manager to check for updates.

    If the error persists but your system updates are installing correctly, Microsoft support specialists often suggest it is a known timing issue that does not require further action.

    Are you currently facing any specific issues with downloading or installing updates, or is the error only appearing in your Event Viewer?

    The error code 0xc0000035 is technically defined as STATUS_OBJECT_NAME_COLLISION, which indicates that a tracking session or logger is attempting to start using a name that is already in use by the system. In the context of "WindowsUpdateTracelog," this often occurs during routine background maintenance or updates and is generally considered benign unless you are experiencing active system instability or update failures. Understanding the Error

    When Windows Update or performance diagnostic tools attempt to initiate a Kernel Event Tracing session, they may encounter this collision if a previous session didn't close properly or if multiple services are requesting the same log name simultaneously. Recommended Solutions

    If this error is cluttering your Event Viewer or causing noticeable performance dips, you can resolve it through several standard Windows repair methods:

    Run Built-in Troubleshooters: The first step should be the Windows Update Troubleshooter, which can automatically detect and clear common logging collisions.

    Repair System Files: Use the System File Checker (SFC) and Deployment Image Servicing and Management (DISM) tools to repair corrupted registry keys or system files that might be triggering the collision: Open Command Prompt as an Administrator. Run sfc /scannow.

    Once complete, run DISM /Online /Cleanup-Image /RestoreHealth.

    Reset Update Cache: If the collision persists, clearing the update cache can force a "clean" restart of the logging session. This is done by stopping the Windows Update service and clearing the C:\Windows\SoftwareDistribution folder.

    Registry Modification (Advanced): Some users resolve the persistent trace log error by navigating to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\AutoLogger\EventLog-System and setting the Enabled and EnableProperty values to 0. Note: Always back up your registry before making changes. Check for third‑party interference:

    If your system is otherwise stable and updates are installing successfully, many Microsoft Community Experts suggest that this specific log error can be safely ignored.

    Are you experiencing any specific performance issues like slow boot times or failed updates alongside this error?

    The error 0xC0000035 (technically STATUS_OBJECT_NAME_COLLISION) is a common "benign" error in the Windows Event Viewer. It typically occurs when a system component, like WindowsUpdateTracelog, tries to start a logging session that is already active or hasn't been properly closed from a previous run.

    If your computer is otherwise running smoothly, this error can often be safely ignored. However, if you are experiencing performance lags or update issues, here are the steps to resolve it: 1. Basic Troubleshooting

    Run Windows Update Troubleshooter: This built-in tool can reset common update components automatically. Find it in Settings > Update & Security > Troubleshoot > Additional troubleshooters.

    Perform a System Scan: Use the System File Checker (SFC) and DISM tools to repair corrupted system files that might be causing the logging conflict. Open Command Prompt as Administrator. Run sfc /scannow. Run DISM /Online /Cleanup-Image /RestoreHealth. 2. Manual Reset of ETW Sessions

    Since the error code indicates a "name collision," stopping the active session manually can clear the block.

    Open Command Prompt (Admin) and type: logman query to list active sessions. Find the session named WindowsUpdateTracelog (or similar).

    Stop it by typing: logman stop "WindowsUpdateTracelog" -ets. 3. Clear the Windows Update Cache

    Corrupted temporary files in the update folder can trigger persistent logging errors.

    Open Services (services.msc) and Stop the "Windows Update" service.

    Navigate to C:\Windows\SoftwareDistribution and delete everything inside. Go back to Services and Start the "Windows Update" service. 4. Advanced Registry Fix

    For persistent errors, you can modify the "Autologger" registry to prevent the session from conflicting on startup.

    Path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\WindowsUpdateTracelog

    Find the Enabled and EnabledProperty keys and set their values to 0. Note: Always back up your registry before making changes.

    Is your computer experiencing any specific slowdowns or failed updates alongside this error? Startup Error in Event Viewer - Microsoft Q&A