Session Windowsupdatetracelog Failed To Start With The Following Error 0xc0000035 Repack [work] Jun 2026

Look for a sub-folder string identifier (GUID) associated with update tracking or trace logging. Common culprits include b675ec37-bdb6-4648-bc92-f3fdc74d3ca2 .

A previous update session didn’t close correctly.

Manual trace logs are interfering with automated ones. Look for a sub-folder string identifier (GUID) associated

Press the , type cmd , right-click Command Prompt , and choose Run as administrator . Execute this command to fix local file damage: sfc /scannow Use code with caution. Once completed, run the deployment image cleanup tool: DISM /Online /Cleanup-Image /RestoreHealth Use code with caution. Restart your computer and check if the error loops stop. 2. Modify the Autologger Value via Registry Editor

However, it is a . While the error itself is safe, its persistence suggests an underlying system issue that could potentially lead to other problems, such as: Manual trace logs are interfering with automated ones

This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later.

In the Windows subsystem, the error code translates to STATUS_OBJECT_NAME_COLLISION . Once completed, run the deployment image cleanup tool:

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.

If the trace log failure is tied to a stuck update service, resetting the cache can help. Microsoft Learn Command Prompt (Admin) and stop these services: net stop wuauserv net stop bits net stop cryptSvc Rename the update folders: