$sessionName = "WindowsUpdateTraceLog" $sessions = logman query -ets | Select-String $sessionName -Context 0,2 if ($sessions) Write-Host "Found conflicting session – removing..." logman stop $sessionName -ets logman delete $sessionName -ets
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. Re-register it: This article will explain exactly what
net start wuauserv net start cryptSvc net start bits net start msiserver The WindowsUpdateTraceLog session depends on a specific ETW provider. Re-register it: In simple terms: An object (file
This article will explain exactly what this error means, why it happens during repacking, and how to resolve it permanently. To fix the problem, you must first decode the message. “Session ‘WindowsUpdateTraceLog’” Windows uses Event Tracing for Windows (ETW) to log system activities. The WindowsUpdateTraceLog is a dedicated ETW session responsible for logging Windows Update operations. It helps Windows track update downloads, installations, and failures. “Failed to start with the following error 0xc0000035” Error code 0xc0000035 translates to STATUS_OBJECT_NAME_COLLISION . In simple terms: An object (file, registry key, or session) with the same name already exists. a PC technician
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.