Corrupt or missing system files can be the root cause of the STATUS_OBJECT_NAME_NOT_FOUND error. Windows has two powerful built-in tools to repair these files.
Change their values from 1 to 0 . This prevents the system from attempting to start that specific trace session, which stops the error from logging in the Event Viewer.
When a repack installer runs, it often executes a script to disable services and background tasks that might interfere with the installation. If the script forcibly kills the Windows Update service or the specific tracing session without properly closing the handle, the system may retain a "ghost" reference to the WindowsUpdateTracelog . Alternatively, some repack scripts attempt to mimic system behaviors to check for update dependencies or to modify system files. In doing so, they might inadvertently trigger the initialization of the WindowsUpdateTracelog . Corrupt or missing system files can be the
Return to the elevated Command Prompt and restart the services: net start wuauserv net start bits net start cryptsvc Use code with caution. 2. Modify the Autologger Registry Keys
: This specific hexadecimal NTSTATUS code means an object name collision has occurred. Windows is trying to launch a service thread under a name that another thread is already using. This prevents the system from attempting to start
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
The WindowsUpdate_trace_log is an ETW session that should normally start and stop seamlessly in the background. When Windows Update attempts to initialize this trace session but fails, Event Viewer logs the 0xC0000035 warning. This error can be accompanied by other failed session logs, such as: Alternatively, some repack scripts attempt to mimic system
If corrupted system files are preventing the logger from starting, use the built-in repair tools: In an administrative Command Prompt, run: sfc /scannow DISM /Online /Cleanup-Image /RestoreHealth
Navigate to the following path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\WindowsUpdateTracelog In the right-hand pane, look for a DWORD value named .