How to launch Overwatch without the extra wait

The extra wait before Overwatch is rarely the game itself. It is one of five pauses, and they do not share a fix. Battle.net can be starting from closed. It can be sitting on a countdown after you press Play. It can be asking you to log in again. It can be downloading a patch. Or the game can already be open while the first minutes hitch, because shaders are compiling.

I play Zarya at Master in Overwatch. For the fight itself, see the Zarya guide, and for sensitivity, head to /tools.

On PC you can launch from the Battle.net desktop app, and Steam since 10 August 2023. Blizzard’s announcement that day says a Steam copy still has to be connected to a Battle.net account. A program that promises to skip both is not a faster launcher.

Start with the delay you notice most.

Pick the wait you actually see. The fix is different for each one.

Before PlayAfter PlayLogin every timeFirst minutes hitch

This is Battle.net starting from closed. Leave it open and logged in if you play often, or let it start with Windows. Exiting it completely last time is why this open is slow.

The names below match the official Battle.net desktop app: open Settings from the Battle.net icon, then App. That’s where you’ll find Startup, On game launch, and the countdown checkbox. Blizzard’s startup article covers that path for the Windows checkbox.

Where to launch from

Blizzard’s How to Install Overwatch article is the install path I will stick to. Download the Battle.net desktop app from download.battle.net. Sign in. Click the Overwatch icon. If the icon is missing, open All Games and pick it from the list. Click Install. When the files are there, click Play.

That is the whole official launch. Play is the button. I queue from that button.

Steam works too, but it doesn’t replace the Battle.net account. Blizzard’s 10 August 2023 post says Overwatch on Steam is in addition to Battle.net, and that Steam players still need to connect the game to a Battle.net account, as Blizzard requires on every platform. Error linking Battle.net and Steam is the support page if that link fails: launch from Steam, and when the game says a Battle.net account is required, use the Open Browser button and finish the connection.

Steam can be the better door if what you want is Play inside a library you already use. It does not delete patches. It does not stop the first shader compile. It does not remove the Battle.net account.

That regional change is not a reason for anyone else to download a third client. I use Battle.net.

The wait before Play

This is the long one people blame on Overwatch. You click the icon, the launcher window appears, it checks for its own update, then it shows the library, and only then can you press Play. Most of that time is Battle.net opening from a full close, not the game loading.

If you play often, leave Battle.net running. Signed in, sitting in the tray, the next session starts at Play. You can also let it start with Windows. Blizzard’s support article Battle.net Always Launches With PC Startup documents the checkbox: Settings, App, Startup, Launch Battle.net when I start my computer. Check it if you actually play most days. Uncheck it if a launcher you never open, starting with the computer, is the opposite of a shorter wait.

The official app also has a line for launching minimized to the system tray. That is the same Startup block. Use it when you want the app present and signed in without a window in the way. The official checkbox is the setting.

Exit Battle.net completely is a real On game launch choice, and it is easy to misuse. It closes the launcher when the game starts, so the app is not sitting in memory during a match. The next time you want to play, you pay the cold start again. Turn that on if the launcher is getting in the way while you play. Leave the app open if the thing you hate is the wait before Play.

If the window opens on Home news instead of Overwatch, Blizzard’s default page article documents the other official switch: Settings, App, On startup, view, then Last Viewed Game Page. That is not Play. It is one fewer tab.

The wait after Play

After you press Play, Battle.net can hold the screen for a short countdown before it closes. The checkbox is under On game launch, beneath Exit Battle.net completely: Show a brief countdown instead of closing immediately. Uncheck it. The pause is the launcher waiting on purpose. It is not an update, and it is not the game.

There is a second, similar line for when you click the window’s close button. That one only matters when you close the launcher yourself. It does not change the countdown after Play. Set the launch line, then close settings with Done.

If you want the window back when the match ends, the other choice under On game launch is to minimize Battle.net to the tray and restore it when the game ends. That keeps the next Play one click away. It also means the launcher stays up while you play. Pick one. You cannot have a cold close during the match and an instant open afterward.

I leave the app signed in and skip the countdown.

The login that comes back

A saved login is the difference between pressing Play and typing a password plus an authenticator code. In the same official Startup settings, leave Remember emails and phone numbers and Keep me logged in on. When you are done for the day, use Exit. Log Out is the button that throws the session away.

Do not log out to “fix” a slow launcher. Sign in once, leave the session, and close the window.

Starting Overwatch.exe from the install folder is not an official launch step. Blizzard’s install article does not offer it. Players who try it report that the saved login does not come with them

Two-factor authentication is an official Battle.net feature, listed on the download page. It is not a wait you remove. It is the account.

If the login servers are full, that wait is also official. Blizzard’s login queue article says to stay in the queue, enter the password and authenticator correctly, and accept any terms promptly. Leaving and restarting the client loses your place. A shortcut does not jump the queue.

A shortcut opens the official app, not a patch

You can pin the official Battle.net app to the taskbar, or make a Windows shortcut to Battle.net.exe. That opens the official door. It does not press Play. It does not skip a download.

Community guides publish extra flags that claim to open a game tab, or even to start the game. Those flags are not in Blizzard’s install article. They are not an official launch step. Make a shortcut to the official app if you want fewer clicks to the library. Test it once. Either way you still wait for a patch that is not on the disk.

If Battle.net is not in Program Files (x86), the shortcut has to use the folder where you actually installed it. A target that points at a missing file does nothing, which feels like a longer wait than the normal button.

The official Play button is still the one on the Overwatch page, after the app is signed in and the files are current.

Do not install a skip tool

Search results for this problem include small programs that wrap the same Battle.net window and claim you never have to press Play. They are unnecessary. An executable from a random repository is a bad trade for one click. Windows sometimes blocks them for the same reason: an unknown installer whose job is to launch another program.

The official paths are the ones already named. Battle.net from download.battle.net. Or Steam, where Blizzard put the game on 10 August 2023, still tied to a Battle.net account. Neither path is a skip-the-launcher download. Any tool that promises to skip Battle.net entirely is a common way accounts get stolen.

Skip tools, GitHub wrappers, and “faster launchers” aren’t official. Stick to Battle.net or Steam.

When the launcher is actually working

A patch is not a bug in your shortcut. Battle.net updates itself, then the game, and it can sit on a scan while it checks files. A fresh install or a new season patch needs that time. Let it finish. Closing it halfway and opening a shortcut does not make the files appear faster.

Blizzard’s repair articles, including BLZBNTAGT00000BCA for bad patch data, say to run the repair tool, and to uninstall and reinstall the game if the repair does not finish the job. Uninstalling and reinstalling the Battle.net app is the line they keep for rare launcher issues. BLZBNTAGT00000843 adds the other official checks: allow Blizzard apps in security software, do not force the game to run as administrator, and on Windows make sure you are on a 64-bit OS. Overwatch does not support 32-bit.

If the bar never moves, close Battle.net fully, including the tray icon, and open it once more before you reinstall the whole game. Check that the drive holding the game has space. A full disk looks like a launcher that is stuck.

Scan and Repair is the official “stuck on a scan” next step. It is not a skip. It is how missing files come back.

The hitch after the game is open

Sometimes the launcher was fast and the first minutes of Overwatch are not. The frame rate stutters, then settles. That is usually shader compilation after a game patch or after a new graphics driver.

NVIDIA’s Auto Shader Compilation page explains it. Shaders have to be translated for the GPU. That compilation begins at game install. It has to be repeated after game patches or GPU driver updates. The first session after those changes can hitch while the work finishes. NVIDIA also says that after you download a game for the first time, you must still generate shaders in-game. Their idle compiler does not replace that first pass.

Play one unranked game, or stand in the practice range, until the hitches stop. Then queue. Clearing a cache you guessed at throws away work the last session just did, so the next open compiles them again.

How to update a GPU driver is the change that most often starts this wait. I update through the NVIDIA App. A newer file is not a higher frame rate. If the frame rate is still low after the first game, the launch is no longer the problem. How to increase FPS is the next page. Roles is the other Overwatch page if the wait was never the launcher.

NVIDIA’s Auto Shader Compilation beta, in the NVIDIA App under Graphics, Global Settings, Shader Cache, can rebuild DirectX 12 shaders after a driver update while the machine is idle. It needs a recent Game Ready driver. It is off by default. It does not remove the first in-game compile after you install the game.

What no official setting removes

A few waits are the game doing something you need:

• Signing the account. Battle.net, or Steam tied to a Battle.net account, is how the client knows who you are. An unofficial exe that asks you to log in every time did not remove that step.
• A patch that is not on the disk yet. No unofficial flag downloads the update in the background if the official launcher never ran.
• The first shader compile after a driver or a patch. NVIDIA’s page says it finishes by being generated in-game, not by a shortcut.
• A login queue. Blizzard’s queue article says to stay in it. Restarting loses your place.

If the pause you hate is still there after the matching official fix above, name which screen it is on. “Overwatch is slow to open” covers five different screens, and only one of them is fixed by the button you were about to change.

Use the official Battle.net or Steam door, fix the one pause you can see, and do not download a skip. More under Guides.

Common questions

Can I launch Overwatch without Battle.net?

No. Overwatch always starts through the Battle.net app or Steam, and even the Steam version needs a Battle.net account linked.

Can a desktop shortcut launch Overwatch directly?

Not really. A shortcut opens the Battle.net app, and you still click Play. Unofficial launch flags from community guides won't skip patches.

How do I turn off the Battle.net launch countdown?

In Battle.net, open Settings, go to App and find On game launch. Uncheck 'Show a brief countdown instead of closing immediately' to skip that pause.

Why does Overwatch stutter right after I launch it?

It's compiling shaders. This happens after installing, after a game patch and after a GPU driver update, so play one unranked game or spend a few minutes in the practice range first.

Is there a program that skips the Battle.net launcher?

No safe one. Only download Battle.net from download.battle.net or use the official Steam version; third-party launcher tools are a common way accounts get stolen.

How do I stay logged in to Battle.net?

In Battle.net, go to Settings, App, Startup and keep 'Keep me logged in' turned on. When you're done, use Exit instead of Log Out so your session stays saved.

Should Battle.net start with Windows?

Yes, if you play most days. Turn on 'Launch Battle.net when I start my computer' under Settings, App, Startup so it's ready and signed in when you want to play.

Is Overwatch faster to launch on Steam than Battle.net?

Not really. Steam is just another official way to start the game, and it still needs Battle.net, patches and shader compiles. Use whichever launcher you already have open.

Why is Battle.net stuck scanning or updating?

Let the patch finish first. If the progress bar never moves, run Scan and Repair on Overwatch, and only reinstall the Battle.net app if that doesn't help.