There are several reasons why the Session Windows Update Trace Log may fail to start, resulting in the error code 0xc0000035. Some of the possible causes include:
Microsoft provides a Windows Update Troubleshooter that can help resolve common issues with Windows updates. To use the troubleshooter:
The hex code 0xc0000035 translates natively to . This happens due to a few specific infrastructure bugs within Windows: There are several reasons why the Session Windows
Third-party repack scripts disable update services but leave autologger hooks active.
0xc0000035 (often paired with Event ID 2) for the WindowsUpdateTracelog indicates a name collision This happens due to a few specific infrastructure
Repair corrupted system files that might be interfering with the tracing session. Microsoft Learn Command Prompt Administrator Run the following commands one by one, letting each finish: DISM /Online /Cleanup-Image /RestoreHealth sfc /scannow Microsoft Learn 2. Clear the Windows Update Cache
If a corrupted or stuck update is holding the trace log hostage, clearing the SoftwareDistribution folder will force Windows to reset its update components and clear out active trace files. Clear the Windows Update Cache If a corrupted
Open .
Type the following command to check the local component store: DISM.exe /Online /Cleanup-image /Restorehealth Use code with caution.