Battle. net on a Snapdragon laptop tends to fail at the least convenient moment: the installer stalls, the app hangs on “Updating Battle. net”, a game update loops, or a freshly installed game refuses to launch.

Most Battle.net failures on ARM are launcher problems, not hardware problems. A stuck Update Agent, corrupt cache, or blocked connection accounts for most reports, and all three are fixable in minutes. Harder cases are individual games whose anti-cheat will not run under emulation — those need recognising, not endless reinstalling.

This guide fixes the launcher first, then updates, then game launches. Test the app after each fix before moving on.

Why this happens

  • x64 launcher and Update Agent under emulation: Battle.net and its background Update Agent are x64 programs, so they run through ARM emulation, which is slower and more prone to hangs during installs and updates.
  • Corrupt Battle.net Update Agent data: The agent stores update state and catalogue data that can corrupt, leaving the app stuck on “Updating” or “Initialising” indefinitely.
  • Installer blocked by permissions or security software: Installing without administrator rights, or with antivirus blocking the agent, produces partial installs that fail in confusing ways later.
  • Firewall or network filtering blocking Blizzard servers: Battle.net needs several Blizzard endpoints, and a firewall, VPN, or parental filter blocking any of them produces login failures and update loops.
  • Disk space and drive speed during large updates: Blizzard games are large, and updates that decompress on a nearly full or slow drive stall in ways that look like network failures.
  • Anti-cheat or legacy components incompatible with ARM: Some titles rely on drivers or components that do not run under ARM emulation, so the game installs but cannot start.
  • Conflicting background software: Overlays, recording tools, and aggressive antivirus can interfere with the agent and with game launches, especially during the first run.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Run the installer as administrator and clear the agent cache

A failed or partial install is the root of many later Battle.net faults, so start by making the install clean. The Update Agent’s cached state is the most common cause of a startup hang.

  1. Fully exit Battle.net and end all Battle.net and Blizzard processes in Task Manager, including the Update Agent.
  2. Delete the Battle.net cache data under ProgramData, and the Update Agent data folder, so the agent rebuilds from scratch on next launch.
  3. Download the latest Battle.net installer from Blizzard and run it as administrator.
  4. Let the installer complete without interruption, keeping the laptop plugged in and awake.
  5. Launch Battle.net and let it finish its first update completely before opening any game — interrupting this first update recreates the stuck state.

Fix 2: Fix the app stuck on updating or initialising

If Battle.net opens but never gets past “Updating Battle.net” or “Initialising”, the agent is wedged or cannot reach Blizzard’s servers.

  1. Close Battle.net completely, including the agent process in Task Manager, and delete the agent cache data again as in Fix 1.
  2. Temporarily disable any VPN and confirm Battle.net and its agent are allowed through Windows Firewall and your antivirus.
  3. Relaunch Battle.net and wait a full two minutes — the agent sometimes needs that long to rebuild its state under emulation.
  4. If it still hangs, try a different network, such as a phone hotspot, to prove whether your network or its filtering is the blocker.
  5. Only if a different network also fails should you uninstall and reinstall the app, since the fault is then local rather than network-based.

Fix 3: Repair login failures and account errors

Login loops and authentication failures are usually account-state or connection problems. Blizzard’s login flow is sensitive to cached credentials, so a stale state can persist across restarts.

  1. Sign out of Battle.net completely, close the app, and sign back in, checking carefully that you are using the correct Battle.net account and region.
  2. If you use an authenticator, confirm its codes are current and that your device time is set automatically — a clock skew breaks authenticator codes.
  3. Clear the app cache again after signing out, so no stale credential state survives into the new login.
  4. Try logging in through a browser on the same machine to confirm the account itself is healthy and not locked.
  5. If browser login works but the app still fails, the app’s network path is the problem — revisit the firewall and VPN checks from Fix 2.

Fix 4: Fix stuck game downloads and updates

A game update that sticks, loops, or reports a corrupt file is usually a disk, cache, or connection issue. Blizzard updates decompress as they download, so the drive matters as much as the network.

  1. Pause the update, then use the game’s options in Battle.net to Scan and Repair — this verifies installed files without redownloading the whole game.
  2. Confirm the install drive has ample free space, ideally at least twice the update size, and prefer the internal SSD.
  3. Clear the Battle.net download cache and resume the update, watching whether it progresses past the previous sticking point.
  4. Disable bandwidth limits in Battle.net settings and pause other large downloads and cloud syncs during the update.
  5. If one game still fails while others update fine, the fault is likely that game’s files or its compatibility, not your connection. For general Windows-side network help, see Microsoft’s Windows support pages .

Fix 5: Troubleshoot games that install but will not launch

Check compatibility early.

  1. Check the specific title’s ARM compatibility reports — titles with kernel-level anti-cheat are the most likely to be genuinely incompatible with ARM emulation.
  2. Update the game’s supporting runtimes, including the latest Visual C++ redistributables, and update your ARM graphics driver from your laptop maker’s support page.
  3. Run Battle.net as administrator and launch the game with all overlays, Discord overlay, and recording software disabled.
  4. Use Scan and Repair on the game before reinstalling it — a single corrupt file is a common launch failure and is fixed in minutes.
  5. If the game uses anti-cheat that still refuses to start after all of the above, that is most likely an ARM incompatibility. This is the same hard wall that blocks Valorant’s Vanguard anti-cheat on ARM , which is documented as unsupported rather than fixable.
  6. Keep the game and Battle.net updated — Blizzard occasionally improves ARM compatibility, and a future patch may resolve a title that fails today.

Fix 6: Do a clean Battle.net reinstall without losing games

When the launcher is erratic across many symptoms, a clean reinstall — agent cache and all — is the final step. Done properly, it does not require redownloading your games.

  1. Uninstall Battle.net from Settings > Apps > Installed apps and restart the laptop.
  2. Back up any local game settings you care about, then remove remaining Battle.net and Blizzard agent folders under ProgramData and AppData.
  3. Confirm no Blizzard agent processes remain in Task Manager before reinstalling.
  4. Install the latest Battle.net app as administrator and point it at your existing game install folders so it discovers them instead of redownloading.
  5. Let the app verify each discovered game with Scan and Repair before launching it.
  6. If voice or camera features misbehave in other apps after this work, remember those are separate pipelines — for example, a Studio Effects voice-focus echo is an audio-pipeline issue, not a Battle.net issue. The same applies to widgets: a Copilot app widget not working is an app-layer fault, not a launcher fault.

Closing

Battle.net on ARM is usually fixable at the launcher layer: a clean administrator install, a cleared Update Agent cache, and an unblocked network path resolve most failures. Once the launcher is healthy, a title that still refuses to launch because of anti-cheat is telling you about ARM’s limits, not a missed setting. Fix the launcher, verify each game once, and move on from titles that cannot run.

Frequently asked questions

Why won't Battle.net install on my ARM laptop?
The Battle.net desktop app is x64 and runs under emulation, and a stuck Battle.net Update Agent or a blocked installer is the usual cause. Running the installer as administrator and clearing the agent cache fixes most install failures.
Why is Battle.net stuck on updating or initialising?
That usually means the Update Agent is wedged, its cache is corrupt, or a firewall is blocking its server connection. Deleting the agent data and restarting the app lets it rebuild cleanly.
Why do Blizzard games fail to launch on ARM?
Some Blizzard titles depend on anti-cheat or older components that do not work under ARM emulation, so they may install but never start. Check the specific title’s ARM compatibility before reinstalling repeatedly.
Does Battle.net work on Windows on ARM at all?
The launcher itself generally works under x64 emulation once its agent and cache are healthy. Individual game compatibility varies, with older and anti-cheat-protected titles being the most likely to fail.