01Separate the Steam directory from the game directory
Most r2modman Steam path problems come from pointing the wrong field at the wrong folder. The manager keeps more than one location setting, and they are not interchangeable. The default Steam directory is C:/Program Files (x86)/Steam, and that folder contains the Steam executable rather than any game executable. The game directory must be the folder holding the game itself. Before editing anything, open Settings, Directories and note what each field currently contains, then decide which one is actually wrong. Changing both values at once hides which one was incorrect and makes it impossible to tell whether the edit helped.
- Steam directory: the folder containing the Steam executable.
- Game directory: the folder containing the game executable.
- C:/Program Files (x86)/Steam is the Steam folder, not a game folder.
02Decode the spawn error literally
The two spawn errors name their own cause. spawn <path> EACCES means the Steam executable requires admin privileges to launch, so restart the manager with elevated privileges and try again. spawn <path> ENOENT means the Steam directory setting is wrong and does not contain the Steam executable at all, so correct that path rather than adding permissions. Read the path printed inside the message: it is the exact file the manager tried to run, and comparing it with the folder you configured usually shows the mistake immediately. The message body is more informative than the error title, which is identical for both cases.
- spawn <path> EACCES: restart the manager with admin privileges.
- spawn <path> ENOENT: the Steam directory holds no Steam executable.
- Use the path in the message as evidence, not the error name.
03Set the game directory from Steam's own file browser
Let Steam define the correct answer. Right-click the game in your library, choose Manage and then Browse local files, and note the folder that opens. In r2modman, select the profile and open Settings, Directories, Change game directory, then choose that same folder. The dialog shows no files because it selects directories, so an apparently empty window is expected. Once the paths match, start modded again. Re-select the folder even when the stored path already looks right, because a stale entry can survive a game being moved. If the paths genuinely matched, move on to loader and launch-option checks.
- Steam: right-click the game, Manage, Browse local files.
- r2modman: Settings, Directories, Change game directory.
- An empty folder-selection dialog is normal, not an error.
04Account for every Steam library
A single Steam installation can hold several libraries, and the game you are modding is not necessarily in the default one. Check Steam's storage settings for the full list of library folders, including any on a second drive, an external disk, or a Steam Deck SD card. Then confirm the path the manager holds points into the library that actually contains the game, rather than into an older copy left behind after a move. If the game was moved between drives, re-select the directory instead of editing the stored path by hand.
- List every library in Steam's storage settings.
- Check secondary, external, and SD card libraries.
- Re-select the directory after a move instead of editing text.
05Point non-Steam games at the executable
For a game that does not run through Steam, the same field means something slightly different: it must resolve to the game executable rather than to a launcher or a store client. Find where the game is actually installed for your store, then set the directory that contains the executable the game starts from. Check that the folder also holds the game's own data files, because the loader is written next to them. Avoid selecting a shortcut, a compatibility prefix, or a parent folder that only holds a launcher, since the manager needs the real game files present.
- Use the installation folder, not a shortcut.
- Select the folder that contains the game executable.
- Confirm the folder holds the game's data files too.
06Failed to start Steam and unlink errors
Two mundane situations produce the Failed to start Steam and unlink errors, and neither is really a path problem. First, the game may still be running: close it completely, including any background process, and start modded again. Second, the manager may have been installed inside the game directory, for example in the Risk of Rain 2 folder. It is an application, not a mod, and it cannot operate correctly from there. Uninstall it and install it somewhere else, because profiles and mods are not lost by moving the application, and confirm the error disappears once it runs from a normal application folder.
- Close the game completely, including background processes.
- Never install the manager inside the game folder.
- Reinstalling elsewhere keeps profiles and mods.
07Flatpak Steam installs a different Steam path
If Steam is installed as a Flatpak, its files live under a sandboxed location rather than the usual home directory path, so a Steam directory copied from a guide will not match. Open the manager through Steam using the AppImage added as a non-Steam game, then set both the game path and the Steam path to the locations your installation actually uses. The game path will resemble a steamapps/common folder inside the Flatpak data directory. Treat the two fields separately, because a path that is correct for a distribution package install is very unlikely to be correct here.
- Flatpak installs use sandboxed paths, not the usual defaults.
- Set the game path and the Steam path as two separate fields.
- Confirm each against the folders your installation really uses.
✦ Frequently asked questions
Common questions, answered directly.
Which folder does r2modman want for the Steam path?
The folder that contains the Steam executable, not a game folder and not the steamapps folder. On a default Windows installation that is C:/Program Files (x86)/Steam. If the manager reports spawn ENOENT, this setting is the one to correct before anything else.
Why does the folder picker show no files?
It is a directory picker, so it lists folders rather than files. Select the folder that contains the game and confirm the resulting path. Compare it with the folder Steam opens through Manage and Browse local files. An empty-looking dialog is not an error.
What is the difference between EACCES and ENOENT?
EACCES means the file exists but could not be launched without elevated privileges, so restart the manager as an administrator and try again. ENOENT means no file was found at that path, so the Steam directory setting is wrong. The two errors have opposite fixes.
My game is on a second drive. Does that matter?
It can. The manager must point at the library that actually contains the game, not the default library or a leftover copy from before you moved it. Check Steam's storage settings for every library folder, then re-select the game directory from the library you really use.
Can I fix the path by typing a compatdata number?
Do not guess one. Proton prefixes are named by the game's Steam App ID, and an incorrect prefix points at the wrong environment while still looking plausible. Use Steam's Browse local files result and the manager's own folder picker so the path comes from the running installation.
Work the checks in order and stop at the first one that changes the symptom. That step is the cause; the checks after it only matter if the symptom survives.
Next: change one thing at a time, relaunch after each change from Start modded, and keep the copy of the working setup you made before you started.