Windows 24H2 breaks /nolauncher argument in Steam?

The Windows 24H2 update might have altered how Steam handles command-line arguments. So here’s how to address the issue:

1. Verify the Argument: Make sure /nolauncher is correctly applied in Steam: right-click the game > Properties > Launch Options > Add /nolauncher.

2. Make sure your system and Steam are fully updated, as compatibility patches might resolve the issue.

3. Check if the game’s executable file can be launched directly from the installation folder without Steam.

spend bill gates money

1. Yeah, the /nolauncher argument is in there correctly. To be clearer, it was working fine before the 24H2 update. That may be anecdotal evidence, but it's the only correlation I can think of and this behavior is replicated on the three computers I play GC4 on.

2. Yeah, I keep everything updated on my systems.

3. Running GalCiv4.exe directly just opens the Stardock launcher as if I had run it from Steam. None of the other executables in the GC4 folder tree look like they have anything to do with directly launching the game.

can you try variations like -nolauncher or --nolauncher in Steam's launch options, as syntax requirements might have changed.

Thank you for reporting this, ill be keeping an eye here to see if anyone finds a syntax change

I tried -nolauncher and --nolauncher, but the Stardock launcher loads as usual. It seems invalid arguments are just ignored.

Yesterday 24h2 was installed... same problem. I don't like launcher.... please fix it

I get the impression that fixing a launcher launching a launcher to launch the game is not a priority.

For the record, issue persists in 25h2.

What worked for me was to set the launch option to "C:\Steam\steamapps\common\Galactic Civilizations IV\GalCiv4.exe" %command% rather than --nolauncher

You'd just need to adjust the path to wherever your game is actually installed if it's not the same

That worked for me. Good find!