I encountered a reproducible launcher error when trying to join any G1R:MP server.
The native game-start supervisor exited (code 25):
A protected game bootstrap path is a reparse point
Environment:
- G1R:MP Launcher: 0.1.0-alpha-build30
- Protocol: 26
- Game version: Steam
- Gothic 1 Remake managed with Vortex
- UE4SS-based single-player mods installed
Steps to reproduce
1. Install Gothic 1 Remake through Steam.
2. Manage the game with Vortex.
3. Install UE4SS and other mods using Vortex’s symbolic-link deployment.
4. Start the G1R:MP launcher.
5. Attempt to join any server.
Investigation
The server and its downloaded resources do not matter—the failure occurs during the local game bootstrap.
The game directory itself and all its parent directories are normal directories, not reparse points. The G1R:MP installation under %LOCALAPPDATA%\G1RMultiplayer also contains no reparse points.
However, Vortex deployed multiple mod files as symbolic links. The most relevant example is:
Gothic 1 Remake\G1R\Binaries\Win64\dwmapi.dll
This file has the following properties:
Attributes: Archive, ReparsePoint
Link type: SymbolicLink
Target: C:\Users\<user>\AppData\Roaming\Vortex\gothic1remake\mods\Main UE4SS Included...\dwmapi.dll
Reparse tag: 0xA000000C
UE4SS.dll and numerous other mod files are also symbolic links.
Using Purge Mods in Vortex and then verifying the game files through Steam removes the reparse points and resolves this particular error.
Expected behaviour
The launcher should identify the exact rejected path and provide actionable guidance.
For example:
G1R:MP cannot start because this protected file is a symbolic link:
E:\...\G1R\Binaries\Win64\dwmapi.dll
This is commonly caused by Vortex or another mod manager.
Purge or disable deployed mods, verify the game files, and try again.
A preflight check before joining a server would also help. It could detect reparse points in protected bootstrap paths and report them before downloading resources or starting the native supervisor.
Documentation should mention that Vortex users may need to use Purge Mods before playing multiplayer and Deploy Mods again when returning to a modded single-player installation.
Greetings
Madixs
The native game-start supervisor exited (code 25):
A protected game bootstrap path is a reparse point
Environment:
- G1R:MP Launcher: 0.1.0-alpha-build30
- Protocol: 26
- Game version: Steam
- Gothic 1 Remake managed with Vortex
- UE4SS-based single-player mods installed
Steps to reproduce
1. Install Gothic 1 Remake through Steam.
2. Manage the game with Vortex.
3. Install UE4SS and other mods using Vortex’s symbolic-link deployment.
4. Start the G1R:MP launcher.
5. Attempt to join any server.
Investigation
The server and its downloaded resources do not matter—the failure occurs during the local game bootstrap.
The game directory itself and all its parent directories are normal directories, not reparse points. The G1R:MP installation under %LOCALAPPDATA%\G1RMultiplayer also contains no reparse points.
However, Vortex deployed multiple mod files as symbolic links. The most relevant example is:
Gothic 1 Remake\G1R\Binaries\Win64\dwmapi.dll
This file has the following properties:
Attributes: Archive, ReparsePoint
Link type: SymbolicLink
Target: C:\Users\<user>\AppData\Roaming\Vortex\gothic1remake\mods\Main UE4SS Included...\dwmapi.dll
Reparse tag: 0xA000000C
UE4SS.dll and numerous other mod files are also symbolic links.
Using Purge Mods in Vortex and then verifying the game files through Steam removes the reparse points and resolves this particular error.
Expected behaviour
The launcher should identify the exact rejected path and provide actionable guidance.
For example:
G1R:MP cannot start because this protected file is a symbolic link:
E:\...\G1R\Binaries\Win64\dwmapi.dll
This is commonly caused by Vortex or another mod manager.
Purge or disable deployed mods, verify the game files, and try again.
A preflight check before joining a server would also help. It could detect reparse points in protected bootstrap paths and report them before downloading resources or starting the native supervisor.
Documentation should mention that Vortex users may need to use Purge Mods before playing multiplayer and Deploy Mods again when returning to a modded single-player installation.
Greetings
Madixs