mod organizer Crash to Desktop when launching Skyrim SE through Mod Organizer 2

[CayugaDuck]

I am having a strange crash-to-desktop error when trying to boot skyrim through MO2. Whether I try and run the game through skse_64 or the regular launcher through MO2, the game boots until the Bethesda logo, then crashes to desktop before the main menu.

The same error occurs when I tried to make a new instance with no mods, both for skse launcher and the regular skyrim launcher through MO2.

The game is able to successfully boot to the main menu if I launch the game from steam (and I am able to start a new game fine), or directly run the skse_64 exe from my files. 

Another strange quirk is that other applications like FNIS and LOOT crash when I attempt to run their functionality. FNIS crashes when I click “generate” and LOOT crashes when I try to sort the load order.  

I tried to see if it was a strict MO2 issue by seeing if my modded FO4 would run, which it did perfectly. Other than the inability to fully boot Skyrim, I cannot tell if there are any other issues with my mods or load order or anything as the crash doesn’t return any error message.

I have tried reinstalling SKSE, I updated MO2 to the latest version, and completely uninstalled and reinstalled Skyrim, to no avail. My game was working fine last I played in late September, since then I haven’t touched anything. All I have done was set my skyrim steam appmanifest file to read only to avoid updates, which hasn’t been a problem on the past. I am truly lost as to what the issue could be.

If you require additional information from me, I’d be happy to provide. 

[TerryDarden]

  On 2/21/2025 at 5:26 PM, CayugaDuck said:

I am having a strange crash-to-desktop error when trying to boot skyrim through MO2. Whether I try and run the game through skse_64 or the regular launcher through MO2, the game boots until the Bethesda logo, then crashes to desktop before the main menu.

The same error occurs when I tried to make a new instance with no mods, both for skse launcher and the regular skyrim launcher through MO2.

The game is able to successfully boot to the main menu if I launch the game from steam (and I am able to start a new game fine), or directly run the skse_64 exe from my files. 

Another strange quirk is that other applications like FNIS and LOOT crash when I attempt to run their functionality. FNIS crashes when I click “generate” and LOOT crashes when I try to sort the load order.  

I tried to see if it was a strict MO2 issue by seeing if my modded FO4 would run, which it did perfectly. Other than the inability to fully boot Skyrim, I cannot tell if there are any other issues with my mods or load order or anything as the crash doesn’t return any error message.

I have tried reinstalling SKSE, I updated MO2 to the latest version, and completely uninstalled and reinstalled Skyrim, to no avail. My game was working fine last I played in late September, since then I haven’t touched anything. All I have done was set my skyrim steam appmanifest file to read only to avoid updates, which hasn’t been a problem on the past. I am truly lost as to what the issue could be.

If you require additional information from me, I’d be happy to provide. 
If Skyrim SE crashes on launch through MO2, try checking for missing or corrupted mods. Sometimes, large mod files can get corrupted during downloads. I recommend using Filemail to transfer and back up large mod files without compression or corruption risks. Hope this helps!

Expand  

Bump

Edit: I forgot to ask, have you resolved it?

Edited February 24 by TerryDarden

[GSDFan]

Hard to say what is causing this, but I would start with asking the usual questions:

Is MO2 and the game installed outside any Windows protected folders. Like Program Files.

Have you created a new profile and disabled all mods, including skse, and tried to launch the game from the launcher?

Sometimes Windows has a habit of quarantining  usvfs_proxy_x64.exe. Check that this is not the case.,

[CayugaDuck]

  On 2/25/2025 at 1:27 PM, GSDFan said:

Hard to say what is causing this, but I would start with asking the usual questions:

Is MO2 and the game installed outside any Windows protected folders. Like Program Files.

Have you created a new profile and disabled all mods, including skse, and tried to launch the game from the launcher?

Sometimes Windows has a habit of quarantining  usvfs_proxy_x64.exe. Check that this is not the case.,

Expand  

Sorry for the late reply, I wasn't getting email notifications and haven't checked back in a while.

 

"Is MO2 and the game installed outside any Windows protected folders. Like Program Files."

- All my instances are stored in my C: drive under Users/"my computer name"/AppData/Local/ModOrganizer. My main MO2 folders ("Mod Organizer 2" and "Mod Organizer 2 Game Directory") are located directly in my 2TB D: drive. It's been this way for years and I've never had any issues. I am also still able to run my Fallout 4 instance through MO2 just fine. The FO4 instance is similarly stored in the same directory as my Skyrim SE instances.

 

 

"Have you created a new profile and disabled all mods, including skse, and tried to launch the game from the launcher?"

- Yes, I created a new instance with 0 mods enabled, and attempted to run the game via "Skyrim Special Edition Launcher" in MO2. I have the same CTD issue before reaching the main menu.

 

"Sometimes Windows has a habit of quarantining  usvfs_proxy_x64.exe. Check that this is not the case."

- I have tried to run the game with all of my firewalls/antiviruses disabled, and still had the same issue. I will try to whitelist this file and get back to you.

[CayugaDuck]

  On 3/26/2025 at 5:04 PM, CayugaDuck said:

"Sometimes Windows has a habit of quarantining  usvfs_proxy_x64.exe. Check that this is not the case."

- I have tried to run the game with all of my firewalls/antiviruses disabled, and still had the same issue. I will try to whitelist this file and get back to you.

Expand  

Just tried this by adding a rule for both usvfs_proxy_x64.exe and usvfs_proxy_x86.exe in my Bitdefender firewall allowing access, and still have the CTD before reaching the main menu. I am not sure if this is what you mean by Windows quarantining the exe, so if I am missing something, please let me know. 

[GSDFan]

By the folder structure I assume you used a Global MO2 instance. You can also do a portable install as a test in the top level of the C drive, C:\MO2. this will keep the folder structure short as possible.

Other things I can think of is how did you install SKSE?  

In the MO2 skse executable configuration do you have anything in the "Overwrite Steam AppId"? You can try entering 489830 for the Special edition.

[CayugaDuck]

  On 3/27/2025 at 11:16 AM, GSDFan said:

By the folder structure I assume you used a Global MO2 instance. You can also do a portable install as a test in the top level of the C drive, C:\MO2. this will keep the folder structure short as possible.

Other things I can think of is how did you install SKSE?  

In the MO2 skse executable configuration do you have anything in the "Overwrite Steam AppId"? You can try entering 489830 for the Special edition.

Expand  

Yes, I used a global instance and didn't change the default directory. Creating a portable instance as you recommended led to the same crash issue for both the default launcher and SKSE. 

 

I installed SKSE as instructed by this video: 

This is how I have installed it in the past with no problems. The CTD issue began with an install of SKSE that was working merely months before. I attempted to uninstall and reinstall SKSE when the issue began ensuring I was downloading the correct version for my game (skse64_1_6_1170), and the issue persisted. As suggested, I added 489830 to the "Overwrite Steam AppID" and nothing changed.

I am really at a loss. It has to be some issue with Skyrim SE specifically, since my Fallout 4 is fine through MO2, but it seems like it isn't just the mods, since a non-modded instance has the same problem. Very confusing.

 

[GSDFan]

Can you run the Skyrim launcher from within MO2 and check your settings are correct? Also try to launch the game from the launcher and the Skyrim drop down shortcuts and see it the game runs without SKSE from MO2. Disable any mods in the left pane if any are installed.

 

 

[CayugaDuck]

  On 3/27/2025 at 6:08 PM, GSDFan said:

Can you run the Skyrim launcher from within MO2 and check your settings are correct? Also try to launch the game from the launcher and the Skyrim drop down shortcuts and see it the game runs without SKSE from MO2. Disable any mods in the left pane if any are installed.

 

 

Expand  

This is the new instance I have created with the shortest file directory possible (C:/ModOrganizer2). I have no mods installed. Nothing is enabled. I run the game via the MO2 Skyrim Launcher and get the CTD. 

 

  On 3/28/2025 at 4:10 PM, CayugaDuck said:

This is the new instance I have created with the shortest file directory possible (C:/ModOrganizer2). I have no mods installed. Nothing is enabled. I run the game via the MO2 Skyrim Launcher and get the CTD. 

 

Expand  

This is the Log when launching. Is there anything out of the ordinary? I see the error for the ini, but I don't know if that is the issue here. 

Edit: I just noticed that the path is the default AppData/Local path even though I told it to locate in the base C: drive. Weird. But again, that has never been an issue in the past

Edited Friday at 04:16 PM by CayugaDuck

[GSDFan]

I am assuming that this instance is a portable one you did for testing.

In that instance of MO2, press the settings icon, crossed screwdriver and wrench, to open the settings.

Find the Paths tab and click on it.

This is where MO2 stores it paths. I am interested in the "Base Directory" field.

If this is the new instance you did at "C:/ModOrganizer2" then it should reflect that. Instead it is showing "C:/Users/USERNAME/AppData/Local/ModOrganizer/Skyrim Special Edition (test no mods)" and the image shows it can't find a profile and using a default from there, which I think is the one from the global instance.

Take a screen capture and post it.

[CayugaDuck]

  On 3/28/2025 at 5:43 PM, GSDFan said:

I am assuming that this instance is a portable one you did for testing.

In that instance of MO2, press the settings icon, crossed screwdriver and wrench, to open the settings.

Find the Paths tab and click on it.

This is where MO2 stores it paths. I am interested in the "Base Directory" field.

If this is the new instance you did at "C:/ModOrganizer2" then it should reflect that. Instead it is showing "C:/Users/USERNAME/AppData/Local/ModOrganizer/Skyrim Special Edition (test no mods)" and the image shows it can't find a profile and using a default from there, which I think is the one from the global instance.

Take a screen capture and post it.

Expand  

When I created this "Skyrim Special Edition (test no mods)" instance, I did make it a global instance and set the file path to C:. Here is the "Base Directory" field for this instance as requested:

I also created an un-modded portable instance with the same directory, C:. I attempted to run the game through there for both SKSE and the base Skyrim SE Launcher, had the same CTD issue. Here is an image of the paths and logs for this portable instance:

 

I am beginning to think this has to do with some disconnect or file read/write error between MO2 and Skyrim, since it only seems to break when I run this game specifically, modded or un-modded, through MO2. 

[z929669]

  On 3/28/2025 at 7:41 PM, CayugaDuck said:

When I created this "Skyrim Special Edition (test no mods)" instance, I did make it a global instance and set the file path to C:. Here is the "Base Directory" field for this instance as requested:

I also created an un-modded portable instance with the same directory, C:. I attempted to run the game through there for both SKSE and the base Skyrim SE Launcher, had the same CTD issue. Here is an image of the paths and logs for this portable instance:

 

I am beginning to think this has to do with some disconnect or file read/write error between MO2 and Skyrim, since it only seems to break when I run this game specifically, modded or un-modded, through MO2. 

Expand  

Just throwing in my 2 cents here (ultimately, follow GSDFan's advice)...

The default Base Dir Path for instances is %LOCALAPPDATA%\ModOrganizer\{instanceName}

The advantage here is that your Windows user profile has full access/privileges under this path, since it exists under %USERPROFILE%. This circumvents any potential security restrictions (like UAC issues). The root of C:\ could be problematic if the OS is installed on C:\. The root of any other drive should be fine, but you probably don't have explicit, user-based privileges there. You might need to mess with advanced security settings under paths outside of %USERPROFILE%.

Step's advice is to use MO Instances and their default paths. It "just works".

[CayugaDuck]

  On 3/28/2025 at 11:37 PM, z929669 said:

Just throwing in my 2 cents here (ultimately, follow GSDFan's advice)...

The default Base Dir Path for instances is %LOCALAPPDATA%\ModOrganizer\{instanceName}

The advantage here is that your Windows user profile has full access/privileges under this path, since it exists under %USERPROFILE%. This circumvents any potential security restrictions (like UAC issues). The root of C:\ could be problematic if the OS is installed on C:\. The root of any other drive should be fine, but you probably don't have explicit, user-based privileges there. You might need to mess with advanced security settings under paths outside of %USERPROFILE%.

Step's advice is to use MO Instances and their default paths. It "just works".

Expand  

All my usual instances are found within the default userprofile appdata paths. I was just creating instances in C: as recommended. Like I said, it seems to be some kind of esoteric read/write or disconnect error with MO2 and Skyrim specifically. The file paths never was an issue in the past and I haven't changed anything since it was working a few months ago. I literally was able to play my game fine, didn't play for a few months, and then it started breaking like this. It has to be some kind of error or change that happened externally with Skyrim that is messing up MO2, I just cannot think of what it could be.

[GSDFan]

I typically only use manually installed, portable instances of my MO2 installs, so my previous comment reflected that instance. Global instances will reflect the "C:/Users/UserName/AppData/Local..." path as a base directory. 

I noticed in the second set if screen shots the Managed game points to "D:\SteamLibramy\steamapps\common\Skyrim Special Edition\SkyrimSE.exe". I think that it should just be the path to the folder, "D:\SteamLibramy\steamapps\common\Skyrim Special Edition". That is probably where the problem is.

 

[z929669]

  23 hours ago, CayugaDuck said:

All my usual instances are found within the default userprofile appdata paths. I was just creating instances in C: as recommended. Like I said, it seems to be some kind of esoteric read/write or disconnect error with MO2 and Skyrim specifically. The file paths never was an issue in the past and I haven't changed anything since it was working a few months ago. I literally was able to play my game fine, didn't play for a few months, and then it started breaking like this. It has to be some kind of error or change that happened externally with Skyrim that is messing up MO2, I just cannot think of what it could be.

Expand  

Apologies, I should have read the OP more carefully.

  23 hours ago, GSDFan said:

I typically only use manually installed, portable instances of my MO2 installs, so my previous comment reflected that instance. Global instances will reflect the "C:/Users/UserName/AppData/Local..." path as a base directory. 

 

Expand  

Defaults in instanced for me, and it works without issue.

 

Assuming that when "uninstalled and reinstalled Skyrim", the game directory is totally clean of any third-party binaries and the like. Since this is specific to SSE/MO and other games run fine though MO, it has to be something associated with the SSE MO profile, SSE itself, or the SSE registry settings. Running via the Steam Launcher should properly set the registry. It might be a good idea to verify the game files via Steam and re-launch via Steam just to satisfy any lingering OCD.

The only thing in the posted MO log I see that stands out is that there is no profile set, so it's reverting to default. Maybe set a profile, and tick all three boxes for profile specific * and auto archive invalidation. This is a shot in the dark.

Can MO be configured to produce a more verbose log?

I would also examine files under \Documents\My Games\Skyrim Special Edition.

[CayugaDuck]

  23 hours ago, GSDFan said:

I typically only use manually installed, portable instances of my MO2 installs, so my previous comment reflected that instance. Global instances will reflect the "C:/Users/UserName/AppData/Local..." path as a base directory. 

I noticed in the second set if screen shots the Managed game points to "D:\SteamLibramy\steamapps\common\Skyrim Special Edition\SkyrimSE.exe". I think that it should just be the path to the folder, "D:\SteamLibramy\steamapps\common\Skyrim Special Edition". That is probably where the problem is.

 

Expand  

That's weird, because my Fallout 4 paths for "Managed Game" also ends with the game application, "Fallout4.exe" and works fine. How would I set it to just the folder directory? It seems to only allow me to select an application or file rather than a folder by itself.