← Back to the stories
Games Linux

Counter-Strike: Source on Linux: Native Steam, Wine and the 2011 Guide

Windows Steam inside Wine remains a separate option for people who prefer that setup. The useful part of the old launcher script is still the same: select the correct Wine prefix, run its Steam client and request AppID 240.

Updated: 25 October 2026. This covers Counter-Strike: Source. The version dated 2 January 2022, 06:08 links back to an article published on 16 October 2011.

What changed · Native Linux · Windows Steam in Wine · Launch script · Proton and VAC · Archived method

What changed since the original guide

The 2011 article by tehcakeswineblog describes a test using Fedora 14 and Wine 1.3.30. It also lists Microsoft fonts, the Visual C++ 2005 x86 runtime and TransGaming Mozilla Control among its prerequisites. Those requirements describe that author’s old setup.

Valve was already publishing Linux-specific CS:S fixes in March 2013. The current Steam listing still offers Linux support, and Valve’s 18 February 2025 update added 64-bit binaries, borderless window mode and interface scaling for high-resolution displays.

SetupWhat runs
Native Linux SteamSteam launches the Linux build of CS:S.
Linux Steam with Proton forced for CS:SSteam launches the Windows build through Proton, using the game’s compatibility environment.
Windows Steam inside Wine or LutrisThe Windows Steam client and game use that Wine installation’s prefix and runner.

These setups have different executables, runtime settings and logs. Keep the selected route consistent while investigating a problem.

Option 1: use the native Linux build

  1. Install the Linux Steam client using the appropriate package for your distribution. Valve’s Steam download page provides its official download.
  2. Sign in to the account that has CS:S, then install the game from the Library.
  3. If you previously forced Proton for this title, remove that per-game override under Properties → Compatibility to return to the Linux build. Let Steam finish any required file updates.
  4. Launch the game, load a map with bots and then test the server you actually want to join.

A Steam Linux Runtime selection runs Linux software inside Valve’s runtime environment. Selecting Proton instead requests the Windows game through a compatibility layer.

If the steam command launches your Linux Steam client, you can request CS:S from a terminal with:

steam -applaunch 240

This uses the game’s existing Compatibility selection. The command itself does not override that setting.

Option 2: install Windows Steam in Wine

Use a maintained Wine build with 64-bit support. Valve’s 2025 CS:S update automatically selects 64-bit binaries on a 64-bit operating system. A fresh 64-bit prefix gives the Windows Steam installation room to run both 32-bit and 64-bit components.

The terminal examples below use ~/Games/steam-css as a new prefix and the wine executable available in that terminal. Keep an existing installation’s actual path if you are maintaining it. A prefix’s architecture is fixed when it is created; changing WINEARCH does not convert an old 32-bit prefix.

1. Create and configure the prefix

mkdir -p "$HOME/Games"
WINEPREFIX="$HOME/Games/steam-css" WINEARCH=win64 winecfg

In Wine Configuration, choose a Windows version supported by the current Steam client, such as Windows 10, then close the window. The old guide’s Windows XP setting is unsuitable for today’s Steam client.

2. Install the current Windows Steam client

Download SteamSetup.exe from Valve’s official Steam page. If it is saved in your Downloads folder, run:

WINEPREFIX="$HOME/Games/steam-css" wine "$HOME/Downloads/SteamSetup.exe"

Complete Steam’s installer and normal sign-in, install Counter-Strike: Source from that Windows client, then test it from its Library. Add dependencies only for an identified failure; do not carry over the entire 2011 prerequisite list automatically.

If Windows Steam is already managed by Lutris

Keep using that entry’s configured Wine prefix and runner. Use Wine tools → Run EXE inside Wine prefix when you need to run the installer in that environment. For a CS:S shortcut based on the same Windows Steam installation, point the entry at its Steam executable and use -applaunch 240 as its arguments.

The standalone script below invokes wine from the shell’s search path. It does not automatically select a different Wine build configured only inside Lutris.

A current version of the launch script

Save this as css-wine.sh. It uses the example prefix above and a Windows Steam path under Program Files (x86). Adjust the prefix and Windows executable path to match your installation.

#!/usr/bin/env bash
export WINEPREFIX="$HOME/Games/steam-css"
export WINEDEBUG=-all

if [[ ! -f "$WINEPREFIX/system.reg" ]]; then
    printf 'Wine prefix not found: %s\n' "$WINEPREFIX" >&2
    exit 1
fi

exec wine 'C:\Program Files (x86)\Steam\Steam.exe' -applaunch 240 "$@"

Make it executable and run it:

chmod u+x css-wine.sh
./css-wine.sh

The final "$@" forwards extra arguments individually. For example:

./css-wine.sh -console

WINEDEBUG=-all suppresses Wine’s diagnostic messages. Remove that line when collecting Wine output for troubleshooting. It is a logging setting, not a repair for a missing component or a failed server connection.

Proton and VAC: test the connection as well as the menu

CS:S uses Valve Anti-Cheat. Valve’s CS:S Proton tracker contains a September 2021 report that the Windows game launched through Linux Steam and Proton started in insecure mode and could not join VAC-protected servers. Adding -secure did not resolve that reported setup.

The issue remained open when checked on 25 October 2026, and also contains a February 2025 report of a launch failure after an update. These are dated compatibility reports, so test the current runner rather than treating the old report as a fresh result.

For ordinary Linux multiplayer, the native build is the direct supported-platform route. The Proton report concerns a Windows game launched by Linux Steam; a Windows Steam installation inside Wine has a different client arrangement. Check server joining in the Wine setup itself before calling it working.

When testing Proton deliberately, select it for CS:S in Steam’s Compatibility settings. For a Proton log, temporarily put this in the game’s Steam launch options:

PROTON_LOG=1 %command%

The default output is ~/steam-240.log. Remove the option after reproducing the problem. This is a Proton logging option, not a logging command for a separate Windows Steam installation in plain Wine.

If the current installation fails

  • Steam itself does not open: record the client error and Wine runner version. Repairing an old Mozilla Control registration is not the starting procedure for a current Steam client failure.
  • The game opens but a server rejects the connection: keep the exact server or VAC message. Reaching the main menu does not test multiplayer authentication.
  • The game stopped working after an update: back up custom files and configurations, then verify the installed files through the Steam client that owns this installation.
  • A script starts the wrong environment: compare its prefix and Wine executable with the launcher that normally works. An installation in another prefix does not repair this one.
  • You need a useful report: keep the game build, native/Wine/Proton route, runner version, first relevant error and server result together. Review private paths before posting logs.

Archived method: 2011 instructions, reposted in 2022

The original method downloaded mozcontrol.tgz, registered mozctlx.dll, installed Steam using SteamInstall.msi, and launched CS:S through Windows Steam. It belongs with a matching legacy Wine environment.

Original itemCurrent handling
TransGaming Mozilla ControlPreserve the registration step as a historical reference, rather than a normal current prerequisite.
SteamInstall.msi over HTTPUse Valve’s current HTTPS download of SteamSetup.exe.
The path .wine/c_driveWine’s usual C: directory is drive_c. Quote paths containing spaces.
Default ~/.wine prefixTarget the prefix that actually contains your Windows Steam installation.
-applaunch 240Still useful for requesting CS:S from the selected Steam client.
WINEDEBUG=-allOptional diagnostic-output suppression. Leave logging available when investigating a failure.

The archived launcher script, with line breaks restored, was:

#!/bin/bash
export WINEPREFIX="$HOME/.wine"
WINEDEBUG=-all wine C:/Program\ Files/Steam/Steam.exe -applaunch 240

The original 2011 source retains the download and registration commands for a matching legacy setup.

References

Leave a Reply

Your email address will not be published. Required fields are marked *