PlayOnLinux simplifies running Windows applications on Linux by providing a graphical interface for Wine. This guide covers installing PlayOnLinux on Ubuntu using APT or Flatpak. Whether you need to run older Windows games, productivity software like Microsoft Office, or legacy business applications without native Linux versions, PlayOnLinux handles the complexity of Wine prefix management and configuration. By the end of this guide, you will have a working PlayOnLinux installation ready to run Windows software, with verification steps confirming everything works correctly.
Choose Your Installation Method
This guide covers two installation methods. The APT method uses Ubuntu’s default repositories, while the Flatpak method provides a newer version with sandboxing benefits.
| Method | Channel | Version | Updates | Best For |
|---|---|---|---|---|
| APT | Ubuntu Repos | 4.3.4 | Automatic via apt upgrade | Ubuntu 22.04 and 24.04 users |
| Flatpak (Recommended) | Flathub | 4.4 | Automatic via flatpak update | All Ubuntu versions including 26.04 |
The APT method works on Ubuntu 24.04 LTS and 22.04 LTS only. Ubuntu 26.04 LTS does not include PlayOnLinux in its repositories. For Ubuntu 26.04 users, the Flatpak method is required. Flatpak also provides a newer version (4.4 vs 4.3.4) with the same interface and functionality.
Method 1: Install PlayOnLinux via APT
The APT method installs PlayOnLinux from Ubuntu’s multiverse repository, which is enabled by default on standard Ubuntu installations. This method only works on Ubuntu 24.04 and 22.04.
Update Package Lists
Refresh the package index and upgrade existing packages:
sudo apt update && sudo apt upgrade
Install PlayOnLinux
Install PlayOnLinux along with its dependencies. The package manager automatically resolves and installs required components including Wine, Python, and various utilities:
sudo apt install playonlinux
Verify the Installation
Confirm that PlayOnLinux installed correctly by checking the version:
playonlinux --version
Expected output:
PlayOnLinux 4.3.4
Method 2: Install PlayOnLinux via Flatpak
The Flatpak method installs PlayOnLinux 4.4 from Flathub. This method works on all Ubuntu versions including 26.04 and provides a newer release than the APT repositories.
Install Flatpak
Flatpak is not pre-installed on Ubuntu. If you have not set it up yet, follow our guide to installing Flatpak on Ubuntu, which covers installing the Flatpak framework and adding the Flathub repository.
Add the Flathub Repository
If Flathub is not already configured, add it as a remote source:
sudo flatpak remote-add --if-not-exists flathub https://flathub.org/repo/flathub.flatpakrepo
Install PlayOnLinux
Install PlayOnLinux from Flathub:
flatpak install flathub com.playonlinux.PlayOnLinux4 -y
The first installation downloads the application and its runtime dependencies, which may take several minutes depending on your internet connection.
Verify the Installation
Confirm PlayOnLinux installed by listing installed Flatpak applications:
flatpak list | grep -i playonlinux
Expected output:
PlayOnLinux 4 com.playonlinux.PlayOnLinux4 4.4 stable system
Launch PlayOnLinux
After installation, launch PlayOnLinux from the desktop environment or command line.
Launch from Applications Menu
Open the Activities overview and search for “PlayOnLinux”. The application appears in your applications list after installation. For Flatpak installations, you may need to log out and log back in, or restart your system, if the application icon does not appear immediately.

Launch from Terminal
For APT installations:
playonlinux
For Flatpak installations:
flatpak run com.playonlinux.PlayOnLinux4
First Run and Basic Usage
When you first launch PlayOnLinux, the application may prompt you to install additional components or update its script repository. Allow these updates to ensure you have access to the latest installation scripts.
Install a Windows Application
To install a Windows application:
- Click Install in the main toolbar
- Browse or search the available installation scripts
- Select the application you want to install and follow the wizard
- Provide the Windows installer when prompted (download from the software vendor)

Each installation creates a separate Wine prefix, isolating applications from each other. This prevents one program’s Wine configuration from affecting another.
Manual Installation
For applications without pre-configured scripts, use the manual installation option. This creates a new Wine prefix where you can run any Windows installer. Manual installations require more Wine knowledge but provide flexibility for unsupported software.
Update and Manage PlayOnLinux
Update PlayOnLinux
For APT installations, PlayOnLinux updates when you upgrade your system packages:
sudo apt update && sudo apt upgrade
For Flatpak installations:
flatpak update
Manage Wine Versions
PlayOnLinux can manage multiple Wine versions independently of your system Wine installation. Access this feature through Tools > Manage Wine Versions in the menu. Installing newer Wine versions can improve compatibility with specific applications.
Troubleshooting
Missing 32-bit Libraries
Many Windows applications require 32-bit libraries. If you encounter errors about missing libraries, enable 32-bit architecture support and install the 32-bit Wine libraries that older Windows applications need:
sudo dpkg --add-architecture i386
sudo apt update
sudo apt install wine32
Graphics Issues
If you experience graphics issues with games or 3D applications, your GPU drivers may need attention. NVIDIA users should install the proprietary drivers for better Wine performance, while AMD users can rely on the built-in Mesa drivers. Our Wine installation guide provides step-by-step GPU driver installation instructions for both NVIDIA and AMD graphics cards.
Script Installation Fails
If a pre-configured installation script fails, check the PlayOnLinux forums for known issues with that specific application. Scripts occasionally break when software vendors change their installers or download locations. Alternatively, use the manual installation option described in the First Run and Basic Usage section to create a new Wine prefix and install the application directly.
Remove PlayOnLinux
If you no longer need PlayOnLinux, remove it using the method matching your installation.
Remove APT Installation
Uninstall PlayOnLinux while keeping configuration files:
sudo apt remove playonlinux
To remove PlayOnLinux and its configuration files completely:
sudo apt purge playonlinux
Remove orphaned dependencies:
sudo apt autoremove
PlayOnLinux stores installed Windows applications and Wine prefixes in
~/.PlayOnLinux/. Removing the package does not delete this directory. To remove all installed Windows applications and their data, delete this directory manually:rm -rf ~/.PlayOnLinux/
Remove Flatpak Installation
Remove PlayOnLinux and its application data:
flatpak uninstall --delete-data com.playonlinux.PlayOnLinux4
Remove unused Flatpak runtimes:
flatpak uninstall --unused
Conclusion
You now have PlayOnLinux installed and configured for running Windows applications. Both installation methods provide the same PlayOnLinux 4.x interface with its extensive script library for automated Windows software installation. The Flatpak method offers the newer 4.4 release and works on all Ubuntu versions, while the APT method integrates with your system package manager on Ubuntu 22.04 and 24.04.
Running version updated version of PlayOnLinux. Trying to create a 64-bit virtual drive but I get the error:
“Error in POL_Wine
Starting 64-bit process /home/brian/Autostakkert4/AutoStakkert.exe is not supported in 32-bit virtual drives”
I am (trying) to install a 64-bit process using a 64-bit computer on a program I assume is 64-bit as well but being told that I am creating a 32-bit virtual drive.
Confused!!!
Good question, Brian. By default, PlayOnLinux creates 32-bit Wine prefixes because they have broader compatibility with older Windows software. To run 64-bit applications like AutoStakkert4, you need to explicitly create a 64-bit virtual drive.
In PlayOnLinux, go to Tools > Manage Wine Versions and install a 64-bit Wine version (look for versions with “amd64” in the name). Then create a new virtual drive by clicking Configure > New, selecting your 64-bit Wine version, and choosing 64-bit Windows installation when prompted.
Alternatively, use the manual installation option from the main menu. When the wizard asks about the virtual drive architecture, select 64-bit. After creating the 64-bit prefix, you can install AutoStakkert4 into it. The key is that the virtual drive architecture must be set during creation, as it cannot be changed afterward.