When trying to open winetricks, I get the following message: wine server not installed

Support and Help
, ,
1

Ubuntu Version:
Example: 26.04 - Ubuntu Studio

Desktop Environment (if applicable):
KDE Plasma

Problem Description:
I have wine version 10.0 installed. It comes preinstalled with Ubuntu Studio.

When trying to open winetricks, I get the following message: wine server not installed.

I tried running winecfg, and it worked.

When running the following command: sudo apt-get install --install-recommends wine-stable or this one: sudo apt-get install --install-recommends winehq-stable

It cannot find the installers for wine. Wine is installed, when looking in discover. I can remove it with synaptic, and re-install, but wanted to see what alternatives there were before doing that.

I did add the repositories, and get an error message about them, when doing sudo update.

Relevant System Information:
Include any details that might help (e.g., hardware, drivers, or special configurations).

Screenshots or Error Messages:
If applicable, paste error messages or screenshots.
We prefer copy-pasted text and screenshots instead of photos of screens.

For multi-line text or logs, wrap them in triple backticks like this or highlight the text and use </> in the composer:

sudo dmesg | tail -20

What I’ve Tried:
List the solutions or workarounds you’ve already attempted.

Before Posting:
:mag: Please check if similar issues have already been reported and resolved.

1 Like
3

The issue probably is not Winetricks itself.

From what you described, your system already has a partially working Wine installation, which is why:

winecfg

still launches.

On Ubuntu Studio 26.04, Wine 10 is already available from Ubuntu’s own repositories, so some Wine components may already be installed by default.

The bigger clue is this part:

“I added the repositories, and get an error during sudo update”

combined with: “wine server not installed”

That usually points to an incomplete or mixed Wine installation rather than Wine being fully absent.

Most likely causes:

  • missing i386 architecture,

  • broken WineHQ repository entry,

  • wrong repository codename,

  • or mixed Ubuntu/WineHQ packages.

Wine on modern Ubuntu is split across multiple packages (wine64, wine32, libwine, etc.), so it is possible for winecfg to work while winetricks still cannot detect wineserver.

First I would check whether i386 support is enabled: dpkg --print-foreign-architectures

If i386 is missing:

sudo dpkg --add-architecture i386

sudo apt update

Then verify whether wineserver actually exists: which wineserver

and check the installed Wine packages: dpkg -l | grep wine

I would also inspect the WineHQ repository entry before reinstalling anything: grep -r winehq /etc/apt/sources.list.d/

because if the repository entry is incorrect or mismatched for 26.04, APT can leave Wine in a partially installed state.

At the moment, this looks more like a repository/dependency consistency issue than an actual Winetricks bug.

4

Here is the output of everything:

$ which wineserver
$ dpkg -l | grep wine
ii libwine:amd64 10.0~repack-12ubuntu1 amd64 Windows API implementation - library
ii wine 10.0~repack-12ubuntu1 all Windows API implementation - standard suite
ii wine-common 10.0~repack-12ubuntu1 all Windows API implementation - common files
ii wine64 10.0~repack-12ubuntu1 amd64 Windows API implementation - 64-bit binary loader
ii winetricks 20250102-1build1 all simple tool to work around common problems in Wine
$ grep -r winehq /etc/apt/sources.list.d/
/etc/apt/sources.list.d/archive_uri-https_dl_winehq_org_wine-builds_ubuntu_-resolute.list.save:# deb https://dl.winehq.org/wine-builds/ubuntu/ focal main
/etc/apt/sources.list.d/archive_uri-https_dl_winehq_org_wine-builds_ubuntu_-resolute.list.save:# deb-src https://dl.winehq.org/wine-builds/ubuntu/ focal main
/etc/apt/sources.list.d/winehq.list:deb [signed-by=/usr/share/keyrings/winehq-archive.key] https://dl.winehq.org/wine-builds/ubuntu/ resolute main
/etc/apt/sources.list.d/archive_uri-https_dl_winehq_org_wine-builds_ubuntu_-resolute.list:# deb https://dl.winehq.org/wine-builds/ubuntu/ focal main
/etc/apt/sources.list.d/archive_uri-https_dl_winehq_org_wine-builds_ubuntu_-resolute.list:# deb-src https://dl.winehq.org/wine-builds/ubuntu/ focal main
/etc/apt/sources.list.d/winehq.list.save:deb [signed-by=/usr/share/keyrings/winehq-archive.key] https://dl.winehq.org/wine-builds/ubuntu/ resolute main

1 Like
5

Your output actually makes the issue much clearer now.

The important detail is this:

which wineserver

returned nothing.

That means Winetricks is correct — the “wineserver” binary is currently not available in your active runtime environment.

At the same time, these packages are installed:

- wine

- wine64

- libwine

- winetricks

So this is not a “Wine missing entirely” situation. It is more likely an incomplete or inconsistent Wine runtime installation.

I also noticed something important in your repository output:

focal

still appears inside old WineHQ “.list.save” files, while your active system is using:

resolute

Those “.save” files are usually ignored by APT, but they strongly suggest the system previously used older WineHQ repository configurations. Mixed WineHQ/Ubuntu Wine states are known to cause missing runtime components and dependency inconsistencies.

Another important detail is that Ubuntu 26.04 already ships Wine 10 directly from the Ubuntu repositories, while WineHQ support for newer Ubuntu releases has had transition issues and repository inconsistencies during rollout periods.

The first thing I would check now is whether the binary physically exists somewhere on disk:

find /usr -name wineserver 2>/dev/null

If it returns something like:

/usr/lib/wine/wineserver

then this is probably a PATH or symlink problem.

If it returns nothing at all, then the Wine runtime itself is incomplete.

At that point, I would try reinstalling the Ubuntu-provided Wine packages cleanly before touching WineHQ again:

sudo apt reinstall wine wine64 libwine winetricks

Then verify again:

which wineserver

wineserver --version

If “wineserver” is still missing after reinstalling, I would fully purge Wine and reinstall from a single source only (either Ubuntu repositories or WineHQ, but not both mixed together).

Right now this still looks more like a broken Wine runtime environment than a Winetricks-specific bug.

1 Like
6

I will come back to this. I decided to format and reinstall. There were self inflicted issues. Thanks for the help.

1 Like
7

Seeing that and the later confirmation:

you probably shouldn’t go right to 3rd party repositories on the first issue encountered.

$ apt-file search wineserver
libwine: /usr/lib/wine/wineserver
playonlinux: /usr/share/playonlinux/etc/setups/wineserver/left.jpg
playonlinux: /usr/share/playonlinux/etc/setups/wineserver/top.png
playonlinux: /usr/share/playonlinux/resources/images/menu/wineserver.png
playonlinux: /usr/share/playonlinux/resources/images/setups/wineserver/left.jpg
playonlinux: /usr/share/playonlinux/resources/images/setups/wineserver/top.png
protontricks: /usr/lib/python3/dist-packages/protontricks/data/scripts/wineserver_keepalive.bat
protontricks: /usr/lib/python3/dist-packages/protontricks/data/scripts/wineserver_keepalive.sh
wine: /usr/bin/wineserver-stable
wine: /usr/share/man/de/man1/wineserver-stable.1.gz
wine: /usr/share/man/fr/man1/wineserver-stable.1.gz
wine: /usr/share/man/man1/wineserver-stable.1.gz
wine64: /usr/lib/wine/wineserver64

This is on plain Ubuntu 24.04, without 3rd party repo. I’m sure the output is identical on 26.04. It seems as if the command you are looking for is wineserver-stable. It looks like that file is either missing in wine on 26.04 or it’s in another package. The above command should be able to tell you.

But you can also just try to run a command whose correct name you know and get something like this in return:

$ apt-file search bin/wineserver
Command 'apt-file' not found, but can be installed with:
sudo apt install apt-file

That’s thanks to a nifty little tool which catches the command not found error and searches for packages and snaps providing said command.

Please put all log and other console/terminal output in pre-formatted code blocks (the </> icon in the editor), ideally wrapped in a “Hide Details” element, when it’s more than a couple of lines. See items 4 and 5 in the Posting Guide.

Optional helper script

If you are so inclined, I took it upon myself to provide a little helper script for that. :sweat_droplets:

8

I reinstall the OS, and purged wine from the system, and then installed it per the instructions from Wine’s website. It works, but getting winetricks installed and working is a nightmare.

9

(emphasis added)

Can’t help you there, because this is for Ubuntu specific issues.

10

Should have looked more carefully.

/usr/lib/i386-linux-gnu/wine/wineserver 	wine32 [i386]
/usr/lib/x86_64-linux-gnu/wine/wineserver 	wine64 [amd64]

So the actual providers of the wineserver binary are still there, but nothing is placed in /usr/bin to link to them, as it seems. I cannot say how this is supposed to work in 26.04, but I’ll wager the use of the alternatives system to provide /usr/bin/wineserver hasn’t changed. A proper wine installation from the official repos should put a symlink in /etc/alternatives. This is usually done by some post-install script. I cannot rule out a packaging bug, though, since I’m still on 24.04 and a little tight on disk space, so spinning up a VM is not an option, sadly.

I guess, I should have read more carefully; that explains a lot. And it is one more instance for why it is important to not only revert distro sources to default but also to uninstall such packages prior to a release upgrade. In this case it may even be required to actually purge wine, because otherwise it’s in the “residual config” state (dpkg -l shows rc in the 1st column), which may result in the package manager skipping the configuration step and thus the missing link in /etc/alternatives for the official Ubuntu packages.

I’m really not a fan of 3rd party repos and avoid them wherever I possibly can. This is yet another cautionary tale, I guess.

11

Updated my last post, so bumping the topic.

12

Same issue here. Fresh install of kubuntu 26.04. Then installed wine and winetricks from ubuntu in Discover.

Running winetricks “wineserver not found”.

Verified I have

/usr/lib/x86_64-linux-gnu/wine/wineserver

But nothing linked in bin or alternatives.

13

Welcome to the Ubuntu Discourse, @milesgb, and thanks for chiming in!

As it turns out, this is by design, see below.

Now that I knew even a clean install shows this, I did:

sudo apt install wine winetricks

and had a look-see. Indeed, there is no wineserver binary linked in /etc/alternatives/, but the manual page is linked there. It only references the binary in /usr/lib/..., so there must be more to the story and /usr/share/doc/libwine/News.Debian.gz has the answer:

wine (10.0~repack-12) unstable; urgency=medium
[...]
    Additionally, the /usr/bin/wineserver helper script is no longer included.
    The wineserver version appropriate to the desired architecture tuple "*"
    may be launched manually from /usr/lib/*/wine/. For more info, please see:
    $ man wineserver

    Finally, the name for the group of wine alternatives has been changed from
    wine to wine.collection. To configure wine's alternatives, please execute:
    $ sudo update-alternatives --config wine.collection

    Please see /usr/share/doc/wine-common/README.Debian.gz for more detail.

 -- Michael Gilbert <mgilbert@debian.org>  Tue, 21 Oct 2025 21:55:00 +0000

Thinking of the best way to deal with this, I figured that one can always install one’s own alternative:

sudo update-alternatives --install /usr/bin/wineserver wineserver /usr/lib/x86_64-linux-gnu/wine/wineserver 10

I don’t know if that’s a good idea, though, because I don’t know why that decision was made to remove the helper script, but it does work; at least I was able to just run winetricks. There is also the $WINESERVER environment variable, which one can set:

mkdir -p "${XDG_CONFIG_HOME:-$HOME/.config}"/environment.d/
echo WINESERVER=/usr/lib/x86_64-linux-gnu/wine/wineserver >> "${XDG_CONFIG_HOME:-$HOME/.config}"/environment.d/winetricks.conf

or, for the less pedantic:

mkdir -p ~/.config/environment.d/
echo WINESERVER=/usr/lib/x86_64-linux-gnu/wine/wineserver >> ~/.config/environment.d/winetricks.conf

(this works on any default installation, where $XDG_CONFIG_HOME is unset)

Then logout and log back in to make that change appear in the user environment.

1 Like