Jump to content
  • 0

Can not Launch SSE though MO



When i try to launch SSE though MO i get the steam error


application load error 3:0000065432


if i open the SSE launcher though MO it opens but when i click play i just get the error


I can launch SSE and SSE launcher though NMM and Steam with out the error


So i am unsure as to why this is happening


Thanks in advance for  any help you can give me


Link to comment
Share on other sites

Recommended Posts

  • 0

Welcome to STEP @Uisca


If your MO2 installation is in a UAC location, such as Program Files(x86), I suggest moving it to some other place.

Steam may be trying to provide MO2 with the correct details but Windows may be hindering it. Since you can launch SSE from the desktop, or NMM, the correct registry settings are set so MO2 should be able to do so also.

Link to comment
Share on other sites

  • 0

I have found them

Deleted at the request of the original poster.


But i cant add the .logs



Here are all the logs i could add i had to make them in to txt but one of them was to large to add


Link to comment
Share on other sites

  • 0

Open the ini in an editor and remove the extra entries here:

2\title=Skyrim Launcher
1\binary=I:/GAMES/STEAM/SteamApps/common/Skyrim Special Edition/SkyrimSE.exe
1\workingDirectory=I:/GAMES/STEAM/SteamApps/common/Skyrim Special Edition
2\binary=I:/GAMES/STEAM/SteamApps/common/Skyrim Special Edition/SkyrimSELauncher.exe
2\workingDirectory=I:/GAMES/STEAM/SteamApps/common/Skyrim Special Edition

Everything in that block starting from: 1\binary=I:/GAMES/STEAM/SteamApps/common/Skyrim Special Edition/SkyrimSE.exe

can be deleted. MO should recognise the default executables and call them without explicitly adding the paths as the registry will hold the correct game paths.
Link to comment
Share on other sites

  • 0

Hmm... is your "I" drive a network attached device or perhaps controlled by software? Since we've ruled out everything else I can only assume there is another layer of software that MO is being hindered from accessing.

If it is try and add it to your anti-virus exceptions list or check to see if that software has full admin access rights.

If it isn't a NAS there still must be some thing interfering with MO's 'hooking' of the Steam game, perhaps an overlay program from your graphics card or similar. My AMD install tried that with Raptr and it messed with me similarly.

Link to comment
Share on other sites

  • 0

Well sad to say, I'm out of ideas. Especially since MO runs FNV from that drive!


I see you've got your Steam details entered in MO (don't worry, there encrypted in the INI so no-one can steal them.), try closing down Steam and see if MO2 will start it for you. It works for me without hassle.

Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.