If the error persists, the issue lies deeper within the Windows Update infrastructure. Resetting the components often clears the "failed to start" log error.
Type the following command to rebuild all performance counters and press : lodctr /R Use code with caution.
: Delete the Problematic Registry Key Many users report that deleting a specific registry key resolves the error. This targets the "session" that is causing the collision. microsoft.windows.windowsupdate.ruximlog failed to start
net start wuauserv net start cryptSvc net start bits net start msiserver Use code with caution.
The error (often accompanied by error code 0xC0000035 ) is a common Event Viewer entry. It typically occurs when the Reusable UX Integration Manager (RUXIM) data collector tries to start while another instance or a conflicting kernel session is already active. If the error persists, the issue lies deeper
Few things are as frustrating as a mysterious Windows error message that appears seemingly out of nowhere. One such error that has puzzled system administrators and everyday users alike is:
If the error persists, proceed with the solutions below. : Delete the Problematic Registry Key Many users
If you have tried all the steps above and the error persists, it may be worth performing a Windows "In-Place Upgrade" (repair install) to fix the OS without deleting your personal files.
The files within C:\Program Files\Ruxim are corrupted or missing.
The information in this article applies specifically to issues reported around the early months of 2026.
If you are still experiencing the error, or if your computer is exhibiting other issues like slow performance or boot failures, it might be related to (as reported by some users in) or a wider corruption of the Windows update mechanism.