Call Of Duty Won't Launch BattleNet

When Call of Duty won’t start from the Battle.net app, work through security checks, file repair, cache cleanup, and conflict removal.

Stuck on “Launching,” a brief splash, or nothing at all? This guide gets straight to the fixes that actually move the needle. You’ll start with the fastest checks, then work toward deeper cures. No fluff—just the steps that solve the most common PC launch blocks.

Fast Fix Checklist

Run through these quick hitters before the deeper work. They solve a big share of launch failures.

Symptom	Quick Action	Where/How
Nothing happens on Play	Restart Battle.net and end leftover processes	Exit app, open Task Manager, end any Blizzard/Agent entries
Stuck on “Launching”	Run Scan and Repair for the game	Game page → cog icon → Scan and Repair
Launches once, then fails	Clear Battle.net cache	Close app → delete cache folder → relaunch
Instant crash or silent close	Disable overlays and close background apps	Turn off Discord/GeForce/Afterburner/RTSS overlays
Anti-cheat or integrity prompt	Enable TPM 2.0 and Secure Boot in UEFI	PC firmware settings (see guide below)
Recent patch, old driver	Clean install your GPU driver	Download driver, use “clean” option or DDU in Safe Mode
Missing runtimes	Install latest Visual C++ redistributables	Microsoft downloads, then reboot

Why Call Of Duty Fails To Launch On Battle.net

There isn’t one cause. Launch blocks usually trace back to file corruption, cached app data, overlay conflicts, GPU driver residue, or new security checks that your system hasn’t met yet. Treat it like a funnel: quick checks first, then the items that take a few minutes, then the surgical options.

Step 1: Confirm The New PC Security Requirement

Recent entries in the series add stronger machine integrity checks on PC. If your firmware has TPM 2.0 or Secure Boot off, the game can stall at launch. Enable both in UEFI, then try again. Activision’s page explains the requirement and what to enable—see TPM 2.0 and Secure Boot.

How To Verify In Windows

Press Win + R, type msinfo32, press Enter.
Look for “Secure Boot State.” It should say On.
Open Windows Security → Device Security → Security processor for TPM details.

How To Enable In UEFI

Reboot and enter firmware setup. Turn on UEFI mode, enable TPM 2.0 (name varies: fTPM/PTT), then enable Secure Boot. Save and reboot. If your drive is MBR, convert to GPT before switching to pure UEFI. Back up files first.

Step 2: Repair Game Files Inside Battle.net

Bad or missing files are a classic reason for a dead launch button. Use the Repair tool in the app. It checks your install against the server copy and replaces broken files.

Open the game page in the desktop app.
Click the cog next to Play → Scan and Repair → Begin Scan.
Let it complete, then launch again.

If the tool finds nothing but the app still won’t start, keep going. You’ll clear stale data next.

Step 3: Clear The Battle.net Cache

Cached launcher files can go stale after patches, driver swaps, or network hiccups. Wiping the cache forces the app to rebuild fresh data. Blizzard’s instructions live here: delete the Battle.net cache.

Windows Cache Reset (Condensed)

Close the app, then open Task Manager and end any “Agent” or “Blizzard” processes.
Press Win + R, paste %ProgramData%, press Enter.
Delete the Battle.net folder, then restart the app.

Step 4: Kill Overlays And Conflicting Apps

Overlay hooks can block a clean start. Close Discord overlay, GeForce Experience overlay, Steam overlay (if present), MSI Afterburner/RTSS, Radeon overlay, and third-party recorders. Exit RGB software and streaming tools for one trial run. If launch succeeds, add them back one by one.

Clean Startup Test

Press Win + R → type msconfig.
On the Services tab, tick “Hide all Microsoft services,” then click “Disable all.”
Open Task Manager → Startup → disable non-Microsoft items.
Reboot and try the app. If it launches, re-enable items in small batches.

Step 5: Refresh Your GPU Driver The Right Way

Driver residue or a half-failed update can break a launch handshake. A clean install helps more than a simple update.

NVIDIA

Download the current Game Ready Driver.
Run the installer with the “clean” option, or use DDU in Safe Mode for a full reset.

AMD

Download the latest Adrenalin package.
Use the built-in “Factory Reset” option, then reinstall.

After a driver refresh, reboot once before testing the game.

Step 6: Install Fresh Runtime Packages

Missing Visual C++ runtimes can prevent a launch without a clear error. Grab the latest x64 and x86 redistributables from Microsoft, install both, then reboot. Many players see an instant win here.

Step 7: Fix Battle.net App Glitches

When the launcher itself acts up—multiple Agent processes, stuck “Starting,” or silent closes—treat the app first, then the game.

Rebuild The App

Uninstall the desktop app from Windows.
Delete the remaining Battle.net folders in %ProgramData%, %AppData%, and %LocalAppData%.
Reinstall the desktop app only, then try the game.

Re-register The Game

If the app rebuild doesn’t help, rename the game folder, click Install on the game page, then point the app to the existing files. This forces a quick scan and relink without a full redownload.

Solve Common PC Causes

Launch failures often tie back to system items that games depend on. Work through this cluster if you’re still stuck.

Windows Updates

Install pending cumulative updates and .NET updates.
Reboot, then test again.

Disk And System File Health

Open an elevated Command Prompt.
Run sfc /scannow then DISM /Online /Cleanup-Image /RestoreHealth.
Reboot after both complete.

Storage And Path Issues

Keep at least 15–20 GB free on the install drive.
Avoid nested install paths with special characters.
Install the game and the desktop app on the same drive for one test.

Fix Network And Login Friction

Occasional stalls come from connection hooks rather than files.

Disable VPN and custom DNS for one trial.
Turn off metered connection and set the app to stay online.
Flush DNS: open Command Prompt as admin → ipconfig /flushdns.
Power-cycle modem/router; test a wired link if possible.

When The App Opens But The Game Window Never Appears

This pattern often points to an overlay, a stuck background process, or a GPU driver path issue. Try a bare-minimum startup, then a driver clean install. If you get a brief black flash, add the game EXE to your GPU control panel with default settings, then relaunch.

Error Hints And What They Usually Mean

Some codes vary, yet the patterns repeat. Use this table to jump straight to the right fix path.

What You See	Likely Cause	Best First Move
Silent close on Play	Cache or file integrity	Clear app cache → Scan and Repair
Anti-cheat/integrity notice	TPM/Secure Boot off	Enable TPM 2.0 + Secure Boot
Black flash then nothing	Overlay or driver residue	Disable overlays → clean driver install
“Starting” loop	Stuck Agent process	End tasks → cache reset → relaunch
Random launch success	Race between startup apps	Clean boot test, add back in batches
After patch won’t start	Mixed versions or bad delta	Scan and Repair → rename folder relink

Clean Reinstall Without The Redownload Pain

A full reinstall is a last resort, yet you can spare your bandwidth.

Rename the game folder to something like _COD_backup.
Uninstall the game from the app.
Click Install, then when asked for an install path, choose the renamed folder. The app will verify and keep most files.

Pair this with a fresh desktop app install if the launcher keeps misbehaving.

Make The Fixes Stick

Once you’re back in, lock in a stable setup so the problem stays gone.

Leave TPM 2.0 and Secure Boot on.
Keep GPU drivers current, but prefer clean installs over layered updates.
Avoid stacking overlays. Use just one screen overlay at a time.
Run the app as administrator if you use tight folder permissions.
Give the app and the game folder full read/write access in your security suite.

When You Still Can’t Launch

You’ve cleared the common blockers. Two paths remain that solve tricky, low-frequency cases.

New Windows Profile

Create a fresh local admin account, install only the desktop app, and try the game. If it works there, the original profile carries a policy, shell extension, or startup item that blocks the launch.

Event Viewer Clues

Open Event Viewer → Windows Logs → Application.
Launch the game and watch for a new Error entry.
Look for faulting module names like a third-party overlay DLL or a codec pack.

Two References Worth Saving

Keep these handy while you work through the steps:

TPM 2.0 and Secure Boot — why this matters and what to enable.
Delete the Battle.net cache — the quick cache reset that fixes many launch stalls.

Quick Win Paths By Scenario

Fresh PC, First Install

Turn on TPM 2.0 and Secure Boot in UEFI.
Install Visual C++ runtimes, then the desktop app.
Install GPU driver, reboot, install the game, and launch.

Old Install That Used To Work

Run Scan and Repair.
Clear the app cache.
Disable overlays and relaunch.

After A Driver Swap Or Major Patch

Clean install GPU driver.
Scan and Repair, then try a rename-and-relink if needed.

Final Checkpoint

After each change, test a launch once. If it works, stop there and play. If not, move to the next step in order: integrity repair, cache reset, overlay cleanup, driver refresh, runtime install, launcher rebuild, and firmware security checks. One of these fixes almost every stuck launch on PC.