Corrupted update caches often trigger duplicate logging loops. Clearing these components resets the session state.
The error code 0xc0000035 translates to STATUS_OBJECT_NAME_COLLISION. In the context of Windows Update Tracelog, this means the operating system is trying to start a new logging session using a name that is already in use by an active or "ghost" process. Essentially, Windows is trying to open a door that is already occupied. Common Causes of the Conflict
If you see an unnamed session with a GUID, stop it using:
Since WindowsUpdateTracelog is tied directly to the Windows Update infrastructure, clearing out cached update files often resolves the resource collision.
If you’re a repacker creating custom images, here’s how to avoid 0xc0000035 entirely: In the context of Windows Update Tracelog, this
If the error is persistent but doesn't affect performance, you can stop it from appearing in your Event Viewer. and navigate to:
Confused and feeling redundant, the first Unit 035 pulled out a red stamp and slammed it onto the Kernel's telegram. Since he couldn't start a job that was already being done, he wrote the only thing his programming allowed for a name collision: .
Navigate to the following path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger
The most effective way to resolve a name collision is to remove the cached log file so Windows can generate a clean one. If you’re a repacker creating custom images, here’s
Circular kernal context logger failed to start - Experts Exchange
Double-click and change its Value Data from 1 (Enabled) to 0 (Disabled). Click OK and restart your computer. 2. Reset the Windows Update Components
Are you currently , or is this just an error in the logs ?
Rename the software distribution folders to clear the cache: For repack builders
Look for another DWORD value named . Double-click it and change the Value data from . Click OK . Close the Registry Editor and restart your computer . Method 2: Repair Corrupt System Files
When the operating system boots or triggers a Windows Update cycle, it attempts to initialize the WindowsUpdateTraceLog Event Trace Session. If an identical logging session name or its associated system resource is already active, the subsystem blocks the secondary request and generates this collision warning.
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.
Open ( regedit ) and navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-System