Microsoft has confirmed that systems which installed the August 2026 Windows cumulative updates are experiencing game crashes and launch failures — and the company is pointing the finger at peripherals and control software tied to RGB lighting. While this is framed as a stability issue rather than a security vulnerability, it has real operational and security consequences for defenders. RGB control suites (Corsair iCUE, Razer Synapse, ASUS Armoury Crate/Aura Sync, MSI Mystic Light, NZXT CAM, Logitech G HUB, SignalRGB, and similar) install kernel-mode drivers that hook low-level hardware access — the same class of drivers that has repeatedly been abused for bring-your-own-vulnerable-driver (BYOVD) attacks and that historically destabilizes the OS after servicing stack changes.
If you manage a fleet that includes gaming endpoints, esports labs, developer workstations, or — increasingly — marketing/streaming rigs inside corporate environments, this is a patch-management and driver-governance problem, not just a helpdesk nuisance. This post breaks down what is happening, how to hunt for affected and crashing endpoints, and how to remediate and harden.
Technical Analysis
What happened
Following installation of the August 2026 Windows updates, users report that games either crash shortly after launch or fail to launch entirely. Microsoft's investigation attributes the behavior to conflicts with RGB lighting devices and their associated control software. This is not the first collision between Windows servicing and the RGB ecosystem — Microsoft has previously had to mitigate RGB-related instability because these utilities reach deep into the graphics stack, input subsystems, and hardware monitoring interfaces.
Why RGB software breaks after Windows updates
From an engineering standpoint, RGB control suites are among the most invasive third-party software you will find on a Windows endpoint:
- Kernel-mode drivers: Most RGB suites ship signed kernel drivers for direct hardware access (SMBus/I2C control of lighting controllers, motherboard sensors, and fan hubs). Well-known examples in the wild include drivers such as
WinRing0x64.sys,inpoutx64.sys,ene.sys,GLCKIO2.sys,Asusgio*.sys,RTCore64.sys, andNTIOLib*.sys. When Microsoft changes kernel interfaces, memory management, or I/O handling in a cumulative update, these drivers are frequent casualties. - Graphics and input hooks: Game-mode overlays, per-game lighting profiles, and SDK integrations inject DLLs into game processes or hook DirectX/DirectInput paths. An update that modifies those code paths can turn a lighting hook into an access violation.
- Services and auto-updaters: Persistent services (
CorsairService,Razer Synapse Service,ArmouryCrate.Service,LightingService,CAM,LGHUB Agent) start at boot and re-inject themselves, so a broken component produces repeatable crash loops rather than a one-time failure.
Affected scope
- Platforms: Windows 10 and Windows 11 systems that installed the August 2026 cumulative updates, on builds where third-party RGB control software or RGB peripherals with software-managed lighting are present.
- Not affected: Systems using firmware-level (hardware-controlled) lighting without a software agent, or systems where the RGB suite and its drivers are fully removed.
- CVE status: None. Microsoft has classified this as a compatibility/stability issue, not a security vulnerability. There is no CVE, no CVSS score, and this is not in CISA KEV. Exploitation status is not applicable — but see the security-relevance note below, because the drivers involved are a known attack surface.
Security relevance for defenders
Treat this incident as a forcing function for driver hygiene:
- BYOVD exposure: Several RGB/monitoring driver families have a documented history of abuse — attackers drop a legitimately signed but vulnerable driver, then use it to gain kernel read/write primitives and blind EDR. If your fleet runs RGB software, you very likely have these drivers on disk whether or not the software is actively used.
- Crash loops mask real incidents: A flood of WerFault and application-error noise after Patch Tuesday is exactly the kind of telemetry chaos that buries genuine intrusion artifacts. Baseline and suppress the known-bad pattern so real signal survives.
- Update paralysis: Users told to "just uninstall the security update" create a vulnerability-management regression. You need a controlled workaround path that doesn't leave endpoints unpatched for weeks.
Detection & Response
This is a technical operational threat with a kernel-driver security dimension, so the detections below serve two purposes: (a) identify endpoints in the crash pattern caused by the August 2026 update, and (b) surface the RGB kernel drivers that represent latent BYOVD risk.
Sigma Rules
---
title: RGB Lighting Software Kernel Driver Load
title_note: Stability and BYOVD risk indicator
id: 4c2e8a91-7b3d-4f5e-9a21-6d8c0b2e4f7a
status: experimental
description: Detects load of kernel-mode drivers commonly shipped with RGB lighting and hardware monitoring suites (Corsair iCUE, ASUS Aura/Armoury Crate, MSI, Gigabyte, NZXT, SignalRGB, OpenRGB). These drivers are implicated in post-update instability and are a known bring-your-own-vulnerable-driver (BYOVD) attack surface.
references:
- https://www.bleepingcomputer.com/news/microsoft/microsoft-blames-windows-gaming-issues-on-rgb-lighting-devices/
- https://attack.mitre.org/techniques/T1068/
author: Security Arsenal
date: 2026/08/25
tags:
- attack.privilege_escalation
- attack.t1068
logsource:
category: driver_load
product: windows
detection:
selection:
ImageLoaded|contains:
- 'WinRing0'
- 'inpoutx64'
- 'inpout32'
- 'ene.sys'
- 'ene_i2c'
- 'GLCKIO'
- 'Asusgio'
- 'AsIO'
- 'RTCore64'
- 'NTIOLib'
- 'gdrv.sys'
- 'aginsm64'
- 'corsairVBusDriver'
- 'LHM-WmiProvider'
condition: selection
falsepositives:
- Legitimate RGB control software and hardware monitoring tools installed by end users
- Fan control and thermal monitoring utilities (e.g., FanControl, LibreHardwareMonitor-based tools)
level: medium
---
title: Application Crash Handled by WerFault from RGB or Game Process
id: 8f1d3b56-2a9c-4e7d-b4f0-1c5e7a9d3b82
status: experimental
description: Detects Windows Error Reporting (WerFault.exe) spawning as a child of known RGB lighting control processes or game launchers, indicating the crash pattern associated with the August 2026 Windows update compatibility issue. Useful for scoping affected endpoints and measuring workaround effectiveness.
references:
- https://www.bleepingcomputer.com/news/microsoft/microsoft-blames-windows-gaming-issues-on-rgb-lighting-devices/
author: Security Arsenal
date: 2026/08/25
logsource:
category: process_creation
product: windows
detection:
selection_image:
Image|endswith: '\WerFault.exe'
selection_parent_rgb:
ParentImage|endswith:
- '\iCUE.exe'
- '\Corsair.Service.exe'
- '\Razer Synapse 3.exe'
- '\RazerCentralService.exe'
- '\ArmouryCrate.exe'
- '\ArmouryCrate.Service.exe'
- '\LightingService.exe'
- '\MSI.CentralServer.exe'
- '\CAM.exe'
- '\lghub.exe'
- '\lghub_agent.exe'
- '\SignalRGB.exe'
- '\OpenRGB.exe'
- '\Aurora.exe'
condition: selection_image and selection_parent_rgb
falsepositives:
- Baseline crashes of RGB software unrelated to the update; tune by correlating with update installation date
level: low
KQL (Microsoft Sentinel / Defender)
This query scopes endpoints exhibiting the crash pattern: WerFault activity tied to RGB software or game processes on devices that received August 2026 servicing, plus a sweep for RGB-associated kernel drivers loading via Defender for Endpoint events.
// Part 1: Endpoints in the RGB/game crash pattern after August 2026 patching
let RgbProcesses = dynamic(["icue.exe","corsair.service.exe","razersynapse3.exe","razercentralservice.exe","armourycrate.exe","armourycrate.service.exe","lightingservice.exe","msi.centralserver.exe","cam.exe","lghub.exe","lghub_agent.exe","signalrgb.exe","openrgb.exe"]);
let PatchWindowStart = datetime(2026-08-11);
DeviceProcessEvents
| where TimeGenerated >= PatchWindowStart
| where FileName =~ "WerFault.exe"
| extend CrashingProcess = tolower(InitiatingProcessFileName)
| where CrashingProcess in (RgbProcesses)
or InitiatingProcessFolderPath has_any ("steamapps","epic games","riot games","battle.net","gog galaxy","xboxgames")
| summarize CrashCount = count(),
FirstCrash = min(TimeGenerated),
LastCrash = max(TimeGenerated),
FaultingApps = make_set(InitiatingProcessFileName, 20)
by DeviceName, DeviceId
| where CrashCount >= 3
| order by CrashCount desc;
// Part 2: RGB / monitoring kernel driver loads (BYOVD surface + stability risk)
let RgbDrivers = dynamic(["winring0","inpoutx64","inpout32","ene.sys","ene_i2c","glckio","asusgio","asio","rtcore64","ntiolib","gdrv.sys","corsairvbusdriver"]);
DeviceEvents
| where TimeGenerated >= ago(14d)
| where ActionType has_any ("DriverLoad", "DriverInstall")
| extend DriverName = tolower(tostring(parse_json(AdditionalFields).DriverName))
| extend FileNameLower = tolower(FileName)
| where DriverName has_any (RgbDrivers) or FileNameLower has_any (RgbDrivers)
| project TimeGenerated, DeviceName, ActionType, FileName, FolderPath, DriverName, InitiatingProcessFileName, InitiatingProcessAccountName
| order by TimeGenerated desc
Velociraptor VQL
Use this artifact during triage to enumerate RGB control processes and confirm whether their kernel drivers are present on disk — this tells you whether the endpoint is exposed to both the crash condition and the driver-risk class.
-- Hunt: RGB lighting software processes and kernel driver artifacts
-- Source 1: Running RGB control processes
SELECT Pid, Name, CommandLine, Exe, Username, CreateTime
FROM pslist()
WHERE Name =~ '(?i)(icue|corsair|synapse|razer|armoury|lightingservice|mystic|cam\.exe|lghub|signalrgb|openrgb|aurora)'
-- Source 2: Known RGB / hardware-monitoring kernel drivers on disk
SELECT FullPath, Size, Mtime AS ModifiedTime
FROM glob(globs=[
'C:/Windows/System32/drivers/WinRing0*',
'C:/Windows/System32/drivers/inpout*',
'C:/Windows/System32/drivers/ene*',
'C:/Windows/System32/drivers/GLCKIO*',
'C:/Windows/System32/drivers/Asusgio*',
'C:/Windows/System32/drivers/AsIO*',
'C:/Windows/System32/drivers/RTCore64*',
'C:/Windows/System32/drivers/NTIOLib*',
'C:/Windows/System32/drivers/gdrv*',
'C:/Windows/System32/drivers/*Corsair*'
])
Remediation / Triage Script
Run this PowerShell triage script (elevated) to inventory RGB exposure, identify whether the August 2026 update is installed, capture the crash evidence, and apply the containment workaround (stopping RGB services) without uninstalling the security update.
# Security Arsenal — August 2026 RGB/Game Crash Triage and Containment
# Run elevated. Read-only inventory + optional containment via -Contain switch.
param(
[switch]$Contain # When set, stops and disables RGB control services as a workaround
)
$rgbServices = @('CorsairService','CorsairDeviceControlService','Razer Synapse Service',
'Razer Game Manager Service','ArmouryCrateService','LightingService','asusgio',
'MSI_Central_Service','CAM','LGHUBUpdaterService','SignalRGB*')
$rgbDrivers = @('WinRing0*','inpout*','ene*','GLCKIO*','Asusgio*','AsIO*',
'RTCore64*','NTIOLib*','gdrv*')
Write-Host "=== [1] Installed August 2026 updates ===" -ForegroundColor Cyan
Get-HotFix | Where-Object { $_.InstalledOn -ge (Get-Date '2026-08-11') } |
Select-Object HotFixID, Description, InstalledOn | Format-Table -AutoSize
# NOTE: Identify the specific August 2026 KB via the Windows release health dashboard
# before any uninstall decision. Do not uninstall blindly.
Write-Host "=== [2] RGB control services present ===" -ForegroundColor Cyan
Get-Service | Where-Object { $s = $_.Name; $rgbServices | ForEach-Object { $s -like $_ } } |
Select-Object Name, Status, StartType | Format-Table -AutoSize
Write-Host "=== [3] RGB / monitoring kernel drivers on disk ===" -ForegroundColor Cyan
foreach ($d in $rgbDrivers) {
Get-ChildItem "$env:SystemRoot\System32\drivers\$d" -ErrorAction SilentlyContinue |
Select-Object Name, Length, LastWriteTime
}
Write-Host "=== [4] Recent application crash events (RGB + games) ===" -ForegroundColor Cyan
Get-WinEvent -FilterHashtable @{ LogName='Application'; Id=1000,1001;
StartTime=(Get-Date).AddDays(-14) } -ErrorAction SilentlyContinue |
Where-Object { $_.Message -match '(?i)(icue|corsair|razer|synapse|armoury|lightingservice|lghub|cam\.exe|signalrgb|openrgb|\.dll)' } |
Select-Object -First 25 TimeCreated, Id, @{N='Detail';E={ ($_.Message -split "`n")[0] }} |
Format-Table -AutoSize
Write-Host "=== [5] Vulnerable Driver Blocklist status ===" -ForegroundColor Cyan
$ci = 'HKLM:\SYSTEM\CurrentControlSet\Control\CI\Config'
$blocklist = (Get-ItemProperty -Path $ci -Name 'VulnerableDriverBlocklistEnable' -ErrorAction SilentlyContinue).VulnerableDriverBlocklistEnable
if ($null -eq $blocklist) { Write-Host "Not explicitly configured (verify via Smart App Control / WDAC)" }
else { Write-Host "VulnerableDriverBlocklistEnable = $blocklist (1 = enabled)" }
if ($Contain) {
Write-Host "=== [6] CONTAINMENT: Stopping RGB services (workaround, update stays installed) ===" -ForegroundColor Yellow
Get-Service | Where-Object { $s = $_.Name; $rgbServices | ForEach-Object { $s -like $_ } } |
ForEach-Object {
Write-Host "Stopping and disabling: $($_.Name)"
Stop-Service -Name $_.Name -Force -ErrorAction SilentlyContinue
Set-Service -Name $_.Name -StartupType Disabled -ErrorAction SilentlyContinue
}
Write-Host "Containment applied. Re-test game launch, then re-enable once vendor fix is available." -ForegroundColor Yellow
}
Remediation
Immediate (stop the crash loop without unpatching):
- Do not reflexively uninstall the August 2026 cumulative update. It carries security fixes; removing it re-opens vulnerabilities. Exhaust the workaround path first.
- Update the RGB vendor software to the latest release. Vendors (Corsair, Razer, ASUS, MSI, NZXT, Logitech, SignalRGB) typically ship compatibility fixes within days of a breaking Windows update. Update both the application and its bundled drivers.
- If no vendor fix exists yet, disable the RGB software as a workaround: stop and disable the associated services (see the script above with
-Contain), or uninstall the suite. Hardware-default lighting will persist; game stability returns. Verify with a controlled game launch before returning the endpoint to service. - Watch the Windows release health dashboard for the specific KB and for a possible Known Issue Rollback (KIR). If Microsoft publishes a KIR, deploy the KIR Group Policy MSI to managed devices — it neutralizes the offending change while keeping the security fixes installed.
- Clean-boot validation for stubborn cases: use
msconfigto disable all non-Microsoft services and startup items, re-enable in halves, and confirm the RGB component as the faulting party before escalation.
Strategic (close the driver-risk class):
- Enable the Microsoft Vulnerable Driver Blocklist (registry:
HKLM\SYSTEM\CurrentControlSet\Control\CI\Config,VulnerableDriverBlocklistEnable = 1) or enforce it via WDAC / Intune policy. This directly reduces the BYOVD exposure that RGB and hardware-monitoring drivers introduce. - Govern RGB software like the privileged software it is. It installs kernel drivers and auto-updaters — it belongs in your application control policy, not on an end-user self-service free-for-all. Where lighting control is cosmetic, standardize on firmware-controlled lighting and remove the software agent entirely.
- Baseline WER telemetry post-Patch Tuesday. Suppress the known RGB crash signature in your dashboards so genuine crash-for-intrusion artifacts (exploit crashes, EDR tampering) remain visible.
- Track this as a recurring pattern. Windows servicing vs. third-party kernel drivers is a repeat offender class (RGB suites, anti-cheat, hardware monitors, VPN filter drivers). Build a post-patch validation ring that includes endpoints with these driver families so you catch the next collision in a pilot ring rather than fleet-wide.
Related Resources
Security Arsenal Healthcare Cybersecurity AlertMonitor Platform Book a SOC Assessment healthcare Intel Hub
Is your security operations ready?
Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.