Some users find success by resetting the "Autologger" session in the registry. Always back up your registry before making changes. Navigate to:
Stop the core deployment services by typing the following commands one by one, pressing Enter after each: net stop wuauserv net stop bits net stop cryptsvc Use code with caution.
If you are seeing this while trying to install or run a (like FitGirl or DODI), it often indicates that a system service or background process is conflicting with the installer's execution. 1. Clear Conflict Sessions
If a simple restart doesn't work, the next logical step is to address potential problems within Windows Update itself. Some users find success by resetting the "Autologger"
If the error is related to Windows Update specifically, clearing the log files can resolve the name collision.
. In plain English: Windows tried to start a logging session, but it found that a session with that exact name was already running or hadn't closed properly from a previous attempt. learn.microsoft.com
This is a targeted fix that directly deals with the reported session. By deleting the session and letting Windows recreate it, you can often resolve a configuration problem or fix minor corruption. If you are seeing this while trying to
Furthermore, some modified Windows installations (such as custom "Lite" or "Gaming" editions of Windows, often distributed via repacks) strip out the Windows Update components entirely to save space and bandwidth. In these "lobotomized" operating systems, the scheduler attempts to start WindowsUpdateTracelog as part of a routine task, but the underlying components are missing or corrupted. When the system tries to map the log file and finds it missing or locked by the modified environment, it may default to the collision error if the cleanup process was not executed correctly by the OS modification.
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
If you notice this error consistently popping up when you boot your PC, it is highly likely that a third-party startup program, antivirus, or background utility is clashing with the Windows Update logging service. Press , type msconfig , and hit Enter . Under the General tab, select Selective startup . Ensure Load startup items is unchecked. If the error is related to Windows Update
Circular kernal context logger failed to start - Experts Exchange
: The first step should be the Windows Update Troubleshooter, which can automatically detect and clear common logging collisions.
Understanding and Fixing Error 0xc0000035 for WindowsUpdateTraceLog