How to Install Wine on Fedora 44

Wine is usually the quickest way to run Windows software on Fedora Linux without carving up your system for dual-booting or managing a full virtual machine. If you need to install Wine on Fedora Linux for a launcher, legacy business app, or Windows-only utility, Wine translates Windows API calls so many programs can run directly on your Fedora desktop. Not every app works perfectly, but the right setup avoids a lot of trial-and-error.

Fedora gives you two practical paths: Fedora’s own wine metapackage for simpler maintenance, or the WineHQ repository when you want upstream stable, staging, or development builds. The Fedora package path also pulls in desktop integration and Wine Mono, while WineHQ keeps its binaries under /opt/wine-*/bin, so the setup details differ in ways that matter after installation.

Install Wine on Fedora Linux

Fedora offers two primary Wine installation paths. Use Fedora’s repositories unless a specific application needs a newer WineHQ channel.

Method	Source	Package or Channel	Update Path	Best Fit
Fedora repositories	Fedora package	wine metapackage; currently Wine 11.0 on Fedora 44 and Fedora 43	Updates through normal dnf upgrade transactions	Most users who want Fedora-tested packages and clean dependency handling
WineHQ repository	WineHQ Fedora packages	winehq-stable, winehq-staging, or winehq-devel	Updates through DNF after the WineHQ repo is added	Users who need newer upstream builds or staging/development features

For most users, the Fedora repository method is recommended because it follows Fedora’s normal package testing and update flow. WineHQ is still useful, but it adds a third-party repository and a separate binary path that you need to manage.

Prepare Fedora Before Installing Wine

Start by confirming that your Fedora system is current and within the releases covered by current Fedora package sources. Fedora 44 is the current stable release, and Fedora 43 remains the previous supported release.

Check your Fedora release:

cat /etc/fedora-release

Example output on Fedora 44:

Fedora release 44 (Forty Four)

If your system still reports Fedora 42 or older, upgrade Fedora Linux before adding fresh Wine packages or third-party repositories.

Update Fedora Packages

Refresh repository metadata and apply available package updates before installing Wine:

Search for “Terminal” in Activities, then run:

sudo dnf upgrade --refresh

If your user account does not have sudo privileges yet, set that up first with the Fedora sudoers walkthrough: How to Add a User to Sudoers on Fedora.

The command refreshes repository metadata and upgrades installed packages. For slower mirrors or repeated downloads, optimize DNF performance on Fedora before retrying large Wine transactions.

Check Whether Wine Is Already Installed

Check whether Wine is already installed so you know whether you are upgrading an existing setup or starting from a clean package state:

wine --version

If Wine is installed, the version command returns output similar to this:

wine-11.0 (Staging)

If Wine is not installed, your shell reports that the command is not found. Continue with one installation method rather than mixing Fedora and WineHQ packages.

Install Wine from Fedora Repositories

The Fedora repository method installs the wine metapackage from Fedora’s normal package sources. On Fedora 44, that package resolves to Wine 11.0 and requires key companion packages such as wine-core, wine-desktop, and wine-mono.

Install the Wine Metapackage

Install Wine from Fedora’s repositories:

sudo dnf install wine

The metapackage pulls in the Wine loader, desktop integration, fonts, audio support, and Wine Mono package needed by many .NET-based Windows applications.

Add 32-bit Application Support (Optional)

Many older Windows applications and game launchers are 32-bit. Fedora publishes an i686 Wine package for this case, and DNF installs the matching 32-bit Wine libraries and dependencies.

Install the 32-bit package when you know an application needs it:

sudo dnf install wine.i686

If you only run modern 64-bit Windows applications, start without wine.i686 and add it later only if an application reports a 32-bit compatibility problem.

Verify Wine Installation

Confirm Wine is available from your shell:

wine --version

Fedora’s Wine package can report (Staging) in the version output even though you installed the Fedora package path:

wine-11.0 (Staging)

That label is normal for Fedora’s Wine build and does not mean you installed the WineHQ staging channel.

Check the package state if you need to confirm the source and release revision:

rpm -q wine wine-mono wine-desktop

Example output on Fedora 44:

wine-11.0-3.fc44.x86_64
wine-mono-10.4.1-2.fc44.noarch
wine-desktop-11.0-3.fc44.noarch

The wine-desktop package provides desktop integration for file associations and launchers; you normally do not install it separately because the wine metapackage requires it.

Install Wine from the WineHQ Repository on Fedora

The WineHQ repository provides upstream stable, staging, and development builds for users who need a newer channel than Fedora’s packaged Wine. Keep this method separate from the Fedora package method because WineHQ installs its main binaries under /opt/wine-*/bin.

Install the DNF Config Manager Provider

The WineHQ setup command uses Fedora’s DNF5 config-manager plugin. Install the DNF5 provider first if your system reports that config-manager is not available:

sudo dnf install 'dnf5-command(config-manager)'

Enable the WineHQ Repository

Add the official WineHQ repository. The $(rpm -E %fedora) expression expands to your Fedora release number, such as 44 or 43, so the repo URL follows the installed system:

sudo dnf config-manager addrepo --from-repofile=https://dl.winehq.org/wine-builds/fedora/$(rpm -E %fedora)/winehq.repo

If you rerun this command and dnf reports that /etc/yum.repos.d/winehq.repo already exists, rerun it with --overwrite to refresh the repository file.

Verify that DNF sees the WineHQ repository:

dnf repo list --all | grep -i winehq

You should see output confirming the repository is enabled:

WineHQ                                         WineHQ packages                                        enabled

You can also confirm that WineHQ exposes the expected channel packages:

dnf repoquery --repo=WineHQ --latest-limit=1 winehq-stable winehq-staging winehq-devel

Relevant Fedora 44 output includes:

winehq-devel-1:11.8-1.1.x86_64
winehq-stable-1:11.0.0-2.1.x86_64
winehq-staging-1:11.8-1.1.x86_64

If you already installed Wine from Fedora’s repositories, the WineHQ commands use --allowerasing so DNF can replace conflicting Fedora Wine components such as wine-core. Review the transaction before confirming because DNF may also remove Fedora’s winetricks package, which depends on Fedora wine-common and conflicts with WineHQ channel packages.

Select a WineHQ Release Channel

WineHQ offers three channels. Install only one channel at a time unless you intentionally manage separate WineHQ paths.

The stable channel is the safest WineHQ choice for general use. Staging and development are better reserved for application testing or fixes that have not reached stable yet.

Install WineHQ Stable Release

Install the stable channel with:

sudo dnf install winehq-stable --allowerasing

Install WineHQ Staging Release

Install the staging channel when you need WineHQ’s staging patches:

sudo dnf install winehq-staging --allowerasing

Install WineHQ Development Release

Install the development channel only when you deliberately want the newest upstream development build:

sudo dnf install winehq-devel --allowerasing

Verify WineHQ Installation

Verify the selected WineHQ build. On Fedora, WineHQ installs binaries under /opt/wine-stable/bin, /opt/wine-staging/bin, or /opt/wine-devel/bin, so plain wine may not be available on PATH immediately.

command -v wine || echo "bash: wine: command not found"

bash: wine: command not found

Use the channel-specific WineHQ binary path to confirm the installation; the stable channel uses this path:

/opt/wine-stable/bin/wine --version

wine-11.0

If you prefer using plain wine commands for the rest of the session, add the selected WineHQ channel path to PATH (replace stable with staging or devel if needed):

export PATH="/opt/wine-stable/bin:$PATH"
command -v wine
wine --version

/opt/wine-stable/bin/wine
wine-11.0

The output confirms the selected WineHQ release is installed and ready to use in that terminal session. Add the path to your shell profile only after you are sure you want the WineHQ channel to be the default for your account.

Configure Wine on Fedora and Install Dependencies

Wine works through per-user prefixes, so the first configuration step usually initializes ~/.wine and opens the graphical settings window. Configure Wine after the Fedora package method or after adding the selected WineHQ path to your shell.

If you installed Wine from WineHQ and did not add its channel path to PATH, replace commands like wine and winecfg with the matching full paths such as /opt/wine-stable/bin/wine and /opt/wine-stable/bin/winecfg.

Configure Wine with winecfg on Fedora

The winecfg tool initializes the default Wine prefix and opens settings for Windows version emulation, audio, graphics, libraries, and drives. Run it after installing Wine or when preparing a new Windows application:

winecfg

Running this command launches the Wine Configuration window. By default, Wine emulates Windows 10, which works well for most applications. Change that setting only when an application’s compatibility notes require a different Windows version.

Within the configuration window, you can customize:

• Audio: Configure sound output and input to match your system hardware. Navigate to the Audio tab to ensure proper sound functionality in games, media players, or communication tools.
• Graphics: Enable virtual desktop mode or adjust screen resolution in the Graphics tab. Virtual desktop is useful for older applications requiring fixed screen sizes or for running games in a contained environment.
• Libraries: Manage DLL overrides in the Libraries tab. Some applications require specific library versions not available by default. Add and prioritize them manually to ensure compatibility.
• Drivers: Select correct graphics and input drivers for applications with specific hardware requirements. Proper driver configuration enhances compatibility and performance for graphics-intensive applications or peripherals like joysticks and gamepads.

After adjusting settings, click Apply and then OK to save changes. Test your configuration by running a sample Windows application to ensure everything works as expected.

Install Wine Mono for .NET Compatibility

Many Windows applications rely on the .NET Framework, which Wine handles through Wine Mono. Fedora’s wine metapackage installs wine-mono through DNF, so Fedora package users often do not see a separate Mono prompt during first setup.

Verify the Fedora package state with:

rpm -q wine-mono

Fedora 44 currently reports:

wine-mono-10.4.1-2.fc44.noarch

If a WineHQ install or a custom prefix shows an error such as wine mono is not installed, run the matching winecfg command for that Wine build and allow the Mono installer prompt to complete.

Use Winetricks with Fedora Repository Wine on Fedora Linux

winetricks is a utility designed to simplify installing additional libraries, fonts, and configurations needed to run Windows applications on Wine. Fedora’s packaged Winetricks fits the Fedora repository Wine method because the package depends on Fedora wine-common. Skip this Fedora package while using WineHQ channel packages unless a future DNF transaction preview shows the conflict has been resolved.

Install Winetricks on Fedora

Install winetricks on your Fedora system when you are using Fedora’s repository Wine packages:

sudo dnf install winetricks

Verify winetricks is available:

winetricks --version

The version output confirms winetricks is ready for use.

20260125

Launch Winetricks on Fedora

Launch winetricks to access its graphical interface:

winetricks

The interface displays a menu where you can browse and install components needed by Windows applications:

• Core Fonts: Add common Windows fonts like Arial and Times New Roman to fix missing characters in applications. For system-wide Microsoft font installation, see how to install Microsoft fonts on Fedora.
• Libraries: Install DirectX, Visual C++ redistributables, or .NET Framework for compatibility with demanding software.
• Graphics Settings: Configure virtual desktops, tweak rendering options, or improve performance for specific applications.

Why Use Winetricks with Wine?

Winetricks is most useful when an application’s compatibility notes name a specific component, such as a Visual C++ runtime, DirectX DLL, or font package. Avoid installing random components into every prefix because unnecessary overrides can make troubleshooting harder.

Example: Install Notepad++ Windows Application on Fedora Linux

Notepad++ gives you a small graphical Windows installer for testing Wine on Fedora before moving on to larger applications or launchers.

Step 1: Download the Notepad++ Installer

Visit the official Notepad++ website and download a Windows .exe installer file.

Step 2: Run the Installer with Wine

Navigate to the directory where the installer is saved, then launch it with Wine. Replace /path/to/installer.exe with the file’s location:

wine /path/to/installer.exe

Alternatively, right-click the .exe file, select Open With, and choose Wine Windows Program Loader.

Step 3: Follow the Installation Wizard

The Windows-style installation wizard will appear. Proceed through the prompts to complete the installation, accepting the default options unless you have specific preferences.

Step 4: Launch Notepad++

After installation completes, run Notepad++ from its Wine prefix path:

wine ~/.wine/drive_c/Program\ Files\ \(x86\)/Notepad++/notepad++.exe

Additionally, you may create a desktop shortcut or add the application to your system menu for easier access.

Step 5: Verify Installation Success

Open Notepad++ and test its features, such as editing text or coding. Confirm that the application functions as expected, then customize settings if needed.

Manage and Update Wine on Fedora Linux

Wine management on Fedora usually means creating separate prefixes for older applications, updating through DNF, and removing package or user-prefix data without mixing Fedora and WineHQ sources.

Create a Dedicated 32-bit Wine Prefix on Fedora

Certain older Windows applications require a 32-bit Wine setup. Create a separate prefix so the 32-bit environment does not overwrite your default ~/.wine prefix:

export WINEARCH=win32

Set the prefix path in the same terminal session:

export WINEPREFIX=~/.wine32

Launch Wine configuration to initialize that 32-bit prefix:

winecfg

Use that same WINEPREFIX value whenever you install or run applications inside the 32-bit prefix.

Update Wine on Fedora

Fedora repository Wine packages and WineHQ repository packages both update through DNF. Refresh metadata and apply updates with:

sudo dnf upgrade --refresh

DNF updates the installed Wine packages along with other available system updates. If you use WineHQ and want to check only that source first, run dnf repoquery --repo=WineHQ --latest-limit=1 winehq-stable winehq-staging winehq-devel before upgrading.

Remove Wine on Fedora

Remove the package source you actually used, then decide whether to remove Wine prefixes from your home directory. Package removal does not delete Windows applications installed inside ~/.wine.

Remove WineHQ Packages and Repository

For Wine installed through WineHQ, remove the channel package you installed. Remove the stable channel with:

sudo dnf remove winehq-stable

Remove the staging channel with:

sudo dnf remove winehq-staging

Remove the development channel with:

sudo dnf remove winehq-devel

Remove the WineHQ repository file after removing WineHQ packages:

sudo rm -f /etc/yum.repos.d/winehq.repo

Verify the repository no longer appears in DNF:

dnf repo list --all | grep -i winehq || echo "WineHQ repository removed"

WineHQ repository removed

If DNF imported the WineHQ signing key during package installation and you no longer use WineHQ repositories, remove the matching RPM key by its current WineHQ fingerprint:

winehq_fingerprint=D43F640145369C51D786DDEA76F1A20FF987672F
winehq_key_id=$(printf '%s\n' "$winehq_fingerprint" | tr '[:upper:]' '[:lower:]')

if rpm -q gpg-pubkey --qf '%{VERSION}-%{RELEASE}\n' | grep -Ei "^${winehq_key_id}-" >/dev/null; then
  sudo rpmkeys --delete "$winehq_fingerprint"
  rpm -q gpg-pubkey --qf '%{VERSION}-%{RELEASE}\n' | grep -Ei "^${winehq_key_id}-" || echo "WineHQ key removed"
else
  echo "WineHQ key is not installed"
fi

WineHQ key is not installed

Remove Fedora Repository Wine Packages

For Wine installed from Fedora’s repositories, remove the Fedora packages you installed:

sudo dnf remove wine

If you installed 32-bit support, remove that package too:

sudo dnf remove wine.i686

Verify the package removal state:

rpm -q wine wine.i686 || true

package wine is not installed
package wine.i686 is not installed

Remove Winetricks (Optional)

If you installed Winetricks, remove it separately:

sudo dnf remove winetricks

Remove Wine User Data

These commands permanently delete Wine configuration files, installed Windows applications, and any data stored within Wine’s virtual Windows environment. Export or backup important data before proceeding.

Remove Wine’s default prefix directory containing Windows applications and settings:

rm -rf ~/.wine

Remove Wine cache and generated desktop entries:

rm -rf ~/.cache/wine ~/.local/share/applications/wine*

If you created the 32-bit prefix during compatibility setup, remove it separately:

rm -rf ~/.wine32

List any other custom prefixes before deleting them:

find ~/.local/share/wineprefixes -mindepth 1 -maxdepth 1 -type d -print 2>/dev/null

Troubleshoot Wine Issues on Fedora Linux

Windows applications can fail through Wine because of dependencies, graphics, audio, or package-source conflicts. Start with the symptom that matches your error, then apply the narrowest fix.

WineHQ Installation Fails with wine-core Conflicts

When switching from Fedora’s Wine packages to WineHQ, dnf can fail because Fedora’s wine-core packages remain installed even after removing wine and wine.i686.

Failed to resolve the transaction:
Problem: problem with installed package
  - installed package wine-core-11.0-3.fc44.x86_64 conflicts with wine-core provided by winehq-stable...
You can try to add to command line:
  --allowerasing to allow removing of installed packages to resolve problems

Check which Wine-related packages are still installed:

rpm -qa 'wine*' | sort

wine-common-11.0-3.fc44.noarch
wine-core-11.0-3.fc44.i686
wine-core-11.0-3.fc44.x86_64
wine-filesystem-11.0-3.fc44.noarch

Install the WineHQ package with --allowerasing so dnf can replace the conflicting Fedora components automatically:

sudo dnf install winehq-stable --allowerasing

Use the same --allowerasing option for winehq-staging or winehq-devel. DNF may also remove winetricks during this replacement, so reinstall it afterward if needed.

Wine or winecfg Command Not Found After WineHQ Installation

WineHQ on Fedora installs binaries under /opt/wine-*/bin, so you may see a command not found error for wine or winecfg immediately after installation.

bash: wine: command not found

Confirm whether wine is available on PATH:

command -v wine || echo "bash: wine: command not found"

bash: wine: command not found

Use the channel-specific path directly or export it for the current shell session. For one-off configuration, run /opt/wine-stable/bin/winecfg directly; the stable channel uses this path for shell access:

export PATH="/opt/wine-stable/bin:$PATH"
wine --version

wine-11.0

Fix Missing 32-bit Libraries in Wine

If a Windows application fails to launch with errors about missing libraries, you may need 32-bit Wine support:

wine: Bad EXE format for Z:\path\to\application.exe

Typically, this error means a 32-bit application requires 32-bit Wine libraries. First, confirm the 32-bit package is missing:

rpm -q wine.i686

package wine.i686 is not installed

To resolve it, install 32-bit support:

sudo dnf install wine.i686

Verify installation, then retry launching the application:

rpm -q wine.i686

wine-11.0-3.fc44.i686

Fix Wine Application Crashes or Visual Glitches

Graphics-intensive applications may crash or display incorrectly due to missing DirectX or graphics driver issues:

err:module:import_dll Library d3dx9_43.dll (needed by L"Z:\\path\\game.exe") not found

For Fedora repository Wine with Winetricks installed, check whether DirectX and Visual C++ components are already installed:

winetricks list-installed | grep -E 'd3dx9|vcrun2015' || echo "d3dx9/vcrun2015 missing"

d3dx9/vcrun2015 missing

Install the required components with Winetricks:

winetricks d3dx9 vcrun2015

Confirm the components are registered, then retry the application. If you use WineHQ packages, avoid installing Fedora’s winetricks package while the WineHQ channel remains installed because it can reintroduce Fedora wine-common conflicts.

winetricks list-installed | grep -E 'd3dx9|vcrun2015'

d3dx9
vcrun2015

For persistent visual glitches, enable virtual desktop mode in winecfg under the Graphics tab. This contains the application in a fixed-size window and often resolves rendering issues. If you have an NVIDIA GPU and experience poor gaming performance or rendering problems, ensure you have proper drivers installed by following how to install NVIDIA drivers on Fedora.

Fix Audio Not Working in Wine

When you hear no sound in Wine applications, you may see errors about missing devices:

ALSA lib pcm_dmix.c:1108:(snd_pcm_dmix_open) unable to open slave

Verify PipeWire or PulseAudio is active and a default sink is set:

pactl info | grep -E "(Server Name|Default Sink)"

Relevant output includes a PipeWire-backed server name and a default sink:

Server Name: PulseAudio (on PipeWire)
Default Sink: alsa_output.pci-0000_00_1f.3.analog-stereo

Next, open winecfg and select the matching audio driver under the Audio tab, then use Test Sound to confirm output. A successful test plays the chime without new audio errors.

winecfg

If testing fails, check that your system audio is working outside Wine with standard Linux applications before retrying.

Useful Wine Resources and Support

Use these official Wine resources when you need compatibility reports, upstream documentation, or a place to check known issues before troubleshooting further.

For related Fedora guides, use Steam on Fedora for Linux-native and Proton-managed games, or PlayOnLinux on Fedora if you want a graphical Wine prefix manager.

• WineHQ Help Center: General Wine documentation and support starting point.
• WineHQ Forums: Community troubleshooting and user discussions for application-specific problems.
• WineHQ Bug Tracker: Check known bugs or report reproducible issues.
• Wine Application Database (AppDB): Compatibility reports for Windows applications, including version-specific notes and workarounds.
• Wine GitLab Wiki: Upstream technical documentation and platform-specific guidance.

Conclusion

Wine on Fedora works best when you choose one package source and keep the related commands consistent. Start with Fedora’s wine metapackage for the simplest maintenance path, add wine.i686 when 32-bit Windows software needs it, and switch to WineHQ only when a specific application benefits from upstream stable, staging, or development builds. Winetricks is most useful as a targeted compatibility tool after Wine itself is installed and verified.