Updating LOOT Problem MO

[reddvilzz]

Hi there,

 

Recently I just updated LOOT from 0.9.0 into 0.9.1, before updating LOOT just run well no problem at all.

After I updated the LOOT now MO won't open LOOT anymore, every time I click run with MO it just showing dialog and then the dialog is closed without showing LOOT. So I tried reverting back to LOOT 0.9.0 to see if it is the problem on 0.9.1 but with LOOT 0.9.0 the same problem occurs.

I tried adding the --single-process in the argument tab, uninstalling then reinstalling, tried with fresh installing MO, deleted LOOT folder on Local/LOOT none fix my problems.

 

Anyone know the solution perhaps?

[GSDFan]

When I updated to 0.9.1 I had a crash on initial run, but a second try it ran fine. Have you tried setting the game in the argument? --game=Gamename, where gamename is the name of the game.

[DMCbr]

Maybe some windows registry issues? Try a cleaner tool, like CCleaner.

I use this tools once a week to keep the system health.

[GrantSP]

Completely remove the contents of the LOOT folder, including the sub-folders, and install the complete contents of the latest zip apackage for LOOT to the same location as the previous install.

All the settings in MO will point to the same files so you should be able to just run it as you did before. If there are problems navigate to the AppData\LOOT folder and remove the settings.yaml file and try again.

The only registry settings LOOT uses are those set by the various games so you should have no need to worry about the registry.

[reddvilzz]

When I updated to 0.9.1 I had a crash on initial run, but a second try it ran fine. Have you tried setting the game in the argument? --game=Gamename, where gamename is the name of the game.

Well I tried adding --game=Gamename nothing happened, I don't think this argument do anything related to LOOT not opening

Maybe some windows registry issues? Try a cleaner tool, like CCleaner.

I use this tools once a week to keep the system health.

Completely remove the contents of the LOOT folder, including the sub-folders, and install the complete contents of the latest zip apackage for LOOT to the same location as the previous install.

All the settings in MO will point to the same files so you should be able to just run it as you did before. If there are problems navigate to the AppData\LOOT folder and remove the settings.yaml file and try again.

The only registry settings LOOT uses are those set by the various games so you should have no need to worry about the registry.

I've cleared the folder even I deleted the entire folder that have LOOT name on it, reinstall and still won't opened. Maybe registry like @DMCbr said? I'm not sure.

[GrantSP]

Does LOOT start outside of MO? If it does then there is an issue with your entries in MO's settings for it.

[GamerPoets]

I know that when you delete any 3rd party application from MO it still points to the old .exe/shortcut. Even if you deleted the old folder it could be pointing to the old, non-existant .exe . Have you tried deleting the LOOT .exe from MO's dropdown and then adding the new binary back? I read where you deleted the LOOT folder but not the MO "gear icon" entry.

[reddvilzz]

Does LOOT start outside of MO? If it does then there is an issue with your entries in MO's settings for it.

Yes it start just fine without any problems

I know that when you delete any 3rd party application from MO it still points to the old .exe/shortcut. Even if you deleted the old folder it could be pointing to the old, non-existant .exe . Have you tried deleting the LOOT .exe from MO's dropdown and then adding the new binary back? I read where you deleted the LOOT folder but not the MO "gear icon" entry.

I've deleted the MO entries twice and re assign the binary to the new LOOT folder. I tried with different LOOT folders and none works.

[GamerPoets]

I'm a bit lost. Shouldn't be much more too it than everything that it appears you have done. 

My prsonal off the head checklist...

-If you installed LOOT using the installer there is an uninstaller that comes with it I believe. Run that. (everyone else's suggestions were good as well but you've done that all)

-When installing the new version install the LOOT folder to the games folder

-Make sure the game has ben launched from its .exe in it's game folder at least once

-If Steam/Game folder is installed to program files folders set the game folder's properties to give full permissions.

-Delete the old .exe from the gears icon and add the new one. (already done). 

 

I've spent the last two days reading over and rewriting every piece of the LOOT "readme" for my own purposes and nothing is coming to mind. Not making sense to me. Hopefully someone else has more info. I'd like to hear about the resolution. 

[reddvilzz]

Maybe I'll recheck every thing from your lists after I get back home and post an update here if it works.

 

Thank you

[GrantSP]

Could you open the Modorganizer.INI and copy in here just the section that defines the LOOT entries? It will look something like this:

9\title=LOOT
9\custom=true
9\toolbar=true
9\ownicon=true
9\binary=D:/Games/Utils/LOOT/LOOT.exe
9\arguments="--game=Skyrim"
9\workingDirectory=
9\closeOnStart=false
9\steamAppID=

Here I have LOOT installed into a folder outside any UAC folders and also away from Steam or game controlled folders, LOOT gets all it needs to know about your game from registry entries and can be installed anywhere. I also have the Skyrim specific game switch, since I use the same executable for all my Bethesda games and this way I don't have to manually switch it using the builtin menu LOOT has.

 

Since it works just fine outside of MO there shouldn't be any issues with Steam updates breaking the registry entries but just incase run the game launcher from the desktop to ensure those are correctly set.

[reddvilzz]

Here is the Modorganizer.ini

 

 

4\title=LOOT
4\custom=true
4\toolbar=false
4\binary=C:/Users/Vague/Desktop/Skyrim Stuffs/LOOT/LOOT.exe
4\arguments="--game=Skyrim --single-process"
4\workingDirectory=C:/Users/Vague/Desktop/Skyrim Stuffs/LOOT
4\closeOnStart=false
4\steamAppID=

 

I never place LOOT in any of the UAC folders, because I know the problem with UAC

 

Edit; I have done GamerPoets checklist and still won't open at all, I've re add it, here is the ModOrganizer.ini

 

 

 

13\title=LOOT
13\custom=true
13\toolbar=false
13\ownicon=false
13\binary=C:/Users/Vague/Desktop/Skyrim Stuffs/LOOT/LOOT.exe
13\arguments=
13\workingDirectory=
13\closeOnStart=false
13\steamAppID=

Edited June 25, 2016 by reddvilzz

[reddvilzz]

Can't edit the previous post

 

So I tried cleaning registry with CCleaner and then decided to follow GamerPoets's installation folder. I decided to install LOOT on my D:/Steam/steamapps/common/skyrim

Then it is working now. But I tried copying the LOOT folder on steam back to all of my skyrim utilities folder it won't work.

I've check permission for that folder and everything is checked, and what seems to bother me is that before LOOT was working when I put there just before I update it

But now it seems not working at all even when I put it just on desktop or anywhere on C:/

 

So I'm guessing it is because something in C:/ that makes the problem. Because permission wise I've put C:/ and D:/ in full control since I am the administrator. Maybe someone can explain what is wrong with my C:/?

In my D:/ there is Authenticated User in the Group or Username section while there is not on C:/ the rest is all the same, SYSTEM, administrator, and me all in full control.

 

Edit: Tried adding new user to match the Group or Username Section in the permission for the my skyrim utilities folder in C:/, LOOT won't open as well.

Edited June 25, 2016 by reddvilzz

[GrantSP]

Check your AV package, the change of version number may have triggered a different response from it and it could become blocked when MO tries to initiate it. Many AV software packages view the 'hooking' by MO as malicious as it is very similar to the way nefarious applications gain access to system files.

Whatever AV you have either temporarily disable it or if you know how, setup an exclusion for MO so it isn't checked.

[reddvilzz]

Check your AV package, the change of version number may have triggered a different response from it and it could become blocked when MO tries to initiate it. Many AV software packages view the 'hooking' by MO as malicious as it is very similar to the way nefarious applications gain access to system files.

Whatever AV you have either temporarily disable it or if you know how, setup an exclusion for MO so it isn't checked.

When I tried using the old version 0.9.0 it won't opened as well even in C, isn't it perhaps permission problem?

Because my AV shows nothing and didn't block anything when I try to open LOOT.

[GrantSP]

 

I decided to install LOOT on my D:/Steam/steamapps/common/skyrim

Then it is working now.

If by that statement you have a working LOOT called from MO, then go with that. I can't see anywhere the system OS specified so I'm assuming Win 10, that being the case we have seen a few oddities with access differences compared to Win 7 so maybe you are seeing that too. It really wasn't a straight-forward upgrade by MS, despite what they say.

The way you describe your setup, I too can't see any reason why there is an issue.