• 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.
Thanks! i made a mistake by increasing the paging file size . Now it run´s when i start the game by .exe. But i cannot start by launcher.
Also the are no DLC´s when i start the game by .exe.
 

Attachments

  • Victoria 3_2023.12.02-23.09.png
    Victoria 3_2023.12.02-23.09.png
    5,6 MB · Views: 0
i made a mistake by increasing the paging file size .
I'm not sure what you are saying there, sorry. - my suggestion was to indeed increase the paging file size,to at least 32gb.

But if you can start the .exe file but the launcher cannot, that is usually an antivirus app getting in the way. What antivirus app do you use? You need to make sure all these apps are in its exceptions lists:

victoria3.exe (in the Steam victoria3-binaries folder)
dowser.exe (in the Steam victoria3-launcher folder)
C:/users/{UserName}/AppData/Local/Programs/Paradox Interactive/launcher-v2.2023..15/paradox launcher.exe
C:/users/{UserName}/AppData/Local/Programs/Paradox Interactive/bootstrapper-v2.exe

IF that doesn't help, also set each of those .exe files (EXCEPT victoria3.exe !) to run as the Windows Admin user.

Then the game should run from Steam/our launcher, and enable all the DLCs.
 
Hello. yes, that was an apology. If I had paid more attention at the beginning, we would have been further.
i use ESET smart security . The Game runs now by launcher .
i set all files to exceptions lists but nothing changed. Now i set the files to Windows Admin user (EXCEPT victoria3.exe).
The Game runs now by launcher . Now there is a new error message (pic), the DLC's are not selected.
 

Attachments

  • Victoria 3_2023.12.04-07.41.png
    Victoria 3_2023.12.04-07.41.png
    5 MB · Views: 0
  • unknown_2023.12.04-07.26.png
    unknown_2023.12.04-07.26.png
    10,1 MB · Views: 0
Sheesh. Is steam.exe running as Admin, or not?
 
This makes no sense ... what if you make a new WIndows user on this machine, and log into it with that? Same issue?