Launching SKSE64 through MO brings up the game launcher

[jimmyjojo]

I'm sorry if this question has been asked before. I've been Googling for hours and haven't found anything. 

 

When I try to launch the game with SKSE64 through Mod Organizer 2 it just brings up the game launcher. Of course, if I load the game through the game launcher none of my mods are detected since they are all installed through MO2. I've had to go directly into my Skyrim SE root folder to launch SKSE64 and I've had to run it as administrator, too. Maybe this isn't a problem but in the past, I've always been able to launch SKSE64 through MO2. This happened after I recently reinstalled MO2 (long story). 

 

MO2 wants me to log into Steam when I try to launch SKSE64. It does this when I try to launch Wrye Bash and LOOT, too; I have to use the executables to run Wrye Bash and LOOT. 

 

Maybe I'm missing something obvious but at this point, I'm so tired my eyes are crossed.

 

I give up.

 

I need help. 

 

Thanks in advance :)

[jimmyjojo]

Actually, never mind this. Turns out I was supposed to install it in my Games folder on my C drive and NOT in Program Files. It's all working fine now. This was a rookie mistake and I should have known better but, there you have it. 

[jimmyjojo]

Actually, never mind, AGAIN. It's doing this AGAIN. Yesterday, it was doing this so I installed MO2 in Program Files because the installer "wanted" to install it there. Fine. Fixed the problem. Then today, it's back to the same old nonsense again so I installed it in my Games folder--which is where it's supposed to go, as far as I understood. Fine. Fixed the problem. 

 

I had to re-install SSE (long story) so I re-installed MO2, as well. Now, it's doing what I originally posted about. 

 

Halp! I'm at my wit's end with this. 

[jimmyjojo]

Sorry for the multiple posts, but I can't see how to edit my original post. 

 

Anyway, I re-installed MO2 on my C drive and NOT in Games folder, where all my Steam games are installed. Everything is working. Fingers crossed. Hopefully, this is the fix, and I have to say, I've never had to install Mod Organizer for Skyrim and Skyrim SE like this before. It's the weirdest thing. 

[GSDFan]

MO2 should not be installed in the games directory, you will most likely have random problems like plugins not being seen by other tools, crashes and so on. It has been proven to mess up the USVFS virtual file system. It is best to install MO2 in its own directory away any Windows UAC controlled folders.

[jimmyjojo]

Well, I installed it directly onto my C drive and it's still bringing up the game launcher instead of launching the game. I have no idea where to go from here or why it is arbitrarily working. It's driving me crazy. If anyone has any ideas I'm open. 

[jimmyjojo]

Not gonna say it's fixed until it's been working for a few days, but I sent a shortcut to MO2 to my desktop and set it to run it as administrator at all times and that seemed to fix it...hopefully. Before that, I had it pinned to my taskbar and was running it from there. It's always been fine doing things that way in the past, but I took a break from Skyrim SE for a few months and evidently everything has changed since then.

[jimmyjojo]

It quit working again. 

[Shadriss]

Just to cover all the bases - where are the following actually installed (actual paths, please - the more info the better):

 

A) MO2

B) Steam (The actual program)

C) SSE (If not in the same place as Steam)

 

ANY of these in UAC controlled portions can screw with MO2 operations.