Battle.net stuck updating fix: repair the Agent on PC safely

For a Battle.net stuck updating fix on Windows 11, first find out whether the desktop launcher, background Update Agent, or a particular game patch is stalled. Fully exit the launcher, check for an existing download or installation in its queue, and restart Windows before removing any files. If the problem returns, test the connection and disk access. Blizzard also documents a targeted repair for damaged launcher data in C:\ProgramData\Battle.net, but use it only after the safer checks: the launcher may forget where installed games are located. You normally do not need to uninstall every Blizzard game.

Identify what is actually stuck

“Updating” in Battle.net is not a single operation. Blizzard’s support library distinguishes an Agent update, a game patch stalled at “Initializing,” a “Waiting on Another Installation or Update” message, and downloads that show 0 B/s. Those symptoms can share causes, but they do not justify the same first fix. Use the exact text on your screen and whether the download or disk counters move.

Stop once the update completes. A working result means the launcher opens normally, its queue no longer repeats the same step, and the affected game displays Play or launches successfully. If it continues patching for some time but disk activity is present, do not repeatedly kill the process solely because the percentage changes slowly.

Start with checks that preserve installed games

1. Check for a service problem. Review official Blizzard service notifications, Battle.net Support, and the relevant game’s official status channels. If Blizzard reports patching maintenance or a widespread update incident, wait for service restoration instead of repeatedly changing Windows settings.
2. Inspect the downloads queue. In Battle.net, open its current downloads/update view. Some app versions expose a downloads icon near the top; UI wording varies. Look for another game being installed, a paused transfer, or a launcher operation that must finish first. Complete or pause conflicting work using the visible controls if available.
3. Check whether the PC is busy. Press Ctrl + Shift + Esc to open Task Manager, then look at Battle.net, Agent, disk, and network activity. Patching can spend time unpacking files with little network traffic. A static number by itself does not prove the installer is frozen.
4. Close the app normally. Exit Battle.net from the app and its system-tray icon, if present, rather than only closing the window. Save work in any other open programs.
5. Restart Windows. Select Start > Power > Restart, sign back in, then launch Battle.net once. Allow the app to finish initializing before starting more downloads.

Expected result: The update resumes and eventually completes, or you can identify a more specific failure such as an Agent loop, a permissions error, or a network stall. If a game is still actively patching, avoid force-closing it mid-write: interrupted file operations can lead to additional verification work.

Restart a stalled Battle.net Update Agent cleanly

Blizzard’s official Deleting Battle.net Files instructions start by closing the desktop app, Agent, and game processes. This is important because an old updater process can hold files in use even after the Battle.net window disappears. Begin with a process restart without deleting anything.

1. Close your Blizzard games and exit Battle.net from the system tray if the tray icon is visible.
2. Open Task Manager with Ctrl + Shift + Esc. Expand the process list if needed.
3. Look for Battle.net, Agent, and any Blizzard game process that remains running. End only the relevant processes after confirming that no game update is actively writing important files.
4. Wait until those processes are gone. If you are unsure what is still running, restart Windows instead of terminating unfamiliar system processes.
5. Open Battle.net again and let its internal update process finish. Do not start multiple launcher instances to force the update.

Verify: The app should stop repeating “Updating Battle.net Agent” and proceed to the main interface or the selected game download. If the Agent stalls immediately on each clean launch, continue with connection and storage checks, then Blizzard’s targeted launcher-data repair below. Repeating the same process kill several times is unlikely to resolve a corrupted folder.

Fix “Waiting on Another Installation or Update”

This message can be legitimate when Battle.net is handling a different patch. It can also appear when a previous update did not release its lock. Blizzard maintains separate support guidance for this exact message, so inspect the queue before assuming that the Agent itself is broken.

1. Open the download queue and identify any other active game, pre-release content download, or launcher update.
2. If another install is running, let it finish if possible. If you intentionally need to prioritize one game, use Battle.net’s own pause and resume controls where offered; do not move game folders while a patch is active.
3. If the queue appears idle but the warning persists, completely exit the launcher and close lingering Agent and game processes using the prior section.
4. Restart the computer and retry the affected update once. Note whether the same warning returns or changes to an error code.

What if it still fails? If every game is blocked, focus on shared launcher data, security conflicts, and connectivity. If only one game is blocked while others patch successfully, treat that game’s installation path and file integrity as the stronger leads. That distinction can save hours of unnecessary downloads.

Check whether “Initializing” or 0 B/s means a real freeze

Blizzard lists Stuck on Initializing While Installing or Patching and Game Install or Update Stuck at 0 B/s as separate support topics. A game may be verifying, unpacking, or changing local files while incoming network data is low. Exact behavior depends on game, patch size, storage, and the launcher version; there is no reliable universal number of minutes at which every update becomes “stuck.”

1. Observe Battle.net’s status text and Windows Task Manager’s network and disk activity for a short, reasonable period.
2. If disk activity continues and the status changes, allow the operation to proceed. Avoid pausing and resuming repeatedly during file preparation.
3. If there is no observable progress and the app responds to controls, pause and resume the download once, if those controls are offered by your current Battle.net version.
4. Check free disk space on the drive containing the game and the system drive. Applying a patch can need temporary working space beyond the advertised download size; there is no single extra-space figure that fits every game.
5. Close other disk-intensive applications and retry. If Windows reports a specific read/write or access error, record its exact wording before moving to repair steps.

Verify: The launcher begins transferring data, completes file preparation, or reports a specific error that can be researched. If the only clue remains 0 B/s, test the network next rather than immediately reinstalling Windows or deleting large game folders.

Check internet access without weakening Windows security

A working web browser does not prove every patch-delivery route is accessible. Blizzard’s update troubleshooting recognizes that connection problems, interfering software, or the network environment can affect patch downloads. Isolate the problem with reversible tests first.

1. Confirm normal connectivity. Load the official Battle.net website and another familiar website. If several services fail, fix the connection before troubleshooting the launcher.
2. Prefer a stable connection. If using Wi-Fi with frequent interruptions, try a trusted Ethernet connection or move closer to your access point. Do not claim a speed threshold without measurement.
3. Review VPN or proxy settings. If you are using a VPN or proxy, temporarily disconnect it for one controlled comparison, assuming your network policy permits that change. Reconnect after the test.
4. Test one alternate network. A short test over another trusted connection, such as a phone hotspot with enough data, helps determine whether the failure follows the computer or the home network. Downloading large patches over cellular data may incur charges.
5. Inspect security software only for an actual block. Use the product’s logs or notifications, then allow the verified Blizzard application if necessary. Microsoft’s Windows Security guidance says an application exception is safer than opening an unnecessary network port.

Do not disable Windows Firewall, antivirus protection, or SmartScreen indefinitely. If a managed school or work network blocks game services, ask its administrator rather than bypassing policy. There is also no reason to edit the registry, change DNS providers at random, or factory-reset your router as a first response to a stalled game patch.

Verify storage space, installation paths, and file permissions

If downloads arrive but cannot be applied, the problem may be local rather than network-related. The launcher and game both need permission to work with their installation locations; external disks or protected folders add more variables. A drive that appears to have room for the download itself can still run out of temporary working space during patching.

1. Open File Explorer > This PC and check available space on both the game drive and your Windows system drive. Free space safely by moving personal files or removing unused applications rather than deleting unknown game files.
2. Confirm that the game drive is connected, accessible, and not in a read-only or failing state. For portable drives, check the connection before restarting a patch.
3. If Battle.net shows a missing path, use its built-in game-location selection or locate-existing-install option when present. Do not select an empty directory and assume the old game is gone.
4. Check for a security alert that specifically names the launcher or its installation directory. If a verified block exists, follow the security vendor’s supported allowlist workflow; remove any test exception when it is no longer needed.
5. Restart after resolving a disk-space or permissions problem, then try the patch again and monitor for the same error.

Some users try “Run as administrator” for every launcher problem. Elevated permission is not a diagnosis, and routine operation should not require unnecessary administrator access. Consider a controlled escalation only if Blizzard’s instructions for a confirmed permission error call for it, and never run third-party “fix” scripts that claim to repair Battle.net automatically.

Repair damaged Battle.net launcher data

Use this step only after you have ruled out an active download, restarted the Agent, and checked the network and drive. In its Deleting Battle.net Files article (34719), Blizzard says outdated, corrupted, or missing Battle.net folders can interfere with the desktop app and game clients. Its Windows procedure targets the Battle.net folder under ProgramData, not the installed-game directories.

Before you proceed: Make a note of the drive and folder where each installed game resides. If you prefer a reversible first test, copy or back up the targeted folder before removing it; Blizzard’s documented step itself is to delete the folder. This can reset launcher state and require the app to rediscover game installations. Never delete the entire ProgramData directory, the directory holding all your game data, or folders with similar names in unrelated locations.

1. Exit Battle.net and your games. Press Ctrl + Shift + Esc and close remaining relevant Agent, Battle.net, and Blizzard game processes as described by Blizzard.
2. Press Windows + R, type C:\ProgramData\, and press Enter. This is a system-wide application-data folder, not your game library.
3. Find the folder named exactly Battle.net in that location. Reconfirm the path before changing anything.
4. Following Blizzard’s official repair procedure, delete that Battle.net folder. If you cannot confidently identify it, do not proceed; use Blizzard Support instead.
5. Launch Battle.net again. The app may recreate its working data and update itself. Retry the game update and check for progress.

Expected result: The launcher rebuilds the damaged state and patches normally. If a game now shows Install rather than Play, do not immediately redownload it. Blizzard explicitly warns that the launcher may forget install paths after this repair. Use Locate this game or the equivalent existing-game location control in your launcher version, point to the actual installation directory, and let the app validate it. If the same updater error returns, move to the next step rather than repeatedly deleting the folder without new evidence.

Repair one game’s files only when the launcher works

A normal game update that fails after the launcher has opened differs from an Agent update that prevents Battle.net itself from starting. For a game-only failure, repairing that game’s files can be more appropriate than reinstalling the desktop app. Blizzard’s game support pages refer to its repair tool, but the available menu and exact label can differ across titles and launcher versions.

1. Let Battle.net complete any app-level update first; confirm the launcher itself opens and connects.
2. Select the affected game’s page and look for a menu beside its installation or Play controls.
3. If the game offers Scan and Repair, close that game, back up important local mods or custom files where applicable, and run the supported check.
4. Follow the results and let the launcher download replacement files when required. A repair may recheck substantial portions of the installation and can remove modified files that conflict with original game data.
5. Try the update or launch again. If the repair fails with a specific error code, use that code and the game’s title when contacting support.

Do not run Scan and Repair as a supposed repair for a broken Battle.net Agent. The launcher must be working well enough to manage the selected game, and the operation targets that game’s files rather than the update service shared by all games.

Reinstall the desktop app only if earlier fixes fail

Blizzard’s troubleshooting articles list uninstalling and reinstalling the Battle.net desktop app as a later option for persistent launcher problems. It is not a shortcut around a failing drive or a network policy, and reinstalling the launcher alone does not guarantee that a particular game patch will be repaired.

1. Record the current error and your installed-game directories. Back up locally stored data that could be affected by application or game changes.
2. Close Battle.net and all associated game/Agent processes.
3. Open Settings > Apps > Installed apps in Windows 11, find the Battle.net desktop app, and use its available uninstall option. Microsoft’s guidance notes that not every desktop app exposes a Repair or Reset button; do not invent a missing menu.
4. Download the installer from Blizzard’s official Battle.net website, not a mirror, sponsored third-party driver page, or repair utility. Install it and sign in using the official authentication flow.
5. Use the launcher to locate previously installed games if needed. Verify the update and launch of one affected game before changing other settings.

What if reinstalling still hangs? The underlying cause may be network filtering, permissions, storage, or user-profile configuration rather than the app binary. Record whether the same stage fails again. Avoid escalating to Windows reset, disk formatting, or broad deletion of program folders merely to fix one launcher update.

Know when to stop and contact Blizzard Support

A support request becomes more useful when it documents what changed, not just that Battle.net is stuck. Blizzard publishes separate articles for Agent problems, initialization, waiting on another update, and patch transfer issues. Provide the exact symptom or error code and the affected game so support can route you to the relevant path.

• Record the full on-screen error text or code, and whether it appears before the launcher opens or while a specific game patches.
• Include your Windows edition, approximate date of the last successful update, and the game title or launcher component involved.
• State whether the issue affects every game or just one, whether Windows reports disk problems, and whether a different trusted connection changes the result.
• List the safe steps already attempted and their outcomes, especially Agent restart, free-space checks, and any targeted Blizzard folder repair.
• Use Blizzard’s official desktop-app log collection guidance if support specifically asks for diagnostics. Review logs for personal information and use the official support channel; never publish passwords, authentication tokens, or private account details.

If you suspect a failing drive, back up valuable files and check disk health before making more writes. If a particular security product blocks Battle.net, keep protection enabled and work with its provider or a system administrator. Neither situation is solved reliably by repeating launcher reinstall attempts.

Frequently asked questions

Does deleting the Battle.net folder in ProgramData uninstall my games?

No; Blizzard’s specific repair targets launcher data in C:\ProgramData\Battle.net, not the folders containing the installed games. However, Blizzard warns that Battle.net may forget the game locations. If a game shows Install afterward, use the locate-existing-install feature rather than assuming its files were removed.

Why does Battle.net show 0 B/s even when a patch is doing something?

Network speed reflects downloaded data, not necessarily local file preparation. The updater may be validating or unpacking files while network transfer is minimal. Check status text and disk activity before deciding it is frozen. If activity and progress remain absent after reasonable observation, use the network and disk checks above.

Should I delete the Agent folder, reinstall Windows, or disable antivirus?

Not as first-line solutions. Use Blizzard’s precisely documented repair for the relevant problem, and do not delete similarly named folders by guesswork. Reinstalling Windows is disproportionate to an isolated launcher problem. Microsoft’s security guidance favors verifying specific blocks and using narrow application exceptions over switching off the firewall.

Will Scan and Repair fix Battle.net itself being stuck updating?

Not usually. Scan and Repair checks the files of a selected supported game. If the Agent or desktop app cannot finish its own update, work through launcher-process, network, storage, and official launcher-data troubleshooting first.

What if Battle.net gets stuck again after every restart?

Look for a repeating error code or a condition that persists across restarts: another updater, a blocked connection, low storage, or a damaged launcher folder. If the issue continues after the documented targeted repair and clean reinstall, collect the details above and contact Blizzard Support instead of repeatedly modifying system security settings.

Final thoughts

The safest Battle.net stuck updating fix is to identify the stalled stage before repairing anything. Check the download queue, restart Battle.net and Agent cleanly, confirm network and storage health, and only then use Blizzard’s documented ProgramData repair for damaged launcher files. If the launcher works but one game does not, investigate that game’s update or file integrity separately. Verify that the patch finishes and the game launches; if it does not, use the exact error and Blizzard’s support channels for a focused next step.