You click Performance in Armoury Crate, the setting slides back to Silent, and your laptop keeps running like it's on a Sunday stroll. This guide on How to Fix Armoury Crate Not Changing Performance Mode on a Gaming Laptop covers the checks that actually work. Most cases come down to four things: power state, a stalled ASUS service, Windows settings fighting back, or a broken install.
ASUS builds these modes on top of the laptop's Embedded Controller, and Armoury Crate reaches it through the ASUS System Control Interface driver. Manufacturer documentation also confirms that Turbo mode is disabled on battery power, so an unplugged machine will refuse the switch without warning. The fix usually starts with what the hardware is being told, not with a reinstall.
Here's the fastest path through it.
How to Fix Armoury Crate Not Changing Performance Mode on a Gaming Laptop
Fixing Armoury Crate's stuck performance mode starts with the power adapter. Turbo is disabled on battery, so plug in first. Then reopen Armoury Crate and select your mode again.
If it snaps back, restart the Armoury Crate Service. Failing that, run the ASUS uninstall tool, reboot, then reinstall cleanly.
How Armoury Crate Performance Modes Interact With BIOS, Firmware, and Windows
Armoury Crate isn't a thermostat. It's a front end.
When you click a mode, the app asks the Armoury Crate Service to send a command through the ASUS System Control Interface driver. That command lands on the Embedded Controller, the small chip that owns fan curves, power limits, keyboard lighting, and the mode itself.
This is the part almost everyone skips over. The UI can look perfectly healthy while the EC never receives a thing.
Here's what each mode is actually changing:
| Mode | What changes | Available on battery |
|---|---|---|
| Silent | Lower fan ceiling, reduced sustained power | Yes |
| Performance | Higher power limits, firmer fan curve | Yes, capped |
| Turbo | Highest TDP, fans near maximum | No |
| Windows | Control handed to the Windows power slider | Yes |
Naming shifts between ROG and TUF lines, and some newer models add a Manual tier. The mechanics stay the same.
Then there's the Windows layer. If Armoury Crate sits in its Windows profile, the power mode slider in Settings decides everything. The mode buttons will look broken because, by design, they do nothing.
Pick Performance or Turbo and Windows stops interfering.
As of 2026, ASUS ships Armoury Crate as a service-backed app that pulls pieces of its install from the Microsoft Store. That hybrid setup breaks more often than the old standalone builds did, which is why partial updates cause so many stuck modes.
One more detail worth knowing. The EC also checks adapter wattage. Plug in a 65W USB-C brick on a 240W machine and the EC quietly caps power regardless of what you select.
Step-by-Step Fix for Armoury Crate Not Changing Performance Mode

Image source: Openverse / Openverse contributor
Work down this list in order. Each step is quick, and the later ones only matter if the earlier ones didn't take.
Plug in the original adapter
Use the brick that shipped with the laptop. Undersized chargers get capped by the EC, and battery alone disables Turbo on most models.
If your frame rates collapse the second the cable comes out, frames collapsing on battery power covers why.
Take Windows out of the driver's seat
Go to Settings, then System, then Power and battery. Set Power mode to Best performance.
Also make sure Battery Saver stuck switched on isn't quietly holding your power ceiling down.
Restart the ASUS services
Open Task Manager and head to the Services tab. Restart these:
- ASUS Armoury Crate Service
- AsusAppService
- ASUS System Control Interface, if it's listed
Reopen Armoury Crate and try the mode again.
Update the System Control Interface driver
This driver carries the command to the EC. When it's missing or half-installed, the UI shows Turbo while the fans stay flat.
Run MyASUS and install every pending driver, or download the current package from ASUS's official support and driver downloads. Reboot afterwards.
Turn off Fast Startup
Fast Startup writes a snapshot of the system kernel to disk. Shutting down and powering back up restores that snapshot, including the old EC state. That single feature explains a huge share of "it worked once" complaints.
Do a full Restart instead, which bypasses the snapshot entirely. To disable it, open Control Panel, then Power Options, then Choose what the power buttons do.
Update the BIOS
MyASUS handles this. Stay on AC power and don't interrupt the flash. EC firmware fixes are where a lot of stuck-mode bugs get patched.
Clean reinstall, in this order
- Download the ASUS Armoury Crate Uninstall Tool.
- Run it, then reboot.
- Reinstall Armoury Crate from the ASUS site.
- Reboot again, then set your mode.
Confirm it actually applied
Watch fan RPM and package power in a monitoring tool while you switch modes. If the numbers move, you're fixed. If they don't, the command isn't reaching the EC, and that points straight back at the driver step.
Common Mistakes That Stop Armoury Crate Performance Mode From Switching
Most people who end up reinstalling software skipped one of these.
- Trusting Shutdown with Fast Startup enabled. Shutdown isn't a clean boot on Windows. Restart is.
- Running a third-party USB-C charger. The EC reads wattage and clamps power when it sees too little headroom.
- Installing two copies of Armoury Crate. The Store version and the standalone version can fight over the same service. Pick one and remove the other.
- Hand-editing the Windows power plan. Change it back to Balanced by accident and your selected mode gets overridden on the next wake.
- Skipping the System Control Interface driver after a Windows feature update. Big updates love to reset chipset and vendor drivers.
- Assuming a BIOS reset fixes software. Clearing the CMOS won't repair a broken service or a corrupt install.
- Blaming thermals. If the mode never applied, heat isn't your problem. Once Turbo is confirmed active and Turbo overheats the chassis, that's a separate conversation.
- Running old fan utilities in the background. Tools like older overclocking apps can latch onto the EC and refuse to let go.
- Chasing settings that keep reverting. If a value resets on every cold boot, settings undoing themselves after reboot explains the pattern.
One thing to avoid: opening the chassis won't fix a mode bug, and it's worth checking repasting and your warranty cover before you grab a screwdriver for the wrong reason.
Final Decision Guide for Armoury Crate Performance Mode Troubleshooting
Use the symptom to pick your next move. That saves you an hour of blind reinstalling.
| What you see | Likely cause | Do this |
|---|---|---|
| Label changes, fans and temps don't | Service or control interface driver stalled | Restart services, reinstall the driver |
| Mode reverts after every reboot | Fast Startup restoring an old EC state | Disable Fast Startup, use Restart |
| Mode buttons greyed out | Battery power, weak adapter, or low power mode | Original adapter in, Best performance set |
| Armoury Crate won't open at all | Corrupt or duplicate install | Uninstall tool, reboot, reinstall |
| Fixed, then broken by a Windows update | Half-installed Store components | Repeat the clean reinstall |
A few conditional calls to finish.
If the mode applies and temperatures spike into throttling territory, that's a cooling issue, not a software one. Work on airflow and repaste instead of reinstalling anything.
If nothing on this page moves the needle and your BIOS, drivers, and services are all current, stop troubleshooting and open a warranty case. Log it through MyASUS with your BIOS version and Armoury Crate Service version attached. ASUS support can read EC logs you can't reach.
If the laptop is out of warranty, a service centre EC reflash is usually cheap and often the last piece of the puzzle.
Use Cases / Best For / Who It's Right For
Not every Armoury Crate mode glitch requires the same solution. The right fix depends on your laptop model, how you use the machine, and what you’re willing to tolerate inside the software.
Scenarios where a quick service restart resolves the issue
If you’ve just updated Windows or installed a new game, the ASUS System Control Interface driver may need a moment to re‑sync with the Embedded Controller. A single restart of the Armoury Crate Service, accessible through Task Manager, clears the cache and restores mode switching in most ROG Strix and TUF units. This takes under two minutes and carries no risk to installed profiles.
Situations that demand a full reinstall
When mode buttons remain greyed out after a service restart, or when the app fails to launch entirely, the installation is likely corrupted. This occurs more frequently with the Microsoft Store variant of Armoury Crate, which can conflict with the standalone version downloaded from ASUS’s support site. A clean wipe using the ASUS uninstall tool, followed by a fresh install from the official .zip package, is the most reliable path forward.
User types who benefit most from each approach
- Casual gamers who switch between a few titles will find the service restart sufficient 80 % of the time.
- Enthusiasts who routinely toggle between Silent for work and Turbo for gaming will hit driver conflicts more often and may prefer the reinstall route from the start.
- Content creators running sustained workloads should verify that the Performance mode actually applies before relying on it for render jobs, as some older EC firmware versions cap power limits even when the UI indicates Turbo is active.
When the problem stems from outside Armoury Crate
If you’ve undervolted the CPU through a separate utility or modified the Windows power plan to “Ultimate performance,” those settings can override Armoury Crate’s mode selections. In those cases, resetting the Windows power plan to Balanced and then re‑selecting the mode in Armoury Crate resolves the conflict without touching the software itself.
The common thread across all scenarios: always start with the laptop plugged in and Fast Startup disabled. Those two conditions alone eliminate the majority of mode‑change failures reported in ASUS forums as of 2026.