Smart Protractor
Learn
TutorialsBasicsAccuracyExportTroubleshooting

Microsoft.windows.windowsupdate.ruximlog Failed To Start [extra Quality] May 2026

The error "Session 'Microsoft.Windows.WindowsUpdate.RUXIMLog' failed to start" is a common event log entry that typically appears in the Windows Event Viewer with Error Code 0xC0000035.

While the technical language sounds alarming, this specific error is usually a "non-critical" event and rarely affects your computer's performance or actual update capability. What is RUXIM?

RUXIM stands for Reusable UX Interaction Manager. It is a legitimate Microsoft system component used by Windows Update to manage user interactions, such as displaying notifications about upcoming updates or end-of-support warnings for older versions like Windows 10. Why Does This Error Occur?

The error code 0xC0000035 translates to STATUS_OBJECT_NAME_COLLISION. In simple terms: The system tried to start a new logging session for RUXIM.

A session or file with the exact same name was already active or existed.

Instead of overwriting it, Windows logged a "failure to start" because the name was already in use. How to Fix RUXIMLog Failed to Start

If your computer is running smoothly otherwise, you can safely ignore this error. However, if you are also experiencing failed updates or system stutters, follow these steps to resolve the underlying conflict. 1. Use the Windows Update Troubleshooter

This is the official first step to reset internal update flags that might be causing the collision.

Go to Settings > System > Troubleshoot > Other troubleshooters. Click Run next to Windows Update. Restart your computer once finished. 2. Repair System Files (SFC & DISM)

Corrupted system files can lead to logging conflicts. Use these commands to verify your Windows image integrity: Open the Command Prompt as Administrator. Type sfc /scannow and press Enter. microsoft.windows.windowsupdate.ruximlog failed to start

Once complete, type DISM /Online /Cleanup-Image /RestoreHealth and press Enter. 3. Clear the Windows Update Cache

Manually clearing the temporary update files often stops the recurring "Name Collision" error.

The error message "Session 'Microsoft.Windows.WindowsUpdate.RUXIMLog' failed to start"

(often accompanied by Event ID 2 and error code 0xC0000035) typically appears in the Windows Event Viewer. While it sounds alarming, it is generally a benign system notification related to

(Reusable UX Integration Manager), a component used by Microsoft to manage background updates and "update health" tools Understanding the RUXIMLog Error

The error usually triggers when the system attempts to start a logging session for an update process that is either already running or has been superseded. Many users have traced this specific log failure to

, a cumulative update designed to improve Windows Update service components.

Because RUXIM is part of the "Update Health Tools," the error signifies that the diagnostic logging session for these tools couldn't initialize properly. In most cases, this does

impact the actual installation of security updates or the stability of your PC. Common Solutions and Mitigations The error "Session 'Microsoft

If you find the error frequently cluttering your logs or suspect it is causing performance lag, you can try these steps: Run System Repairs System File Checker (SFC)

tools to ensure no core system files are corrupted. In an elevated Command Prompt, run: sfc /scannow DISM /Online /Cleanup-Image /RestoreHealth Reset Update Components

: If updates are failing alongside this error, resetting the Windows Update cache can help. This involves stopping the update services and renaming the SoftwareDistribution Manage Update Health Tools

: Some users have resolved the persistent log entry by uninstalling Microsoft Update Health Tools

from the "Apps & Features" menu, then restarting the computer to allow Windows to reinstall a clean version. Registry Adjustment

: A more advanced fix involves navigating to the registry key

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\RUXIMLog

and deleting it (after backing up the registry), which prevents the system from attempting to start that specific failed session. For the vast majority of users, the

failure is a "ghost" error—a diagnostic session failing to record data for a process that may not even need to run at that moment. Unless your computer is experiencing "soft crashes" or failing to install critical security patches, this error can safely be ignored. step-by-step guide Part 3: 8 Detailed Fixes for "ruximlog failed to start" c

on how to run the registry fix or reset your update components? Startup Error in Event Viewer - Microsoft Q&A 8 May 2024 —

Part 3: 8 Detailed Fixes for "ruximlog failed to start"

c. Reset Windows Update components (as admin in CMD):

net stop wuauserv
net stop cryptSvc
net stop bits
net stop msiserver
ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
ren C:\Windows\System32\catroot2 catroot2.old
net start wuauserv
net start cryptSvc
net start bits
net start msiserver

Solution 2: Use the Windows Update Troubleshooter

If you are uncomfortable editing the registry, start with the built-in troubleshooter.

  1. Go to Settings > Update & Security > Troubleshoot (Windows 10/11).
  2. Select Additional troubleshooters.
  3. Click Windows Update and run the troubleshooter.
  4. The tool may detect and fix corrupted service registrations, including orphaned entries like ruximlog.

Fix 3: Run DISM and SFC Scans

Corrupted system files can break the Windows Update stack.

Step 1: Run DISM (Deployment Imaging Service and Management)

DISM /Online /Cleanup-Image /RestoreHealth

This may take 15–20 minutes.

Step 2: Run System File Checker

sfc /scannow

Step 3: Reboot and test.

Q3: Will a clean Windows installation fix it?

Absolutely. A clean install removes all corruption, but it’s a last resort due to data loss risk.

Solution 3: Run DISM and SFC (System File Checker)

Corruption in system files can sometimes cause phantom log errors.

  1. Open Command Prompt as Administrator.
  2. Run the Deployment Imaging Service Management (DISM) tool: 
    DISM /Online /Cleanup-Image /RestoreHealth
    (This may take 15-20 minutes.)
  3. Once DISM completes, run the System File Checker: 
    sfc /scannow
  4. Reboot after the scan.

Common Symptoms Accompanying This Error

Microsoft.windows.windowsupdate.ruximlog Failed To Start [extra Quality] May 2026