mrshadow116 Posted July 2 Posted July 2 I was previously using the Game Pass version of Expedition 33 with no issues. However, after switching to Steam version I am now getting the incorrect executable error. I've made sure that Vortex is pointed to the correct Steam folder. I've unmanaged/managed the game. Uninstalled Game Pass version. Validated steam game files. and I'm unable to launch Expedition 33 via Vortex. The game does load and it seems some of the mods are working as they do install.
ChemBoy1 Posted July 2 Posted July 2 The executable is set dynamically at runtime. You have to get Vortex to clear the state object for the game to refresh the executable. 1. Stop Managing game in Vortex. 2. Restart Vortex. 3. Manage game again. I've tested this procedure and if works.
mrshadow116 Posted July 3 Author Posted July 3 18 hours ago, ChemBoy1 said: The executable is set dynamically at runtime. You have to get Vortex to clear the state object for the game to refresh the executable. 1. Stop Managing game in Vortex. 2. Restart Vortex. 3. Manage game again. I've tested this procedure and if works. After unmanaging the game. Followed by closing the Vortex software. Upon restarting the Vortex software, I search the games list for the game, click manage and get 56 instances of the following error. I forgot to include this in my original posting. "TypeError: Cannot read properties of null (reading 'replace') at template (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\node_modules\string-template\index.js:21:19) at pathPattern (C:\Users\khann\AppData\Roaming\Vortex\plugins\Vortex Extension Update - Clair Obscur Expedition 33 Vortex Extension v0.1.4\index.js:226:12) at Object.getPath (C:\Users\khann\AppData\Roaming\Vortex\plugins\Vortex Extension Update - Clair Obscur Expedition 33 Vortex Extension v0.1.4\index.js:1464:15) at C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:3396:186 at Array.reduce (<anonymous>) at Object.get (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:3396:146) at getCurrentActivator (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:5616:22) at C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:5010:41 at Debouncer.mFunc (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:5065:125) at Debouncer.run (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:8848:34) at Debouncer.runNow (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:8846:149) at C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:5066:197 at EventEmitter.<anonymous> (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:10288:190) at EventEmitter.emit (node:events:517:28) at ExtEventHandler.emit (C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:8899:42) at C:\Program Files\Black Tree Gaming Ltd\Vortex\resources\app.asar\renderer.js:7398:12" the error heading is to load the game at least once.
mrshadow116 Posted July 3 Author Posted July 3 After un-managing the game. close Vortex. Start game via Steam. Open vortex and search for the game I chose the option to manually set the game location prior to selecting manage game. The Steam folder opened and on the pop-up confirmation window I chose Steam. I installed the mods, enabled and deployed them. I clicked the Launch button on Vortex and did not get the 56 errors stating to launch the game at least once, but did get the gamelaunchhelper.exe error.
ChemBoy1 Posted July 3 Posted July 3 I opened a bug report on the Vortex GitHub related to this: https://github.com/Nexus-Mods/Vortex/issues/17848 This is an issue with the Vortex application itself. It does not handle moving between game store versions where the executable names are different well. The PR has a procedure I used to bypass this problem. But it can probably be addressed by the Vortex devs as well. Basically, the Vortex data gets "stuck" on the old executable name, even when the discovered game path is changed. The function to set the executable is run at Vortex startup, and should update the state with the new executable name. But that doesn't appear to be working properly. 1
mrshadow116 Posted July 3 Author Posted July 3 19 minutes ago, ChemBoy1 said: I opened a bug report on the Vortex GitHub related to this: https://github.com/Nexus-Mods/Vortex/issues/17848 This is an issue with the Vortex application itself. It does not handle moving between game store versions where the executable names are different well. The PR has a procedure I used to bypass this problem. But it can probably be addressed by the Vortex devs as well. Basically, the Vortex data gets "stuck" on the old executable name, even when the discovered game path is changed. The function to set the executable is run at Vortex startup, and should update the state with the new executable name. But that doesn't appear to be working properly. Bummer, I was hoping I was just doing something wrong! But thank you! My next step was going to be reinstalling Vortex but that would require re-downloading and reconfiguring all mods for all games correct?
Solution ChemBoy1 Posted July 3 Solution Posted July 3 1 hour ago, mrshadow116 said: Bummer, I was hoping I was just doing something wrong! But thank you! My next step was going to be reinstalling Vortex but that would require re-downloading and reconfiguring all mods for all games correct? Did you read the PR for the workaround, like I suggested? Reinstalling Vortex does not affect your mods. And would not fix this particular issue. It's important to note that issue only affects launching the game. All of your mods will install correctly once the new path to the game folder is discovered. Workaround: Quote I am able to resolve this by renaming the new installation folder briefly, then restarting Vortex, which will cause the game to no longer be found. I can then rename the folder back to its original name and restart Vortex again. It now detects the correct executable.
mrshadow116 Posted July 7 Author Posted July 7 On 7/2/2025 at 10:39 PM, ChemBoy1 said: Did you read the PR for the workaround, like I suggested? Reinstalling Vortex does not affect your mods. And would not fix this particular issue. It's important to note that issue only affects launching the game. All of your mods will install correctly once the new path to the game folder is discovered. Workaround: I did not previously see the workaround, but it worked! thank you! On 7/2/2025 at 11:08 PM, jack990j said: Error: "Executable does not exist, gamelaunchhelper.exe" in Expedition 33 is called the game is missing a needed file. Try verifying game to the files in Steam to fix it. correct! gamelaunchhelper.exe is a file used by the Game Pass version of Expedition 33. Steam version does not have this file
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now