MO does not start (Win 10)

[Clausi]

Hey,

 

I recently wanted to get back into Skyrim, so I installed the game new and wanted to install some mods with ModOrganizer as I already had done in the previous installation.

But ModOrganizer (1.3.11) does not start, it only appears a process called "Mod Organizer UI" which closes immediately. In the logs folder there is one logfile "mo_interface.log" with one line

[W] QMutex: destroying locked mutex

I also tried previous versions, same happens with other 1.3 versions.

1.2 seems not to work with Nexusmods, I have to try this version again with manual downloading mods and installing.

But perhaps someone can help me to get 1.3.11 running, do I miss some libaries? 

My system:

Win 10 64 Bit Home

AMD FX-6300

8gb Ram

Skyrim and ModOrganizer are installed on my 2nd harddrive (not system drive), I also tried to run with admin privileges and deactivating Avast, but the same happens. 

 

Thanks for your help ;) If any information is missing please let me know.

Edited April 4, 2016 by Clausi

[GrantSP]

Welcome to STEP @Clausi

 

There are no additional libraries that you need to install, the only thing you might need to do is enable the .NET Framework 3.5 via Windows. Examine the MO manual to see how that is done.

 

The log entry is referring to multiple thread executions and how they are handled in MO. Possibly you started MO, and it was minimised, and the small tutorial or update dialogues that show on the first instance of MO's use, were open but not visible and you tried to start another instance of MO.

 

Reboot your system, to ensure no running instances of MO persist, and install MO via the archive version. Simply extract the contents into a folder all its own, away from any UAC folders such as Program Files, and run it from there. If the main UI does not show Alt-Tab to bring to the front any other running processes and if the tutorial or update notice are showing, dismiss them and the UI should display.

 

If all is well read the manual on how to setup your Nexus accounts and start to add mods. If not please post here your logs and any other INIs that are created upon MO's install.

[Clausi]

Hey,

thanks for your answer :)

I double checked the .Net Framework 3.5 entry, it is active. I deleted the complete MO folder, rebooted and downloaded the archive version of MO. On start a process ModOrganizer.exe appears, some folders and files are created, then the process closes and nothing happens. Alt+Tab does not show any dialog or window.

The log on first start contains the same line as already posted above. 

 

For now I use 1.2.18 with manual downloading mods and adding archives. 

[Greg]

Do you see anything relevant in Event Viewer that might explain why Mod Organizer isn't starting?

[Clausi]

There are no new entries created in Windows Event Viewer if I start the MO.exe

I'm wondering what is wrong on my Windows installation  :confused:

[GrantSP]

Make sure you have NO AV packages running in the background. The 'hooking' mechanic is often seen by AV software as a bad thing and often gets removed.

[Clausi]

I paused avast av and tried to start, same situation as posted above.

I wonder if there is a problem with some python packages I had installed for some apps I wrote for a web project?

[Greg]

This shouldn't affect Mod Organizer's ability to run because Mod Organizer is a portable application that includes pretty much everything it needs to run (including Python 2.7 and Visual C++ 12.0 runtime) and Python is not used when starting Mod Organizer. Python is required to run some of the plugins, but this comes into play only when you run these plugins.

[GrantSP]

The biggest difference with 1.2.18 and the 1.3.x series is the removal of support for Windows XP. Some functions that Windows 7 and above have are not possible with XP.

Even though you state you are running Windows 10 Home, the fact 1.2.18 works for you and 1.3.x doesn't makes me believe there is something wrong with your installation of Windows.

 

Can you try to run MO under 'Compatibility mode' from Windows explorer?

Right-click on the exe and choose: Properties.

Select the 'Compatibility' tab and then check the box and select Windows XP (Service Pack 3) from the dropdown list.

[Jarda]

I have the same problem as well.

Was doing fine, finished S.T.E.P. guide, but then it happened.

I was able to launch it one more time, but then I realized it didnt downloaded some files from Nexus. I closed MO, and then I couldn't open it again.

 

mo_interface log says: [W] QMutex: destroying locked mutex

[GrantSP]

I have the same problem as well.

Was doing fine, finished S.T.E.P. guide, but then it happened.

I was able to launch it one more time, but then I realized it didnt downloaded some files from Nexus. I closed MO, and then I couldn't open it again.

 

mo_interface log says: [W] QMutex: destroying locked mutex

So are you saying that for a time your current installation of MO was working? Only after some downloading did this matter show up?

Tthis makes me think there may be some processes trying to load to handle failed downloads and they are not letting the main UI load.

Did you suffer any problems with downloading?

[Jarda]

So are you saying that for a time your current installation of MO was working? Only after some downloading did this matter show up?

Tthis makes me think there may be some processes trying to load to handle failed downloads and they are not letting the main UI load.

Did you suffer any problems with downloading?

No problems at all, everything was working fine.

While following S.T.E.P., I was installing some mods that were already saved on NMM "downloads folder" (I was using NMM before switching to MO with a clean Skyrim install).

Then I moved the already installed mods from NMM to some other folder, since I was not sure if it was fine to place them on MO downloads folder.

Tried to launch MO after moving the files and it was the first time it didn't started. I thought MO could be looking for the files on NMM folder, so I moved the files back to NMM downloads folder. Oddly enough, MO started after doing this, but after thinking a bit, I thought it was just coincidence, and moved the files again from NMM folder to some other folder.

Then I was using MO just fine, browsing Nexus and stuff. When I came back to MO to install some files I was downloading, the files were not there. I've clicked the links on mod's page again, and then realized it was not triggering on MO.

Closed the program, but it doesn't start anymore.

Restarted Windows, but nothing. Tried a clean MO manual install, but it still refuses to launch.

 

I'm using Windows 10 x64.

[GrantSP]

No problems at all, everything was working fine.

While following S.T.E.P., I was installing some mods that were already saved on NMM "downloads folder" (I was using NMM before switching to MO with a clean Skyrim install).

Then I moved the already installed mods from NMM to some other folder, since I was not sure if it was fine to place them on MO downloads folder.

Tried to launch MO after moving the files and it was the first time it didn't started. I thought MO could be looking for the files on NMM folder, so I moved the files back to NMM downloads folder. Oddly enough, MO started after doing this, but after thinking a bit, I thought it was just coincidence, and moved the files again from NMM folder to some other folder.

 

In your ModOrganizer.INI are the paths to the MO downloads folder pointing to the correct folder? ie. the folder that does actually contain the downloads.

 

Then I was using MO just fine, browsing Nexus and stuff. When I came back to MO to install some files I was downloading, the files were not there.

 

Where were they being downloaded to? Is that the folder used by NMM?

 

I've clicked the links on mod's page again, and then realized it was not triggering on MO.

 

The files your just mentioned were downloading, how did you initiate these downloads? Via MO? Manually? Using NMM?

 

Closed the program, but it doesn't start anymore.

Restarted Windows, but nothing. Tried a clean MO manual install, but it still refuses to launch.

 

I'm using Windows 10 x64.

If you could post your MO INI and the last set of logs from the 'logs' folder please? Either here in spoiler tags or via PasteBin or similar.

[Jarda]

 

MO.ini
LOG_1
LOG_2
LOG_3
LOG_4
LOG_5

 

• Yeah, I've checked it before jumping here, and I think the folders are ok on ini.
• They were being dowloaded(should be, but in fact they were not being downloaded in this particular case) on MO's download folder. And no, the only reason I kept NMM and mentioned it here, is because I didn't wanted to download all the stuff again, so I kept NMM installed but didn't touch it, just pointed MO to NMM downloads folder via "Install Mod" whenever I knew I had already downloaded the file in question.
• I've initiated the downloads via "Download with manager" button on Nexus.

I would like to thank you for your support.
 
EDIT: Just tried 1.2.18 and it works just fine. Other versions greater than 1.2.18 still doesn't work here. Guess I need some help to figure out which files I can copy to 1.2.18 directory, so I don't need to reinstall and configure all those 17Gb of mods again.
 
EDIT 2: After finishing setting 1.2.18 with the old profile, I accidentally clicked the 1.3.11 executable and it opened. I did nothing in my system, was just browsing with Firefox and messing around mod files. I will keep the 2 versions with shared downloads/mods folders for now, just in case 1.3 fails to launch again.

Edited April 12, 2016 by Jarda

[GrantSP]

Hmm... well the good thing is none of your downloaded mods will need to sourced again. The only change made by MO when you download a mod is the creation of a file named <name of the downloaded file>.meta, which is a simple text file that records information such as time, actual mod name, whether it is installed, Nexus URL, etc. These files can safely be removed when you move downloads.

 

If you move your MO install, all you need do is move the actual files from their current folder to the folder defined in MO as the "Downloads" folder. This also means these downloads are not the cause of this issue.

 

Now the execution of the NXM protocol used by Nexus needs to be examined since you say there was an issue here and when you installed a new MO (1.2.18) it worked and then the old MO (1.3.11) worked once more.

 

In the folder of each MO is an executable called: NXMHandler. Run it and note the path listed as to where each game is calling the ModOrganizer executable. You may have numerous versions of Skyrim listed and only one will point to the desired program.

 

e.g.

Skyrim -- D:\Games\MO\TES5\ModOrganizer.exe

Skyrim -- D:\Games\ModOrganizer\TES5\ModOrganizer.exe

 

In this case the top listed installation will handle the downloads and the files will be found in the "Downloads" folder of that install. This may not be the install that you desire.