How To Install Wine on Ubuntu 26.04 LTS

Install Wine on Ubuntu 26.04 LTS

You need to run a Windows-only .exe file on your Ubuntu 26.04 LTS desktop. Maybe it is a legacy business tool, a niche utility, or an older application that simply has no Linux equivalent. The fastest path forward, without spinning up a full virtual machine or dual-booting, is to install Wine on Ubuntu 26.04 LTS and get it running in minutes.

Wine (Wine Is Not an Emulator) is a compatibility layer that translates Windows API calls into POSIX system calls your Linux kernel understands. It does not simulate hardware. It does not run a hidden copy of Windows. It intercepts what a Windows program asks the OS to do and converts those requests directly into Linux operations, which is why most lightweight Windows apps run at near-native speed under Wine.

This guide walks you through every step from a freshly updated Ubuntu 26.04 LTS (Resolute) system to a fully working Wine environment. You will enable 32-bit support, install Wine 10.0 from Ubuntu’s Universe repository, set up Winetricks, configure your Wine prefix with winecfg, and run your first .exe. Each step includes an explanation of why it matters, not just the command to copy.

By the end of this tutorial, you will have a working Wine installation and enough understanding to troubleshoot the most common errors on your own.

Prerequisites

Before you run any command, confirm the following:

  • OS: Ubuntu 26.04 LTS (Resolute) installed on a 64-bit x86 system
  • Desktop session: You must be in a graphical desktop environment. winecfg and most Windows apps need a display server to launch. Headless servers can initialize a Wine prefix partially, but cannot complete GUI-based configuration.
  • User account: Your account must have sudo privileges. All package management commands in this guide require elevated permissions.
  • Internet connection: APT downloads Wine, Winetricks, and all 32-bit libraries from Ubuntu’s package servers.
  • Disk space: At minimum 1.5 GB of free space for Wine 10.0, its 32-bit libraries, and Winetricks.
  • Terminal access: Open your terminal with Ctrl+Alt+T or find it in your application menu.

Step 1: Update Your System

Before installing anything, refresh your package metadata and apply pending upgrades.

sudo apt update && sudo apt upgrade -y

What this does: apt update contacts every enabled repository and rebuilds APT’s local package list. apt upgrade then installs newer versions of any packages already on your system.

Why this matters: APT resolves dependencies against its local cache, not against live repository data. If your cache is stale, APT may try to install an outdated version of Wine or fail to resolve a dependency that was already updated upstream. Running this first takes less than two minutes and prevents a class of errors that are genuinely frustrating to debug later.

Expected output: You will see a list of packages being upgraded. If nothing needs upgrading, APT prints 0 upgraded, 0 newly installed. Either result is fine. Proceed when the prompt returns.

Step 2: Enable 32-Bit Architecture (i386)

Ubuntu 26.04 is a 64-bit system. Wine needs 32-bit libraries to run a large number of Windows applications, installers, and game launchers that are still compiled as 32-bit binaries.

Register the i386 Architecture

sudo dpkg --add-architecture i386

What this does: This command tells dpkg, the low-level Debian package manager, to start tracking packages built for the i386 (32-bit x86) architecture alongside the native amd64 packages.

Why this matters: Without this step, APT has no awareness of 32-bit packages. When you try to install wine32 in the next step, APT will return a “package not found” error because i386 packages are simply invisible to it. This is a one-time, system-level registration.

Verify the Architecture Was Registered

dpkg --print-foreign-architectures

Expected output:

i386

If i386 appears in the output, the registration worked. Do not skip this verification. If the architecture was not registered correctly due to a permission issue or a terminal copy-paste error, the Wine installation in Step 3 will fail with confusing error messages.

Refresh APT Package Lists

sudo apt update

Why this matters: After registering a new architecture, APT must rebuild its package index to include i386 packages from all enabled repositories. Until you run this command, APT still cannot see the 32-bit Wine libraries. This second apt update is not redundant; it is required.

Step 3: Install Wine on Ubuntu 26.04 LTS

With 32-bit support active and APT refreshed, you are ready to install Wine on Ubuntu 26.04 LTS. Ubuntu 26.04 (Resolute) ships Wine 10.0 in its Universe repository. WineHQ does not currently publish a Resolute-specific repository, so this distro package is the correct and supported install path for this release.

Install Wine 64-Bit and 32-Bit Packages

sudo apt install wine64 wine32 -y

What this does: wine64 is the main Wine binary that runs 64-bit Windows executables. wine32 provides the 32-bit libraries registered in Step 2. Installing both in a single command gives you maximum application compatibility from day one.

Why install both: Many Windows application installers are 32-bit even when the application itself is 64-bit. A 32-bit installer unpacking a 64-bit app is a common pattern. If you skip wine32, those installers fail to launch with a cryptic library error.

Note about the Universe component: Wine and Winetricks both come from Ubuntu’s Universe repository, which is enabled by default on standard desktop installs. If APT cannot find wine64, your system may have Universe disabled. Enable it before retrying with:

sudo add-apt-repository universe
sudo apt update

Verify the Wine Installation

wine --version

Expected output:

wine-10.0 (Ubuntu 10.0~repack-12ubuntu1)

If you see this output, Wine is installed, the binary is in your PATH, and you are ready to configure it. If the command is not found, the package installation encountered a silent error; re-run sudo apt install wine64 wine32 and check for error messages in the output.

Step 4: Install Winetricks

Winetricks is a separate helper script that installs common Windows runtime dependencies inside a Wine prefix. Wine provides the compatibility layer; Winetricks fills in the gaps that Wine does not bundle by design.

sudo apt install winetricks -y

Verify Winetricks

winetricks --version

Expected output:

20250102

Why Winetricks is essential: Many Windows programs fail to launch not because Wine is broken, but because they expect specific Microsoft runtimes, fonts, or DirectX components that Wine does not include for legal reasons. Winetricks gives you a single command to install those components inside your Wine prefix without touching the rest of your system.

Common Winetricks recipes you will use:

  • winetricks allfonts installs Microsoft core fonts that productivity apps expect for correct text rendering
  • winetricks vcrun2015 installs the Visual C++ 2015 redistributable required by many modern Windows apps
  • winetricks dotnet48 installs .NET Framework 4.8 for .NET-dependent applications
  • winetricks d3dx9 adds DirectX 9 support for older games

Step 5: Configure Wine with winecfg

Before you run any Windows executable, you need to initialize the Wine prefix. The prefix is a virtual Windows environment stored in your home folder at ~/.wine. It contains a virtual C: drive, a registry, and all DLLs that Wine uses to simulate the Windows environment.

Initialize the Wine Prefix

winecfg

What this does: The first time you run winecfg, Wine creates the ~/.wine directory, populates it with a Windows-like folder structure (drive_c, windows, system32), and sets up a basic registry. It then opens the configuration window.

Why you must do this before running any .exe: Running an installer without initializing the prefix first can result in a corrupted or incomplete prefix. The installer may fail partway through, leaving behind broken registry entries that cause every subsequent Wine launch to behave erratically.

Wine Mono Prompt

When winecfg runs for the first time, Wine may ask you to install Wine Mono. Accept this prompt.

Why: Wine Mono is a lightweight implementation of the .NET framework designed specifically for Wine. It installs inside your prefix, not system-wide, and handles any .NET calls that Windows applications make. Without it, .NET-dependent apps fail immediately with a runtime error.

Key Configuration Settings in winecfg

The winecfg window has several tabs. Focus on these:

  • Applications tab: Sets the Windows version Wine reports to applications. Windows 10 is the safest default for modern apps. Change this to Windows 7 or Windows XP only if a specific older application refuses to run.
  • Drives tab: Maps Linux paths to Windows drive letters. Your default prefix maps ~/.wine/drive_c to C:\. Add additional drives here if an application expects data on D:\ or E:\.
  • Graphics tab: Controls screen resolution and window behavior for GUI applications.
  • Audio tab: Maps your Linux audio output to Wine’s virtual audio device.

Why the Windows version setting matters: Some applications check the reported Windows version at startup and refuse to run if it does not match an expected range. This setting is the first variable to change when an app launches and immediately quits with no error message.

Step 6: Run a Windows Application with Wine

With Wine configured, you can now run Windows executables directly from the terminal.

Run a Windows Installer

wine /path/to/installer.exe

What this does: Wine intercepts the installer’s Windows API calls, translates them to Linux system calls, and opens the standard Windows installer wizard on your Ubuntu desktop. The program installs into ~/.wine/drive_c/Program Files/ by default.

Why the full path matters: Wine resolves file paths using its virtual C: drive mapping. A relative path from an arbitrary terminal directory can fail not because the file is missing, but because Wine cannot resolve the path inside the virtual prefix. Always use the full absolute path.

Launch an Already-Installed Windows Application

wine "$HOME/.wine/drive_c/Program Files/AppName/app.exe"

Right-Click Alternative

After installation, the file manager Nautilus registers Wine as an “Open With” handler for .exe files. You can right-click any .exe and select Open With Wine Windows Program Loader without touching the terminal. This works for both installers and standalone executables.

Before running any Windows app: Check the WineHQ Application Database at appdb.winehq.org. Community members rate and document the compatibility of thousands of Windows programs. You will find specific winecfg settings, Winetricks recipes, and known workarounds for many popular applications before you spend time troubleshooting from scratch.

Step 7: Create a Separate 32-Bit Wine Prefix (Recommended for Legacy Apps)

The default Wine prefix is 64-bit. Some older 16-bit and 32-bit Windows applications behave erratically inside a 64-bit prefix. A dedicated 32-bit prefix isolates these apps without touching your main Wine environment.

WINEARCH=win32 WINEPREFIX="$HOME/.wine32" winecfg

What this does: The WINEARCH=win32 environment variable tells Wine to create a pure 32-bit Windows environment. WINEPREFIX points Wine to a new, separate directory (~/.wine32) instead of the default ~/.wine.

Why this is safer than modifying the default prefix: Each prefix is fully independent. You can delete ~/.wine32 at any time without affecting your main Wine setup. This is the right approach for legacy accounting software, old CAD tools, and any Windows XP-era utilities that refuse to install into a 64-bit prefix.

Practical use: Any time you want to use this secondary prefix, prepend WINEPREFIX="$HOME/.wine32" to your Wine command:

WINEPREFIX="$HOME/.wine32" wine /path/to/legacy-app.exe

How to Update Wine on Ubuntu 26.04

Wine updates flow through APT like any other package. To upgrade only Wine without touching the rest of your system:

sudo apt install --only-upgrade wine wine64 wine32 winetricks

Why use --only-upgrade instead of apt upgrade: This flag restricts the operation to packages already installed on your system. It updates only Wine and Winetricks, without upgrading unrelated packages that you may want to handle separately during a scheduled maintenance window.

Why keep Wine updated: Wine releases frequently improve compatibility for existing applications and add support for new Windows API calls. Running Wine 10.0 with six-month-old library patches is a common but underappreciated cause of application regressions that appear to be app bugs.

Troubleshooting Common Wine Errors on Ubuntu 26.04

Error 1: “Cannot find the i386:i386 package”

Cause: The 32-bit architecture was not registered before apt update was run, or Step 2 was skipped entirely.

Fix: Run the steps in the correct order:

sudo dpkg --add-architecture i386
sudo apt update
sudo apt install wine64 wine32 -y

Error 2: App Crashes Immediately After Launch

Cause: The Windows version set in winecfg does not match what the application expects.

Fix: Open winecfg, go to the Applications tab, and try a different Windows version. For apps from the early 2000s, use Windows XP. For apps from 2010 to 2018, try Windows 7. For modern apps, Windows 10 is the correct default.

Error 3: Missing DLL Errors (e.g., vcruntime140.dll not found)

Cause: The application depends on a Microsoft runtime that Wine does not include and that was not installed by Winetricks.

Fix: Identify the required runtime from the error message and install it with Winetricks:

winetricks vcrun2015
# or
winetricks vcrun2019
# or
winetricks dotnet48

Error 4: “wine: cannot find L’C:\\windows\\system32\\winemenubuilder.exe'”

Cause: This warning appears when the Wine prefix is not fully initialized. It is non-fatal but indicates the prefix was never properly set up.

Fix: Run winecfg first to complete prefix initialization before running any .exe.

Error 5: Graphical Glitches or Black Screen in Apps

Cause: The application uses DirectX, and Wine’s default software renderer cannot handle it.

Fix: Install DirectX support via Winetricks and optionally enable DXVK for Vulkan-based DirectX translation:

winetricks d3dx9
winetricks dxvk

DXVK translates DirectX 9, 10, and 11 calls to Vulkan, which dramatically improves rendering performance and compatibility on modern GPUs.

How to Remove Wine from Ubuntu 26.04

If you no longer need Wine, remove both the packages and the Wine prefix directories separately. APT manages packages; your home folder data is invisible to it.

Remove Wine Packages

sudo apt remove --autoremove wine wine64 wine32 winetricks

Why --autoremove: This flag also removes the dependency libraries that APT installed automatically with Wine. Without it, hundreds of megabytes of 32-bit libraries remain on your system as orphaned packages.

Remove Wine Prefix Directories

rm -rf ~/.wine ~/.wine32

Warning: Deleting a Wine prefix permanently removes all Windows programs, registry data, and application files stored inside it. Back up any important files from ~/.wine/drive_c/ before running this command. There is no recovery from rm -rf.

Congratulations! You have successfully installed Wine. Thanks for using this tutorial for installing Wine on the Ubuntu 26.04 LTS (Resolute Raccoon) system. For additional help or useful information, we recommend you check the Wine website.

VPS Manage Service Offer
If you don’t have time to do all of this stuff, or if this is not your area of expertise, we offer a service to do “VPS Manage Service Offer”, starting from $10 (Paypal payment). Please contact us to get the best deal!
r00t is a Linux Systems Administrator and open-source advocate with over ten years of hands-on experience in server infrastructure, system hardening, and performance tuning. Having worked across distributions such as Debian, Arch, RHEL, and Ubuntu, he brings real-world depth to every article published on this blog. r00t writes to bridge the gap between complex sysadmin concepts and practical, everyday application — whether you are configuring your first server or optimizing a production environment. Based in New York, US, he is a firm believer that knowledge, like open-source software, is best when shared freely.

Related Posts