. If the error appeared immediately after an update, you may choose to uninstall that specific update via Control Panel Programs and Features View installed updates Microsoft Learn Are you currently experiencing any performance issues failed update installations , or did you just happen to notice this error in your Event Viewer
Multiple users have traced the first appearance of this error to the installation of , an update for Windows Update Service Components that Microsoft released starting in October 2023. This update appears to have introduced changes to how Windows Update manages its diagnostic sessions, leading to the session name collision error on many systems.
Once finished, run the DISM tool: DISM /Online /Cleanup-Image /RestoreHealth 3. Manage Update Tools & Logs microsoftwindowswindowsupdateruximlog failed to start full
If a corrupt Windows Update module is failing to feed data to the RUXIM manager, built-in system deployment tools can check and replace the broken dependencies.
Then, the power fluctuated. Or the antivirus quarantined the file. Or the hard drive hiccuped. The installation failed mid-stream. Once finished, run the DISM tool: DISM /Online
The UXIMLog is part of the modern Windows Update infrastructure (often managed by the Unified Update Platform, or UUP). It deals with the user experience aspects of updates—notifications, readiness checks, and interactive prompts. When this log fails, the "UX" of Windows Update suffers. Windows Update stuck on "Checking for updates." Error code 0x800704b3 or other update errors.
MicrosoftWindowsWindowsUpdateRuximLog failed to start Event ID: 1001, 7023, 7000, or 7001 Source: Service Control Manager or .NET Runtime Or the antivirus quarantined the file
There it was.
I scrolled past the standard entries— WinDefend , wuauserv , EventLog —until I found the suspect. The key existed. The registry hive was intact. I examined the ImagePath .
that might be causing this (like KB5001716).