Wine 11 (to better run Windows applications)

App Center (deb) offers the ancient Wine 9.0 and the “official way” is nothing short of overwhelming, just look at this in the eyes of a Linux new comer:

Preparation

WineHQ uses the distribution name to add the repository. If you don’t know the name or are using a distribution derived from Debian or Ubuntu, it can be found using:

cat /etc/os-release

Look for the line with either UBUNTU_CODENAME or VERSION_CODENAME. If both are present, use the name after UBUNTU_CODENAME.

WineHQ repository

Download and add the repository key:

sudo mkdir -pm755 /etc/apt/keyrings
wget -O - https://dl.winehq.org/wine-builds/winehq.key | sudo gpg --dearmor -o /etc/apt/keyrings/winehq-archive.key -

Add the repository:

The WineHQ packages for Ubuntu 25.10 and Debian Testing (wine versions 10.18 and up) are WoW64. Therefore, the 32-bit packages are no longer necessary. The new WoW64 can run 32-bit programs from a 64-bit wineprefix, but it cannot use 32-bit wineprefixes. If you have any 32-bit wineprefixes from a previous installation, you will need to reinstall your 32-bit applications to a 64-bit wineprefix. Older versions of Ubuntu and Debian require the 32-bit architecture to be enabled.

If your distribution name is not on the list, older packages may be available on the download server.

Only add the repository that corresponds to your distribution.



Questing

Ubuntu 25.10

Add the sources file:

sudo wget -NP /etc/apt/sources.list.d/ https://dl.winehq.org/wine-builds/ubuntu/dists/questing/winehq-questing.sources

Plucky

Ubuntu 25.04

Enable the 32-bit repository:

sudo dpkg --add-architecture i386

Add the sources file:

sudo wget -NP /etc/apt/sources.list.d/ https://dl.winehq.org/wine-builds/ubuntu/dists/plucky/winehq-plucky.sources

Noble

Ubuntu 24.04 & Linux Mint 22

Enable the 32-bit repository:

sudo dpkg --add-architecture i386

Add the sources file:

sudo wget -NP /etc/apt/sources.list.d/ https://dl.winehq.org/wine-builds/ubuntu/dists/noble/winehq-noble.sources

Jammy

Ubuntu 22.04 & Linux Mint 21.x

Enable the 32-bit repository:

sudo dpkg --add-architecture i386

Add the sources file:

sudo wget -NP /etc/apt/sources.list.d/ https://dl.winehq.org/wine-builds/ubuntu/dists/jammy/winehq-jammy.sources

Forky

Debian Testing

Add the sources file:

sudo wget -NP /etc/apt/sources.list.d/ https://dl.winehq.org/wine-builds/debian/dists/forky/winehq-forky.sources

Trixie

Debian 13

Enable the 32-bit repository:

sudo dpkg --add-architecture i386

Add the sources file:

sudo wget -NP /etc/apt/sources.list.d/ https://dl.winehq.org/wine-builds/debian/dists/trixie/winehq-trixie.sources

Bookworm

Debian 12

Enable the 32-bit repository:

sudo dpkg --add-architecture i386

Add the sources file:

sudo wget -NP /etc/apt/sources.list.d/ https://dl.winehq.org/wine-builds/debian/dists/bookworm/winehq-bookworm.sources


Update

Update the package information:

sudo apt update

Install Wine

Install one of the following packages:

Wine branch Command
Stable branch
sudo apt install --install-recommends winehq-stable
Development branch
sudo apt install --install-recommends winehq-devel
Staging branch
sudo apt install --install-recommends winehq-staging

The User’s Guide explains the differences between the branches.


Help

Sometimes there are problems installing Wine. If your problem is not listed, search the forum or if you can’t find an answer ask your question.

Ubuntu 25.10/ Debian Testing

The WineHQ packages are WoW64. This means that the 32-bit packages are unnecessary. The new WoW64 wine-devel package is set to conflict with and replace wine-devel-i386 and wine-devel-amd64, which are no longer separate packages. Upgrading users should get a message about the replacement and asked if they want to continue. If updating an older Wine version does not work, uninstall the old packages first.

sudo apt remove winehq-devel wine-devel wine-devel-amd64 wine-devel-i386:i386

Missing dependencies

Read the FAQ about dependency errors and tips for troubleshooting dependency issues. The most common issues are:

Third-party repositories

WineHQ packages are created and tested on a clean installation. Using PPAs or third-party repositories may prevent the installation of Wine. Often the problem is that these repositories are not multiarch. The required 32 and 64-bit packages are missing or cannot be installed side by side. The deb.sury.org repository is known for causing problems.

Downgrade the problematic dependency packages to the official version.

KDE Neon

Ubuntu 22.04 KDE Neon users report problems with the libpoppler-glib8 dependency. The solution is to downgrade this package to the official Ubuntu version. sudo apt install libpoppler-glib8:{i386,amd64}=22.02.0-2ubuntu0.3

Backports

Another cause may be the use of backports. A newer 64-bit version of a library is already installed, but the 32-bit version isn’t. These packages are given a lower priority so they will not be installed automatically. The solution is to manually install the missing 32-bit package from backports.

FAudio

Older versions of Wine (prior to version 6.21) have FAudio as a dependency. These packages are missing on Ubuntu 18.04. These can be downloaded from the Open Build Service. For Debian 10, these packages are available in backports.

Winehq key problems

  • The WineHQ repository key was changed on 2018-12-19

    If you downloaded and added the key before that time, you will need to download and add the new key and run sudo apt update to accept the repository changes.

  • Apt-key is now deprecated

    Previously, apt-key was used to add the Wine key. If you get this warning, remove the Wine key with:

    sudo apt-key del "D43F 6401 4536 9C51 D786 DDEA 76F1 A20F F987 672F"
    

    And remove the the line about the WineHQ repository from /etc/apt/sources.list(.d/*).

Mirror sync in progress?

If you get an error message when trying to install a package from WineHQ that includes the line Mirror sync in progress? that is most likely the problem. There are many packages to sync, and it can take a long time to complete.

Wait a few hours, and try again. If the problem persists for more than a day, file a bug.

My Debian/Ubuntu version is not listed

When a Debian/Ubuntu version is no longer supported, no new Wine packages are built. And the repository will no longer appear in the list above. Since no new versions are built, it is not necessary to add the WineHQ repository. Just download and install the four WineHQ deb packages.

Please note that these packages are no longer maintained and are no longer supported.

Notes

  • Menu items are not created for Wine’s builtin programs (winecfg, etc.). If you upgrade the Wine distro packages that had added them, they will be removed. You can recreate them yourself using your menu editor.

  • The Wine files are installed in /opt/wine-<branch>/

  • WineHQ does not offer wine-gecko or wine-mono packages. When creating a new wineprefix, you will be asked if you want to download those components. For best compatibility, it is recommended to click Yes here. If the download doesn’t work for you, please follow the instructions on the Gecko and Mono wiki pages to install them manually.

  • Beginning with Wine 5.7, the WineHQ packages have an optional debconf setting to enable CAP_NET_RAW to allow applications that need to send and receive raw IP packets to do so. This is disabled by default because it carries a potential security risk, and the vast majority of applications do not need that capability. Users of applications that do need it can enable CAP_NET_RAW after installing Wine by running dpkg-reconfigure wine-<branch>-amd64 wine-<branch> wine-<branch>-i386 and answering yes to the three questions.

  • Binfmt_misc registration is not added. Consult your distro’s documentation for update-binfmts (man update-binfmts) if you wish to do this manually.

  • A complete Wine installation on a 64-bit system consists of four packages. The Debian Testing / Ubuntu 25.10 packages are WoW64. These distributions only have the winehq-<branch> and wine-<branch> packages.

    • winehq-<branch> This package ensures that the wine command is available system-wide.

    • wine-<branch> This package has the following two packages as dependencies and provides a working Wine installation.

    • wine-<branch>-amd64 The 64-bit part of Wine.

    • wine-<branch>-i386 The 32-bit part of Wine.

    By splitting a Wine over different packages, it is possible to install different branches side by side.

    For example: Use Wine stable as the default Wine version and install Wine staging to test other programs.

    Install Wine stable:

    sudo apt install --install-recommends winehq-stable

    Install Wine staging:

    sudo apt install --install-recommends wine-staging (Note the missing hq after wine)

    Run a program with Wine stable:

    wine program.exe

    Run a program with Wine staging:

    WINEPREFIX=~/wine-staging /opt/wine-staging/bin/wine program.exe

    (It is recommended to give each Wine branch its own wineprefix.)

  • There are several versions of Wine on the repository. The latest version is installed by default. Usually, the latest version is recommended. However, it may happen that an older version is desired. Use apt policy winehq-<branch> to list the different available versions.

    Install an older version of your choice with

    sudo apt install winehq-<branch>=<version>
    

    For example:

    sudo apt install winehq-staging=7.12~bookworm-1
    

    When the Wine packages are downgraded, all four Wine packages must be downgraded.

    sudo apt install winehq-staging=7.12~bookworm-1 wine-staging=7.12~bookworm-1 wine-staging-amd64=7.12~bookworm-1 wine-staging-i386=7.12~bookworm-1
    

Installing without Internet

To install Wine on a machine without internet access, you must have access to a second machine (or VM) with an internet connection to download the WineHQ .deb package and its dependencies.

On the machine with internet, add the WineHQ repository and run apt update as described above.

Next, cache just the packages necessary for installing Wine, without extracting them:

sudo apt-get clean
sudo apt-get --download-only install winehq-<branch>
sudo apt-get --download-only dist-upgrade

Copy all of the .deb files in /var/cache/apt/archives to a USB stick:

cp -R /var/cache/apt/archives/ /media/usb-drive/deb-pkgs/

Finally, on the machine without internet, install all of the packages from the flash drive:

cd /media/usb-drive/deb-pkgs sudo dpkg -i *.deb

Building from Source

  • Beginning with 4.0-rc2, the WineHQ repository includes the .dsc, .diff.gz, and .orig.tar.gz files generated by the Open Build Service(OBS). These source packages can be found on https://dl.winehq.org/wine-builds/<debian|ubuntu>/dists/<version>/main/source/<matching filename>

  • The latest version of Debian and Ubuntu are multiarch. It is possible to install all 64 and 32 bit dependencies side by side. This allows Wine to be built using the steps listed under Shared WoW64.

  • On older versions of Debian/Ubuntu the multiarch implementation could be incomplete. You can’t simply install 32-bit and 64-bit libraries alongside each other. If you’re on a 64-bit system, you’ll have to create an isolated environment for installing and building with 32-bit dependencies. See Building Wine for instructions on how to build in a chroot or container.

So now that Wine 11 is out and soon with all the Adobe installer goodies upstreamed, if we’d finally have a Snap package for Wine (with all the needed extras included such as dpkg --add-architecture i386) :crossed_fingers:

https://gitlab.winehq.org/wine/wine/-/releases/wine-11.0

Ps. If there is some fundamental problem that is the reason for a Wine Snap still not existing to this day, i bet many others also would love to know what’s the obstacle!

Creating a specific package for Wine shouldn’t be complicated, but Wine is generally used by launchers.

For example, Zordeer, which has a Snap version and access to Wine 11.

Could you test it to see if it works for you?

From what I’ve seen, the name “wine” isn’t available; I have no idea who owns that Snap.

I changed my Snap, called “wine-kyu,” so it can be used directly, instead of just serving as a content Snap.

If you want to test it:

I tested something here; if you use the command sudo snap alias wine-kyu wine, wine-kyu can be called using the wine command, so system apps can use wine-kyu as well.

However, I don’t recommend trying to use wine-kyu with Lutris. I tested it on version 0.5.19 and it’s causing some bugs when trying to create a prefix; Lutris deletes the folder I chose.

Oh my word, so there is a Wine snap but someone has taken the actual “Wine” space for hostage to be used as a name and for easier comprehension.

Was wondering, could you add this ```sudo snap connect wine-kyu:joystick && sudo snap connect wine-kyu:removable-media``` right inside the snap to install? I’m sure most people installing won’t just do it because of god awful terminal and -or don’t realize it should be done. Tinkering with Wine is still too extensive as is. Most users don’t want to touch “some darn terminal” nowadays.

I also think it’s very complex, and that’s precisely why launchers exist.

It doesn’t make much sense for novice users to download Wine directly.

I made this modification to wine-kyu to show that it’s possible, but as you already know, it doesn’t work so well in practice.

1 Like

To clarify, one of the reasons for this main request is the fact that the game which is attempted to install and run, played: Heroic Games Launcher (and Lutris) once again don’t work. Like at all almost. Regular upstream Wine then again launches the setup.exe and afterwards the main game exe right away and without any hiccup or tinkering from file manager. But that is not ideal. Game launched through a launcher would be. So as the Heroic was installed as deb and Wine as flatpak, started to think if that is the reason for dysfunction. And Heroic Games Launcher website recommends flatpak, but it is known to have permission issues and so on.

Heroic and Lutris do not include the upstream “normal” Wine and none of these GE and Lutris versions launch the game. If the common upstream Wine can be installed on Heroic and Lutris, i can’t fathom HOW and i’m a seasoned user.

Also: when you tinker enough on Heroic for example, the “Play” launcher button goes to grey for some reason and everything has to be deleted and start over (to attempt the changing of different GE-Wines and so on. None work so far but from filer manager the regular upstream Wine works off the bat.

Yes, we are definitely on the same page here. I want to say *thank you* at this point already.

This one now suddenly stopped from showing on Snap Store and also App Center, few moments ago searching with “wine” the Wine [Kyu] DID come up on search results but not anymore :confused: this is quite confusing.

I hid the wine-kyu from being used because of what we discussed here.

It’s more complicated to deal with Wine without a launcher, plus I would need to request automatic connection of plugs for wine-kyu as well.

The wine-kyu Snap was created to be just a content Snap for Zordeer, which is a launcher.

I’m confused, if i install this Wine Zordeer, is it also a regular Wine? Can i use it to right click on setup.exe and so on straight from file manager? Or is Zordeer a Heroic type launcher? (i haven’t tried this Zordeer yet).

Or do i now gotta install the Wine flatpak back now that the Wine [Kyu] is not available? I isntalled the Wine [Kyu] and it seemed to work but now that it’s gone, does Wine Zordeer kind of “take its place” or?

Zordeer is a launcher like Heroic, Lutris, Faugus, etc.

I’m specifically talking about this app:

1 Like

Ohh ok now its clear, i guess i’ll try it because Heroic and Lutris just didn’t do anything with this retro game (Back to the Future, Telltale 2010) i tried to install and run (but stock Wine 11 did and it can’t be added to Heroic nor Lutris).

Will report back.

Ok it does seem to work, but the installation program’s window is pitch black after creating an invocation for it and launching). Earlier this screen showed as expected with that upstream Wine (no launcher of any kind). What seems to prevent the graphics to show?

Edit: NOW it shows!

I wonder why it at first was black but when i clicked it up from dock this shows. WIll proceed now if can actrually game this!

1 Like

Ok the game installed. Now i’m trying to create an invication for the actual game and its autorun.exe but it is nowhere to be found. Where did the game in other words install? Because all i can find is:

THe location is ~/snap/zordeer/17/.local/share/applications/wine/Programs/R.G. Mechanics/Back To The Future - The Game but it is not the right one and that .desktop file isnt allowed as executable for invocation.

The prefixes that Zordeer creates are located in $HOME/AppsFiles/Zordeer/invocation

In this case, you don’t need to create a new invocation, just change the file that will be executed.

Ok i found it, created an invocation and the autorun.exe took to episode launcher of the game. But then after clicking on 1st episode to start game, happened this:

And i cannot click the error window to show (it just takes to that “black and white window” where the game should be. So this is ALMOST there!

This is the launcher. The 1st episode could be gamed through launching from upstream Wine from file manager. But now that black and white screen prevents (some graphic problem).

Just to confirm, does the invocation that starts autorun.exe use the same prefix as where you installed the game?

Whattaa…. NOW it worked after just launching the invocation again! Look yay:

1 Like