Running Windows software on Fedora 45: Wine 11.0 costs 592 MiB to install

Wine works on Fedora, but price it before you start.

What the repository has

dnf list --available wine

wine.x86_64    11.0-3.fc44    fedora

Note the fc44 suffix: this package was built for Fedora 44 and shipped in the F45 repository. It works, but it is not a rebuild for this release.

dnf info wine

Version        : 11.0
Release        : 3.fc44
Summary        : A compatibility layer for windows applications

It is not installed by default:

rpm -q wine

package wine is not installed

What installing actually costs

Measured transaction:

sudo dnf install --assumeno wine

Installing:       147 packages
Total size of inbound packages is 592 MiB. Need to download 592 MiB.

147 packages and 592 MiB of downloads. That is the first number to look at — Wine is not something to install casually.

Caution

592 MiB is the download alone; the installed footprint is larger. If you need exactly one program, confirm it runs under Wine before paying that size.

Using it

sudo dnf install wine
wine --version

The first Windows program you launch creates a prefix (an emulated C: drive):

winecfg

The default location:

~/.wine/drive_c/

winecfg opens the configuration UI for the Windows version, drive mapping, display and audio. It needs a graphical session — it cannot run on a headless server.

Isolate programs with separate prefixes

Keep unrelated programs apart so they cannot pollute each other:

WINEPREFIX=~/.wine-app1 wine program.exe

WINEPREFIX decides which isolated environment the program sees.

Everyday commands

Command	Purpose
wine program.exe	run a program
winecfg	configuration UI
wine uninstaller	uninstall installed programs
wineserver -k	kill all Wine processes
WINEPREFIX=... wine ...	use a specific prefix

Judging compatibility

Compatibility is per program; there is no blanket “Wine supports Windows software”. Check in this order:

1. Look the program up in Wine’s AppDB and read its rating (Garbage / Bronze / Silver / Gold / Platinum)
2. Below Silver usually means DLL overrides or registry tweaks
3. When extra components are needed, install them with winetricks (fonts, runtimes, .NET and so on)

Note

Wine needs somewhere to create a window. On a machine with no graphical session you can only run console programs or tunnel X11; GUI tools such as winecfg fail outright.

When not to use Wine

Situation	Better option
a native Linux build exists	use the native build
ordinary Windows office software	a virtual machine (GNOME Boxes, virt-manager)
exact Windows behaviour required	a virtual machine, do not gamble on Wine
one small tool	check AppDB first, only proceed for Platinum or Gold

Wine’s value is running Windows programs without Windows. Once you are repeatedly adjusting DLLs and the registry for one application, a virtual machine is cheaper in time.

Common traps

Symptom	Cause
winecfg will not open	no graphical session
program exits immediately with no output	missing runtime in the prefix; add it with winetricks
Chinese text shows as boxes	the prefix lacks CJK fonts
an upgrade broke an old program	the prefix was upgraded underneath it; use a separate WINEPREFIX
download much larger than expected	147 packages and 592 MiB is normal

Related pages

• Podman in practice — another way to run Windows software
• Editors — desktop tool selection
• Official: Wine AppDB