Battle.Net is the game launcher for Blizzard and Activision games.
Battle.Net won't work correctly if it was installed on an NTFS partition. Please choose an Ext4 drive as destination instead.
Wine dependencies are required for Overwatch to work. Please follow the instructions on Wine Dependencies page to get them.
Battle.net requires up-to-date, Vulkan capable graphics drivers.
For instructions on how to install them, refer to How to: Installing Drivers.
Otherwise, Battle.Net may not work.
If you are on an AMD GPU with Mesa/RADV drivers (most common on Arch, Fedora, Pop!_OS, and Ubuntu-based distros), use the AMD (Wine Staging) installer variant when installing Battle.net through Lutris. This installer:
- Pins a known-working Wine Staging build (vanilla Wine and GE-Proton have known issues with the Battle.net login flow on AMD/Mesa systems)
- Disables the
locationapiDLL, which causes a crash on the login screen under Mesa - Sets the DXVA2 backend to VA-API for AMD hardware video decode
- Disables hardware acceleration in the Battle.net client (required to avoid a blank login screen)
- Configures the DXVK shader cache and Wine Staging shared memory flags
The installer YAML and full configuration details are available at: https://github.com/ghostrunner42/battlenet-lutris-amd
If the AMD installer variant is not yet available in Lutris, you can apply these settings manually after installation — see the troubleshooting section below.
Bugs, misconfigured systems and missing dependencies can sometimes cause issues with Battle.Net:
Make sure your hostname resolves to 127.0.0.1. Edit /etc/hosts with sudo nano /etc/hosts and the first line should be something like 127.0.0.1 localhost myhostname.localdomain myhostname where myhostname is replaced by your actual hostname. You can get your hostname by launching the hostname command. Do not touch the rest of the file and be careful with mistakes and typos as they can cause serious issues with your system.
Usually it's caused by missing wine dependencies, but sometimes it's a result of an unknown bug in KDE. There are no known workarounds to this, so the only solution is to use another DE.
If you are behind a proxy, or behind a DNS Filter like PiHole, and your installation stalls with an "Object moved" error, whitelist *.blizzard.com and *.battle.net to allow agent installation. There is built-in telemetry that can cause the installation to fail, even with all the correct system dependecies.
This is caused by broken or missing installation of 32-bit nvidia-utils (or mesa).
It's a very common problem among users who attemped to install Nvidia driver using .run file. To fix it, it's suggested to completely reinstall your system and get drivers from repositories instead.
Same issue as the previous one, caused by missing 32 bit nvidia-utils (or mesa).
Also may be caused by not rebooting after installing drivers.
If the message appears when DXVK is in use, and it works with DXVK disabled, make sure you installed Vulkan correctly, including 32 bit packages.
If the issue persists, try removing Lutris's DXVK catalog in .local/share/lutris/runtime/dxvk (.local is a hidden folder inside your Home directory).
Go to Battle.Net options and disable hardware acceleration.
You might also have success if you try deleting the app's cache directory, which will be in the wine prefix's drive_c/ProgramData/ directory.
AMD/Mesa users: If disabling hardware acceleration alone does not resolve the issue, add a Wine DLL override for locationapi and set it to disabled. This is a known cause of the login screen failing to render under Mesa. To apply it:
- In Lutris, right-click Battle.net → Configure → Runner Options
- Under DLL Overrides, add
locationapiwith valued(disabled) - Restart Battle.net
Alternatively, set it via the terminal:
env WINEPREFIX=/path/to/your/battlenet/prefix wine reg add "HKCU\Software\Wine\DllOverrides" /v locationapi /t REG_SZ /d "" /fGo to options for Battle.Net — disable streaming.
Click to view screenshots
Greyed out install button:
Blizzard Agent went to sleep:
Here is what you can try:
- Use wine version 3.20 or newer. Wine Staging is recommended — vanilla Wine has known compatibility issues with the Battle.net login flow, particularly on AMD/Mesa systems.
- Close Battle.Net fully and wait a bit until all its processes exit. But just in case, terminate Battle.Net, Agent.exe and wineserver with:
killall Agent.exe Battle.net.exe wineserver
Then, inside the prefix Battle.Net is installed in, find drive_c/ProgramData folder and delete Battle.net. Open Battle.Net again and wait a little bit, the error should disappear.
To restore your existing game installations after this, simply open Settings>Game Install/Update and click "Scan for Games".
If you're using an AMD GPU, try setting radeon_icd.x86_64.json in Lutris System preferences -> System options -> Vulkan ICD loader. Make sure to tick "Show advanced options".
Try to change executable from Battle.net Launcher.exe to Battle.net.exe, and try again.
This can be caused by bad fonts (for example, all-repository-fonts from AUR). Try removing them.
It can also be caused by missing 32-bit Vulkan loader. Refer to How-To:-DXVK for instructions.
See: https://us.battle.net/support/en/article/32248
When you install the nvidia-driver package, it might not necessarily install the 32-bit libraries, which is a problem because Battle.net is a 32-bit app. Check your distribution's documentation for the correct packages.