Protontricks lets you run Winetricks commands against a Steam game’s Proton environment. It is useful when a particular game needs an additional Windows runtime, DLL, or Wine setting. The important part is targeting the correct game and applying the fix that game actually needs.
For this source installation, I use pipx to keep Protontricks in its own Python environment. Protontricks itself is a Python application: its build configuration uses setuptools, so there is no separate make step for the tool.
Updated: 24 October 2026. The latest published release on PyPI is 1.15.0, released on 4 October 2026. A checkout of the development branch can include changes beyond that release.
Choose a method · Install from source · Use Protontricks · Updates · Flatpak · Troubleshooting
What Protontricks does
A Proton prefix is the game’s Windows-style environment, including its registry and installed Windows components. Protontricks selects that environment for Winetricks instead of leaving you to assemble the relevant Wine commands yourself.
The maintained project is Matoking/protontricks, a fork of the original project by Sirmentio. The 1.15.0 changelog includes ARM64 Proton support, improved Steam Linux Runtime 4.0 handling, and support for forwarding Winetricks arguments through the GUI using --.
Choose the installation method
The project recommends distro packages where suitable, Flatpak, or pipx. Choose one installation route. The main walkthrough below uses a local Git checkout with pipx.
| Method | When it fits |
|---|---|
| Distro package | You want the distribution to manage Protontricks and its dependencies. Check that its Protontricks and Winetricks versions are recent enough. |
| Flatpak | You use Flatpak Steam or want the recommended Steam Deck route. See the separate commands below. |
| PyPI release with pipx | You want the published Python package: pipx install protontricks. Skip the Git checkout steps. |
| Source checkout with pipx | You want to install the repository’s code, inspect it, or work on local changes. |
The upstream installation guide explains these options. A Python installation through pipx still needs external tools such as Winetricks and the GUI helper installed separately.
1. Prepare Steam and Python
- Use a currently maintained Linux distribution and a working Steam installation.
- Install the game, select its Proton compatibility tool in Steam, and launch it through Proton at least once. This creates the environment Protontricks needs to find.
- Close the game before applying a runtime or settings change.
- Install Git, pipx, Winetricks, and either YAD or Zenity for the GUI. The package commands below use Zenity.
Protontricks declares Python 3.7 or newer, while the current upstream pipx documentation requires Python 3.11 or newer. Older distro-packaged pipx versions can have different requirements. Use a supported Python version suitable for the pipx version you install.
python3 --version
2. Install the supporting packages
Run the block for your distribution. These commands install the supporting tools; Protontricks itself is installed from source in the next section.
Debian / Ubuntu
sudo apt update
sudo apt install git pipx python3-pip python3-setuptools python3-venv winetricks zenity cabextract
Fedora
sudo dnf install git pipx python3-pip python3-setuptools python3-libs winetricks zenity cabextract
Arch Linux
sudo pacman -Syu git python-pipx python-pip python-setuptools python-virtualenv winetricks zenity cabextract
Package availability depends on your enabled repositories and release. Winetricks is packaged by Fedora, and Arch calls its pipx package python-pipx. If your distro’s Winetricks is too old for the required fix, use its supported update route or the Winetricks project’s installation instructions.
3. Make pipx commands available in your shell
pipx ensurepath
Close and reopen your terminal afterwards so the updated PATH takes effect.
pipx --version
If you already installed Protontricks through another route, check what your shell will run before adding another copy:
type -a protontricks
pipx list
4. Clone and install Protontricks from source
The following commands create the checkout at ~/src/protontricks. If that directory already contains your checkout, use the update section instead of cloning over it.
mkdir -p "$HOME/src"
git clone https://github.com/Matoking/protontricks.git "$HOME/src/protontricks"
cd "$HOME/src/protontricks"
pipx install .
The final dot means “install the project in this directory.” pipx builds and installs it inside an isolated environment, then exposes its commands to your user account. Run this command as your normal user.
Optional: editable mode for development
If you are working on the Python code, use this instead of the regular install command:
pipx install --editable .
Editable mode points at your local checkout so code edits can be used directly. It does not fetch Git changes automatically. Keep the checkout in place; changes to dependencies or package metadata can still require a reinstall. The pipx command reference documents the installation options.
5. Check the installation and desktop launcher
protontricks --version
protontricks --help
winetricks --version
For the application-menu entry and launcher integration, run:
protontricks-desktop-install
Then open the game-selection interface:
protontricks --gui
The desktop instructions also cover opening an external Windows executable through Protontricks Launcher.
6. Find the correct game and apply a specific fix
List games for one Steam installation:
protontricks -l
With Protontricks 1.14.0 or newer, you can list games across all detected Steam installations:
protontricks -L
You can also search by name. For example, if Fallout 4 is installed:
protontricks -s "Fallout 4"
The results show Steam AppIDs. Use the ID of the game you intend to change. Protontricks’ command-line implementation documents these flags and passes the actions after the AppID to Winetricks.
Example: a fix that specifically requires vcrun2019
The vcrun2019 verb installs Microsoft Visual C++ 2015–2019 libraries. Use it when a game-specific fix calls for those libraries. The following Bash example prompts for the AppID from your game list:
read -r -p "Steam AppID from the Protontricks list: " protontricks_appid
protontricks "$protontricks_appid" vcrun2019
The verb is listed in the Winetricks DLL catalogue. After installation, launch the game again to check whether the original problem is fixed.
Put Protontricks-specific flags before the AppID. Arguments after the AppID belong to Winetricks.
7. Update or remove this installation
Update a local source checkout
cd "$HOME/src/protontricks"
git pull --ff-only
pipx reinstall protontricks
protontricks --version
This updates the tracked branch, then reinstalls from the original local source location. It applies to the checkout-based installation above. The pipx management guide explains that reinstalling rebuilds the environment from its recorded installation metadata.
If you have local code changes or switched to a detached release tag, handle that Git state before updating the branch.
Update a PyPI installation
For the separate route installed with pipx install protontricks, use:
pipx upgrade protontricks
Remove the pipx-installed tool
pipx uninstall protontricks
This removes the pipx environment and its command links. It does not uninstall your Steam games or delete their Proton prefixes.
Flatpak Steam and Steam Deck
The Protontricks Flatpak package supports both native and Flatpak Steam. For Flatpak Steam, follow this route; it is also the project’s recommended Steam Deck option. Install Flatpak and configure Flathub first using the official setup instructions.
flatpak install flathub com.github.Matoking.protontricks
flatpak run com.github.Matoking.protontricks --gui
To list games without adding a shell alias:
flatpak run com.github.Matoking.protontricks -l
For an additional Steam library on another drive, give Protontricks access to that library’s actual directory. This Bash example asks for the full path:
read -r -p "Full Steam library directory: " protontricks_library
flatpak override --user --filesystem="$protontricks_library" com.github.Matoking.protontricks
Use the directory containing that library’s steamapps folder. The same permission issue can affect external EXEs that need files outside the sandbox’s existing access. The package’s configuration instructions explain the filesystem permissions.
Troubleshooting
“Command not found”
Run pipx ensurepath, open a new terminal, and check pipx list. Use type -a protontricks to spot an older executable or Flatpak alias taking precedence.
“Found no games” or an AppID cannot be found
Launch the Windows version of the game through Proton at least once. Check which Steam installation you selected, use -L when appropriate, and check additional-drive permissions for Flatpak. Protontricks is looking for Proton-compatible game environments; a native Linux game does not need a Windows runtime installed into it.
“Externally managed environment”
This is Python packaging protection used by modern distributions. Keep application packages in a virtual environment or use pipx, as described by the Python Packaging Authority specification. The pipx installation above keeps Protontricks separate from the distro-managed Python environment.
“Unknown arg” or “Unknown option”
Check the spelling of the Winetricks verb and whether your Winetricks version supports it. Also check argument order: Protontricks options go before the AppID. The upstream troubleshooting page covers both cases.
A warning about a 64-bit WINEPREFIX
Proton uses 64-bit prefixes. The upstream troubleshooting guide says this warning alone can be ignored when the command otherwise works. Check for an actual failing step before treating the warning as the cause.
Get useful diagnostic output
protontricks -vv --gui
When asking for help, include your Protontricks and Winetricks versions, distro, Steam installation method, selected Proton version, and the actual error output. Those details make it much easier to identify which part of the setup needs attention.
