Go to > System > Troubleshoot > Other troubleshooters . Click Run next to Windows Update . Run System File Checker (SFC) Open Command Prompt as Administrator. Type sfc /scannow and hit Enter.
Corrupted temporary files in the update folder can cause logging session collisions. Open the app ( services.msc ). Right-click Windows Update and select Stop . microsoftwindowswindowsupdateruximlog failed to start full
I dug deeper. I checked the Task Scheduler . There was a task designed to trigger on "System Event Log 7000" to restart services. Because the file was permanently missing, this task was triggering, failing, and retrying in a loop every 60 seconds. Go to > System > Troubleshoot > Other troubleshooters
Select and click Run next to Windows Update . More details can be found on the Microsoft Support page. 3. Clear Registry Autologger Entry Type sfc /scannow and hit Enter
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger Microsoft.Windows.WindowsUpdate.RUXIMLog Right-click it and select Restart your computer. Run the Windows Update Troubleshooter