If none of the above work, consider:
Final note: Do not delete or modify registry keys unless absolutely sure. When in doubt, use the Windows Update Troubleshooter or reset components – these are safe and effective for most users.
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.
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.
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
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. microsoftwindowswindowsupdateruximlog failed to start full
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
"Session 'Microsoft.Windows.WindowsUpdate.RUXIMLog' failed to start" is a common Windows Event Viewer entry (Event ID 2) that typically indicates a conflict or failure in the Re-Usable UX Integration Manager (RUXIM)
. This component is responsible for managing the user experience during Windows updates, specifically for notifications and health checks. Microsoft Learn
Users often report this error appearing after installing specific updates, such as
, which aims to prepare devices for future Windows versions. Microsoft Learn Common Fixes for RUXIMLog Errors
If you are seeing this error in your logs, you can try the following troubleshooting steps: Uninstall Microsoft Update Health Tools Installed Apps (or Apps & Features). Find Microsoft Update Health Tools , select it, and click . Restart your computer afterward. Run System File Checker (SFC) Command Prompt as an administrator and run the command sfc /scannow
to find and repair corrupted system files that may be interfering with logging sessions. Clear the Windows Update Cache services.msc ) and stop the Windows Update Navigate to C:\Windows\SoftwareDistribution and delete all contents within the folder. Restart the Windows Update Registry Adjustment (Advanced)
Some users resolve session startup failures by deleting the specific log registry key. Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\Microsoft.Windows.WindowsUpdate.RUXIMLog Right-click and the key, then restart your PC. Run the Windows Update Troubleshooter Troubleshoot Other troubleshooters
. This automated tool can often reset the underlying components that the RUXIM session relies on. Microsoft Support Why this happens
The "failed to start" message usually means the logging session was already running or the buffer for that specific session was full. While it looks alarming in the Event Viewer, it is often a cosmetic error
that does not stop actual security updates from being installed. Microsoft Learn Are you experiencing failed updates If none of the above work, consider:
alongside this log error, or is the error message the only symptom? Troubleshoot problems updating Windows - Microsoft Support
The error Microsoft.Windows.WindowsUpdate.RUXIMLog failed to start (often with error code 0xC0000035) typically indicates a conflict or corruption within the Re-Usable UX Integration Manager (RUXIM), a component Windows uses to manage update-related notifications and diagnostic data. While often harmless, it can cause frequent Event Viewer warnings or occasional system stutters. Direct Solutions Modify the Windows Registry: Press Windows + R, type regedit, and hit Enter.
Navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\RUXIMLog. Right-click the RUXIMLog folder and select Delete.
Restart your computer to allow Windows to recreate a clean instance of the logger. Uninstall Microsoft Update Health Tools:
Go to Settings > Apps > Installed Apps (or Apps & Features). Search for Microsoft Update Health Tools.
Select it and click Uninstall. This tool is often responsible for RUXIM operations and will be automatically reinstalled via Windows Update if needed.
Run System Repairs:Use the Deployment Image Servicing and Management (DISM) and System File Checker (SFC) tools to fix underlying file corruption: Open Command Prompt as an administrator.
Run DISM /Online /Cleanup-Image /RestoreHealth and wait for completion. Run sfc /scannow. Secondary Troubleshooting
Reset Windows Update Components: If the error persists, use the Windows Update Troubleshooter or manually clear the update cache by stopping the Windows Update service and deleting the contents of C:\Windows\SoftwareDistribution.
Check Hardware Compatibility: In rare cases, frequent soft crashes accompanied by this error have been traced to faulty or incompatible RAM.
Error Overview
The error "Microsoft Windows Windows Update RUXIM log failed to start full" is a relatively rare issue that occurs on Windows operating systems, particularly on Windows 10 and Windows Server 2016 or later versions. This error is related to the Windows Update service, specifically with the Remote Ux Improvement (RUXIM) logging component. Final note: Do not delete or modify registry
Symptoms
When this error occurs, users may experience the following symptoms:
Causes
The following are potential causes of the "Microsoft Windows Windows Update RUXIM log failed to start full" error:
Solutions
To resolve the "Microsoft Windows Windows Update RUXIM log failed to start full" error, try the following steps:
Prevention
To prevent this error from occurring in the future:
By following these steps, users should be able to resolve the "Microsoft Windows Windows Update RUXIM log failed to start full" error and ensure that Windows Update functions properly.
The error usually appears in the System or Setup logs (Event ID 1001 or 10005, depending on your build). According to Microsoft’s sparse documentation (and thousands of frustrated forum posts), the failure typically stems from one of three culprits:
RUXIM stands for Redirected Unsupported User Interaction Manager.
The "Microsoft-Windows-WindowsUpdate-RUXIM\log failed to start" error is generally a non-critical issue related to event logging permissions or file corruption. Unless you are actively unable to install Windows updates, no action is strictly required. If updates are failing, resetting the Windows Update components (Method B) is the most reliable solution.
| Aspect | Assessment | |--------|-------------| | Is this a legitimate Microsoft component? | No | | Is it critical for Windows Update? | No | | Common cause | Malware or leftover from a broken tool | | Risk of ignoring | Low, unless it’s malware trying to run | | Best fix | Identify and remove the rogue service or clean registry corruption |
If you’re not seeing actual performance issues or failed updates, this error is usually harmless once the offending entry is removed. But if it persists after cleanup, it may indicate deeper system file corruption or an undetected rootkit — in that case, consider an in-place Windows upgrade repair or clean install.