Asus Motherboard Not Showing Up in iCUE | Quick Fixes

How Asus And iCUE Work Together

When everything is set up correctly, iCUE talks to your Asus motherboard through a chain of software layers.
iCUE relies on its Asus plugin, Windows services, and Asus Armoury Crate with Aura Sync to read lighting data and send new RGB effects.
If any piece in this chain is missing or out of date, the motherboard tile can vanish from the iCUE home screen.

The basic flow looks like this: your Asus board exposes lighting control to Aura Sync, Armoury Crate handles device management, the Asus lighting service sits in the background, and the iCUE Asus plugin hooks into that service.
A bad update, a removed plugin, or a blocked SDK process can stop this link, so iCUE no longer sees the board even though Aura Sync still does.

Before you worry about hardware failure, treat an asus motherboard not showing up in icue as a software handshake issue first.
In most cases, methodical checks around plugins, services, and versions bring the motherboard tile back without touching cables or headers.

Symptom	What To Check	Where To Check It
Motherboard tile missing in iCUE	Asus plugin and SDK access	iCUE > Settings > Plugins / SDK
Aura Sync works, iCUE does not	iCUE plugin, game list entry	Armoury Crate > Aura Sync > In-game lighting
Random disconnects	Updates, service crashes, USB instability	Windows Update, Task Manager, chipset drivers

Quick Checks When Asus Motherboard Not Showing Up in iCUE

Start with simple steps.
These quick checks often clear a stuck link between iCUE and Armoury Crate without a full reinstall.

1. Restart iCUE And Windows — Close iCUE from the tray, end any remaining iCUE tasks in Task Manager, then reboot your PC so background services start in the right order.
2. Open Armoury Crate And Confirm Detection — Make sure your Asus board shows under the Devices page and reacts to Aura Sync changes.
   If Armoury Crate does not see the board, fix that first.
3. Check The iCUE Home Screen — After Windows loads, wait a minute, then open iCUE and look for an Asus motherboard tile.
   If the tile flashes in briefly and then disappears, you likely have a plugin or SDK issue.
4. Verify USB And Power — Confirm the 24-pin power, CPU power, and any RGB headers are fully seated.
   If you recently moved the PC, a loose header can break lighting control even when the system boots fine.
5. Confirm Single RGB Controller — Avoid running older standalone Aura software next to Armoury Crate and iCUE.
   Multiple lighting suites can fight for the same service and stop iCUE from reading the board.

If these quick checks change nothing and the asus motherboard not showing up in icue problem stays the same, move on to version and plugin checks.
Most long-term fixes live there.

Update iCUE, Asus Plugin, And Armoury Crate

Version mismatch sits near the top of real-world causes.
A new iCUE release can require an updated Asus plugin, while Armoury Crate updates can change how the Aura service exposes lighting.
Keeping all three parts in sync gives you the best shot at a clean handshake.

1. Update Windows First — Run Windows Update and install pending cumulative updates.
   Some Aura and iCUE components rely on up-to-date system libraries and .NET versions.
2. Update Armoury Crate And Aura Sync — Open Armoury Crate, go to Settings then the update center, and apply all listed updates.
   Restart the PC after they finish so the lighting service refreshes.
3. Update iCUE To The Latest Stable Build — Use the built-in updater or grab the current installer from the Corsair download page.
   Avoid very old versions unless a known bug forces a temporary roll-back.
4. Verify The Asus Plugin In iCUE — In iCUE, open Settings, switch to the Plugins tab, and confirm the Asus plugin is listed and enabled.
   If the plugin is missing, install it, then fully restart Windows.
5. Wait For The First Sync — After the reboot, give iCUE and Armoury Crate a full minute after login before checking the iCUE home screen.
   The first handshake can take a moment while services load.

If the Asus motherboard tile appears after these updates, set a habit of checking for new builds every few months so the connection stays steady.
Skipping updates for long stretches is a common path to silent breakage after a big Windows release.

Check SDK, Aura Sync, And Background Services

Even with current versions, iCUE still needs explicit permission to talk to Asus lighting services.
That permission lives in SDK settings, service entries, and Aura Sync in-game lighting options.
A single blocked process can stop detection while every app claims to be installed correctly.

1. Enable iCUE SDK Access — In iCUE, open Settings, then the SDK section.
   Make sure SDK support for external applications is turned on so iCUE can interact with Asus lighting services.
2. Allow LightingService Processes — Still under the SDK section, check the list of applications.
   If you see entries related to Asus lighting, such as LightingService, make sure they are allowed rather than blocked.
3. Configure Aura Sync In-Game Lighting — In Armoury Crate, go to Aura Sync, open Aura Effects, then enable in-game lighting and open the game list.
   Drag the iCUE device plugin entry over the Aura Sync line so the two can share control.
4. Confirm Background Services Are Running — Open Task Manager and look for Asus lighting services, Armoury Crate services, and iCUE processes.
   If any of them crash or vanish, try restarting those entries or rebooting.
5. Test With Simple Lighting Effects — In Armoury Crate, set a basic static color on the motherboard.
   Then open iCUE and see whether the tile appears and accepts a new effect.
   Simple effects reduce confusion while you test the link.

This SDK and service pass solves many cases where iCUE and Armoury Crate both claim to be healthy yet the board never shows in the device list.
Once the Asus plugin can talk to the Aura lighting service without blocks, the tile usually returns.

Reinstall iCUE And Armoury Crate Without Leftovers

If updates, plugins, and SDK checks do not help, a clean reinstall of both suites is the next step.
The goal is to clear leftover files, stale registry entries, and service hooks that a normal uninstall leaves behind.

Prepare For A Clean Reinstall

1. Back Up iCUE Profiles — In iCUE, export your custom profiles to files so you can restore them later.
   This keeps lighting layouts and macros safe while you experiment.
2. Uninstall iCUE And Asus Software — Use Windows Apps & Features to remove iCUE, Armoury Crate, and any older Aura Sync tools.
   Restart once the removals finish.
3. Run Official Cleanup Tools If Available — Asus and Corsair both offer cleanup utilities for stubborn installs.
   Run them once, follow their prompts, then restart again to clear remaining services.

Install Armoury Crate Before iCUE

1. Install Armoury Crate Fresh — Download the latest installer from the Asus site and install it first.
   Once it opens, let it detect your motherboard and install required device packages.
2. Update Armoury Crate Components — Visit the update center inside Armoury Crate and apply every pending item, then restart so the new lighting service version takes over.
3. Install The Latest iCUE — Grab the current iCUE installer from the Corsair download page and install it.
   After the setup finishes, open iCUE and confirm that the Asus plugin appears in the Plugins tab.
4. Turn On SDK And Check For The Tile — Re-enable SDK access, restart Windows one more time, then open iCUE and look for the Asus motherboard tile on the home screen.

This reinstall order gives Armoury Crate a clean base before iCUE adds its own plugin.
In many stubborn cases, this is the first time iCUE can talk to the board again after a long string of small updates and partial removals.

When Asus Motherboard Still Not Showing Up in iCUE

If you still face an Asus motherboard not showing up in iCUE after a clean reinstall and careful SDK checks, the problem may sit with a specific software build or a rare compatibility edge case.
At that point, your next steps focus on version workarounds and direct help from the vendors.

1. Check Known Issues For Your iCUE Version — Visit the iCUE release notes and user forum to see if others with the same motherboard and iCUE build report missing devices.
   When a release breaks Asus detection, you will often see a pattern of similar posts.
2. Test One Older Or Newer Build — If many reports match your case on a specific build, try one step back or forward in iCUE versions if a newer hotfix is available.
   Stay close to the current branch so you still receive security and bug patches.
3. Confirm Motherboard Model Support — Double-check that your exact Asus board appears on the Aura Sync and iCUE compatibility lists.
   Most recent Aura-capable boards do, but very old or entry-level models may never expose full lighting control to iCUE.
4. Test Lighting In Armoury Crate Only — As a final cross-check, close iCUE and use only Armoury Crate for a short session.
   If lighting still behaves oddly, the root cause may be a firmware or board-level fault instead of iCUE alone.
5. Open Tickets With Asus And Corsair — Gather logs, screenshots, exact version numbers, and your motherboard model, then open help tickets with both vendors.
   Clear details give their teams more to work with and may reveal a hidden patch or beta build that fixes detection.

Motherboard detection bugs can be stubborn, but methodical testing around versions, plugins, and services narrows the field.
Once you know whether the issue follows a certain iCUE build, Armoury Crate release, or just your own system, it becomes much easier to get a targeted fix from the vendor teams.

Keep iCUE And Asus Lighting Stable Over Time

Once your Asus motherboard shows up again in iCUE, a few simple habits help keep it that way.
Treat iCUE and Armoury Crate as a pair: when you update one, check the other on the same day, and always reboot once so new services start cleanly.

Try to avoid stacking multiple RGB suites from other vendors alongside iCUE and Armoury Crate.
Extra apps that hook into the same lighting services can cause silent conflicts that look just like the original problem.
If you add new hardware from a third brand, keep its lighting tool off unless you really need it for a specific device setting.

Finally, take a moment to export your iCUE profiles whenever you make large changes.
That simple backup step turns future troubleshooting into a low-stress process because you can reinstall software, bring back your profiles, and confirm that both your Corsair gear and Asus motherboard light up exactly the way you like.