Supported Devices List (Keyboards Mice Headsets Hubs): 2025 Edition

Windows Dynamic Lighting lets Windows 11 control the RGB lighting of supported keyboards, mice, headsets, hubs, laptops, and even motherboards through an open HID standard called LampArray. If you’ve ever struggled to keep lighting in sync across brands, or you want fewer apps to run in the background, this guide is for you.

This 2025 Edition focuses on compatibility and setup. You’ll learn which devices work, what Windows and app versions you need, how to enable the feature, and how to fix common issues like devices not appearing, desync, or effects resetting after a reboot. We also include best practices to keep CPU usage low and examples for gaming, streaming, and productivity.

What is Windows Dynamic Lighting
Windows Dynamic Lighting is a built-in Windows 11 feature that exposes a universal way to control lighting on devices that support the HID LampArray standard. In practice, it means:

• One place in Windows to set color, brightness, and basic effects for multiple brands.
• Optionally sync lighting with your Windows accent color.
• Fewer vendor apps needed, fewer conflicts, and less CPU overhead.

Typical scenarios where Dynamic Lighting shines:

• Gaming: match your setup to game art, team colors, or stream scenes.
• Streaming/content creation: drive lighting from one profile without juggling multiple apps.
• Productivity: use color cues for notifications, focus time, and app context.

System requirements and prerequisites

• Windows version:
  • Windows 11 23H2 or later strongly recommended.
  • Best results on build 22631.3007 or newer (2024-2025 cumulative updates). Keep Windows Update current.
• Hardware/driver requirements:
  • Your device must support the HID LampArray standard natively or via a vendor “bridge” (a setting in OEM software that exposes the device to Windows).
• Vendor app versions (when required to enable the “Windows control” bridge):
  • Razer Synapse 3.9+ (Windows Dynamic Lighting toggle)
  • Corsair iCUE 5.7+ (Windows Dynamic Lighting toggle)
  • ASUS Armoury Crate 5.9+ / Aura Sync components (Windows Dynamic Lighting or “Enable in Windows” toggle)
  • Logitech G HUB 2024.x+ (Dynamic Lighting support for selected Logitech G devices)
  • HyperX NGENUITY 2.3x+ (Windows Dynamic Lighting toggle on select devices)
  • HP OMEN Gaming Hub 11.x+ (expose lighting to Windows for supported OMEN gear)
  • Acer PredatorSense 4.x+ (supported Predator laptops/peripherals)
  • MSI Center Mystic Light 2.x+ (varies by board/device)
  • Others may add support over time; always check release notes.
• Connection:
  • USB (wired) is most reliable for initial detection. Some devices support Bluetooth control; results vary by model.
• Permissions:
  • If your organization manages PCs, Dynamic Lighting can be blocked via policy. You’ll need admin rights to install vendor bridges/firmware when required.

Supported devices list: 2025 Edition
Important: A device must identify itself (directly or via vendor bridge) as a HID LampArray for Windows to control it. Vendor lists evolve quickly; firmware and app versions matter. Use the “How to check” steps below to confirm support on your system.

How to check if your device supports Dynamic Lighting

1. In Windows:

   • Go to Settings > Personalization > Dynamic Lighting.
   • If you see your device by name, it’s supported.

2. In Device Manager:

   • Expand Human Interface Devices.
   • Look for entries containing “LampArray” or “Lighting”.
   • If present, your device is exposing the HID LampArray interface.

3. With PowerShell:

   • Run as Administrator:
     PowerShell
     Get-PnpDevice -Class ‘HIDClass’ | Where-Object { $_.FriendlyName -match ‘Lamp|Light|RGB’ } | Format-Table -Auto

4. In vendor software:

   • Look for a setting such as “Enable Windows Dynamic Lighting,” “Allow Windows to control lighting,” or “Expose to Windows.” Turn that on, apply, then re-open the Windows Dynamic Lighting page.

Keyboards (examples and families commonly reported as compatible)

• Razer (Synapse 3.9+ with Windows Dynamic Lighting enabled)
  • Families: Razer BlackWidow (V3/V4), Huntsman (Mini/TE/V2/V3), DeathStalker V2, Ornata V3
  • Notes: Most per-key RGB models are supported; update firmware.
• Corsair (iCUE 5.7+ with Dynamic Lighting)
  • Families: K-series (K65/K70/K95, Pro variants), K100/K70 Max, Strafe RGB
  • Notes: Per-key control works; use iCUE toggle to hand off control to Windows.
• ASUS ROG (Armoury Crate 5.9+ / Aura components)
  • Families: ROG Strix Scope II, ROG Falchion, ROG Azoth, TUF Gaming K-series
  • Notes: Ensure Aura service and AC modules are up to date; enable “Windows control.”
• Logitech G (G HUB 2024.x+)
  • Families: G Pro X TKL, G915/G815, G513, G213
  • Notes: Newer releases add models; check G HUB release notes.
• HyperX (NGENUITY 2.3x+)
  • Families: Alloy Origins, Alloy Rise series
  • Notes: Toggle Windows control in NGENUITY.
• HP OMEN
  • Families: OMEN Sequencer, OMEN Spacer, select Victus/OMEN laptop keyboards
  • Notes: Use OMEN Gaming Hub to bridge control to Windows.
• Acer Predator
  • Families: Predator laptops with RGB keyboards; select Predator Aethon keyboards
  • Notes: PredatorSense required for hand-off.
• Other brands with growing support (model-dependent): Cooler Master, Glorious, Ducky (per-key RGB variants with updated firmware), Keychron gaming lines, and boutique brands that ship LampArray firmware. Check vendor notes for “Windows Dynamic Lighting” or “HID LampArray” support.

Mice (examples and families)

• Razer
  • Families: Basilisk V3, Cobra, Naga (RGB variants), Viper (RGB variants)
• Logitech G
  • Families: G502 X, G203/G305 (RGB models), G Pro/G Pro X (RGB ring/logo)
• Corsair
  • Families: M65, Scimitar, Dark Core, Nightsabre, Harpoon RGB
• ASUS ROG/TUF
  • Families: ROG Gladius III/IV, Keris, Strix Impact
• HyperX
  • Families: Pulsefire Haste 2 (RGB), Pulsefire Surge
• Notes: Some “Pro” mice remove RGB for weight/battery. For wireless, use the dongle; some Bluetooth modes do not pass LampArray.

Headsets, microphones, webcams (RGB-capable models)

• Razer
  • Kraken V3 line, BlackShark V2 Pro (RGB variants), Seiren Emote (mic)
• HyperX
  • Cloud Alpha/Cloud II (RGB variants), QuadCast S (mic, per-zone RGB)
• Logitech G
  • G733/G935 (RGB headsets), StreamCam with RGB ring (if present)
• Corsair
  • Void/HS80 RGB, Virtuoso RGB, Elgato Wave DX with RGB ring (model-dependent)
• ASUS ROG
  • ROG Delta S/Theta (RGB variants)
• Notes: Audio gear varies widely; look for explicit mention of Windows Dynamic Lighting or HID LampArray in release notes.

RGB hubs, controllers, motherboards, laptops

• Motherboards with addressable RGB headers
  • ASUS ROG/TUF boards with Aura Gen 2 headers
  • MSI Mystic Light boards
  • Gigabyte AORUS boards with RGB Fusion
  • ASRock Polychrome
  • Notes: Most require OEM software to bridge headers as a LampArray to Windows; look for a “Windows control” toggle.
• Controllers/Hubs
  • Corsair iCUE Commander Core/XT/Pro
  • Razer Chroma Addressable RGB Controller
  • ASUS ROG Aura Terminal / ARGB Controller
  • NZXT RGB & Fan Controller (model-dependent through CAM updates)
  • Notes: These often do not natively present as LampArray; OEM software must expose them to Windows.
• Laptops and prebuilts
  • ASUS ROG/Strix, Acer Predator/Helios, HP OMEN/Victus, select Lenovo Legion, MSI gaming laptops
  • Notes: Use the OEM’s utility to enable Windows control of the keyboard underglow or light bars.

Devices that typically do NOT work

• Peripherals with single-color LEDs only (no RGB).
• Legacy devices whose drivers were never updated to HID LampArray.
• Some wireless-only/Bluetooth-only devices without vendor bridge support.
• ARGB strips connected to controllers that don’t expose LampArray (and no OEM bridge).

Step-by-step: Enable and configure Dynamic Lighting

1. Update Windows and drivers

   • Settings > Windows Update > Check for updates.
   • Install optional driver/firmware updates if available.
   • Reboot.

2. Update vendor software and firmware

   • Open the OEM app (e.g., Razer Synapse, Corsair iCUE, ASUS Armoury Crate, Logitech G HUB, HyperX NGENUITY, OMEN Gaming Hub).
   • Update to the latest version.
   • Apply any firmware updates for each device.

3. Turn on the bridge/toggle in the OEM app

   • Look for settings like:
     • “Enable Windows Dynamic Lighting”
     • “Allow Windows to control lighting”
     • “Expose to Windows / HID LampArray”
   • Turn it on for each device you want Windows to control.
   • If the app asks, select “Let Windows control lighting” or similar.

4. Enable Dynamic Lighting in Windows

   • Go to:
     Settings > Personalization > Dynamic Lighting
   • Toggle “Use Dynamic Lighting on my devices” to On.
   • Optionally enable “Match my Windows accent color.”
   • Adjust Brightness and choose an Effect (e.g., Solid color, Breathing, Rainbow/Wave; options vary by build).
   • Select individual devices to set per-device behavior.

5. Resolve control conflicts

   • In OEM apps, set device profiles to “Windows control” or “No effect” to avoid dueling effects.
   • If you want Windows to be the only controller, disable OEM background effects.

6. Optional: Sync more deeply

   • For multi-brand rigs, keep vendor apps installed only to expose devices to Windows, but turn off their effects.
   • Keep color temperature/brightness consistent across devices by using the Windows page as the single source of truth.

Troubleshooting: common issues and fixes
Device not detected in Dynamic Lighting

• Use a direct USB connection (avoid unpowered hubs). Try a different port.
• Confirm the OEM “Enable Windows control” toggle is on and firmware is updated.
• Device Manager > Human Interface Devices: verify a LampArray entry exists. If not, reinstall the vendor app.
• PowerShell check:
  PowerShell
  Get-PnpDevice -Class ‘HIDClass’ | Where-Object { $_.FriendlyName -match ‘Lamp|Light|RGB’ }
• Uninstall and reinstall the OEM app; reboot.
• For wireless devices, connect via the USB dongle and ensure the dongle firmware is current.
• If on a managed PC, ask your admin whether Group Policy restricts Dynamic Lighting.

RGB desync or wrong colors

• Disable effects in all OEM apps; let Windows be the only active controller.
• Set all devices to the same color space/brightness in Settings > Personalization > Dynamic Lighting.
• Avoid mixing per-key effects with global effects at the same time.
• Update all apps/firmware; mismatched firmware can cause color drift.

Profiles reset after reboot or wake

• In your OEM app, verify that “Windows control” persists across reboots (some apps have a “make default” option).
• Don’t clean-start vendor services you still need for LampArray bridging.
• Check Fast Startup:
  • Control Panel > Power Options > Choose what the power buttons do > Change settings that are currently unavailable > uncheck “Turn on fast startup” > Save.
• If using multiple Windows user accounts, configure Dynamic Lighting for each account separately.

Flickering, stutters, or high CPU usage

• Use simpler effects (Solid/Breathing) and reduce effect speed.
• Close redundant OEM lighting engines (e.g., only iCUE running to expose devices, but effects off).
• Disable third-party overlays and SDKs that also grab lighting (e.g., game integrations, stream tools) and test again.
• Update GPU drivers; compositing conflicts can affect lighting effects timing.
• Check USB power:
  • Device Manager > USB controllers > disable aggressive USB power savings for hubs where devices are connected.

Device turns off or changes color when the screen locks

• Settings > Personalization > Dynamic Lighting:
  • Verify lock screen behavior. Some builds include “Allow effects on lock screen.”
• Some OEMs revert to hardware profiles when the PC is locked or asleep. Enable “Windows control” on resume in the OEM app if available.

Bluetooth devices don’t respond

• Use the USB dongle or wired connection for initial setup.
• Some Bluetooth modes don’t pass LampArray; check your device manual and firmware notes.

Performance and best practices

• One controller to rule them all: pick Windows Dynamic Lighting as the master, and in every OEM app:
  • Turn on the “Expose to Windows” toggle.
  • Turn off vendor effects and game integrations to reduce background CPU.
• Minimize running apps: uninstall legacy RGB suites you no longer need. Keep only the app that’s required to expose LampArray (if necessary).
• Keep firmware aligned: update all devices at the same time to avoid desync or lost zones.
• Use USB wisely: connect high-bandwidth RGB devices to motherboard ports instead of daisy-chaining through hubs.
• Prefer static or slow effects if you’re sensitive to CPU spikes or micro-stutter in games.
• Back up your settings:
  • Many OEM apps let you export device firmware profiles.
  • Take a screenshot of your Dynamic Lighting page for a quick restore reference.

Use cases and creative ideas

• Gaming themes
  • Match team or game colors across brands with a single Windows setting.
  • Set a subtle ambient color for long sessions to reduce eye fatigue.
• Streaming/Recording
  • Align peripheral lighting to your stream branding or scene transitions.
  • Use vendor SDK features only when needed; otherwise let Windows hold the baseline look.
• Productivity cues
  • Use a calm blue or warm white for focus time; switch to vivid colors for breaks.
  • Combine with Focus sessions in Windows to change accent color and keep lighting in sync.
• Notifications and status
  • Tie accent color to system theme switches (e.g., night mode warms up lighting).
  • Some third-party tools can change Windows accent color via scripts; your RGB can follow automatically.

Quick reference: Windows settings

• Open the panel:
  Settings > Personalization > Dynamic Lighting
• Common controls:
  • Use Dynamic Lighting on my devices
  • Match my Windows accent color
  • Brightness, Effects, Speed
  • Per-device overrides

Quick reference: What the OEM toggle might be called

• Razer Synapse: “Enable Windows Dynamic Lighting”
• Corsair iCUE: “Enable Windows Dynamic Lighting” or “Allow Windows control”
• ASUS Armoury Crate: “Enable in Windows” / “Expose to Windows” under Aura
• Logitech G HUB: “Dynamic Lighting” switch for the device
• HyperX NGENUITY: “Windows Dynamic Lighting”
• HP OMEN Gaming Hub: “Allow Windows to control lighting”

Notes on RGB hubs and ARGB strips

• Many ARGB controllers don’t natively speak LampArray. The vendor app must create a “bridge” device so Windows sees a LampArray and sends commands through the app to your strips/fans.
• If your fans/strips aren’t showing:
  • Confirm the controller is detected in the OEM app.
  • Enable the Windows control bridge in that app.
  • Ensure all ports/zones are assigned to the same controller profile that Windows is allowed to control.

Security and privacy considerations

• You don’t need to grant broad network permissions just for Windows Dynamic Lighting to work.
• If an OEM app requests firewall exceptions only for cloud features, you can usually decline and still use the local Windows control bridge.

Conclusion
Windows Dynamic Lighting in 2025 makes mixed-brand RGB setups much simpler. With the right Windows build, current vendor apps, and the “Enable Windows control” toggle, you can keep keyboards, mice, headsets, hubs, and even motherboard lighting in sync—without juggling multiple lighting engines. If a device doesn’t show, update firmware, confirm the LampArray interface appears in Device Manager, and remove conflicting effects. Once configured, Dynamic Lighting delivers a stable, low-overhead lighting setup you can rely on.

FAQ
How do I know if my device is officially supported?

• Check Settings > Personalization > Dynamic Lighting; if it appears by name, it’s supported. You can also look in Device Manager for a LampArray device after enabling the OEM bridge.

Do I still need my vendor app after turning on Dynamic Lighting?

• Often yes, but only to expose the device to Windows and handle firmware updates. Turn off OEM effects to avoid conflicts; let Windows drive the color/effects.

Why does my lighting change when I lock or sleep the PC?

• Some devices fall back to a hardware profile when Windows isn’t in control. Check Windows lock screen options and your OEM app for a “resume with Windows control” setting.

Can I use game integrations (like Chroma/iCUE) and Dynamic Lighting together?

• You can, but for stability choose one controller at a time. If a game takes over lighting via an OEM SDK, you may see desync. For best consistency, stick with Windows for baseline and enable game integrations only as needed.

Does Bluetooth support Dynamic Lighting?

• It depends on the device. Many vendors support LampArray over wired/USB dongle but not over Bluetooth. Use the dongle or a cable for full control, especially during setup.