- Top Pick: Keychron V3 Wired Mechanical Keyboard (Knob Version)
- Runner-up: Samsung T9 Portable SSD 2TB
- Also consider: Logitech G502 HERO Gaming Mouse
Every Wine user eventually meets the game that almost runs: the launcher opens, the menu renders, and then a missing DLL error ends the evening. The component the game wants is usually a standard Microsoft library Wine cannot ship for licensing reasons, and fetching it by hand is a chore of installers and fake Windows folders. Winetricks compresses that whole chore into one word.
Winetricks is a single shell script, maintained by Austin English and released under the GNU Lesser General Public License, that downloads genuine Windows components from their original sources and installs them into a Wine prefix using named recipes called verbs. Nearly every Linux gaming frontend either bundles it, calls it or imitates it. This guide covers installing it, aiming it at the correct prefix, the verbs most players actually need, and the one place it should never be pointed: a Steam-managed Proton prefix.
As an Amazon Associate, we earn from qualifying purchases.
Quick answer
Winetricks is a single shell script that installs genuine Windows DLLs, runtimes and fonts into a Wine prefix using named recipes called verbs. Install it from your distribution or as the self-updating script, aim it at one prefix at a time, and add only the verb a game error or guide names. Keep it away from Steam Proton prefixes; Protontricks is the tool built for those.
What Winetricks is, and what it is not
The project’s own description is plain: Winetricks is an easy way to work around problems in Wine. Each recipe is a verb, a short name such as vcrun2022 that stands for a tested sequence of downloading the real Microsoft package, verifying it against a recorded checksum, extracting it and registering the pieces inside the prefix.
Just as important is what the script is not. It is not a Wine replacement, a compatibility layer or a launcher; it changes nothing until you name a verb. Its everyday job is narrower than its apps and games categories suggest: adding the one runtime or font a specific title is missing. And it is not a tool for modifying Proton prefixes, a boundary covered below.
Installing Winetricks: the package or the script itself
The project recommends the packaged version when one is available and current. Packages exist for most mainstream systems, including Arch, Debian, Fedora, Gentoo and Ubuntu, so first check your distribution’s repository. One pointed exception: packaged Debian and Ubuntu versions are typically outdated, and a manual installation is recommended there instead, because a stale verb can fetch the wrong file.
The manual route treats Winetricks as what it is, one script. Download the latest stable release and run its make install step, or fetch the current script directly and place it on your path with the executable bit set. The README is blunt about sequencing: uninstall any packaged copy first, or you get to pick up the pieces. A scripted install can then update itself with the documented self-update command. Some verbs lean on helper programs, so cabextract, unzip, unrar and a 7z tool are worth having.
Aim it at the right prefix first
Everything Winetricks does lands inside one Wine prefix, the fake Windows drive Wine builds for a program, and which prefix receives the verb is decided before the verb runs. With no direction, Winetricks works on the default prefix, the .wine folder in your home directory, which is exactly right for a game run through plain Wine. The WINEPREFIX environment variable is the documented way to point it elsewhere, and its own prefix selector places a named prefix under the wineprefixes folder inside your local share directory.
Two companion selectors matter for older games. An architecture selector, given before the prefix selector, creates a 32-bit or 64-bit prefix; it cannot retrofit the default prefix, and 32-bit remains the safer home for many disc-era releases. The isolate option gives each app or game its own bottle, so one title’s workaround can never leak into another’s. Confirm the prefix first, then run the verb: most Winetricks horror stories are stories about a correct verb in the wrong prefix.
The graphical face and the command line
Run Winetricks with no arguments and it opens a graphical window, built on Zenity or Kdialog depending on what your desktop provides. The window walks you through choosing a prefix, then offers the categories as menus, the friendliest way to browse what exists: the dlls, fonts and settings lists become clickable entries rather than memorised names.
The command line earns its keep for repeat work. Listing commands show the verbs in each category, which download automatically, which need a manual download step, and which are already installed in the current prefix. The unattended flag installs without asking questions, which is how frontends drive it. A documented last resort deletes everything inside a stuck prefix; use it only after your saves are copied somewhere safe.
The verbs readers actually need
Start from the error, not from a shopping list. A crash dialog or a ProtonDB report names the missing piece, and the verb almost always shares that name. In the dlls category the recurring cast is small. The Visual C++ runtime verbs, running from the 2005 release through vcrun2022, answer the most common missing-library errors in modern games. The DirectX helper verbs d3dx9 and d3dx11_43 supply the legacy D3DX libraries older titles were built against, while d3dcompiler_47 provides the shader compiler many engines expect. The dotnet48 verb installs the .NET Framework 4.8 that launchers and mod managers frequently demand. Around those sit xact for the old XACT audio stack, physx for the standalone PhysX package, and quartz for the DirectShow components behind some game videos.
The fonts category solves a different failure class: launchers that render as blank boxes or mangled text are often simply missing the Windows core fonts. The corefonts verb installs that standard set in one pass, and tahoma covers the interface font many older tools assume exists. In settings, the win10 verb sets the prefix’s reported Windows version, which some installers check before proceeding, and the sandbox verb cuts the prefix off from parts of your home folder. One caution: the dxvk verb is for plain Wine setups; Proton already chooses its games’ translation layers.
The Proton warning, and the Protontricks boundary
Steam builds one prefix per game inside its compatdata folders and manages those prefixes as part of the platform. Proton versions change, Steam verifies and repairs game files, and a prefix that no longer matches what the configured Proton build expects can be regenerated or left inconsistent. Running raw Winetricks against such a prefix edits a managed environment with an unmanaged tool: it uses your system Wine rather than the game’s assigned Proton build.
That gap is why Protontricks exists: a wrapper that feeds Winetricks verbs to one Steam game’s prefix using that game’s own Proton version, targeted by app ID so a fix for one title cannot leak into another. The folder’s dedicated Protontricks guide covers its use. Plain Wine prefixes, Lutris bottles and hand-built prefixes belong to Winetricks; prefixes Steam created belong to Protontricks. When in doubt, ask who created the prefix, and use that creator’s tool.
Prefix hygiene rules that prevent most damage
A few habits keep Winetricks boring, which is the goal. Keep one demanding game per prefix, so a workaround stays quarantined. Add one verb at a time and launch the game between additions; stacking five guesses at once leaves you unable to say which helped and which hurt. Back up the prefix folder before surgery on a game with hours of progress in it. Check the installed list before reinstalling anything, use the force flag only when a component is genuinely broken, and keep the script current.
Gear for long prefix sessions
Keychron V3 Wired Mechanical Keyboard (Knob Version)
A tenkeyless wired board suits terminal work: the knob handles volume between log reads, and QMK and VIA remapping runs on Linux.
Specs:
- Layout: tenkeyless, wired USB-C connection
- Polling rate: 1,000 Hz with N-key rollover, maker listed
- Switches: Keychron K Pro Brown, hot-swappable, 3-pin and 5-pin MX support
- Firmware: QMK and VIA programmable, including the knob
Samsung T9 Portable SSD 2TB
Prefix libraries and download caches move between machines far more easily on a fast external drive; the T9 carries a game library and every prefix backup in one pocketable drive.
Specs:
- Capacity: 2 TB, model MU-PG2T0B/AM
- Interface: USB 3.2 Gen 2×2 over USB-C
- Maker-rated sequential reads up to 2,000 MB/s, requiring a host port of the same generation
- Drop resistance: maker rated to 9.8 feet
Logitech G502 HERO Gaming Mouse
Rebuilding prefixes involves a lot of log scrolling and save-folder archaeology; the G502 HERO brings a precise sensor and eleven buttons for binding shortcuts.
Specs:
- Sensor: HERO 25K optical, maker rated to 25,600 DPI
- Buttons: 11 programmable
- Weight: five optional 3.6 g weights included, maker listed
- Connection: wired USB
Valve Steam Deck OLED 512GB
The Deck is where the Winetricks boundary matters most: its SteamOS prefixes are Steam-managed, while desktop mode still runs plain Wine and frontends.
Specs:
- Display: 7.4-inch HDR OLED, 1280 by 800
- Storage: 512 GB NVMe SSD, microSD expansion
- Wireless: Wi-Fi 6E, Bluetooth
How to choose your approach
Choose the distribution package when it is current, and the self-updating script when it is not, particularly on Debian and Ubuntu, where the documentation itself warns the packages lag. Choose the graphical window for exploring an unfamiliar prefix and the command line once you know the verb you need. Choose Winetricks for prefixes you or your frontend created, and Protontricks for anything under Steam’s compatdata. Above all, choose restraint: the right number of verbs is the smallest set that makes the named error go away.
Who should skip Winetricks
Skip it if every game you play comes from Steam and already works, because Proton ships its own component handling and there is nothing for Winetricks to add. Skip it if you only use Bottles or Lutris and have never needed a component their built-in dependency tools lack. Skip it, firmly, as a tool for editing Steam’s prefixes directly. And never install runtimes before a game has actually asked for one; an untouched prefix that works beats a decorated one.
FAQ
Is Winetricks safe to run on my main prefix?
It changes only what the named verb changes, and its verbs are checksum-verified downloads. The real risk is aim, not malice: confirm the selected prefix first, and back up prefixes holding save files.
Why did a verb fail with a checksum or download error?
Usually because the upstream file moved or your copy of the script is old. Update Winetricks first, since verbs are revised as Microsoft relocates packages, then try again. The listing commands also mark which verbs need a manual download step.
Can Winetricks fix a Steam game that will not launch?
Not directly. Steam prefixes are managed by Proton, and the supported route for adding a component to one is Protontricks, which applies the same verbs through the game’s own Proton build.
What is the difference between a verb and a category?
A category is a shelf: dlls, fonts, settings, apps, games and benchmarks. A verb is one item on the shelf, a named recipe such as corefonts or vcrun2022 that installs one component or applies one setting.
Final verdict
Winetricks endures because it solves a narrow problem completely: a Windows game on Linux is missing a genuine Microsoft component, and one named verb installs that component correctly into the prefix you point it at. Learn the short list of runtime, DirectX and font verbs, keep the script updated, respect the Proton boundary, and it becomes the quietest tool in your setup, forgotten between fixes.










