Installing Overwolf into a Proton / umu-launcher prefix on Linux (no Steam)

overwolf-proton-linux-install.md

Installing Overwolf into a Proton / umu-launcher prefix on Linux (no Steam)

Getting the Overwolf client installed into a Wine/Proton prefix driven by umu-launcher, without Steam. The normal Overwolf web installer fails inside Wine; this is the route that actually works.

What you need

• An existing Proton prefix to install into. If you came here from a Warframe/AlecaFrame guide, that's your game's prefix. Otherwise any umu prefix works — you can make a throwaway one by running WINEPREFIX="$HOME/ow-prefix" GAMEID=umu-default STORE=none umu-run wineboot once.
• umu-run on PATH, plus curl and 7z (p7zip) on the host.

Export your prefix details once so the commands below are copy-pasteable (adjust to taste):

export WINEPREFIX="$HOME/Games/Warframe-Proton-Prefix"
export GAMEID="umu-warframe"
export STORE="none"
PFX="$WINEPREFIX/drive_c"

The Windows user inside a Proton prefix is steamuser — app data lives under "$PFX/users/steamuser/AppData/...", not under your Linux username.

1. Install WebView2 first

Overwolf's installer UI is built on Microsoft Edge WebView2, which a fresh prefix doesn't have. Without it the installer just throws an error and quits. Install the Evergreen runtime into the prefix (it runs silently and exits on its own):

curl -fL --compressed -A "Mozilla/5.0 (Windows NT 10.0; Win64; x64)" \
  -o /tmp/WebView2.exe "https://go.microsoft.com/fwlink/?linkid=2124701"

env WINEPREFIX="$WINEPREFIX" GAMEID="$GAMEID" STORE="$STORE" \
  umu-run /tmp/WebView2.exe /silent /install

2. Get the Overwolf installer, but run the inner core

The Overwolf download is a tiny stub that pulls down the real installer and then verifies it — and that verification wrongly fails under Wine ("File did not pass MD5"), even though the download is fine. So skip the stub's broken handoff: let it fetch the payload once, then run the real installer it extracted.

Download and start the stub so it downloads its payload into the prefix:

curl -fL --compressed -A "Mozilla/5.0 (Windows NT 10.0; Win64; x64)" \
  -o /tmp/OverwolfSetup.exe "https://download.overwolf.com/install/Download?Channel=website"

env WINEPREFIX="$WINEPREFIX" GAMEID="$GAMEID" STORE="$STORE" \
  umu-run /tmp/OverwolfSetup.exe

Let it run until it shows the MD5 error (or just give it ~30s), then close it. The real installer is now sitting in the prefix's Temp as a .7z. Extract the core .exe from it:

SEVENZ="$(find "$PFX/users/steamuser/AppData/Local/Temp" -iname OverwolfSetup.7z 2>/dev/null | head -1)"
7z e -y -o"$(dirname "$SEVENZ")" "$SEVENZ" OverwolfSetup.exe
CORE="$(dirname "$SEVENZ")/OverwolfSetup.exe"   # ~450 MB, the actual installer

In this stub's web UI the cursor may be invisible (a Wine/CEF quirk) — it still takes clicks if you need to dismiss it. The core installer in the next step doesn't have this problem.

3. Run the core installer

env WINEPREFIX="$WINEPREFIX" GAMEID="$GAMEID" STORE="$STORE" umu-run "$CORE"

A small, plain Overwolf setup window opens (a basic progress dialog — not the fancy web UI from the stub). Click through it. It installs to C:\Program Files (x86)\Overwolf\ and the window closes itself when done.

4. Launch Overwolf

env WINEPREFIX="$WINEPREFIX" GAMEID="$GAMEID" STORE="$STORE" \
  umu-run 'C:\Program Files (x86)\Overwolf\OverwolfLauncher.exe'

---

Installing a specific app (e.g. AlecaFrame) and getting it to actually read game data is a separate topic — see the AlecaFrame-on-Linux guide.

Tested with: umu-launcher + UMU-Proton 10.0 (Wine 10), Overwolf installer 2.304.x / client 0.304.x, WebView2 Evergreen 149.x. Overwolf's CDN and installer change over time; adapt filenames if needed.

This guide was largely written by AI (Opus 4.8). Every step was run and verified on a live system.