Microsoftwindowswindowsupdateruximlog Failed To Start Full //top\\

The error "Microsoft.Windows.WindowsUpdate.RUXIMLog failed to start" (often paired with Event ID 2 and error 0xC0000035) is a common Event Viewer entry. It typically occurs because a logging session for the Re-Usable eXperience Interaction Manager (RUXIM) is already running or encounters a name collision when attempting to start.

In most cases, this error is harmless and can be ignored if your system is otherwise stable and receiving updates. Problem Overview Source: Microsoft-Windows-Kernel-EventTracing.

Component: RUXIM (RUXIMICS.EXE), which handles interaction campaigns related to Windows Update diagnostics.

Cause: Error 0xC0000035 (STATUS_OBJECT_NAME_COLLISION) means the system tried to create a log file that already exists or is already in use by another session. microsoftwindowswindowsupdateruximlog failed to start full

Correlation: Often appears after installing specific updates like KB5001716, which updates Windows Update service components. Troubleshooting Steps

If you are experiencing actual performance issues or update failures, follow these steps to clear the conflict: 1. Clear the Windows Update Cache

Corrupted update files can trigger persistent logging errors. Open Services (type services.msc in the Start menu). Stop the Windows Update service. The error "Microsoft

Navigate to C:\Windows\SoftwareDistribution and delete all files in the folder. Restart the Windows Update service. 2. Run System Repair Tools Use built-in tools to fix underlying file corruption.

Right-click the Start menu and select Terminal (Admin) or Command Prompt (Admin). Run the System File Checker:sfc /scannow

Once finished, run the DISM tool:DISM /Online /Cleanup-Image /RestoreHealth 3. Manage Update Tools & Logs Disable the service from services

Uninstall Update Health Tools: Some users resolve this by uninstalling Microsoft Update Health Tools via Settings > Apps and letting Windows reinstall it automatically during the next update cycle.

Manual Registry Clean (Advanced): In the Registry Editor (regedit), some find success deleting the RUXIMLog entry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\, though this is usually unnecessary as the error is benign. 4. Run the Official Troubleshooter

If it’s a fake/malware service:

  1. Disable the service from services.msc or via: 
    sc stop "ServiceNameHere"
sc config "ServiceNameHere" start=disabled
  2. Delete its registry key under HKLM\...\Services
  3. Run Malwarebytes, Windows Defender Offline scan, Autoruns (Sysinternals) to find and delete the file.

Solution 3: Remove the "Ruximlog" Scheduled Task

Some driver packages create a scheduled task named Ruximlog_Task or similar.

  1. Press Win + R, type taskschd.msc, press Enter.
  2. In the left pane, navigate to Task Scheduler Library > Microsoft > Windows > WindowsUpdate (or check under Realtek if visible).
  3. Look for any task with "Ruximlog" in the name.
  4. Right-click it and select Disable (or Delete).
  5. Close Task Scheduler and reboot.

A Message from Redmond (Sort Of)

Microsoft has never officially acknowledged the "Ruximlog failed to start full" error in a public KB article. However, a leaked Windows 11 Insider build (25987) contains a reference to a deprecated logging service named RuximLog.dll. The file is still present in shipping versions of Windows 10 and 11 as of early 2026, but its functions are slowly being migrated to the newer UsoSvc (Update Orchestrator Service).

In other words, Ruximlog is a ghost that knows it is being phased out. It fails to start because, in some small way, it has already been replaced.