How to Fix ASUS ROG Ally Controller Not Detected in Windows

Mine died mid-boss-fight, of course — joysticks just went limp while the screen stayed on, and switching to desktop mode brought it right back like nothing happened. That desktop-works-but-game-mode-doesn’t pattern shows up constantly in ASUS‘s own ROG forum, and it’s genuinely one of the more diagnosable versions of “controller not detected,” so if that’s your exact symptom, you’re in a good spot to fix this fast.

Quick Answer

• Try the soft reset first: hold the power button a full 10 seconds until it fully powers down, wait 10 seconds, boot back up
• Check joy.cpl (Windows Game Controllers panel) to confirm whether Windows even sees the controller at all
• Open Command Center and confirm Embedded Controller is set to Enabled — toggle it off and back on if it already is
• Check for a stray Handheld Companion, Chiaki4Deck, or emulator process running in Task Manager — these are known to silently break the controller driver
• If nothing else works, a factory reset (Keep My Files) reinstalls Windows and all ASUS drivers cleanly

Why This Happens

So the frustrating thing about this specific problem is that “not detected” actually covers a few genuinely different failure states, and they need different fixes. Worth sorting out which one you’re actually dealing with before troubleshooting further.

Armoury Crate SE crashed without taking the whole system down. On several ROG Ally generations, the built-in controller input routes through Armoury Crate SE itself. If that app freezes or crashes silently — which happens more often right after a Windows update — the controller goes unresponsive even though everything else on the device still works fine.

The Embedded Controller setting got disabled, sometimes automatically. ASUS’s own support documentation flags this directly: if you’ve ever connected an external controller, some games default to that instead of the built-in one, and the Embedded Controller toggle in Command Center can end up switched off as a result, even after you disconnect the external one.

Third-party software is interfering with the controller driver. This is the one that surprised me most digging into ASUS’s forums — tools like Handheld Companion, Chiaki4Deck, or certain emulators can conflict with the Xbox 360 Controller for Windows driver that the Ally’s gamepad relies on. Multiple users specifically traced their “controller works in desktop but not gaming mode” issue back to one of these running quietly in the background.

Windows lost the driver binding, especially after sleep/wake cycles. Sometimes the hardware is completely fine, but Windows itself has just lost track of the connection. This shows up as the controller appearing as “Not connected” in the Game Controllers panel even though nothing physically changed.

Aggressive power-saving settings cutting power to the USB bus. In Silent mode specifically, battery-saving behavior can cut power to the internal USB bus the controller relies on, which produces symptoms that look identical to a driver problem but are actually a power management setting.

Common Scenarios

• Works in desktop mode, dead in-game or in Armoury Crate itself — classic Embedded Controller or driver binding issue, very commonly fixable
• Right after a Windows update — Armoury Crate SE crash is the most likely culprit
• After using Chiaki4Deck, an emulator, or Handheld Companion — third-party software conflict with the controller driver
• Only in specific games (reported with titles like Disney Dreamlight Valley) — game-specific control mode conflict, often fixed by switching to Auto Mode
• After extended time in Silent/battery-saver mode — power management cutting the USB bus

Technical Comparison Table

Step-by-Step Fixes

Step 1: Try the soft reset first

Hold the power button for a full 10 seconds until the screen goes completely black — don’t just tap it for a normal shutdown. Wait about 10 seconds, then press it again to boot up. This clears whatever temporary state the controller driver or Armoury Crate SE got stuck in, and it resolves the issue in the majority of one-off cases.

Step 2: Check if Windows even sees the controller

Press the Windows key, type joy.cpl, and hit Enter. This opens the Game Controllers panel directly. If you see ASUS ROG Ally Controller listed and its status is OK, the driver binding is fine and the problem is more likely at the app level (Armoury Crate, Steam, or a specific game). If it shows “Not connected,” Windows has lost the driver binding entirely.

Step 3: Check the Embedded Controller setting

Press the Command Center button to bring up the tool menu. Look for Embedded Controller and confirm it’s set to Enabled. If it’s already enabled but the controller still isn’t working, disable it, wait a moment, then re-enable it — this forces a fresh handshake rather than relying on whatever state it was stuck in.

If you don’t see Embedded Controller as an option at all, it’s likely been removed from your Command Center layout. Open Armoury Crate, select Edit Command Center, and add Embedded Controller back into an empty slot.

Step 4: Check Task Manager for conflicting software

Open Task Manager and look specifically for Handheld Companion, or any emulator or streaming tool (Chiaki4Deck being a specifically documented culprit) running in the background. If you find one, close it, restart the Ally, and test the controller again before reopening that program.

Step 5: Reinstall the controller driver through Device Manager

Open Device Manager, expand Human Interface Devices, and locate the ROG Ally controller entry. Right-click and select Uninstall device, then restart. Windows will automatically reinstall the driver fresh on boot, which resolves cases where the existing driver binding got corrupted.

Step 6: Check for pending updates across all three layers

Controller issues on the Ally often trace back to a mismatch between Windows, Armoury Crate SE, and BIOS/firmware versions rather than any single one being outdated. Check Armoury Crate for app updates, check MyASUS for firmware, and check Windows Update — updating just one of these in isolation sometimes doesn’t fully resolve the issue if the others are also behind.

Step 7: Switch to Auto Mode if it’s a specific game

If the controller works fine everywhere except one particular game, try switching your control mode to Auto Mode rather than manually forcing Gamepad or Desktop Mode. Manually switching modes overrides per-game custom profiles, and some games specifically need Auto Mode to correctly recognize the embedded controller.

What Actually Worked For Me

My first move was the soft reset, mostly out of habit, and it did absolutely nothing — controller stayed dead in-game, worked fine navigating the desktop, which honestly made me second-guess whether it was even a real hardware problem versus something more specific.

Turned out I’d installed an emulator a few days earlier and completely forgotten about it sitting in the background. Found it in Task Manager, closed it, restarted the Ally, and the controller came right back to life in-game. Kind of an anticlimactic fix after assuming I’d need a full driver reinstall, but it’s exactly the kind of thing that’s easy to overlook because it doesn’t feel related to a “controller” problem at all.

Advanced Fixes and Edge Cases

HideHid and similar controller-remapping utilities. If you’ve ever installed a tool that hides or remaps HID devices (HideHid specifically has been flagged in ASUS’s own forums), uninstalling it entirely — not just disabling it — has resolved cases where standard troubleshooting didn’t touch the problem.

Factory reset when nothing else works. If you’ve tried the soft reset, driver reinstall, and closed all conflicting software and it’s still unreliable, a factory reset gives you a genuinely clean slate. Go to Windows Settings > System > Recovery > Reset this PC, choose Keep my files to preserve your games and data, and let it reinstall Windows along with all ASUS drivers fresh. Update Windows fully and reinstall the latest Armoury Crate SE afterward.

BIOS-level detection as a diagnostic clue. If the controller is detected correctly when you’re inside BIOS but not once Windows loads, that’s a strong signal the hardware itself is fine and the issue lives entirely within Windows or Armoury Crate — worth mentioning specifically if you end up needing to contact ASUS support, since it rules out a hardware fault immediately.

When it’s genuinely a hardware issue. If a full factory reset with a completely fresh Windows install still doesn’t resolve it, and the controller is confirmed non-functional even at the BIOS level, that points toward an actual hardware fault rather than anything software-side, and warranty service becomes the realistic next step.

Prevention Tips

• Keep Windows, Armoury Crate SE, and BIOS/firmware updated together rather than letting one lag behind the others
• Avoid running emulators, Chiaki4Deck, or Handheld Companion unless you’re actively using them, and fully close them afterward rather than leaving them running in the background
• Use Auto Mode as your default control mode unless a specific game requires manual switching
• Do a soft reset as routine maintenance if you notice Armoury Crate behaving oddly, rather than waiting for a full controller failure

FAQ

Why does my controller work in desktop mode but not in games? This is most often an Embedded Controller setting that’s been disabled, or a driver binding issue specific to gaming/gamepad mode. Check joy.cpl and the Command Center setting first.

Is this a hardware problem or software? Software in the vast majority of documented cases — driver conflicts, Armoury Crate crashes, or third-party software interference. Hardware failure is possible but should be your last conclusion, not your first.

Does a factory reset erase my games? Not if you choose “Keep my files” during the reset process. It reinstalls Windows and drivers while preserving your personal data and installed games.

Can Chiaki4Deck or emulators really break the built-in controller? Yes, this has been specifically documented in ASUS’s own community forums as a real conflict with the Xbox 360 Controller for Windows driver the Ally depends on.

Should I update Armoury Crate, Windows, or BIOS first? There’s no strict order, but update all three around the same time rather than just one — a mismatch between versions is a more common cause of persistent issues than any single outdated component.

Editor’s Opinion

check task manager for stray background apps before you touch device manager or reinstall anything — chiaki4deck and handheld companion specifically have a track record of quietly breaking the controller driver, and its an easy thing to forget you even have running. soft reset first since its free and fast, but dont expect it to fix an actual software conflict; those need the process closed, not just a restart.