Where Does Armoury Crate Store Profiles and Logs?
Armoury Crate splits state between ProgramData ASUS for machine packages and LocalAppData ArmouryCrate for per-user logs. Profiles move with versions.
Last updated
Armoury Crate keeps two homes. Machine-level packages and diagnostics sit under ProgramData ASUS, while your session logs sit under LocalAppData ArmouryCrate. Back up both or you only have half the picture.
Profiles are the unstable part. Their on-disk spot changes between Crate and Crate SE builds, and the handheld UWP variant uses a Packages LocalState tree instead. Export anything important through the app UI. Lighting that survives a wipe is firmware, not a file you missed.
Where Armoury Crate stores this, by platform
C:\ProgramData\ASUS\ArmouryCrate
Machine-level packages and diagnostics. Version and edition change the files inside without notice, and Crate SE on handhelds uses a Packages LocalState tree instead. Pair this with the per-user logs folder for a full backup.
%LOCALAPPDATA%\ArmouryCrate\logs
Per-user session logs as plain .log files. The official support bundle is generated separately inside the app under Settings, About, App Diagnostics. RGB behavior itself persists in device firmware rather than here.
Frequently asked questions
How do I back up Armoury Crate before reinstalling?
Copy C:\ProgramData\ASUS\ArmouryCrate and %LOCALAPPDATA%\ArmouryCrate with Crate fully quit. The first holds packages and diagnostics, the second holds session logs. Scenario Profile locations shift per release, so export profiles from inside the app as well instead of relying on files alone.
How do I collect Armoury Crate logs for ASUS support?
Use Settings, About, App Diagnostics, Record Log, Generate log data inside Crate. That produces the official encrypted bundle support wants. The plain .log files under %LOCALAPPDATA%\ArmouryCrate\logs help for a quick look but are not the support artifact.
Why did my RGB survive a full reinstall?
It does not move. Lighting and fan behavior persist in device firmware and NVRAM on many boards, so a fresh Windows install can show the same effects with no Crate files present. Change it in Crate on any machine and the device remembers.
Notice an outdated path? Let us know.