"Session 'Microsoft.Windows.WindowsUpdate.RUXIMLog' failed to start" is a common event log entry (Event ID 2)

• Set BITS, Cryptographic Services, Windows Update to Manual (or Automatic) and start them: sc config bits start= demand sc config cryptsvc start= auto sc start bits sc start cryptsvc

The coffee in the mug on my desk had gone cold hours ago, a stagnant pool of black mud reflecting the fluorescent lights of the server room. Outside, the city of Seattle was drowning in the usual grey drizzle, but inside, the atmosphere was far more oppressive.

Reboot your PC and check if the error persists.

If the error persists, the application itself may need a reset Apps & features Search for Microsoft Update Health Tools Select it and click Run a manual Windows Update

Sometimes, the Windows Update service itself has a corrupted data store. When the Update Orchestrator service attempts to enumerate all update-related tasks, it stumbles upon a dead reference to "Ruximlog" and logs the failure.

• 0x80070422 / ERROR_SERVICE_DISABLED: Set service start type to Manual/Automatic and start dependencies.
• 0x80070424 / ERROR_SERVICE_DOES_NOT_EXIST: Windows Update service registry entries missing — restore registry or perform repair install.
• 0x80070643: Corrupted update components or MSI issues — run SFC/DISM and clear SoftwareDistribution.
• 0x8024402F: Network/connectivity issue — check proxy, firewall, and internet access.

stuck on a specific update

Is your system currently , or are you just seeing this error in the logs?