Microsoftwindowswindowsupdateruximlog Failed To Start Full Portable Jun 2026

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

The error with Event ID 2 in the Windows Event Viewer indicates that a specialized diagnostic logging process used by the Windows Update Remediation UX Interaction Manager (RUXIM) cannot initialize. This problem typically surfaces alongside error codes like 0xC0000035 (indicating duplicate instance names) or during cumulative Windows update cycles—such as the rollouts for KB5001716. microsoftwindowswindowsupdateruximlog failed to start full