Armoury Crate Stuck on Loading Screen: 7 Proven Fixes (2026)

by

I opened Armoury Crate one morning after a Windows update and watched the loading spinner go for eleven minutes. Not buffering, not thinking. Just spinning. The app had loaded fine the night before. Nothing changed except a 2am update that apparently disagreed with whatever Armoury Crate was trying to do.

I’ve since fixed this on four different machines, including two ROG desktops, one TUF laptop, and one build that belonged to someone who had been staring at that spinner for two weeks before asking for help. The root causes vary but the fix list is finite. Here’s every solution that has actually worked for me, ordered from fastest to most involved.

Why Armoury Crate Gets Stuck on the Loading Screen

Before the fixes, it’s worth understanding why this happens. Armoury Crate isn’t one program. It’s a front-end UI that depends on a stack of background services, and those services have to start in a specific order. ASUS System Control Interface loads first because it handles hardware detection. Everything else, AsusCertService, AsusFanService, LightingService, ArmourySocketServer, depends on it being ready.

When one of those services doesn’t start, starts too slow, or gets blocked by something (a Windows update, a conflicting app, a permission issue), the UI opens but never gets the data it needs to finish loading. The spinner keeps going because the app is genuinely waiting for a response that’s never coming.

That’s what the infinite loading screen is: Armoury Crate waiting for its own backend to respond. Once you know that, the fixes make a lot more sense.

Fix 1: Restart the ASUS Services (Fastest, Works Half the Time)

This takes about two minutes and fixes the loading screen issue probably 40-50% of the time. Don’t skip it just because it sounds simple.

Open Task Manager (Ctrl+Shift+Esc), go to the Services tab, and look for these:

  • ArmouryCrateControlInterface
  • AsusCertService
  • AsusFanControlService
  • LightingService
  • ArmourySocketServer

Right-click each one and hit Restart. Do them in order, starting with ArmouryCrateControlInterface. If any of them shows “Stopped” instead of “Running,” right-click and select Start.

After restarting the services, close Armoury Crate completely (check the system tray, right-click the icon and Exit), wait 30 seconds, then reopen it. On a lot of systems, this is enough. The services were in a bad state after a sleep/wake cycle or update, and a manual kick gets them back in sync.

If Armoury Crate still hangs after this, continue to Fix 2.

Fix 2: Run Armoury Crate as Administrator

This one sounds too basic to matter and I ignored it for years. It actually fixes the loading screen on Windows 11 24H2 systems more reliably than I expected.

Windows 11’s 24H2 update tightened some UAC behavior, and Armoury Crate’s services occasionally can’t get the elevated access they need for hardware detection when launched normally. Running as admin bypasses the prompt that’s silently blocking them.

Right-click the Armoury Crate icon on your desktop or in the Start menu, select “Run as administrator,” and click Yes on the UAC prompt. If it loads, the fix is to make this permanent: right-click the icon, go to Properties, Compatibility tab, and check “Run this program as an administrator.” That way it always launches elevated.

I know it’s not elegant to permanently run software as admin. But Armoury Crate’s service architecture kind of requires it on some systems, especially after 24H2. If it works, it works.

Fix 3: Disable Windows 11 Dynamic Lighting

This is the fix that started causing new cases after the Windows 11 24H2 update rolled out in late 2024. If your loading screen issue started around that time, this is probably your problem.

Windows 11 24H2 introduced a native Dynamic Lighting system that lets Windows control RGB devices directly, without third-party software. Sounds nice in theory. In practice, it fights with Aura Sync for control of compatible devices. When both are trying to own the same hardware, neither works correctly, and Armoury Crate can get stuck in a detection loop that manifests as the infinite loading screen.

Here’s how to turn it off:

  1. Open Windows Settings (Win + I)
  2. Go to Personalization
  3. Scroll down to Dynamic Lighting
  4. Toggle off “Use Dynamic Lighting on my devices”
  5. Also toggle off “Compatible foreground apps can control lighting” if it’s visible

Restart Armoury Crate after making this change. On systems where Dynamic Lighting was the conflict, the app loads instantly after disabling it. I’ve seen this fix posted repeatedly in the ROG Forum threads and it’s become one of the most-cited solutions since 24H2 launched.

Note: On some Windows 11 systems, the Dynamic Lighting option under Personalization only appears if the OS has detected RGB-capable hardware. If you don’t see it, this fix doesn’t apply to your setup.

Fix 4: Clear the Armoury Crate Device Cache

Armoury Crate stores device detection data in a local cache. When that cache gets corrupted, usually after an update or an abrupt shutdown while AC was writing to it, the app loads, tries to read its cached device list, fails, and hangs waiting for a valid response.

To clear it, you need to delete two folders. Close Armoury Crate completely first (including from the system tray).

Open File Explorer and navigate to:

C:\ProgramData\ASUS\AURA

Delete everything inside the AURA folder. Don’t delete the folder itself, just the contents. Then navigate to:

C:\ProgramData\ASUS\ArmoryCrate

Delete the contents of this folder as well, specifically any files with .json or .db extensions. These are the device config and cache files that can go corrupt.

After deleting these, restart the ASUS services (as in Fix 1) and then open Armoury Crate. It will regenerate fresh config files on startup and re-detect your hardware from scratch. This takes a bit longer on first launch (it’s rebuilding its device list), but it should load completely instead of hanging.

Fix 5: Check for Conflicting Software

If you have other RGB software installed alongside Armoury Crate, they may be fighting for device access in a way that blocks Armoury Crate from completing its hardware scan.

The main culprits I’ve seen:

AI Suite 3. ASUS’s older system utility conflicts with Armoury Crate on many machines. If you have both installed, the loading screen issue often comes from AI Suite 3’s fan and power services running at the same time as Armoury Crate’s equivalents. They step on each other. Uninstall AI Suite 3 first, then run the AI Suite 3 Cleaner tool (available on ASUS’s support page), then restart and try Armoury Crate again.

OpenRGB or SignalRGB. If either of these is running in the background when Armoury Crate opens, they may have already claimed the USB RGB controller interfaces that Armoury Crate is trying to access. The result is AC sitting on the loading screen waiting for device access that’s already been taken. Close or disable autostart for these before opening Armoury Crate.

Corsair iCUE. Similar SMBus conflict. If iCUE is running, it may be holding the I2C/SMBus access that AC needs for RAM RGB detection. Closing iCUE before opening AC sometimes breaks the hang.

MSI Center or Dragon Center. Same category. These apps don’t target ASUS hardware directly, but they run services that can interfere with shared system interfaces. If you have a mixed build (ASUS motherboard, MSI GPU, for example), and both vendor apps are active, disable MSI Center’s autostart and see if AC loads cleanly.

The general rule: Armoury Crate does not play well with other RGB or system control software running simultaneously. If something else was loaded before AC, close it, restart AC, and see what changes.

Fix 6: Repair or Reinstall ASUS System Control Interface

ASUS System Control Interface (sometimes listed in Device Manager as “ASUS System Control Interface v3” or similar) is the driver layer that lets Armoury Crate talk to your motherboard’s embedded controller. If this driver is corrupted or the wrong version, Armoury Crate’s services start but never get valid hardware responses, hence the infinite loading screen.

To check and repair it:

  1. Open Device Manager (Win + X, then Device Manager)
  2. Look under “System devices” for “ASUS System Control Interface”
  3. If it has a yellow warning triangle, right-click and select “Update driver” then “Search automatically for drivers”
  4. If no update is found, right-click and “Uninstall device,” then restart your PC
  5. Windows will reinstall the driver on boot, or you can download the latest version from ASUS’s support page for your motherboard model

On some systems this driver doesn’t show in Device Manager at all, which means it’s either not installed or got removed. In that case, download the “Armoury Crate and AURA Creator Installer” from your motherboard’s support page on the ASUS website. Running this installer will re-deploy ASUS System Control Interface along with the Armoury Crate suite.

This fix is more involved but it’s the right answer when the loading screen issue happens on a fresh Windows install or after a major version upgrade (like an in-place upgrade to a newer Windows 11 build).

Fix 7: Clean Uninstall and Fresh Install Using the Official Tool

If none of the above fixes work, the installation has probably reached a state where incremental fixes won’t help. The right move is a clean uninstall and fresh install.

The critical part: don’t use Windows’ Add or Remove Programs for this. Armoury Crate leaves behind services, registry entries, and driver files that the standard uninstaller doesn’t clean. Using the wrong uninstall method means your “fresh install” is actually installing on top of leftover debris, and the loading screen issue may come right back.

ASUS provides an official uninstall tool specifically for this situation. Search “ASUS Armoury Crate uninstall tool” on the ASUS support site to find the current version. Run it, select everything it offers to remove, and let it finish. Restart when prompted.

After the uninstall completes and you’ve restarted:

  1. Check Services (services.msc) and confirm there are no ASUS-named services remaining. If any are still there after the uninstall tool ran, they didn’t get cleaned. Stop them, set them to Disabled, and manually delete the service using sc delete ServiceName from an elevated command prompt.
  2. Check C:\ProgramData\ASUS and delete anything remaining there.
  3. Check HKEY_LOCAL_MACHINE\SOFTWARE\ASUS in the registry (regedit) and remove leftover ASUS entries if you’re comfortable in the registry. This is optional but helps with truly clean reinstalls.
  4. Restart again.
  5. Download the latest Armoury Crate installer from ASUS’s official website for your motherboard or laptop model, not from a mirror or Microsoft Store.
  6. Run the installer, let it complete, restart, and open Armoury Crate.

I’ve done this process on two machines where everything else failed. Both times, Armoury Crate loaded normally after the clean reinstall. The second restart between uninstall and reinstall is important, by the way. Some of the ASUS driver components don’t fully release their handles until the system goes through a full power cycle.

Windows 11 24H2 Specific Notes

If you updated to Windows 11 24H2 and then started seeing the loading screen issue, there’s a specific subset of causes worth knowing about beyond Fix 3 (Dynamic Lighting).

The 24H2 update changed how Windows handles USB device enumeration, and some ASUS motherboards had timing issues where Armoury Crate’s services started before Windows had fully re-enumerated the USB controllers after the update. This manifests as loading screen freezes specifically on first boot after the update, which then resolves on subsequent boots.

If the loading screen issue happened right after 24H2 and then went away by itself after a restart or two, that’s what you experienced. It’s not a permanent problem but it rattles a lot of people who don’t know why it happened.

For persistent 24H2 issues, the fix sequence that’s worked most consistently on ROG Forum is: Fix 3 (Dynamic Lighting) + Fix 2 (Run as Admin) + Fix 1 (Service Restart). That combination handles the majority of post-24H2 cases without needing a full reinstall.

When None of This Works

There’s a smaller category of loading screen issues that aren’t fixable through software alone. These include:

Unsupported hardware combinations. If you installed a new GPU, RAM kit, or AIO cooler and then started seeing the loading screen issue, Armoury Crate may be hanging on a detection attempt for that hardware. Check the ROG Forum for your specific component combination. Sometimes a specific piece of hardware causes an endless detection loop and the only fix is to disable that hardware’s RGB control within Armoury Crate’s settings, which you may need to access through a temporary workaround like launching with just that device disconnected.

Corrupted Windows component. In rare cases, a Windows system file involved in Armoury Crate’s service startup has gotten corrupted. Running sfc /scannow from an elevated command prompt and then DISM /Online /Cleanup-Image /RestoreHealth can repair this. These are safe commands that check and restore Windows system files. Let both complete fully (the DISM one can take 20-30 minutes).

Genuine software incompatibility. Some users on specific hardware (certain Intel Arc GPUs, some Thunderbolt docking station setups) have reported loading screen issues that ASUS hasn’t fully resolved. The ROG Forum’s Armoury Crate board is the best place to check for hardware-specific known issues and any workarounds the community has found.

Frequently Asked Questions

Why does Armoury Crate get stuck on the loading screen after every Windows update?

Windows updates can stop or reset ASUS background services, change USB device enumeration timing, and on Windows 11 24H2 specifically, can re-enable Dynamic Lighting which conflicts with Aura Sync. After a major Windows update, restart your ASUS services manually (Fix 1) and check that Dynamic Lighting is still disabled (Fix 3). Those two steps cover most post-update loading screen cases.

Is it safe to delete the ASUS AURA and ArmoryCrate folders in ProgramData?

Yes, those folders contain only cache and config files that Armoury Crate regenerates on next startup. You won’t lose any critical data by deleting them. Your saved lighting profiles may be reset, but the profiles are also stored in the app itself, so as long as you delete the cache files (not the entire app installation), your configured effects should still be there.

The loading screen hangs only on the first launch after boot. Is that normal?

It’s common but not exactly normal. On some systems, Armoury Crate’s services start loading before all the hardware interfaces they need are fully ready after boot. If the hang goes away on second launch, you can work around it by delaying Armoury Crate’s startup: Task Manager > Startup apps > right-click Armoury Crate > Disable, then add it to your startup folder with a task scheduler delay of 60-90 seconds. That gives Windows time to fully initialize everything before AC starts.

Does running Armoury Crate as administrator always fix the loading screen?

Not always, but it fixes it often enough on Windows 11 24H2 that it should be the second thing you try (after the service restart). If running as admin makes it load correctly, make it permanent via the Properties > Compatibility > Run as administrator checkbox so you don’t have to do it manually every time.

Can I prevent the loading screen issue from happening again after I fix it?

Partially. The most durable prevention is keeping Armoury Crate updated, keeping Dynamic Lighting disabled, and not running other RGB software alongside it. After major Windows updates, give it a manual service restart. And if you’re using AI Suite 3, remove it, they genuinely conflict. You can’t completely prevent it because Armoury Crate’s architecture is fragile, but you can reduce how often it breaks.

Should I just uninstall Armoury Crate and use something else?

For desktop builds: if you’re primarily on ASUS hardware and use Aura Sync with peripherals, staying on Armoury Crate and applying these fixes as needed is probably the better path than switching. For ASUS gaming laptops specifically, G-Helper is a genuinely better alternative for performance and fan control without Armoury Crate’s instability. For mixed-brand desktops where you only had Armoury Crate for an ASUS motherboard, OpenRGB or SignalRGB can replace it and are more stable.

Related Guides

Leave a Comment