• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.

yi_anjiu

Recruit
Feb 2, 2024
5
1
How do I use Paradox Launcher v2 correctly?
 

Attachments

  • 1.png
    1.png
    92,7 KB · Views: 0
  • 2.png
    2.png
    12,2 KB · Views: 0
  • 3.png
    3.png
    26,7 KB · Views: 0
  • 4.png
    4.png
    12,6 KB · Views: 0
Please try this:

- uninstall Paradox Launcher v2 from the Windows "Apps and features" utility, if still present.

Delete the following folders if still present:

- C:/users/{userName}/AppData/Local/Programs/Paradox Interactive/
- C:/users/{userName}/AppData/Local/Paradox Interactive/
- C:/users/{userName}/AppData/Roaming/Paradox Interactive/launcher-v2/
To see the AppData folder you'll need to enable View Hidden Items in File Explorer.

- exit the Steam app entirely
- run steam.exe as the Windows Admin user
- run the game from the PLAY button in Steam
OR
- exit the Epic app entirely
- run EpicGamesLauncher.exe as the Windows Admin user
- run the game from the Epic client

IF that doesn't help, in this folder are some .log files:
C:/users/{userName}/AppData/Local/Paradox Interactive/launcher-v2/
Please attach them here.
To see the AppData folder you'll need to enable View Hidden Items in File Explorer.
 
When I figured out the above three points and started the game using steam, nothing happened
If me manually install Paradox Launcher v2, it will look like the picture I sent at the beginning.
 
2024-02-03 07:33:52 [main] [ERROR] Couldn't start the bootstrapper:
%s C:\Users\Administrator\AppData\Local\Paradox Interactive\bootstrapper-v2.exe
2024-02-03 07:33:55 [main] [CRITICAL] Could not start the Paradox Launcher at C:\Users\Administrator\AppData\Local\Paradox Interactive:
open NUL: The system cannot find the file specified.

Does this file physically exist?
C:\Users\Administrator\AppData\Local\Paradox Interactive\bootstrapper-v2.exe

If so what happens if you run it manually from File Explorer?
 
@AndrewT, I will continue this thread if it's ok.

I have an issue with Launcher 2 v. 2024.3 as it does not start any game I have on Steam Vic3, Stellaris, etc. It fails with the same issue. I have already contacted the support team. However, none of the solutions worked.

The issue occurs when Launcher tries to launch a game and do something with Steam. I can successfully start the game by going to the Steam folder and finding actual binaries. However, this will allow me to play with mode, but no DLC are available. I guess that's the part where Steam comes in and tells the game that DLCs are available.

We've tried a clean-up of both the launcher and games.
We've tried a Steam reinstall and installed everything from scratch.
I have installed a standalone launcher. Unfortunately, it does not show anything I bought on Steam.

Any ideas, suggestions?

MacBook M1,
OS: MacOS Sonoma 14.2.1

The console output:
dyld[46019]: tried: '/Users/artsiomkharytonc/Library/Application Support/Steam/Steam.AppBundle/Steam/Contents/MacOS/steamloader.dylib' (fat file, but missing compatible architecture (have 'i386,x86_64,arm64', need '')), '/System/Volumes/Preboot/Cryptexes/OS/Users/artsiomkharytonc/Library/Application Support/Steam/Steam.AppBundle/Steam/Contents/MacOS/steamloader.dylib' (no such file), '/Users/artsiomkharytonc/Library/Application Support/Steam/Steam.AppBundle/Steam/Contents/MacOS/steamloader.dylib' (fat file, but missing compatible architecture (have 'i386,x86_64,arm64', need '')), '/Users/artsiomkharytonc/Library/Application Support/Steam/steamapps/common/Victoria 3/steamloader.dylib' (no such file), '/Users/artsiomkharytonc/Library/Application Support/Steam/steamapps/common/Victoria 3/bin/steamloader.dylib' (no such file), '/usr/local/lib/steamloader.dylib' (no such file), '/lib/steamloader.dylib' (no such file), '/usr/lib/steamloader.dylib' (no such file, not in dyld cache)
 
I will continue this thread if it's ok.
Always best to start your own thread in future, thanks. Your issue is completely different to the OP's, and is on a different OS too.

Have you perhaps disabled SIP in your MacOS installation? If so try enabling it, see if that helps.