Jump to content
  • 0

Why do I have to keep deleting ModOrganizer.ini?


toolio20

Question

Decided to run through Skyrim again - its been a while and I wanted to try some of the newer mods that have come out. I usually manually install mods but wanted to try out MO. So far it's been...well, somewhat broken, and I'd like to find out why.

 

I 've solved some of the frustrating issues with this forum and google - although I still can't make it past the "must download at least one file" part of the tutorial (even after downloading several mods from Nexus through the UI) at least I was finally able to get the thing to launch SKSE. Although that's fine and dandy, I have to go into the MO folder and manually delete the ModOrganizer.ini file EVERY TIME I want to start Skyrim via MO, otherwise it won't launch. And I'm not just talking about SKSE either, vanilla launcher gives the same "Executable "" not available" error.

 

Has anyone had to deal with this crap and, more importantly, does anyone have a fix? I can see the use in this program, and would really like to start using it regularly, but this is  ...

Link to comment
Share on other sites

7 answers to this question

Recommended Posts

  • 0

I'm going to guess that it is your antivirus.

Your instincts were correct...about 90%, but that's good enough for me!

 

I say partially, because the issue is twofold - concerning not just the AV but MO itself. I've discovered MO will - without any prompting or coaxing - automatically convert the SKSE path to "stylesheets" upon closing the program after the first run. Why it does that is anyone's guess, and it really threw off my troubleshooting. So in summary, this is what I would've had to do to out of the gate to mitigate this problem:

 

Install MO/close it/add an exception in AV/open MO, install SKSE/close it/open MO, manually configure SKSE path/close it/open MO, verify path and functionality/mod and play game.

 

If anyone experiencing the same issue sees this thread down the line, it should be noted this link is helpful as well.

 

Dub, thanks again - I'd give reps but since that's not doable, credit where it's due will have to suffice.

Link to comment
Share on other sites

  • 0

There are several possibilities that come to mind for this error, but all require more information from you. You might have your Skyrim on a portable drive that is constantly changing the drive letter so that when you go to launch the executable, it simply is not there. You could be attempting to launch SKSE, etc. from shortcuts which are outdated/point to the wrong path. Your antivirus may be interfering. UAC might be being mean to you.

 

I'm going to guess that it is your antivirus.

Link to comment
Share on other sites

  • 0

Why are you deleting the MO ini? There should be no need to do this.

Why are you not reading? There should be every need to do this before responding. As I said, deleting ModOrganizer.ini before launching the program is the ONLY WAY the utility will actually launch the game. If I close MO and re-open it without deleting the .ini, I get "Executable "" not found" errors, regardless if I choose SKSE or the vanilla launcher. I have to shut MO down, delete the .ini and open it again in order for Skryim to actually launch through the UI.

There are several possibilities that come to mind for this error, but all require more information from you. You might have your Skyrim on a portable drive that is constantly changing the drive letter so that when you go to launch the executable, it simply is not there. You could be attempting to launch SKSE, etc. from shortcuts which are outdated/point to the wrong path. Your antivirus may be interfering. UAC might be being mean to you.

 

I'm going to guess that it is your antivirus.

Skyrim is not on a portable drive - it's in my SteamLibrary, which is on a secondary SSD apart from my OS drive, but the drive letter is not changing. SKSE launches just fine if I've deleted the .ini, so I don't believe the shortcut is to blame - but if you can assist me with checking that, I'll gladly see if that can fix it. Actually, I just did some digging - it seems the .ini that keeps spawning changes the binary path for SKSE to:

Z:\SteamLibrary\steamapps\common\Skyrim\Mod Organizer\stylesheets

I've tried to manually change it to the SKSE launcher executable, but the change won't "stick" - every time I restart MO the path has reverted back to the "stylesheets." In fact, if I manually set the path of SKSE correctly, select yes at the "You made changes to the current executable, do you want to save them?" prompt, if I reopen the edit tab it's already converted back to sytlesheets.

This is all while the AV is disabled, MO is run as admin, and I've already taken ownership of the entire Z:\ drive. It appears to be a read/write or ownership issue, but everything looks to be set correctly. I'm stumped.

BTW THANK YOU for actually trying to help with the issue instead of "derp that's weird." I'm very appreciative...

Link to comment
Share on other sites

  • 0

 

I've tried to manually change it to the SKSE launcher executable, but the change won't "stick" - every time I restart MO the path has reverted back to the "stylesheets." In fact, if I manually set the path of SKSE correctly, select yes at the "You made changes to the current executable, do you want to save them?"

If you get a dialog to asking to save the changes after modifying the executable line then you did not do it right, you pressed the close button before pressing the modify button.

Link to comment
Share on other sites

  • 0

@toolio20

 

Can you just check a theory I am currently running with.

In the shortcuts to MO on your desktop/startmenu, is the "Start in" field filled in with that path to your stylesheets?

 

 

PS. I asked why you are deleting the ini because, as fixes go, that is definitely one of the worst. All your settings will be removed and nothing you set will be saved. If you had of simply stated at first the 'actual' problem and not the method you chose to get around it. Anyway, I fully understand the frustration you were no doubt experiencing at the time, no issue. I'm not having a shot at you, just a suggestion on how to get resolutions to problems in the future.

Edited by GrantSP
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
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

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