Ever since steam allowed to add non steam games to it that it become my gaming hub having all my games there ready to be launched.

There’s many ways to add blizzard games to steam, but I’ve made bnetlauncher to be the simplest method while retaining the benefits of automatic login.

Howto Use

  1. Extract the included exe to any location you want (ex: steam folder)
  2. Add the exe to steam as a non-steam game shortcut
  3. On the shortcut properties open Set Launch Options… and add one of the following codes:
wowWorld of Warcraft
wowclassicWorld of Warcraft Classic
wowptrWorld of Warcraft Public Test Realm
d3Diablo 3
d3ptrDiablo 3 Public Test Realm
owptrOverwatch Public Test Realm
sc2Starcraft 2
hotsHeroes of the Storm
scrStarcraft Remastered
w3Warcraft 3: Reforged
codbo4Call of Duty: Black Ops 4
codmw2019Call of Duty: Modern Warfare (2019)
codmw2crmCall of Duty: Modern Warfare 2 Campaign Remastered
codbocwCall of Duty: Back Ops Cold War

The result should look something like this:

Additionally, can also use Change Icon to use the icon of the game you’re adding. If you’re still unsure how it should work you can watch a video bellow of bnetlauncher in action:

Destiny 2

Note: Destiny 2 has moved to steam on the 1st of October.


In case of problems logging can be enabled by creating a enablelog.txt file inside %localappdata%\\bnetlauncher\, you can open the location by pasting the path into explorer or the run dialog in windows (WinKey+R)

Known Issues

  • Launching WoW Classic and PTR version of game depends on the client gaining focus for bnetlauncher to send a keypress to it so it will launch the game. Not letting the client gain focus will break the functionality.
  • Slow computers might take too long causing to bnetlauncher to think something went wrong, see additional options on how to use –timeout to fix it.
  • Enabling multiple instances of client in it’s options might break bnetlauncher functionality.
  • Users of MSI Afterburner, Fraps and other overlay software might experience crashes do to incompatibility with their own overlay and steam’s, to solve the issue disable the 3rd party application overlay.
  • The game, bnetlauncher and steam must all have the same running permissions to work properly, this means if one of them is running has Administrator/Elevated Permissions, then all of them must also be run has Administrator/Elevated Permissions.
  • It’s not possible to automatically launch games with a specific region set. The client provides no direct option to do this, however a workaround can be done by creating a new game entry and the nolaunch option and manually selecting the region before clicking play.
  • client “ads” will interfere with the PTR and WoW Classic wow launch, when it happens user will need to press the play button manually to continue the game launch.
  • Default launching the client trough a scheduled task may be incompatible with some setups, workaround is provided with --notask switch/option.
  • Starting multiple copies of Startcraft Remastered may cause bnetlauncher to show an error since the game only allows one instance to be run at the same time.
  • There’s no built in routine to clean up the log files if they pile up (logging is disabled by default)

Aditional options

There’s also the following additional options provided by command line switches:

  • --timeout <seconds>, -t <seconds> changes how many seconds it tries to look for the game before giving an error (15 seconds by default).
  • --notask, -n starts the launcher directly instead of trying to use a scheduled task
  • --leaveopen, -l leaves the client open after launcher the game. If combined with --notask option it will show you as playing on steam until you close the client.


To remove all traces of bnetlauncher from your system:

  • type ‘Task Scheduler’ in start menu and open it, expand library and delete bnetlauncher folder to remove the tasks used to start the client
  • type %localappdata%\ in start menu and open the folder, delete bnetlauncher folder to remove log and gamedb.ini files


Special Thanks

internet coder Maruf for ghost tray icon fix code github Ethan-BB for the new parameters to launch games on
github RobFreiburger and iMintty for Starcraft Remastered and Destiny 2 support respectively.
/u/fivetwofoureight for creating and allowing me to use his icon. /u/malecden, Maverick, /u/sumphatguy and others for their help pointing out bugs.

github repo (Source Code, Issue Tracking, Complete
Other versions

214 thoughts on “bnetlauncher”

  1. hello
    after last modern warfare update, overlay launch only on battlenet
    it seems they disabled 3rd party programs
    is there a way to force it with args on launch ?

      1. too bad
        is nvidia ansel using overlay ?
        because it popup(alt+f2) during cod mw launch
        if it’s overlay maybe we can figure out something

        1. bnetaluncher is just a helper tool to assist with launching games under steam. It does not mess with the overlay in anyway, doing so is beyond my current knowledge and could make bnetlauncher be detected as a hack by anti-cheat.

          You’re best chance is asking Infinity Ward or Valve to address the issue.

  2. thanks for the .exe,

    when i launch overwatch with ow the battle net launcher doesn’t close himself.

    1. By design bnetlauncher doesn’t exit if it’s already running. If you just mean the closing the client window, that’s an option you can set on the client itself in “settings \ general \ when I launch a game”

      1. that’s what is weird, i don’t have running and the option you say enabled. Also when launching warzone it close by itself but not with overwatch (i only play those two games so idk if other games has this same issue).

        1. The only other possibility I see is that you added –leaveopen or -l option to the overwatch shortcut which will leave the client running.

          1. didn’t even know those commands, i just follow the instructions for both titles.

          2. I can’t reproduce your issue, so I believe it’s something specific to your system that’s causing it, I wouldn’t know what though.

  3. somebodyfromthedistance

    Any way to fix steam overlay in latest version of Modern Warfare/warzone? After yesterday’s update,overlay doesn’t seem to be working anymore.. Help?

  4. Pingback: Bnetlauncher v2.06 –

  5. Steam dont show the Game i am playing, overlay works… codmw2019
    I tried it with the gamedb.ini, but dont work… it shows for a second and then its away

    1. did you try adding waitforexit on the options?


      name=Call of Duty: Modern Warfare

    2. hi there,
      same for me too.
      it works well with the exception of show me playing CoD:MW on steam
      I use version 206. tried “options=waitforexit” aswell but it just show for few seconds that im playing. any other ideas?

      1. Only thing i can think of is that there’s some intermediary launcher which might be making bnetlauncher think the game exited earlier.

        I don’t currently have access to Modern Warfare so i’m unable to try and find out what’s happening.

          1. I appreciate the offer but account sharing is against Blizzard ToS and I wouldn’t want to put anyone’s account at risk.

  6. Where would I input the additional options at? I’d like to input notask and leaveopen

  7. I am running into a small issue with COD:MW. I have set it up, 𝘁𝗵𝗲 𝗼𝘃𝗲𝗿𝗹𝗮𝘆 𝘄𝗼𝗿𝗸𝘀 𝗳𝗶𝗻𝗲 𝗶𝗻-𝗴𝗮𝗺𝗲, however the game’s title isn’t displayed on steam. When the game launches it shows the title for a split second before it goes away again.

    Thanks for your work, I use this tool for other bnet games and I love it!

    1. If you mean it stops showing you as playing then it’s because by default bnetlauncher exits after it’s down.

      You can tell bnetlauncher to wait until the game exits by adding the waitforexit option on a custom gamedb.ini

      So cod would look like this:

      name=Call of Duty: Modern Warfare

  8. Pretty sure im being dumb, trying to add modernwarfare. made a custom gamedb.ini, put it into %localappdata%\\bnetlauncher put codmw into launch options. error comes up with cant find ID

      1. Sweet that works loading it up. though same issue with bo4 beta last year. where after a few seconds all controller inputs stop apart from the steam button for BP overlay.

        tis a strange one

  9. Axios_Moirai

    I must be missing something, I cant add custom settings to WOW. Im trying to add the nolaunch option, but it keeps launching automatically.

  10. With the launch of WoW Classic upcoming do you know if theres a string we can pass in the .ini file to trigger wow to open separately between ‘retail’ and ‘classic’?

    1. As far as I know there’s no direct way to launch an option from a game. Best you can do is use the nolaunch option and manually change to classic 🙁

  11. I want to ask about steam overlay’s overlapping in Call of Duty: Black Ops 4. When I chatting using overlay, game recognizes the key’s commands, because of it happens missclicks. For example, when I use numbers (0-9) in overlay’s chat, my character use equipment or weapons. Even happened that while I chatted, the pressed keys were recognized as “Exit the game”.
    It very much disturbs. Is there a way to fix it?

      1. Thanks for previous answear.
        I checked various forums, including Steam Client Beta forums. I’m not only who have that problem. not but unfortunally no one can’t answear what to do in that situation. Therefore I don’t see sense to create the same topic which nobody will answer.

        Links with that problem from players:

  12. windows 10
    without parameter –leaveopen (i add just hs) – client is still opened

    1. The leaveopen option is to leave the client running after launching the game. client is needed to start the games so it always starts.

  13. Your Bnetlauncher is so usefull.
    All my friends are on steam, And I can finally use steam chat overlay in Sc2 and overwatch.

    I see on version 2 you can add more games.
    I hope you will support different client in the futur 🙂

  14. Pingback: How To Play Destiny 2 with Steam Input – Game News City

  15. World of Warcraft crashes on Startup with this LOG:

    This application has encountered a critical error:

    ERROR #132 (0x85100084) Fatal exception!

    Program: D:\World of Warcraft\_retail_\Wow.exe
    ProcessID: 1784

    The instruction at “0x00007ffa06834ee7” referenced memory at “0x0000000000000fa0”.
    The memory could not be “read”.

    Press OK to terminate the application.

    best regards

    1. Never experienced crashing caused by bnetlauncher, so right now i’m unable to reproduce the issue. Check if you don’t have other overlay software that may cause instability when interacting with steam overlay or even aggressive antivirus software.

    2. OK, the bnetlauncher won’t work if DirectX12 is enabled in Wow.

      If i switch to DirectX 11, the bnetlauncher works fine.

      Steam doesn’t support DirectX 12 apps.

      best regards

      1. Daniel Marian Cirjeu


Leave a Reply

Your email address will not be published.