Mod Organizer not working since 1.3

[M0rr1s0n]

Hi guys!

I just wanted to start a new setup and therefore made an update with Mod Organizer to the recent version 1.3.11. But since then I can't start the program anymore, because there's always an error with loading the "archive.dll" file.

I saw a few posts here and on Nexus forums where there were people who had the same issue, but no one could give any advice to resolve those issues. The bug tracker has this issue as well, but it was closed as "not reproducable" (https://issue.tannin.eu/tbg/modorganizer/issues/1100)

I already did a clean install a few times, but it doesn't seem to help :(

 

Every version below 1.3 is working fine, I'm using Win 7 x64.

 

[GrantSP]

Welcome to STEP @M0rr1s0n

 

The issue reported was not closed because it is "not reproducible", that specific error was because the user did not have his setup correct. As he notes after creating a 'downloads' folder the archive.dll now knows where to grab the files for processing.

 

I'm not entirely why he, or you experienced that issue, the installation should create all the necessary folders and therefore not see this problem.

 

If your issue is not related to importing files from NMM perhaps you could actually detail what is the circumstance that triggers this? Your INI and logs would also be helpful.

 

 

As a reminder, the "Bug Genie" has been closed for some time now as all work is now shifted to the GitHub repo and the issues are now handled there.

[Greg]

Have you tried disabling your antivirus software or adding an exception for Mod Organizer to see if this solves the problem? You might also verify you haven't installed Mod Organizer in a UAC protected folder (like C:\Program Files or C:\Program Files (x86).

[M0rr1s0n]

Welcome to STEP @M0rr1s0n

 

The issue reported was not closed because it is "not reproducible", that specific error was because the user did not have his setup correct. As he notes after creating a 'downloads' folder the archive.dll now knows where to grab the files for processing.

 

I'm not entirely why he, or you experienced that issue, the installation should create all the necessary folders and therefore not see this problem.

 

If your issue is not related to importing files from NMM perhaps you could actually detail what is the circumstance that triggers this? Your INI and logs would also be helpful.

 

 

As a reminder, the "Bug Genie" has been closed for some time now as all work is now shifted to the GitHub repo and the issues are now handled there.

Thanks for the welcome, I read a lot passively and followed STEP a few times, now I had to make an actual account for the issue I have with MO :(

The folders are all there, I just checked it, my MO.ini was set back a few times, but that also didn't fix the problem. Here is the content of the mo_interface.log:

 

00:47:02 [D] ssl support: 0

00:47:02 [D] Working directory: F:\Steam\steamapps\common\Skyrim\Mod Organizer

00:47:02 [D] MO at: F:\Steam\steamapps\common\Skyrim\Mod Organizer

00:47:02 [D] initializing core

00:47:04 [D] save F:/Steam/steamapps/common/Skyrim/Mod Organizer/webcache/nexus_cookies.dat

And this is my ModOrganizer.ini:

https://pastebin.com/Es3287aq

 

Have you tried disabling your antivirus software or adding an exception for Mod Organizer to see if this solves the problem? You might also verify you haven't installed Mod Organizer in a UAC protected folder (like C:\Program Files or C:\Program Files (x86).

Hi, yes I made an exception for the Skyrim folder and also for the "archive.dll" file as well! It is, and ever was, installed in the Skyrim-folder which is on a different drive. So UAC shouldn't be the problem.

Edited January 30, 2016 by M0rr1s0n

[GrantSP]

Your log seems short. It's last entry is the webcache, delete everything from that folder and try to start MO again.

Also clear the logs folder and can you post all logs that are created?

[M0rr1s0n]

I cleared the webcache folder and startet the MO.exe again, the error was the same. This is the log-folder and its opened log beneath it:

 

 

Nothing more unfortunately.

[Greg]

From looking at the generic "cannot load library the device is not ready" error, this seems to be caused by permissions or something is locking the file so Mod Organizer can't load it. As silly as this might sound, browse to the ModOrganizer/dlls folder in Window Explorer, right click on archive.dll, click Properties, and see it is has an "Unblock" icon in the bottom right of the Properties dialog. If it does, click it and try running Mod Organizer again. If this isn't it, temporarily disable your antivirus and try running ModOrganizer.

 

The only other thing I can think of is possibly installing the Visual C++ Redistributables Package for Visual Studio 2013, but I wonder if Mod Organizer will even start if it's missing mscvrt120.dll -- although I suppose this is dependent on the order of LoadLibrary calls in the code.

[M0rr1s0n]

Disabling my AV was something which came to my mind too, but it didn't help. I just checked it again, same result.

Archive.dll ist not "read only", the unblock dialog was there and I just clicked it and confirmed. But I get the error anyway, with the same error message. :(

 

I also repaired my install of VisualC++ for Visual Studio 2013 because the 64bit version was already installed, but guess what... no success!

 

I'm really pulling my (last) hair out because of this...

[GrantSP]

This is an installation that's had some updates applied isn't it? Although it should make no difference, grab the archive version of MO and extract it to a temp location and run MO from there. This will provide us with a base mark to work from. If it works from there then there is something up with your settings in MO, which can then be fixed. If it doesn't work from there then there is some system wide error causing it.

 

It's really strange how that error comes up for so few people. For the record I have never seen it on any installs, from 1.2.x onward on a Win7 -- Win10 upgrade machine, all the way to my current Win10 fresh install.

You would imagine if there was a system file mismatch or missing component more people would have noticed.

[M0rr1s0n]

No I haven't made any updates, it was a fresh install of MO, because I haven't modded for approx. half a year and wanted to set it up all fresh and new.

I installed it on a different drive for testing purposes, the result was as expected:

 

 

It must be a system wide issue, but it's nearly impossible to find out, when there are so few people who have the same problem. At least there are a few people, and I'm not alone in this.

[GrantSP]

I'm sorry I have nothing more to add. Perhaps you can post this as an issue on the GitHub? @Tannin is in active development of MO version 2 but he spends more time there than here. He will have more insight.

[M0rr1s0n]

Thanks anyway for your help, guys! I just opened an issue on GitHub: https://github.com/TanninOne/modorganizer/issues/533

Maybe Tannin has an idea, what I might try to get it working! :)