Dennis HilkLinux diagnosticsDE

Linux Gaming Repair Center

Proton game on NTFS fails to create its prefix

Identify unsupported shared-library layouts and protect saves before migrating.

Editorial source review: Open the diagnostic assistants
On this page
  1. Identify the failing layer
  2. Collect discriminating evidence
  3. Compare safely and record limitations
  4. Gather evidence
  5. A controlled test
  6. Related diagnostics
  7. Sources & limitations

Identify the failing layer

Sharing one NTFS Steam library between Windows and Linux is not an equivalent replacement for a native Linux filesystem. Valve's Proton wiki prominently warns that its NTFS instructions are community-maintained, not an official recommendation, and can be associated with data loss. Compatibility prefixes have Unix filesystem expectations, including links and naming behavior. A game download completing on NTFS does not establish that its Wine prefix can be created there safely.

Collect discriminating evidence

Determine which partition holds the game files, steamapps/compatdata and shadercache. An external drive might be writable but use different case-handling or mount options, and Windows Fast Startup can leave a shared volume in an unsuitable state. Capture the Proton log and the exact failed path before considering relocation. Never delete compatdata or make blind symlinks: those directories may contain local saves, configuration, credentials and launcher state.

Compare safely and record limitations

The conservative comparison is a backed-up installation or test game on a native Linux filesystem, with compatibility data stored there. Keep the original disk untouched while testing the alternative and retain a record of Steam's library selection. If the error disappears, that supports a filesystem- or layout-sensitive failure but cannot identify which NTFS feature failed. Forcing world-writable mount options does not repair missing Unix semantics or establish data safety.

Gather evidence before changing the system

Run one command at a time in the relevant host or game environment. Read its requirements and interpretation first. The website displays commands and never runs them.

Read-only observation

lsblk -f

Requirements: Run in the relevant host/session; compare with the actual game environment and redact private paths before sharing.

Identify the filesystem types; volume labels alone do not prove the game location.

Read-only observation

findmnt -t ntfs,ntfs3,exfat

Requirements: Run in the relevant host/session; compare with the actual game environment and redact private paths before sharing.

List mounted shared filesystems and compare with Steam's actual library path.

A controlled test with a way back

Back up saves and prefix first; compare one affected game installed on an ext4 or btrfs library without modifying the shared NTFS original.

Rollback: Switch back to the prior Steam library; do not remove either prefix without checking saves.

What this test cannot establish: A successful Linux-filesystem test narrows hypotheses but does not imply every NTFS deployment fails.

Sources and scope

This editorial review uses primary project and distribution references. It does not establish that a fix has been reproduced on your hardware. Installed versions, the game runtime and the selected graphics API can change the result.