{{{1}}} WineHQ Repository

From WineHQ Wiki
Jump to: navigation, search

WineHQ Packages

[[File:Icon-distro-{{{2}}}.png|40px|link=]] Although {{{1}}} offers its own Wine packages, these are often several versions behind.

To make installing the latest version of Wine as easy as possible, WineHQ has its own {{{1}}} repository. Should a newer version of Wine give problems, it is also possible to install an older version of your choice.


If your system is 64 bit, enable 32 bit architecture (if you haven't already):

sudo dpkg --add-architecture i386 

Download and add the repository key:

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

Add the repository

Please select your {{{1}}} version and download the WineHQ sources file:


Update the package information:

sudo apt update

Install Wine

Install one of the following packages:

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 WineHQ Wiki explains the differences between the branches.


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.

Missing dependencies

  • WineHQ packages are created and tested for a clean {{{1}}} 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.

  • 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.

  • 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.

  • Read also the FAQ about dependency errors and tips for troubleshooting dependency issues.

Winehq key problems

  • W: GPG error: https://dl.winehq.org/ ... NO_PUBKEY 76F1A20FF987672F

Currently, the Wine servers are being synchronized. This means that some users still getting the older .sources file. If you get this warning, edit the winehq-<distro>.sources file and replace /usr/share/keyrings/ to /etc/apt/keyrings/.

For example: sudo sed -i s@/usr/share/keyrings/@/etc/apt/keyrings@ /etc/apt/sources.list.d/winehq-focal.sources

  • 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/*).

Ubuntu 22.04 and Wine stable

There are no stable packages for Ubuntu 22.04 yet. Ubuntu Jammy Jellyfish did not exist when Wine 7.0 was released. There will be stable packages whenever 7.0.1 comes out.

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.


  • 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.
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 {{{1}}} machine without internet access, you must have access to a second {{{1}}} 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/<distro>/dists/<version>/main/source"
  • The latest version of {{{1}}} is 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 {{{1}}} 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.

See Also