Problem: Battle.net “Initializing” / “Waiting on another update” loops (and Update Agent stalls) that block installs, patches, or even Battle.net itself
Published: 2026-01-06 10:35 (local time)
Quick Summary
- Many PC players report Battle.net getting stuck on “Initializing” (often 0%) or “Waiting on another update,” preventing installs/patches and sometimes game launches.
- Blizzard’s own troubleshooting confirms common fixes (clearing Battle.net folders, deleting Tools, rebooting), but outcomes are inconsistent.
- A surprisingly effective workaround for a subset of users is resetting Windows WMI (Windows Management Instrumentation), which Blizzard documents as required for the Battle.net desktop app to work correctly.
- There’s no single guaranteed fix because the issue appears to have multiple root causes (corrupt cached data, stuck agent processes, WMI problems, security software interference, or maintenance/patching windows).
- Below are several real-world, repeatable workarounds you can try in escalating order, plus clear “stop and contact support” points.
What’s happening
On Windows PCs, the Blizzard Battle.net Desktop App can fail to patch or install games (and sometimes fail to install or update itself). Players commonly see the downloader sit at “Initializing” (often at 0%), loop between “Initializing” and “Waiting on another update,” or stall while “updating Battle.net Update Agent” (commonly cited around mid-progress percentages, such as 45%). Blizzard has an official help article specifically for being stuck at “Initializing,” and another for “Waiting on another installation or update,” indicating this is a recurring, widespread launcher-layer problem rather than a single-game bug.
Who is affected: primarily Windows users installing/updating Blizzard titles through Battle.net (e.g., World of Warcraft, Diablo, Overwatch, Call of Duty via Battle.net). The issue can also impact people who can’t update the launcher itself, which blocks all Blizzard games on that machine until resolved. Reports appear regularly on Blizzard’s forums and community spaces, and Blizzard continues updating related support articles (including WMI guidance) recently, suggesting the problem remains current and relevant.
Likely causes (what research suggests)
- Corrupted cached installer/update data in ProgramData: Blizzard’s “Stuck on Initializing While Installing or Patching” guidance points directly to clearing specific folders in %programdata% so the app can rebuild them.
- Battle.net Update Agent data missing/corrupted or Tools folder issues: Blizzard error documentation for Update Agent failures recommends rebuilding by deleting the Battle.net Tools folder and other standard remediation steps.
- Windows Management Instrumentation (WMI) corruption/disablement: Blizzard states the Battle.net Desktop Application requires access to WMI; if corrupted/disabled, the app can misbehave. They document a WMI repository reset procedure as a fix, and community threads repeatedly cite it as the only thing that worked for some.
- Maintenance/patching windows or stuck concurrent updates: Blizzard’s “Waiting on another installation or update” article notes that regional patching/maintenance can block updates, and instructs checking whether other Battle.net items are updating.
- Software conflicts (security tools, background processes, permissions): Blizzard’s troubleshooting repeatedly points to rebooting, closing background apps, scanning for malware, and resolving permissions/software conflicts, implying these can be contributing factors.
Solutions & Workarounds
1) Clear Battle.net’s ProgramData cache folders (official “stuck on Initializing” fix)
Who it helps: Windows PC users stuck at “Initializing (0%)” while installing or patching any Battle.net game.
Steps:
- Fully exit the Battle.net app (right-click the tray icon → Quit).
- Press Windows Key + R, type %programdata%, press Enter.
- Delete these folders (if present): Battle.net, Battle.net_components, Blizzard Entertainment.
- Reopen Battle.net and retry the install/update.
Risks / tradeoffs: You’ll force Battle.net to rebuild cached data; this is usually safe but can require re-login and re-checking files.
Stop & contact support when: Battle.net still loops after repeated retries, or if deletion fails due to permissions you can’t resolve.
2) Fix “Waiting on another update” by ruling out real concurrent updates and rebooting (official baseline)
Who it helps: Players seeing “Waiting on Another Installation or Update,” especially right after patch days or maintenance.
Steps:
- In Battle.net, check if any other game (or the app itself) is updating; pause/cancel other downloads.
- Reboot Windows (not just “Restart Battle.net”).
- After reboot, launch Battle.net and try again.
Risks / tradeoffs: Minimal; the downside is time and repeated retries.
Stop & contact support when: The issue persists across multiple reboots and you also cannot update/install the Battle.net app itself.
3) Reset the Windows WMI repository (official fix that often resolves stubborn loops)
Who it helps: Windows users where normal cache-clearing doesn’t work, especially if Battle.net behaves “broken” across multiple games and installs.
Steps (from Blizzard):
- Press Windows key, search cmd.
- Right-click Command Prompt → Run as administrator.
- Run these commands one at a time:
- net stop winmgmt
- winmgmt /resetrepository
- net start winmgmt
- Restart your PC, then test Battle.net again.
Risks / tradeoffs: This changes Windows management instrumentation state; it can temporarily affect other software that relies on WMI until the system stabilizes after reboot. If you see “Access denied,” don’t brute-force it—move to the support step.
Stop & contact support when: You get access errors even as admin, or the launcher still won’t install/update after the reboot.
4) Rebuild Battle.net Update Agent data (Tools folder / agent errors)
Who it helps: Users hitting Update Agent-related errors (including cases where files are missing/corrupt) or the app can’t download new copies.
Steps (high-level, per Blizzard guidance):
- Restart your PC to clear stuck services.
- Follow Blizzard’s instructions to delete/rebuild the Battle.net Tools folder (they use this to rebuild outdated/corrupt files).
- Reopen Battle.net and retry.
Risks / tradeoffs: Incorrect deletion in the wrong directory can cause extra reinstall work—follow the official steps exactly.
Stop & contact support when: You can’t locate folders safely, or the app repeatedly fails to regenerate required files.
5) Reduce software conflicts (security/VPN/background apps) and retest
Who it helps: Users whose downloads start but repeatedly reset, or where the agent appears to “sleep”/hang.
Steps:
- Temporarily disable VPN and third-party network filters (if any) and retry once.
- Whitelist Battle.net and Blizzard game folders in your security software (instead of fully disabling long-term).
- Close background apps that hook networking/overlays (then test).
Risks / tradeoffs: Disabling protections can increase risk if you browse/download unrelated content; keep the test brief and re-enable afterward.
Stop & contact support when: You must disable critical security controls just to patch; that’s not a sustainable “fix.”
Prevention (so it doesn’t come back)
- Keep Windows fully updated and avoid running multiple launchers/large downloads simultaneously on patch day.
- Don’t “power kill” the PC mid-update; let Battle.net finish or pause cleanly.
- If you use aggressive endpoint/security tools, add proper exceptions for Battle.net rather than relying on repeated reinstalls.
- When you see repeated loops, try the official ProgramData cache reset early—waiting hours rarely improves outcomes.
FAQ
Q: Is this a Blizzard server outage?
A: Sometimes maintenance/patch windows can block updates, but many cases are local launcher/Windows issues (cache, agent, WMI). Blizzard explicitly recommends checking maintenance and then doing local steps.
Q: Why does it say “Waiting on another update” when nothing else is updating?
A: The app may think another task is active or stuck. Rebooting and clearing cached folders often breaks the loop; WMI reset can help in harder cases.
Q: Does reinstalling Battle.net always fix it?
A: No. Community reports show reinstalls can fail if the underlying agent/WMI/cached state remains broken. Try the ProgramData reset and WMI reset before repeated reinstalls.
Q: What’s the fastest “high success” fix if I’ve tried the basics?
A: If cache clearing and reboots don’t work, Blizzard’s WMI repository reset is one of the most consistently cited next steps, and Blizzard documents it as a requirement for Battle.net to function correctly.
Q: When should I stop troubleshooting?
A: Stop if you hit “Access denied” in admin CMD for WMI steps, if Battle.net won’t reinstall at all after official procedures, or if you’re forced into unsafe security compromises.
Q: Will this affect only one game (like WoW) or everything?
A: Often it affects multiple Blizzard titles because it’s at the launcher/update-agent layer, not inside a single game install.