federation25

I just wanted to let you know since you wanted an update... though it has drifted a bit off the topic. All the tools work with the new MO unless they run for longer than a few minutes, then the virtual file system craps out. This means that DynDOLOD never has time to complete before the VFS becomes unstable (though TexGen was able to finish). I'm not going to report this to Sheson since the error clearly points the finger at MO2 (which is still in beta). I think I can make this work, but it will likely involve using both the stable and beta versions of MO to get around the respective issues. LOOT still doesn't work on the stable build with no clear reason why.

I myself am not really a proponent of using test software for daily use, but it may be a near necessity in my case, given my issues with the stable release. I'll find out this weekend if it is able to do the job once I rebuild my STEP profile.

It started out as 1.3.11 from the Nexus. After making little headway, I installed the v2 beta more or less out of desperation. For whatever reason, that version launched LOOT without any problem. I just tried to launch into safe mode fifteen or so minutes ago and something is going on there. If I were to hypothesize, I'd say the problem is a damaged Windows system file. If that is the case, MO v2's 64-bit support could mean that it is either binding to a 'safe' entry point in said library or an entirely different library in order to support 64-bit games. I did look up the specific error code that was logged when LOOT fails to start with the stable version of MO. Error c0000005 is an Access Violation, specifically writing into a restricted memory space (based on my reading).

I'll play with the stable build a bit as well and see if I can puzzle out the root cause in the event that anyone else runs into it. Thank you for taking the time to try to help me out though.

Blowing away the AppData\Loot folder did not work either. My current install is from the archive version, though I believe that the original install (i.e. the one that original broke) was via the installer. What just worked though is installing the Mod Organizer v2.0.7 Beta 3. With this beta build, LOOT launches without a problem. This makes me suspect an issue in the current stable release that has been fixed for the next release.

Crazy thing is that I also did a manual install of one of the old 0.8.1 version to test and that one was effected too. Except for MSE AV updates, I don't see any Windows updates during the period when it broke. I *did* install a new Wi-Fi card into my computer over the weekend though its a bit weird that it would stop LOOT from working (at least from my perspective). Naturally, I went to the LOOT Github only to find a disclaimer that they didn't support issues when used with MO. Also disabling AV real time protection and adding exclusions did not have any effect. My copy of Malwarebytes is the free (on-demand) version that only runs manually.

Yes, the exe reference in MO was completely redone. I have even gone so far as to completely wipe everything and re-install MO and LOOT from scratch again, configuring both per the STEP guide. I tried turning on DEBUG logging after launching LOOT directly to see if it could log a cause of the crash. However, it doesn't seem to actually get very far when run through MO as no log file (even an empty one) is generated during that run through.

Unfortunately, LOOT still won't launch from within MO. On the plus side, moving my Steam install did let me clean things up a bit. Its the same error message as before albeit for the new install directory. LOOT will launch successfully from outside of MO. Furthermore, LOOT is the only application impacted. xEdit and Wrye Bash both launch without any problems.

I'll move my Steam install and report back the results.

I fear that I have to report the same issue, but this time it was with LOOT 0.9.0 (which had been running happily since not long after release) on Windows 7. LOOT runs when launched as standalone, but it won't open when launched through Mod Organizer. I tried adding the --single-process argument, but that did not show any change in behavior. I also remove 0.9.0 and updated to 0.9.1 with no change. [spoiler=Event viewer shows this exception]Faulting application name: LOOT.exe, version: 0.9.1.0, time stamp: 0x576b84b3 Faulting module name: ntdll.dll, version: 6.1.7601.23418, time stamp: 0x5708a73e Exception code: 0xc0000005 Fault offset: 0x0004e6df Faulting process id: 0x1f40 Faulting application start time: 0x01d1d1285ab049ab Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Skyrim\LOOT\LOOT.exe Faulting module path: C:\Windows\SysWOW64\ntdll.dll Report Id: 98eace68-3d1b-11e6-b4d0-0c84dc7885d6 I would note that I ran LOOT without problem just a day or two earlier, but it broke on Monday (June 27) evening without obvious cause.