Troubleshooting

When a control does nothing, a mode will not stick, or the app will not start.

Start with the affected setting, the app’s reported status and its log. Device support, permissions and another utility changing the same setting can produce different symptoms.

Check other hardware-control software

If modes or lighting revert, check whether Armoury Crate, another tuning utility or Windows Dynamic Lighting is changing the same control. Advanced can stop and start the ASUS services Arsenal manages; stopping them also affects their startup behavior.

Arsenal will not start

Install .NET 10 Desktop Runtime for Windows x64. The public package requires the Desktop Runtime.
If Windows blocks the executable, verify its source and published SHA-256 before deciding whether to run it.
Check the notification-area overflow for a hidden tray icon.
A second launch activates the running instance. It does not open a separate app or forward CLI actions.

A control does nothing

Check model and driver support. Missing or disabled controls can also indicate unavailable access.
Use Advanced → Restart as administrator for operations requiring elevation.
On Performance, enable the relevant apply switch and select Apply changes.
On Lighting, use Apply colour after choosing colour and speed. On Devices, use the apply button for the edited group.
Check the log for failed hardware writes.

A setting changes back

Review AC/battery mode choices in Automation, Optimized GPU mode and automatic refresh. Power-source events can reapply their saved choices. Another application or firmware policy may also change the setting.

Eco mode will not engage

Review Display & graphics → Applications holding the dGPU. Save work and close those applications before retrying. Displays connected through the dedicated GPU can also affect switching. Leaving Ultimate may require a restart.

Fan curves or readings look wrong

Check the selected performance profile, its custom-fan switch and Apply changes. Firmware can enforce its own minimum speeds or thermal response. Calibrate max RPM measures maximum fan readings; it does not automatically tune the curve.

A custom plan is missing or changed

Open Performance → View all to check the complete plan library. Home, the tray menu and AC/battery Automation show only Silent, Balanced and Turbo; choose custom plans on Performance or assign them to the Quick Panel’s three performance shortcuts. Deleting a custom plan removes its saved tuning and returns to Balanced if that plan was active.

Lighting problems

Check brightness, effect, power states and idle timeouts, then check for competing lighting software. If only the preview shape is wrong, use Lighting’s Number pad and Tall Enter key switches. Preview layouts are based on chassis families and may need correction.

Update or driver problems

Use About → Check for Arsenal releases and Drivers → Scan again for ASUS packages. Check connectivity and the displayed error. If an Arsenal update fails verification, retry or obtain the package from the download page; do not bypass the integrity checks.

Reset configuration

Quit Arsenal from the tray.
Back up the active config.json. The normal location is %AppData%\Arsenal; a file beside the executable takes priority.
Move the active configuration and its .bak out of that location. Check the shared fallback in %ProgramData%\Arsenal if old settings return.
Restart Arsenal and review setup and model-specific settings.

Resetting configuration does not remove scheduled tasks, firewall rules or the companion certificate. See Saved data for the relevant locations.

Report a problem

Include the Arsenal version, model and BIOS from About, steps to reproduce the issue, the expected result, and whether other ASUS utilities are running. The log is normally %AppData%\Arsenal\log.txt; Advanced has an Arsenal log shortcut. Review it for personal information before sharing.