The Battle.net launcher – now officially called the Blizzard Battle.net Desktop App – reached version 2.51.6.17477 on June 18, 2026, adding cross-library support for Bethesda and Xbox Game Studios titles alongside Blizzard’s own portfolio. If you have never installed it before, or you are migrating to a new Windows 11 machine, this step-by-step guide walks you through every part of the process: download, account setup, game installation, performance tuning, social features, and the eight most common error fixes you will actually hit.
Don't miss new tech stories on Google
Add Tech Insider once in the Google app and our stories appear in your news suggestions.
What Is the Battle.net Launcher in 2026?
Battle.net is Blizzard Entertainment’s first-party game client, managing authentication, patching, downloading, and social features for every major Blizzard and Activision PC title. Following Microsoft’s acquisition of Activision Blizzard, the launcher expanded beyond its original scope. In February 2025, Avowed (Xbox Game Studios) became the first non-Blizzard, non-Activision title distributed through Battle.net. Three months later, in May 2025, Doom: The Dark Ages (Bethesda Softworks) launched on the platform, signaling a broader consolidation of Microsoft’s PC gaming catalog into a single client.
As of June 2026, the Battle.net launcher supports the following games:
| Game | Studio | Notes |
|---|---|---|
| World of Warcraft | Blizzard Entertainment | Includes The War Within expansion |
| Diablo IV | Blizzard Entertainment | Vessel of Hatred expansion available |
| Overwatch 2 | Blizzard Entertainment | Free-to-play; replaced original Overwatch |
| Hearthstone | Blizzard Entertainment | Card game; free-to-play |
| Warcraft Rumble | Blizzard Entertainment | Mobile-first title with PC launcher wrapper |
| Call of Duty (series) | Activision | Warzone, Black Ops 6, and others |
| Avowed | Xbox Game Studios | Added February 18, 2025 |
| Doom: The Dark Ages | Bethesda Softworks | Added May 15, 2025 |
Games that have been removed from Battle.net include the original Overwatch, Destiny 2 (which moved to Steam), and Warcraft III: Reign of Chaos. If you are looking for those titles, you will need Steam or Bungie’s standalone launcher instead.
Prerequisites: System Requirements and What to Prepare
Before starting the installation, confirm you meet the minimum requirements. Installing on a system that fails any of these checks will result in launcher crashes or authentication failures that take time to diagnose.
| Requirement | Minimum | Recommended |
|---|---|---|
| Operating System | Windows 10 64-bit (build 19044+) | Windows 11 64-bit (22H2 or later) |
| Processor | Any 64-bit CPU | Intel Core i5-8400 or AMD Ryzen 5 2600 |
| RAM | 4 GB | 16 GB (required for Diablo IV / Call of Duty) |
| Storage – launcher only | 1.5 GB free | SSD strongly recommended |
| Storage – games | 10 GB minimum | 50–150 GB for a full library |
| Internet connection | Broadband | 50 Mbps or faster for rapid patching |
| Blizzard Account | Free account required | Authenticator enabled for security |
| Visual C++ Runtime | 2015–2022 Redistributable | Latest version (both x64 and x86) |
The Visual C++ 2015–2022 Redistributable is the most commonly missed prerequisite. Without it, Battle.net.exe exits silently on first launch with no error message, which confuses new users into thinking the download was corrupt. You need both the x64 and x86 packages even on a 64-bit system because some 32-bit game components depend on the x86 runtime. Download both from Microsoft’s official Visual C++ Redistributable page before running the Battle.net installer.
You should also confirm that Windows Update is current. Battle.net’s authentication system requires TLS 1.2 or later, and certain Windows 10 builds older than the November 2021 Update (19044) have TLS configuration issues that cause login failures with no informative error code.
Step 1: Download the Battle.net Installer from the Official Source
Always download the Battle.net installer exclusively from Blizzard’s official download server. Search engine results for “battle.net download” frequently surface third-party mirror sites that bundle adware, outdated launcher versions, or worse. The correct URL is:
https://download.battle.net/en-us/desktop
The file name is Battle.net-Setup.exe. Its download size is approximately 150–200 MB. After installation, the full launcher footprint grows to roughly 1.5 GB before any games are installed – this covers the launcher binary, update agent, and initial content manifests.
Verify the Installer File Hash
Before running any downloaded executable, verify its SHA-256 hash against the value published in Blizzard’s release notes. Open PowerShell and run:
# Verify Battle.net installer integrity before running it
$installerPath = "$env:USERPROFILE\Downloads\Battle.net-Setup.exe"
$hashResult = Get-FileHash $installerPath -Algorithm SHA256
Write-Host "SHA-256: $($hashResult.Hash)"
Write-Host "File: $($hashResult.Path)"
# Compare this output against the hash shown on Blizzard's download changelog
# A mismatch means the file was modified – delete it and re-downloadIf the hash matches, proceed. If it does not match, the file was either corrupted in transit or substituted – delete it immediately and download again from the official URL.
Step 2: Run the Installer and Choose Your Install Path
Right-click Battle.net-Setup.exe and select Run as administrator. Do not simply double-click it – on some Windows 11 configurations the UAC prompt is suppressed when launching from the Downloads folder, causing the install to fail silently at 0% because it lacks write permission to Program Files.
The installer presents one decision point: the installation folder. The default is:
C:\Program Files (x86)\Battle.net\You can redirect the launcher binary to any drive with at least 2 GB free. However, one important caveat: the ProgramData cache folder always lands on C:, regardless of where you install the launcher. This folder – C:\ProgramData\Battle.net\ – holds update agent files, cached login tokens, and network configuration. It is not configurable during setup. You must keep at least 2 GB free on your C: drive at all times, even if the launcher binary and all games live on a secondary drive.
Critical pitfall: Do not choose an installation path that contains non-ASCII characters – accented letters (ñ, ü, é), Cyrillic characters, or Chinese/Japanese/Korean characters in any part of the path string. On Windows 10 with non-English system locales, the installer silently fails with no error message when it encounters a special character in the path. Use ASCII-only paths such as D:\Games\Battle.net\.
After installation, Battle.net launches automatically and connects to Blizzard’s servers to download the latest version of the launcher itself. This secondary download is typically 50–100 MB and happens in the background during your first login.
Step 3: Create or Log In to Your Blizzard Account
The launcher prompts you to log in or create an account immediately after installation. Battle.net accounts are free.
If you are creating a new account:
- Click Create a Free Account on the login screen.
- Enter your email address and a password (minimum eight characters with at least one number and one letter).
- Choose a BattleTag – your permanent display name across all Battle.net games. The tag format is
Name#1234where the four-digit number is assigned automatically. Select your name carefully: Blizzard charges for BattleTag name changes. - Verify your email address by clicking the link in the confirmation message Blizzard sends to your inbox.
- Return to the launcher and log in with your new credentials.
If you see error BLZBNTBNA00000005 immediately after entering your credentials, your network is blocking Blizzard’s authentication endpoint. The complete fix is in the troubleshooting section – the short version is to disable any active VPN, flush your DNS cache with ipconfig /flushdns, and try again.
Step 4: Enable Two-Factor Authentication Before Installing Games
Account security is not optional for Battle.net. Blizzard game accounts are targeted constantly by credential-stuffing attacks using leaked username-password combinations from data breaches on other services. The Battle.net Authenticator adds a time-based one-time password (TOTP) layer that stops the overwhelming majority of unauthorized login attempts cold.
Set up the Authenticator before you purchase any games or connect payment methods. You have two options:
- Battle.net Mobile App (preferred): Download the free app for iOS (version 1.35.1, released June 1, 2026) or Android (updated May 8, 2026). In the app, navigate to Account > Authenticator and scan the QR code shown in your Blizzard account security settings. The app also provides your friends list, real-time “what they’re playing” status, and in-app Warcraft Rumble access – so it delivers value beyond just 2FA.
- Third-party TOTP apps: If you prefer not to install the Blizzard app, any standards-compliant TOTP generator (Google Authenticator, Authy, 1Password) works. In your Blizzard account portal under Security, choose Set up Authenticator and select the manual key entry option to export the TOTP seed to your preferred app.
After enabling the Authenticator, Blizzard marks your current device as trusted for 30 days. On trusted devices, you are not prompted for the TOTP code on every login. On a new device, you will always be asked for the code once to establish trust.
Keep your device clock synchronized. TOTP codes expire every 30 seconds and a clock drift of more than 90 seconds between your phone and Battle.net’s servers will cause authentication to fail even with the correct code. Windows clock sync is automatic via time.windows.com; mobile devices sync via the cellular network.
Step 5: Configure Core Settings Before Your First Game Install
Click the Battle.net logo in the top-left corner of the launcher and select Settings. Spending five minutes here before your first game install avoids several hours of rework later.
Default Game Install Location
Under Game Install/Update > Default Install Directory, change the path from the C: default to whichever drive has the most free space – typically a secondary SSD or HDD. This setting applies to all future installs. Games already installed will not move automatically; relocating them requires a manual process described in Step 8 below.
Download Bandwidth Cap
Under Downloads, the Latest Updates Download Rate slider defaults to unlimited. If you share a home network with others or are on a metered connection, cap the download to 60–70% of your total bandwidth. For a 500 Mbps connection, 300 Mbps is a sensible cap. One of the most common causes of “Battle.net downloads slowly” reports in support forums is a forgotten bandwidth cap from a previous configuration.
Hardware Acceleration
Under App Settings > Advanced, the Hardware Acceleration toggle uses your GPU to render the launcher interface, reducing CPU usage by 5–15% on most systems. Leave it on unless you see flickering, green artifacts, or black regions in the launcher UI – symptoms that appear on certain Intel integrated graphics configurations with outdated drivers on Windows 11.
Language Per Game
Under App Settings > Language, configure your preferred text and audio language. Each game on Battle.net can be set to a different language. The key warning: changing a game’s audio language after installation triggers a re-download of the voice pack, which can be 10–30 GB for World of Warcraft or Call of Duty. Set language correctly the first time to avoid this re-download.
Step 6: Install Your First Game
Click the game icon in the left sidebar. For free-to-play titles (Overwatch 2, Hearthstone, Warcraft Rumble), click Install and the download begins immediately. For paid titles (Diablo IV, World of Warcraft, Avowed, Doom: The Dark Ages), you must own the game or have an active subscription before the Install button activates.
Game storage sizes you should plan for in 2026:
| Game | Download Size | Full Install Size | Streaming Install Available? |
|---|---|---|---|
| World of Warcraft | ~40 GB (core) | ~100 GB (all content) | Yes – play after ~20 GB |
| Diablo IV + Vessel of Hatred | ~90 GB | ~100 GB | No |
| Overwatch 2 | ~50 GB | ~55 GB | No |
| Call of Duty: Black Ops 6 | ~100 GB | ~120 GB | No |
| Hearthstone | ~3 GB | ~3.5 GB | No |
| Doom: The Dark Ages | ~65 GB | ~70 GB | No |
| Avowed | ~50 GB | ~55 GB | No |
World of Warcraft’s streaming install lets you begin playing zone content once approximately 20 GB of core data has downloaded. The remaining world content streams in the background as you explore new zones. To disable streaming and download everything before playing – useful on slow connections where interruptions would cause in-game loading issues – uncheck Enable Streaming on the install confirmation dialog.
Monitor download progress in the bottom status bar of the launcher. It displays real-time download speed, remaining file size, and an estimated time-to-completion. If the speed drops to near zero without a visible reason, open Windows Task Manager and sort by Network column – another application (Windows Update, OneDrive, or a game already installed applying a background patch) is likely competing for your bandwidth.
Step 7: Understand Battle.net’s Folder Structure on Windows
Knowing where Battle.net stores its files is prerequisite knowledge for effective troubleshooting. The folder layout is split across three locations on Windows:
# Launcher application binaries
C:\Program Files (x86)\Battle.net\
└── Battle.net.exe ← Main launcher executable
# Cache, update agent, and config (ALWAYS on C: – cannot be changed)
C:\ProgramData\Battle.net\
├── Agent\
│ └── Agent.exe ← Update agent (version 2.34.1.8636)
├── Cache\ ← Content manifests; safe to delete when launcher is closed
└── Setup\ ← Temporary installer components
# Per-user settings and session tokens
C:\Users\YourName\AppData\Roaming\Battle.net\
└── Battle.net.config ← User-specific preferencesThe Agent.exe process runs silently in the background whenever Battle.net is open. It handles downloading, patching, and validating game files. If you see elevated CPU usage from Agent.exe when you are not actively downloading, it is usually performing a background file integrity check triggered by a recent game patch – this typically completes within 15–30 minutes and returns to idle on its own.
The Cache folder under ProgramData is safe to delete at any time when the launcher is fully closed. Battle.net rebuilds it on next launch. Clearing this cache is one of the first diagnostic steps for most launcher issues because stale manifests in this folder are a common source of update loops and install failures.
Step 8: Move an Existing Game to a Different Drive
Battle.net does not have a built-in “move game” button, but you can relocate any installed game without re-downloading it. The process takes under ten minutes.
- In the Battle.net launcher, select the game and click Options (gear icon) > Uninstall Game. This removes the registry reference only – it does not touch any game files on disk.
- Move the game folder to the target drive. Use
robocopyfor large games to preserve file attributes and handle errors gracefully:
REM Open Command Prompt as Administrator, then run:
robocopy "C:\Program Files (x86)\Overwatch" "D:\Games\Overwatch" /E /COPYALL /R:3 /W:5
REM /E – copy all subdirectories including empty ones
REM /COPYALL – preserve timestamps and file attributes
REM /R:3 – retry failed files up to 3 times
REM /W:5 – wait 5 seconds between retries- Back in Battle.net, click Install on the same game.
- When the install dialog asks for the location, navigate to the folder you just copied the files into (e.g.,
D:\Games\Overwatch) and select it. - Battle.net detects the existing files and runs a validation pass rather than downloading everything again. Validation on an SSD takes 5–15 minutes for most games; on a mechanical HDD, allow 25–45 minutes.
After validation completes, confirm the original files on C: were fully copied before deleting them. You can run robocopy again with the /L flag (list only, no copy) to compare the two directories without risk.
Step 9: Configure Social Features – Friends, Voice, and Groups
Battle.net’s social layer is one of its genuine advantages over competitor launchers. A chat message you send from within World of Warcraft appears immediately in your friend’s Diablo IV launcher – cross-game instant messaging persists regardless of which title each person is playing. This is functionality that Epic Games Launcher and Rockstar’s launcher do not currently offer.
Adding Friends
Click the Friends icon (person silhouette) in the bottom bar of the launcher. Select Add a Friend and enter either the full BattleTag (PlayerName#1234) or the email address associated with the account (if that option is enabled by the recipient). Friend requests appear as launcher notifications and can be accepted from any Battle.net client, including the mobile app. Your friends list shows real-time status: online, in-game with the game name visible, or away.
Voice Chat and Channels
Built-in voice chat in Battle.net is available from the Friends panel – click the microphone icon next to an online friend to initiate a call. For group voice without a specific game context, create a Chat Channel under the Chat menu. Channels persist indefinitely, can hold up to 100 participants, and are accessible to anyone you invite regardless of what game they are playing. Note that in-game voice – for example, Overwatch 2 team communication or Call of Duty squads – is separate from Battle.net voice chat. The two systems run independently and do not conflict.
Groups
Battle.net Groups are cross-game communities accessible through the launcher’s Groups tab. Unlike game-specific clans (which exist within a single title), a Group spans multiple games. You can create a group for your gaming community, invite members who play different Blizzard and Activision titles, and maintain a single shared news feed and chat regardless of what each member is playing. Groups are particularly useful for organizing sessions across Overwatch 2, Diablo IV, and Call of Duty simultaneously without switching between separate in-game social systems.
Step 10: Set Up the Battle.net Mobile App
The Battle.net mobile app – iOS version 1.35.1 (June 1, 2026) and Android (updated May 8, 2026) – is free and extends core launcher features to your phone without requiring a game subscription.
Core features available through the mobile app:
- Friends list and real-time chat: See who is online and what they are playing. Send and receive messages from anywhere.
- Battle.net Authenticator: Generates the TOTP codes used for two-factor authentication on login. This alone is reason enough to install the app even if you use none of its other features.
- Support ticket management: Open new Blizzard support tickets, check existing ticket status, and reply to agent messages without opening a browser.
- Warcraft Rumble: The mobile game runs natively within the Battle.net app – one of the few cases where the companion app is also a full game client.
To link the mobile app to your Blizzard account, log in with the same credentials you use on PC. For Authenticator setup, navigate to Account > Authenticator in the app and scan the QR code shown in the Blizzard account security portal at us.battle.net/support. If you use a TOTP app instead of the Blizzard app for 2FA, this step is not needed.
Step 11: Use Scan and Repair for Corrupted Game Files
After a game update, unexpected system shutdown, or interrupted download, individual game files can become corrupted or missing. Battle.net’s Scan and Repair feature re-validates every installed file against the official manifest and re-downloads only the damaged or missing pieces – far faster than a full uninstall and reinstall.
To run Scan and Repair on any game:
- Select the game in the left sidebar of Battle.net.
- Click the Options (gear) icon next to the Play button.
- Select Scan and Repair.
- Click Begin Scan in the confirmation dialog.
- Wait for the scan to complete. Do not close the launcher or launch the game during this process.
Expected scan duration by drive type:
| Game | Install Size | SSD Scan Time | HDD Scan Time |
|---|---|---|---|
| Hearthstone | ~3.5 GB | ~1 minute | ~3 minutes |
| Overwatch 2 | ~55 GB | ~5 minutes | ~20 minutes |
| Diablo IV | ~100 GB | ~8 minutes | ~35 minutes |
| World of Warcraft | ~100 GB | ~8 minutes | ~35 minutes |
| Call of Duty: Black Ops 6 | ~120 GB | ~10 minutes | ~45 minutes |
If Scan and Repair completes successfully but the game still crashes on launch, the issue is not file corruption. Common causes at that point include: an incompatible overlay application (Discord overlay, MSI Afterburner, RTSS), an outdated GPU driver, a Windows permission conflict on the game folder, or antivirus interference with the game’s anti-cheat software.
Step 12: Update Battle.net Manually When Auto-Update Fails
Battle.net normally self-updates silently. The current stable version as of June 18, 2026, is 2.51.6.17477 with Update Agent version 2.34.1.8636. If the launcher falls two or more versions behind, some games refuse to launch with a “launcher version mismatch” error. To check your version:
- Click the Battle.net logo in the top-left corner.
- Select Settings.
- Look at the bottom-left of the Settings panel for the version string.
You can also verify the version through PowerShell without opening the launcher:
# Read Battle.net version from the Windows registry (PowerShell)
$regPath = "HKLM:\SOFTWARE\WOW6432Node\Blizzard Entertainment\Battle.net"
if (Test-Path $regPath) {
$info = Get-ItemProperty $regPath
Write-Host "Launcher Version: $($info.DisplayVersion)"
Write-Host "Install Location: $($info.InstallLocation)"
} else {
Write-Host "Battle.net not found in registry – may not be installed."
}If the launcher is stuck in an update loop (reinstalling itself repeatedly without completing), run this sequence from an elevated Command Prompt to clear the stale update cache and force a clean re-download of the update components:
REM Force a clean Battle.net update (run Command Prompt as Administrator)
REM Step 1: Kill all Battle.net processes
taskkill /F /IM "Battle.net.exe"
taskkill /F /IM "Agent.exe"
taskkill /F /IM "Battle.net Helper.exe"
REM Step 2: Clear the stale setup cache
del /F /Q "C:\ProgramData\Battle.net\Setup\*.*"
for /D %%d in ("C:\ProgramData\Battle.net\Setup\*") do rmdir /S /Q "%%d"
REM Step 3: Clear the general Battle.net cache
del /F /Q "C:\ProgramData\Battle.net\Cache\*.*"
REM Step 4: Relaunch – Battle.net will rebuild update components on startup
start "" "C:\Program Files (x86)\Battle.net\Battle.net.exe"This sequence is the recommended manual update approach from Blizzard’s own support documentation. It clears the cached setup files that the auto-update mechanism uses as reference points, forcing Battle.net to re-fetch everything fresh on the next launch.
Common Pitfalls: 6 Mistakes That Create Hours of Problems
These mistakes account for the large majority of Battle.net support requests. Avoiding them from the start is significantly easier than diagnosing them after the fact.
- Downloading from unofficial sources. Mirror sites for “Battle.net download” frequently bundle adware, keyloggers, or outdated launcher versions that generate spurious error codes. Use only
download.battle.net/en-us/desktop. - Not running the installer as administrator. Battle.net writes to
Program FilesandProgramDataduring setup and updates, both of which require elevated privileges. If you double-click the installer without admin rights, it may appear to run but stall at 0% with no error message. - Running a VPN during authentication. Blizzard performs GeoIP validation on login. A VPN routing you through a flagged region triggers error
BLZBNTBNA00000005. Disable VPN before logging in; re-enable it afterward if required. - Installing to a path with special characters. Non-ASCII characters in any part of the installation path cause silent failures on Windows 10 with non-English system locales. Use ASCII-only directory names.
- Running a significantly outdated Windows version. Battle.net’s TLS-based authentication requires Windows 10 build 19044 or later. Older builds may fail login with cryptic network errors that do not mention the real cause.
- Manually deleting Agent.exe. Some users mistake
C:\ProgramData\Battle.net\Agent\Agent.exefor malware because it runs silently. Without Agent.exe, the launcher cannot patch games or itself. Restore it by running the Battle.net installer, which detects the missing agent and reinstalls it without affecting your games.
Troubleshooting: 8 Battle.net Errors With Step-by-Step Fixes
The following errors are the most frequently reported on Windows 10 and Windows 11 in 2025–2026, based on Blizzard’s support article data and community forums.
| Error / Symptom | Root Cause | Primary Fix |
|---|---|---|
| BLZBNTBGS000003F8 | Session token validation failure; network cannot reach Blizzard auth servers | Flush DNS (ipconfig /flushdns). Add Battle.net.exe and Agent.exe to Windows Firewall exceptions. Restart router. |
| BLZBNTBNA00000005 | VPN or proxy routing auth traffic through a blocked IP range | Disable all VPN/proxy. Restart router to get a fresh DHCP lease. Flush DNS after VPN is off. |
| Launcher won’t open (no error code) | A background instance of Battle.net is already running but not visible | Open Task Manager. End all Battle.net.exe, Battle.net Helper.exe, and Agent.exe processes. Relaunch. |
| “Agent went to sleep, attempting to wake it up” | Agent.exe lost its IPC connection to the launcher process | Open File Explorer, navigate to C:\ProgramData\Battle.net\Agent\, right-click Agent.exe, and select Run as administrator. Then relaunch Battle.net. |
| Update loop (launcher installs itself repeatedly) | Corrupted update cache; partial files from a previous failed update | End all Battle.net processes. Delete contents of C:\ProgramData\Battle.net\Setup\ and C:\ProgramData\Blizzard Entertainment\. Relaunch. |
| Black screen on launcher startup | Hardware acceleration incompatible with current GPU driver | In Settings > Advanced, disable Hardware Acceleration. Update GPU drivers. Re-enable acceleration after driver update. |
| Game download stalled at 0 B/s | Firewall or antivirus blocking access to Blizzard’s CDN | Add %ProgramFiles(x86)%\Battle.net\ and %ProgramData%\Battle.net\ to antivirus exclusions. Temporarily disable Windows Defender Real-Time Protection to test. |
| Login fails after recent password change | Cached session token contains old credentials | In the Blizzard account portal, log out all sessions. Delete C:\Users\YourName\AppData\Roaming\Battle.net\. Relaunch and log in with the new password. |
Full Network Reset for Persistent Connectivity Errors
If BLZBNTBGS000003F8 persists after basic fixes, run this network reset sequence from an elevated Command Prompt. Each command resets a different layer of the Windows networking stack:
REM Network reset sequence for persistent Battle.net connectivity errors
REM Run Command Prompt as Administrator
REM 1. Flush DNS resolver cache
ipconfig /flushdns
REM 2. Release and renew DHCP lease
ipconfig /release
ipconfig /renew
REM 3. Reset TCP/IP stack (requires restart to take effect)
netsh int ip reset resetlog.txt
REM 4. Reset Winsock catalog (requires restart to take effect)
netsh winsock reset
REM 5. After reboot, verify DNS is resolving Blizzard servers
nslookup us.battle.netThe netsh int ip reset command rewrites Windows TCP/IP registry keys and should be treated as a last resort before considering a fresh Windows installation. You must restart your PC after running steps 3 and 4 for them to take effect. After the restart, launch Battle.net before re-enabling any VPN or security software to isolate whether those tools are contributing to the issue.
Advanced Tips: Performance Optimization and Automation
Once the standard setup is complete, these configurations extract additional value from Battle.net.
Launch Individual Games Directly via Desktop Shortcuts
You can bypass the Battle.net home screen entirely and launch a specific game directly using the --game command-line flag. Right-click the desktop, select New > Shortcut, and enter the target:
:: Launch Overwatch 2 directly (skips Battle.net home screen)
"C:\Program Files (x86)\Battle.net\Battle.net.exe" --game=Pro
:: Launch Diablo IV directly
"C:\Program Files (x86)\Battle.net\Battle.net.exe" --game=OSI
:: Launch World of Warcraft directly
"C:\Program Files (x86)\Battle.net\Battle.net.exe" --game=WoW
:: Launch Hearthstone directly
"C:\Program Files (x86)\Battle.net\Battle.net.exe" --game=WTCGBattle.net still authenticates and runs in the background – this flag skips the visual home screen, not the login step. If you are already logged in with a trusted device session, the game launches in 2–4 seconds without any launcher interaction required.
Reduce Background Resource Usage
Battle.net’s background processes – particularly the news feed renderer and social activity polling – can consume 5–10% CPU on budget CPUs and 300–500 MB of RAM while idle. To reduce this impact:
- Under Settings > App Settings, disable Open Battle.net when I start my computer. Launch the app manually before gaming sessions only.
- Under Settings > Notifications, disable notification categories you do not actively monitor. Each enabled notification type registers a background polling listener.
- In Windows Task Scheduler, locate any Battle.net-related tasks and set their trigger to On demand rather than At startup to prevent background agent initialization on boot.
Automate Monthly Cache Cleanup
If you run Battle.net daily, the cache folder can accumulate several gigabytes of stale manifests over months. Automate cleanup with this PowerShell script, saved as CleanBattlenet.ps1 and added to Windows Task Scheduler with a monthly trigger:
# CleanBattlenet.ps1 – Safe monthly Battle.net cache cleanup
# Schedule this in Task Scheduler: monthly, with Run as Administrator
$cachePath = "C:\ProgramData\Battle.net\Cache"
$logPath = "C:\Logs\BattlenetClean.log"
# Abort if launcher is still running
$running = Get-Process -Name "Battle.net","Agent" -ErrorAction SilentlyContinue
if ($running) {
Write-Host "ERROR: Battle.net is still running. Close it before running this script." -ForegroundColor Red
exit 1
}
# Measure cache size, delete, log result
if (Test-Path $cachePath) {
$sizeMB = (Get-ChildItem $cachePath -Recurse -ErrorAction SilentlyContinue |
Measure-Object Length -Sum).Sum / 1MB
Remove-Item "$cachePath\*" -Recurse -Force -ErrorAction SilentlyContinue
$entry = "{0} – Removed {1:N1} MB from Battle.net cache" -f (Get-Date -Format 'yyyy-MM-dd HH:mm'), $sizeMB
New-Item -ItemType Directory -Path (Split-Path $logPath) -Force | Out-Null
Add-Content -Path $logPath -Value $entry
Write-Host $entry -ForegroundColor Green
} else {
Write-Host "Cache path not found. Battle.net may not be installed." -ForegroundColor Yellow
}Run this with powershell.exe -ExecutionPolicy Bypass -File CleanBattlenet.ps1 in the Task Scheduler action to bypass execution policy restrictions on managed machines.
Battle.net vs Competing Launchers in 2026
Battle.net is a first-party, deliberately narrow launcher – every title in its library is either Blizzard-developed or published by a Microsoft-owned studio. This is its key trade-off versus broader platforms. Steam controls approximately 74% of PC gaming transactions by market share; the Xbox App (Microsoft Store) offers Game Pass access; the Epic Games Launcher provides free games weekly across a large third-party catalog. Battle.net cannot match any of those on library breadth.
What Battle.net does better than most competitors is depth of integration within its own ecosystem: persistent cross-game messaging, TOTP Authenticator, built-in voice chat, and streaming game installs – features that launchers serving hundreds of publishers struggle to implement uniformly. For players whose library is primarily Blizzard and Activision titles, this integration justifies keeping Battle.net as a dedicated client rather than routing through a universal aggregator like GOG Galaxy or Playnite.
| Feature | Battle.net 2.51.6 | EA App | Rockstar Launcher | Epic Games Launcher |
|---|---|---|---|---|
| Cross-game messaging | Yes – all titles | Yes – EA titles only | No | No |
| Built-in TOTP 2FA | Yes (Authenticator) | Yes | No | Yes |
| Built-in voice chat | Yes | No | No | No |
| Streaming game install | Yes (select titles) | Yes (select EA titles) | No | No |
| Mobile companion app | Yes (iOS & Android) | Yes | No | No |
| Third-party game catalog | Limited (Xbox/Bethesda) | EA titles only | Rockstar titles only | Large third-party catalog |
| Auto-update background | Yes (Agent.exe) | Yes | Yes | Yes |
Frequently Asked Questions About Battle.net Setup
Is the Battle.net launcher free?
Yes, the Battle.net launcher and account are completely free. Three games on the platform – Overwatch 2, Hearthstone, and Warcraft Rumble – are free-to-play with optional in-game purchases. Diablo IV, World of Warcraft, Call of Duty titles, Avowed, and Doom: The Dark Ages require a separate purchase.
Does Battle.net work on Windows 11?
Yes. Version 2.51.6.17477 is fully compatible with Windows 11 22H2 and 24H2. The most common Windows 11-specific issue is a black screen in the launcher UI caused by GPU driver incompatibility with hardware acceleration – resolved by disabling that option in Settings > Advanced and updating your GPU drivers.
Can I install Battle.net on multiple PCs?
Yes. A Blizzard account is not locked to a single device. You can install Battle.net on as many machines as you own and log in with the same credentials. Games must be downloaded separately on each PC – there is no transfer mechanism. Only one active game session is permitted per account at a time; a simultaneous login on a second device will not boot the first device from the launcher, but launching a game while it is already running on another machine will generate an authentication conflict in the game itself.
What ports does Battle.net require?
The launcher uses TCP port 1119 for login and authentication, and TCP/UDP port 3724 for live game connections. Individual games require additional ports: Overwatch 2 uses UDP 3478–3479 and 5060; World of Warcraft uses TCP 6112–6114 for older features. If you are behind a strict firewall or a corporate network, whitelisting TCP 1119 and UDP/TCP 3724 covers the baseline launcher connectivity requirement.
Why does Agent.exe run in the background constantly?
Agent.exe (located at C:\ProgramData\Battle.net\Agent\Agent.exe, version 2.34.1.8636) is Battle.net’s update agent. It handles background downloading of game patches even when the launcher UI is closed, and it validates game file integrity after updates. It is a legitimate Blizzard process. Elevated CPU usage from Agent.exe typically means an integrity check or patch download is in progress – it returns to near-zero CPU within 15–30 minutes on its own.
How do I uninstall Battle.net without losing my game data?
Use Windows Settings > Apps > Installed Apps and uninstall “Battle.net”. This removes the launcher and its cache but leaves all game installations intact in their original folders. After reinstalling Battle.net from the official download page and logging in, use the in-launcher Install button for each game and point it to the existing folder – the launcher will run a validation pass rather than re-downloading everything.
Is Battle.net available on Mac?
Yes. The macOS client is available at the same official download URL. However, Mac game availability is more limited: World of Warcraft and Hearthstone have native Mac clients; Diablo IV, Overwatch 2, Call of Duty, and the newer Xbox/Bethesda titles do not have macOS versions as of June 2026. Mac players who want to run those titles need Windows via Boot Camp – cloud gaming clients like Xbox Cloud Gaming offer a browser-based workaround without a Windows installation.
How do I check what version of Battle.net I have?
Click the Battle.net logo (top-left corner), select Settings, and look at the bottom-left of the panel. The version displays as two numbers: the launcher version and the Update Agent version. As of June 18, 2026, the current versions are 2.51.6.17477 (launcher) and 2.34.1.8636 (Update Agent). If your version is older than these numbers, the auto-update mechanism has likely stalled – use the manual update steps in Step 12 above to force a refresh.
Related Coverage
- EA App vs Ubisoft Connect vs Battle.net 2026: Which Wins? – head-to-head comparison of all three first-party launchers on speed, library size, and features
- Epic Games Launcher Rebuilt: $400M Spend, 78M Users [2026] – inside Epic’s multi-year launcher overhaul and what it means for game delivery performance
- Rockstar Games Launcher 2026: 18.3M Players, GTA 6 PC Signals – how Rockstar’s proprietary launcher is being positioned ahead of GTA 6’s eventual PC release
- GOG Galaxy vs Playnite 2026: 44 Plugins vs 20 [Tested] – the two best tools for aggregating your entire library – including Battle.net – into a single unified interface
- Steam vs Microsoft Store 2026: 74% Market Share vs $13.99 Game Pass [Tested] – the dominant alternative platforms for games not covered by Battle.net’s focused library
- Gaming Platforms 2026 – our cluster hub covering all major platforms, stores, and launchers
