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

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.

Troubleshooting Session Windows Update Trace Log Failed to Start: Error 0xc0000035

The Windows Update Trace Log is a valuable tool for system administrators and power users to diagnose and troubleshoot issues related to Windows updates. However, sometimes this log may fail to start, hindering the troubleshooting process. One such error that users may encounter is "Session Windows Update Trace Log failed to start with the following error: 0xc0000035." In this article, we will explore the possible causes of this error and provide step-by-step solutions to resolve the issue, specifically focusing on the "repack" aspect.

Understanding the Error Code 0xc0000035

The error code 0xc0000035 is a Windows error code that typically indicates a problem with the Windows registry or a failure to access a required system resource. In the context of the Windows Update Trace Log, this error may occur due to corrupted system files, registry entries, or issues with the Windows Update service.

Causes of the Error

Based on user reports and Microsoft support forums, the following are some possible causes of the error:

1. Corrupted system files: Corrupted or missing system files required by the Windows Update service can cause the error.
2. Registry issues: Malformed or incorrect registry entries can prevent the Windows Update Trace Log from starting.
3. Windows Update service issues: Problems with the Windows Update service, such as incorrect configuration or failure to start, can lead to the error.
4. Incompatible or outdated drivers: Incompatible or outdated drivers can cause system instability, leading to the error.

Repack and Its Relation to the Error

The term "repack" refers to a repackaged version of a software or driver, often modified to bypass certain restrictions or requirements. In some cases, repackaged software or drivers may cause system instability or compatibility issues, leading to errors like 0xc0000035.

If you have installed a repackaged version of Windows or a software component, it may be contributing to the error. To resolve the issue, you may need to:

• Uninstall the repackaged software or driver
• Reinstall the original software or driver
• Perform a System File Checker (SFC) scan to repair corrupted system files

Solutions to Resolve the Error

To troubleshoot and resolve the "Session Windows Update Trace Log failed to start with the following error: 0xc0000035" issue, follow these steps:

Step 4: Reset Windows Update Components (Repack-Safe)

For a repack, you want to clean without breaking customizations. Run these commands in an admin CMD:

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver

Technical Analysis: WindowsUpdateTraceLog Error 0xC0000035

Step 5: Re-register the Windows Update ETW Provider

The WindowsUpdateTraceLog session depends on a specific ETW provider. Re-register it:

cd /d C:\Windows\System32
regsvr32.exe /u wuapi.dll
regsvr32.exe wuapi.dll
regsvr32.exe wuaueng.dll
regsvr32.exe wucltux.dll

Then rebuild the ETW manifest:

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

(If the .man path doesn’t exist, run wevtutil el and find the update client’s manifest.)

5. Best Practices for Repackaging to Avoid Recurrence

To prevent this error from appearing in future repackaging workflows:

1. Clean Machine State: Always perform repackaging on a "clean" VM snapshot. This ensures no stale ETW sessions from previous software installations or updates exist.
2. Disable Services Pre-Capture: Create a PowerShell script to run before the capture tool starts. This script should disable non-essential services that generate logs:

   Stop-Service wuauserv -Force
   Set-Service wuauserv -StartupType Disabled
   

3. Exclude Trace Directories: In your repackaging tool configuration (e.g., App-V Sequencer exclusion list), add exclusion paths for Windows Update logs (e.g., C:\Windows\Logs\WindowsUpdate\*). This prevents the packager from trying to "capture" the log file generation, which often triggers the collision error.

Abstract

This paper analyzes the Windows event indicating "Session WindowsUpdateTraceLog failed to start with the following error 0xc0000035 repack". It examines root causes, diagnostic steps, and remediation approaches, and provides a reproducible troubleshooting workflow and preventive recommendations. Corrupted system files : Corrupted or missing system

A. Duplicate ETW Session Registration

When repacking, you might have:

• Run a Windows Update trace manually (e.g., via logman or wpr).
• Integrated an update that pre-creates the trace session.
• Your custom image contains leftover configuration from a previous system state.

On a clean boot, Windows attempts to start WindowsUpdateTraceLog but finds that another session (or a stale handle) is already using its GUID or name.