You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After Windows 11 forced the Feburary 2024 (KB5034765) cumulative update, MO2 suddenly fails to start games which use a script extender loader if you use a moshortcut:// via Steam.
Example:
This is necessary in order to use ModOrganizer2 when also playing with SteamLink Streaming, due to needing a 'one-click' route into the game for BigPicture mode.
To Reproduce:
Steps to reproduce the behavior:
Update to Windows 11 with KB5034765 (which put me on build 22621.3155)
Configure Steam to launch your game using ModOrganizer.exe with a moshortcut://
Make sure ModOrganizer.exe is not already running
Attempt to start the game in Steam
Observe error message every time
Environment:
Mod Organizer Version that exhibits the issue: 2.50
Last Mod Organizer Version that did not exhibit the issue (if applicable): 2.50
Desktop OS/version used to run Mod Organizer: Windows 11 22H2 (build 22621.3155)
Details:
Using launch options in Steam to run ModOrganizer2.exe with an appropriate moshortcut:// had worked fine in previous windows builds.
The specific error is:
The failure happens with both Fallout4 + Fallout New Vegas, and likely any other game using a script extender loader exe.
Other notes:
Still works if you click the 'Run' button from within MO2.
Still works if you run the moshortcut:// via Steam while MO2 is already running.
Still works if you double click a MO2 generated shortcut that runs the moshortcut://, even if MO2 was not running before.
Having Windows Security exceptions for ModOrganizer doesn't seem to help.
Issue still happens if Steam is started as an administrator.
USVFS:
It's short so I'm just going to in-line
22:30:13.364 [I] usvfs dll 0.5.5.1 initialized in process 27224
22:30:13.365 [D] remove from process 27224
22:30:13.365 [I] create config in 27224
22:30:13.365 [I] 0 processes
22:30:13.365 [I] mod_organizer_instance_1 created in process 27224
22:30:13.365 [I] attached to mod_organizer_instance_1 with 1 nodes, size 4,194,304 B
22:30:13.365 [I] inv_mod_organizer_instance_1 created in process 27224
22:30:13.365 [I] attached to inv_mod_organizer_instance_1 with 1 nodes, size 131,072 B
22:30:13.365 [D] context current shm: mod_organizer_instance (now 2 connections)
22:30:13.365 [D] clearing blacklist
22:30:13.365 [D] blacklisting 'Chrome.exe'
22:30:13.365 [D] blacklisting 'Firefox.exe'
22:30:13.365 [D] blacklisting 'TSVNCache.exe'
22:30:13.365 [D] blacklisting 'TGitCache.exe'
22:30:13.365 [D] blacklisting 'Steam.exe'
22:30:13.365 [D] blacklisting 'GameOverlayUI.exe'
22:30:13.365 [D] blacklisting 'Discord.exe'
22:30:13.365 [D] blacklisting 'GalaxyClient.exe'
22:30:13.365 [D] blacklisting 'Spotify.exe'
22:30:13.365 [D] blacklisting 'Brave.exe'
22:30:13.365 [D] clearing forced libraries
22:30:13.678 [D] clearing forced libraries
22:30:13.683 [E] failed to spawn "D:\SteamLibrary\steamapps\common\Fallout 4\f4se_loader.exe"
The problem:
After Windows 11 forced the Feburary 2024 (KB5034765) cumulative update, MO2 suddenly fails to start games which use a script extender loader if you use a
moshortcut://
via Steam.Example:
This is necessary in order to use ModOrganizer2 when also playing with SteamLink Streaming, due to needing a 'one-click' route into the game for BigPicture mode.
To Reproduce:
Steps to reproduce the behavior:
ModOrganizer.exe
with amoshortcut://
Environment:
Details:
Using launch options in Steam to run ModOrganizer2.exe with an appropriate
moshortcut://
had worked fine in previous windows builds.The specific error is:
The failure happens with both Fallout4 + Fallout New Vegas, and likely any other game using a script extender loader exe.
Other notes:
moshortcut://
, even if MO2 was not running before.USVFS:
MO Interface:
The text was updated successfully, but these errors were encountered: