Session Windowsupdatetracelog Failed To Start With The Following Error 0xc0000035 ◎

Navigate to the following path: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-System

Navigate to the SoftwareDistribution folder: cd %systemroot%\SoftwareDistribution Tools like , a powerful utility from Microsoft,

Select all files and folders within this directory ( Ctrl + A ) and delete them. If prompted for administrator permissions, grant them. The SFC tool often detects corruption after this

Corrupt system files—especially those related to ETW (Event Tracing for Windows)—can cause this error. a powerful utility from Microsoft

Tools like , a powerful utility from Microsoft, can help you identify and disable unnecessary ETW providers that might be causing the conflict.

Click , close the Registry Editor, and restart your computer.

| Cause | Description | |-------|-------------| | | Corrupted system files remain the most common culprit. The SFC tool often detects corruption after this error appears. | | Update conflicts | A problematic Windows Update has triggered this error for many users. | | Corrupt Windows Update components | Damaged SoftwareDistribution folder or Catroot2 files can prevent proper trace log initialization. | | Faulty registry entries | Corrupt or orphaned Autologger registry keys under WMI can cause session start failures. | | Microsoft Update Health Tools | This utility sometimes creates conflicts that produce the error. | | USB or external devices | Connected USB devices during update processes have been known to trigger the error. | | RAM issues | A Microsoft Q&A thread reports RAM problems as a potential cause. | | WSUS deployment issues | Organizations using WSUS for Windows 11 24H2 cumulative updates encountered this error during the KB5063878 rollout. |