MO2 Crashes when trying to do anything other than install a mod

[jwingrider]

I have been struggling with this for the past 2 days and about at my wits end... I switched all my mods from NMM to MO2 because I loved the original MO and believe it is such a better utility! (So thank you for continuing to develop it!) I am using it for Skyrim SE. I was able to get everything I wanted installed and it will run the game, which is great but I am experiencing the following problems.

 

1. MO2 will crash every time I try to install from an archive file

2. MO2 crashes when I try to run LOOT

3. MO2 will crash every time I try to create a new executable (such as FNIS or Wrye Bash). This isn't even tryng to run them. Every time I click the ... box to create a path, MO2 crashes with a "Woops" message and I can't even create the path. This is the biggest problem for me. I feel confident in my load order and found a way around loading from archive files, but I need to make a bashed leveled list and I can't make it work. I am not the most knowledgeable when it comes to programs but I was able to make executables work fine in the original MO so I don't THINK it's something I messed up (but it could be!) I would appreciate any help/workarounds anyone can provide on this matter!!

 

A few more points, MO2 is installed in C:\Steam\steamapps\common\Skyrim Special Edition\Mod Organizer 2 and I think I made sure it has full permissions... I am running Windows 10. 

 

Thanks to anyone who may offer insight! I'm pulling my hair out here!

[Freso]

A few more points, MO2 is installed in C:\Steam\steamapps\common\Skyrim Special Edition\Mod Organizer 2 and I think I made sure it has full permissions... I am running Windows 10.

What version of MO2 are you using? 2.0.8.3 is known to have issues with long paths, so assuming your expanded mods are in "C:\Steam\steamapps\common\Skyrim Special Edition\Mod Organizer 2\Skyrim Special Edition\mods\..." that's some pretty long paths already, not even considering how the paths will be further increased by long mod names and mods with lots of deeply nested loose files.

 

See https://github.com/LePresidente/modorganizer/issues/82 and https://github.com/LePresidente/modorganizer/issues/85

 

I personally have MO2 itself (the executable) install in its default install path, but have its "downloads", "mods", "cache", etc. directories on another drive, as X:\MO\FO4\{mods,downloads,cache,...} (I'm playing Fallout 4, you would probably want "SSE") and I haven't encountered the bug reported in the mentioned issues.

[jwingrider]

I really appreciate the response. I tried to move MO to a shorter file path and it does the same thing. Crashes every time I try to do anything other than install a mod. It's so frustrating... Any other thoughts for me to try before I give up and go back to NMM? :/

[GrantSP]

Check the link in my signature about tricky software and take special note of the instructions about the game bar in Win 10.

Let us know if this is the issue in your case, there have been a few reports about the Creator update of Win 10 breaking MO's functionality but since I don't have that update, and I have otherwise fixed MS from spying on me, I can't test this.