LOOT wont run?

[Tykune]

I was going through the STEP Guide and I ran LOOT earlier through MO, and it seemed to work fine. I then started downloading and installing mods, but when I got towards the end, I tried to open LOOT to adjust some metadata... and it doesn't seem to open. It brings up the message that my MO is being locked, but after a few seconds it just unlocks and LOOT doesn't come up. Opening LOOT outside of MO brings it up just fine, and it is definitely set up properly in MO as an executable.

 

Looking through ModOrganizer.log, it shows all of my mods being read and indexed, but somewhere in there I get a message saying "Windows Exception (c0000005). Origin: "C:\WINDOWS\SYSTEM32\ntdll.dll" (77d26d79). Last hooked call:"

 

That error is listed twice in a row and then some mods being indexed afterwards, but it doesn't seem to get through indexing all the mods.

 

Any help with this would be appreciated.

Edited May 28, 2016 by Tykune

[Tykune]

I have resolved the issue. Apparently is was Webroot SecureAnywhere's Heuristic Analyzer that was preventing LOOT from running completely.

[GrantSP]

I was going through the STEP Guide and I ran LOOT earlier through MO, and it seemed to work fine. I then started downloading and installing mods, but when I got towards the end, I tried to open LOOT to adjust some metadata... and it doesn't seem to open. It brings up the message that my MO is being locked, but after a few seconds it just unlocks and LOOT doesn't come up. Opening LOOT outside of MO brings it up just fine, and it is definitely set up properly in MO as an executable.

 

Looking through ModOrganizer.log, it shows all of my mods being read and indexed, but somewhere in there I get a message saying "Windows Exception (c0000005). Origin: "C:\WINDOWS\SYSTEM32\ntdll.dll" (77d26d79). Last hooked call:"

 

That error is listed twice in a row and then some mods being indexed afterwards, but it doesn't seem to get through indexing all the mods.

 

Any help with this would be appreciated.

The error would seem to indicate that LOOT, or at least a module associated with it, is still active in memory and therefore MO won't open another instance of it.

Reboot and see if that clears the issue, if not try simply removing the LOOT install and re-install it. Maybe there is a rogue setting retained that is somehow messing with its operation.

 

Lastly make a back-up of your ModOrganizer.ini and delete the current one. Run MO again and see if it works that time, if so simply reenter the settings for your executables again in the new one.

[rick830]

Did you add -single-process in arguments part of LOOT?

[pStyl3]

Did you add -single-process in arguments part of LOOT?

It's --single-process, and that argument was only advertised as a 'fix' for LOOT being blank if run through MO 1.3.11. If Tykune is using LOOT 0.9.0, this particular issue (LOOT being blank) shouldn't happen anylonger, because wrinklyninja was able to fix the bug on his end during the development of v0.9.0.

 

Tykune should follow GrantSP's advice for now.

[Tykune]

The error would seem to indicate that LOOT, or at least a module associated with it, is still active in memory and therefore MO won't open another instance of it.

Reboot and see if that clears the issue, if not try simply removing the LOOT install and re-install it. Maybe there is a rogue setting retained that is somehow messing with its operation.

 

Lastly make a back-up of your ModOrganizer.ini and delete the current one. Run MO again and see if it works that time, if so simply reenter the settings for your executables again in the new one.

I tried all of these and LOOT still seems to have an issue working. I even tried doing the --single-process in the off-chance that it may work, but no.

 

Update: So I disabled all of my mods and LOOT seems to work fine through MO, but when I re-enable all my mods, it refuses to open. Is a mods causing it to not open?

 

Update 2: So I decided to deactivate all of the mods and work my way down the list to see what mods may be causing the issue... but when I got down to soul gems differ and SSIRT, LOOT started to just open a blank white window, activating a few more caused it to just not come up. I deactivated all the mods and just ran those ones that it started having issues, and they ran through LOOT just fine. Is it possible that LOOT has a limit to how many mods/plugins it can handle?

Edited May 28, 2016 by Tykune

[GrantSP]

Just a reminder that correlation doesn't equal causation. In other words just because you experience the issue when you activate those mods doesn't mean they are to blame. Case in point SSIRT has no plugins that are handled by LOOT, so the chances it is causing this issue are slim.

 

Let's see what you're dealing with. Either zip the entire MO profile that you are using and post that here, or host it on an offline site and post the link. Also include yoiur ModOrganizer.ini and the contents of the 'logs' folder.

[Tykune]

Just a reminder that correlation doesn't equal causation. In other words just because you experience the issue when you activate those mods doesn't mean they are to blame. Case in point SSIRT has no plugins that are handled by LOOT, so the chances it is causing this issue are slim.

 

Let's see what you're dealing with. Either zip the entire MO profile that you are using and post that here, or host it on an offline site and post the link. Also include yoiur ModOrganizer.ini and the contents of the 'logs' folder.

Here is everything that was requested. Hope it helps.

STEP Core.7z

logs.7z

ModOrganizer.ini

[GrantSP]

Are you seeing any other issues with your MO install? Your INI seems to be very small and is missing a lot of settings.

Regardless let's try moving everything out of the UAC folder: 'C:\Program Files (x86)\' to somewhere where Windows doesn't have a strangle on those files.

Both MO and LOOT can simply be moved with explorer to another folder, or if you wish simply install separate copies and move the 'downloads, mods & profiles' folders into that new install. That way you can fallback if you bork the move.

I would also advise you to move your Skyrim into another location, but for the time being just MO & LOOT should suffice.

 

Additionally the logs show on this last set you provided that the error is happening on another mod to the one you initially thought, reaffirming that the actual mod it happens on is not the problem.

[Tykune]

Are you seeing any other issues with your MO install? Your INI seems to be very small and is missing a lot of settings.

Regardless let's try moving everything out of the UAC folder: 'C:\Program Files (x86)\' to somewhere where Windows doesn't have a strangle on those files.

Both MO and LOOT can simply be moved with explorer to another folder, or if you wish simply install separate copies and move the 'downloads, mods & profiles' folders into that new install. That way you can fallback if you bork the move.

I would also advise you to move your Skyrim into another location, but for the time being just MO & LOOT should suffice.

 

Additionally the logs show on this last set you provided that the error is happening on another mod to the one you initially thought, reaffirming that the actual mod it happens on is not the problem.

Wouldn't moving Skyrim out of the Steam folder cause more issues?

[GrantSP]

Skyrim + Steam can be moved to another location. All we want is to be free of the UAC folders. Steam has a setting that enables you to move games from their default location.

My Steam install is in a folder all its own.

Try moving just MO & LOOT first before tackling Skyrim as it may not be needed.

[rick830]

It's --single-process, and that argument was only advertised as a 'fix' for LOOT being blank if run through MO 1.3.11. If Tykune is using LOOT 0.9.0, this particular issue (LOOT being blank) shouldn't happen anylonger, because wrinklyninja was able to fix the bug on his end during the development of v0.9.0.

 

Tykune should follow GrantSP's advice for now.

Ah, you're right. I had an old version of LOOT. Updated yesterday and works without problems.

You should follow GrantSP'advice and move MO outside program folder and run every executable, skse, tesv, loot, fnis, mod organizer, as administrator. 

[Greg]

Running every executable as administrator is not necessary and is not advised.

[rick830]

Running every executable as administrator is not necessary and is not advised.

It's a suggestion based on my experience.

Running every executable as administrator solved some problems in my installation.

[GrantSP]

There is a big difference to 'solving' and 'obscuring' problems. Running MO, and tools called from it, as admin is not advised.

[Tykune]

Skyrim + Steam can be moved to another location. All we want is to be free of the UAC folders. Steam has a setting that enables you to move games from their default location.

My Steam install is in a folder all its own.

Try moving just MO & LOOT first before tackling Skyrim as it may not be needed.

Well, I moved MO and LOOT out of the UAC folders, but no luck. Still seems to be giving me that issue. I don't think running LOOT is even touching the skyrim folder at this point, since all the mods are in the MO folder, which isn't even in the UAC folders anymore. Should I still try moving Skyrim out to fix my LOOT issue?

 

Also, I just don't understand why it only does it when I am trying to run LOOT when a certain amount of mods are active.

Edited May 30, 2016 by Tykune