The first time I saw “Update failed (error code 0)” in Armoury Crate, I assumed it was a network blip and hit retry. It failed again. And again. I spent the next hour going through every suggestion I could find before landing on the fix that actually worked, which turned out to have nothing to do with Armoury Crate itself and everything to do with which drive Windows was trying to install apps on.
That’s the thing about Armoury Crate install failures. There isn’t one cause. I’ve seen this exact symptom stem from leftover service files, an out-of-date .NET runtime, a Windows Store glitch, a secondary drive app install setting, and a corrupted ASUS platform driver. This guide covers all of them, in order from fastest to most involved, so you don’t have to spend three hours figuring out which one applies to you.
Understanding the Error Types
Before getting into fixes, it helps to know which error you’re actually seeing. Armoury Crate surfaces a few different failure modes, and each one points toward a different root cause.
“Update failed (error code 0)” at the Armoury Crate startup prompt is the most commonly reported one. You get two options: Reboot system or Exit update. Neither fixes the underlying issue. This usually means the update package downloaded but couldn’t be applied, typically because leftover files from a previous version are blocking the installer, or the app install location is wrong.
0x80070005 (Access Denied) means the installer couldn’t write to a directory it needs. Almost always a UAC or permissions problem. Running the installer as administrator solves this the majority of the time.
0x80070002 (File Not Found) means the installer is looking for a dependency or file that doesn’t exist on your system. Common when ASUS System Control Interface isn’t installed or is the wrong version.
0x80072EFE (Connection Interrupted) is a network error. The update server was reached but the download was cut off before completing. Usually a temporary issue, sometimes a firewall or VPN problem.
General installation stuck/frozen with no error code is usually a service conflict or a corrupted Microsoft Store component that’s blocking the installation process.
Now for the fixes.
Fix 1: Check Your Windows App Install Location
This one gets missed by almost every guide out there, and it fixed the “error code 0” problem for me and several people I’ve helped since.
If you have a secondary drive (a game drive, a storage HDD, anything that’s not your Windows C: drive) and Windows is set to install new apps there by default, Armoury Crate’s installer and update mechanism breaks. Armoury Crate has hardcoded paths that expect to live on the same drive as Windows. When Windows tries to put it somewhere else, the installation partially succeeds, then the update component can’t find what it needs.
To check and fix this:
- Open Windows Settings (Win + I)
- Go to System, then Storage
- Scroll down to “Advanced storage settings” and click “Where new content is saved”
- Find “New apps will save to:” and make sure it’s set to your Windows drive (usually C:)
After changing this, run a clean uninstall of Armoury Crate (see Fix 3 for the proper method), restart, and reinstall. I’ve seen this single change resolve “error code 0” when everything else had failed.
Fix 2: Run the Installer as Administrator
If you downloaded the Armoury Crate installer from the ASUS support site and ran it normally, try again with elevated permissions. Right-click the .exe and select “Run as administrator.”
For the 0x80070005 (Access Denied) error specifically, this is the first thing to try. Armoury Crate’s installer writes to system directories and modifies services. On Windows 11 with UAC at default settings, a non-elevated install can silently fail partway through when it hits a protected path, leaving you with a broken partial install that then generates “error code 0” on every subsequent update attempt.
Also make sure no other ASUS software is running while you install. Close MyASUS, Aura Sync if it’s open separately, and any RGB tools from other brands. These can hold file locks that interfere with the installer writing its components.
Fix 3: Clean Uninstall First, Then Reinstall
If Armoury Crate is already installed and updates keep failing, the most common cause is leftover files and registry entries from a previous version. The solution is not to retry the update, it’s to fully remove everything and start clean.
Don’t use Windows’ “Add or Remove Programs” for this. It doesn’t remove everything.
Method A: ASUS Official Uninstall Tool
ASUS provides an official uninstall tool on their support page specifically for this situation. Search “ASUS Armoury Crate uninstall tool” on the ASUS global support site. Download it, run it as administrator, check every option it gives you to remove, let it finish, and restart your PC.
After restarting, check C:\ProgramData\ASUS and delete any remaining folders. Then download the latest Armoury Crate installer directly from your motherboard’s or laptop’s support page on the ASUS website and run it as administrator.
Method B: Community Cleanup Tool (More Thorough)
For cases where the official uninstall tool still leaves things behind, the community-made uninstall tool by allenk on GitHub is more aggressive. It removes services, registry keys, and driver entries that the official tool sometimes misses. Search for “allenk armoury crate uninstall” on GitHub to find the current version.
One important caveat for laptop users: the allenk tool removes the acsevirtualbus.inf driver, which some ASUS laptops (especially older ones) need for certain hardware functions. If you’re on a laptop, check the allenk tool’s GitHub readme for your model before using it. Desktop users can generally use it without issues.
After running either uninstall tool, restart twice before reinstalling. The second restart ensures Windows fully releases the driver handles from the removed services.
Fix 4: Fix the Windows Store Component
Armoury Crate installs and updates through the Microsoft Store in some configurations. When the update mechanism keeps failing with no clear error, a broken Windows Store component is often the culprit. The fix is to reset the Store.
Open an elevated command prompt (search “cmd,” right-click, Run as administrator) and run:
wsreset.exe
This resets the Microsoft Store cache without losing your app data. A blank command prompt window will appear, wait for it, then the Store will open automatically when the reset completes. After wsreset, try the Armoury Crate update again.
If wsreset doesn’t help, try re-registering the Store apps. In an elevated PowerShell window (search “PowerShell,” right-click, Run as administrator), run:
Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
This takes a minute or two and will show some red error lines for apps it can’t register, that’s normal. Restart after it completes and try Armoury Crate again.
Fix 5: Update or Reinstall ASUS System Control Interface
Armoury Crate can’t install or update successfully if its underlying driver layer (ASUS System Control Interface) is missing, outdated, or corrupted. This is common on fresh Windows installs, after in-place upgrades, or after using aggressive system cleanup tools that removed old drivers.
To check it:
- Open Device Manager (Win + X, then Device Manager)
- Look under “System devices” for “ASUS System Control Interface” (may be listed as v2 or v3)
- If it has a yellow warning triangle, right-click and update the driver
- If it’s missing entirely, go to your motherboard or laptop’s support page on the ASUS website and download the “ASUS System Control Interface” driver separately
Install this driver before attempting to install or update Armoury Crate. Without it, Armoury Crate’s installer may complete but the app will fail to detect hardware, which then causes the update component to enter a broken state and show “error code 0” on every subsequent launch.
Fix 6: Temporarily Disable Antivirus and Firewall
For the 0x80072EFE (Connection Interrupted) error and for cases where the download starts but never completes, antivirus or firewall interference is a common cause. Some security software quarantines Armoury Crate’s installer or blocks its connections to ASUS update servers.
Temporarily disable your antivirus real-time protection and any third-party firewall, then try the installation again. Re-enable them immediately after. If this fixes it, you’ll want to add Armoury Crate’s installation directory and executable to your antivirus exclusions so it doesn’t keep getting blocked on future updates.
Common false positive triggers: Windows Defender SmartScreen (which doesn’t know the ASUS certificate by default), Malwarebytes’ real-time protection, and some VPN clients that redirect or inspect outbound connections.
Also, if you’re connected via VPN, disconnect it before updating Armoury Crate. ASUS’s update servers can behave unexpectedly when accessed through VPN exit nodes, especially ones in regions where the servers have geolocation throttling.
Fix 7: Repair Windows System Files
When Armoury Crate fails to install on a system that has never successfully run it, and nothing else in this list resolves it, there’s a chance a core Windows component involved in service installation or driver loading has gotten corrupted. Running the Windows repair tools addresses this.
Open an elevated command prompt and run these two commands in order:
sfc /scannow
Wait for this to complete fully. It scans Windows system files and restores any that are corrupted. Then run:
DISM /Online /Cleanup-Image /RestoreHealth
This one takes longer (20-30 minutes on some systems) and requires an internet connection because it downloads replacement files from Windows Update. Let it run fully without interrupting it.
After both complete, restart and try the Armoury Crate installation again. This combination fixes a surprisingly large number of stubborn installation failures that have nothing directly to do with Armoury Crate itself.
Fix 8: Uninstall AI Suite 3 if Present
If you have ASUS AI Suite 3 installed, it directly conflicts with Armoury Crate. The two apps share services that fight over the same system interfaces, and having AI Suite 3 present can prevent Armoury Crate from installing or updating correctly even when everything else looks fine.
Uninstall AI Suite 3 through Add or Remove Programs, then run the AI Suite 3 Cleaner tool (available on ASUS’s support page) to remove the leftover service entries. Restart, then attempt the Armoury Crate install again.
This is a common scenario on older ASUS systems where someone upgraded from an earlier era when AI Suite 3 was the recommended ASUS tool. If you see both in your installed programs list, AI Suite 3 needs to go before Armoury Crate will install cleanly.
Fix 9: Reinstall from the Full Package, Not the Lite Installer
Armoury Crate has two installer types. The “lite” version downloads and installs components on-the-fly during setup. The full package includes everything. If your internet connection drops partway through a lite install, you get a broken partial installation that then fails on every update attempt.
To get the full package, go to your specific motherboard or laptop’s support page on the ASUS website (search for your model number). Under Drivers and Utilities, look for “Armoury Crate” in the software section. Some model pages offer both a lite installer and a full offline installer. Download the full offline version if available.
If only the lite installer is available, make sure you’re on a stable connection (ideally wired, not Wi-Fi) before running it. Lite installer failures are usually just incomplete downloads caught at a bad moment, and retrying on a stable connection often resolves them.
If Nothing Works: The Fresh Windows Install Scenario
There’s a subset of Armoury Crate installation failures that happen specifically on fresh Windows installs on existing hardware, and it took me a while to understand why. When you reinstall Windows and then immediately try to install Armoury Crate, some motherboards haven’t yet properly loaded their USB and I2C controller drivers. Armoury Crate’s installer tries to detect hardware during setup, fails because the drivers aren’t ready yet, and enters a failed state.
The fix is simple but counterintuitive: run Windows Update first. Let Windows fully update, including optional driver updates. Then install Armoury Crate. On most modern ASUS motherboards, Windows Update delivers the chipset and USB controller drivers that Armoury Crate’s detection needs. Installing AC before those drivers are in place is why the fresh-install scenario fails.
After Windows Update completes and you’ve restarted, try the Armoury Crate install again. This has resolved fresh-install failures for me on an ROG Strix Z590-E and a TUF Gaming Z690-Plus, both cases where installing AC immediately after Windows gave “error code 0” but installing it after Windows Update ran fully worked without issues.
Frequently Asked Questions
What does “Update failed (error code 0)” actually mean in Armoury Crate?
Error code 0 in Armoury Crate means the update process encountered an unspecified failure, not a specific system error. The most common causes are leftover files from a previous AC version blocking the new installer, an incorrect app install drive setting in Windows, or a corrupted Windows Store component. Fix 1 (install location), Fix 3 (clean uninstall), and Fix 4 (wsreset) cover the three main scenarios.
Can I skip the Armoury Crate update and keep using the old version?
You can click “Exit update” when the error appears, which lets you keep using the current version without updating. However, ASUS’s update mechanism will show the prompt on every launch until the update installs successfully. If you want to stop the prompts without fixing the update issue, you can disable the Armoury Crate update service (ArmouryCrateControlInterface update component) in services.msc, though this means you’ll also miss future bug fix updates.
Why does Armoury Crate fail to install on a new Windows install?
On fresh installs, the chipset and USB controller drivers AC needs for hardware detection haven’t been installed yet. Run Windows Update fully first, including optional driver updates. Let it install everything and restart before attempting to install Armoury Crate. AC installed before the board’s drivers are loaded will partially fail during the hardware detection phase.
Is the allenk GitHub uninstall tool safe to use?
Generally yes for desktops. The tool is open source and widely used in the ROG community. For laptops, check the readme for your model before using it, as it removes the acsevirtualbus.inf driver that some ASUS laptops need. The tool’s GitHub page lists known laptop model caveats.
Armoury Crate installed but shows “error code 0” every time it opens. What now?
This usually means the update component installed but the app itself is in a broken state. The fix is to run the official ASUS uninstall tool, then delete the remaining ProgramData\ASUS folders, restart, and reinstall from the full offline package from your motherboard’s support page. Also verify your Windows app install location is set to the C: drive before reinstalling (Fix 1).
Does installing Armoury Crate on a secondary drive cause problems?
Yes. Armoury Crate has hardcoded path expectations relative to the Windows system drive. Installing or having Windows install it to a secondary drive breaks its update mechanism and can cause persistent “error code 0” errors. Always ensure Windows apps install to the same drive as Windows itself when dealing with Armoury Crate.
Related Guides
- Armoury Crate not working fix guide — after install, when the app misbehaves.
- How to remove Armoury Crate properly — the clean uninstall before retrying.
- Completely uninstall Armoury Crate — the deeper registry-level removal.
- ASUS Aura Sync setup guide — what to do once it’s installed.