GrantSP

Whether the staff or the general user I stand by my statement that I can count on one hand the number of times any user has been advised to go elsewhere for help. In future anytime a user comes to you saying STEP has told them to come and ask you for help, you can rest assured they have probably never even posted here first.

The title of your thread refers to mods not being installed but the posts actually describe problems you have changing settings... so which is it?

Since you are using MO for Skyrim and not the new SSE version, you should use the latest 32bit version: 1.3.11.

On purely managerial level MO shouldn't be installed into your 'Documents' because it isn't a document! Defeats the purpose of named folders if you don't follow the schema. However the true purpose of renaming it is due to the name of the chosen folder: "Mod Organizer v1_3_11-1334-1-3-11" . No need for the duplication of the version numbering or to have the Nexus number included in it, MO is preferred or 'Mod Organizer' if you want more. Moving this is just a simple case of renaming the folder and then checking your INIs to see that nothing is 'hard-written' to point to the previous folder. Removing MO and installing fresh is also an option, ensuring to save your "profiles, mods and downloads" folders. Regarding FNIS, your included screenshot shows FNIS - XXL being called from: D:/documents/Mod Organizer v1_3_11-1334-1-3-11\mods\Fores New Idles in Skyrim - FNIS\FNIS Behaviour 6.3 XXL\Data\tools\GenerateFNIS_for_user This is not the location it needs. If installed correctly in MO FNIS will be called from something like: D:\steam\steamapps\common\Skyrim\data\tools\GenerateFNIS_for_Users MO parses the installed location to appear as though it is coming from the game's data folder, just as is done for all other mods. One last thing to mention. Your screenshot also shows the game launcher set to be run, your MO should be calling SKSE as the executable to run. Doing anything else will cause your game to fail.

Don't change those permissions! They are fine for the setup you have. Also not a good idea to make changes at the root level, at best you should examine the MO folder, but it will be exactly the same. If it isn't then there are some oddities with your Windows install. I only use Defender and it has never posed any trouble for me so you should be good to re-enable it. Without taking control of your system myself and seeing what is happening, the only thing I can think of is an installed programme is the default handler for some filetype that is common in your 'mods' folder. I personally have never seen anything do that but then again I've never seen the level of interference you have been dealing with on your system. Can you change the properties of MO's executable to only run as administrator? There is a context menu option to do so accessible from the shortcut. That's the last option I can offer. I usually advise against running it as admin because it can affect other tools called from MO but what options are left?

A couple of issues: You've installed MO into an overly complex folder. This will impact on Windows in the future with exceeding file length limits. Also I would advice against installing into 'Documents', just make a folder somewhere else and install MO there, ie. C:|Games\MO\ Secondly it looks like you have installed FNIS and then FNIS - XXL on top of that. Only one or the other is needed, best to stick with just FNIS.That second issue also raises something you need to be aware of with some archives installed in MO. It looks like you just pressed OK in the install dialogue instead of checking to make sure the mod was installing in the 'top level'. Please check the MO wiki and watch the video tutorials on what to do with this.

If you have space on your HDD you can create a D: drive and use that, but that is probably overkill for this issue. No, I wouldn't recommend installing Steam and your games in My Documents, any newly created folder directly off the C: drive will be fine. The main issue faced with the default location of these installs is that they are in UAC folders. Windows in its wisdom deemed some folders as too important for the user to fiddle with and placed account control on them, Program Files % Program Files (x86) being the main ones. As long Steam is outside those folders you shouldn't face permission issues. However I still think you need to track down what process is trying to gain control of those files. Anything non-Microsoft should be examined first. Then any driver software that you 100% are sure of comes next. This leaves software that may have been installed along with other software setups. Often bundle software slips through when you just let an installer do it automatically, choosing 'Custom' and then unticking stuff you don't need is the best way to go. I have an AMD graphics card and I always have to check that their extra software, like game overlays, doesn't get installed.

Those options will have no bearing on the issues you have been seeing.

@hazelwolf I just noticed you asked if there may be a problem with the guide and the latest version of NMM. Yes, most definitely. All the STEP hosted guides, including F&LNV, use MO as the manager of choice since it doesn't overwrite any files during installation of mods. If you actually meant to say MO then continue on regardless but otherwise your entire install will need to checked very thoroughly to make sure the correct files are winning the conflicts.

Once you have the two fully installed Skyrims in each computer it will just be a simple case of: installing MO on each install STEP on one copy the 'mods' & 'profiles' folders to the other PC ensure INI settings are correct on both enjoyThe only registry entries are for Skyrim and those are set once you start the game from the launcher at least once. To make things easier use the same drive and folder structure on both PCs, other wise you may need to tweak those as you go. At any stage just ask here and someone can step you through at tricky point. (shouldn't be any though)

That's the reason for your issues then, there is a rogue programme causing interference with your files. There is a tool I use called System Explorer, it's like Task Manager on steroids as it shows ALL running processes on your system, not just the ones Windows thinks you should see. Eliminate any suspicious processes and see if that allows you to progress further. So to sum up. MO isn't giving you grief, your system is. find and remove that process and all should be fine. On an unrelated matter, why use both Firefox and Edge? I prefer Chrome but Firefox is also a good choice but in my tests of Edge I wouldn't use it anywhere.

Just to clarify, you are talking about the number of mods, ie. those installed and shown in the left pane or are you referring to the number of plugins, ie those in the right pane? There is no limit to the number of mods you can have but Skyrim has a limit of the number of plugins that can be used, you have hit that limit now.

If you're looking at the properties for MO's install folder via Explorer, then that's fine, my folder too is shown as read-only yet I can make as many changes to those files as I like. It seems to me as though there is some other process stopping you from operating on those files. Are you sure there are no other software running on your system that is taking control? Or perhaps you are examining the contents in another window or maybe Skyrim hasn't completely terminated? Can you elaborate something for me? What exactly do you mean by this statement: Are you saying you have no access to those installed mods, even if viewed in explorer with MO not running? Navigating to MO's 'mods' folder will show a list of folders, each corresponding to your installed mods. Deleting them here will remove them from MO.

If you have subscribed to Steam then, yes, that will interfere with MO's operations. Unsubscribe from all Steam installed mods and use MO as the only manager of mods. There is nothing inherently wrong with Windows 10 with regards to MO. There are other issues with Win10 but that isn't the point. You may find this post of mine helpful with Win10's other issues.

Despite what your technician may claim, this problem is not due to MO. If it were then we would have 1000's of complaints of this nature. However this doesn't mean there is no solution. The error messages, though somewhat cryptic, are in fact providing you with a little information that may assist. In ability to perform actions on files/folders may be due to account access but can also be due to another programme having control over those assets. Check the settings of your AV software and make MO exempt from interference and redo those actions. This link may provide you with some more ideas as to what can interfere with MO.

As the MO wiki explains, 'Overwrite' ALWAYS has priority so anything inside it will always win a conflict. Not knowing what is in the plugin I can't say whether the INI tweak will be needed or not, trial and error.

While I'm glad you are able to use LOOT again, I fear the true solution is still out there. Running LOOT, or MO for that, matter, is not a true solution as both these tools work perfectly well for many users on Win10. Something else is different with your setup and it is that which needs to be isolated. Nevertheless it isn't your task to suffer through hours of trial just to find out what. Have fun.

LOOT issue does seem to be related to your Windows system, not specifically a MO or FNV fault. Aside from the usual recommendations to avoid UAC folders, which it looks like you have, try disabling any AV software or any game related tools also running such as those from Razer/AMD/Steam or the like. (In game helper applications) As for the error in the MO log, the mod tweak plugin looks to have an extra "." in the name, try renaming it.

Sounds like the message is coming from Windows, so I'd investigate your system, maybe a recent MS update has broken something. Perhaps you can take a screenshot so we can see what exactly is said and from whom/where.

When you made changes to the plugin using the CK the resulting file, Modname.esp, was saved into the 'Overwrite' psuedo-mod as expected. What you need to do is either drag that file into the mod that provided that plugin or create a new mod from the contents. The *.bak file can either be saved along with it or deleted, your choice.

Do your previous saves have mods that are not enabled, or in a different load order than that you are now running?

I can categorically state that STEP never sends users back to the pages of LOOT, xEdit, Wrye Bash or any other tool unless we are absolutely sure the matter is due to those tools. Incidentally this happens very very few times as all those tools are maintained correctly by authors that know what they are doing. MO2 is IMHO not in a state that warrants fulltime use, hence the disclaimer in the sub-forum header that it is very much a "beta" release. My apologies to you and the other maintainers that are coping some flak over MO2's quirks, but I can assure you it is not due to STEP shirking our responsibility.

I'm not sure what is going wrong with your install, try using these settings for LOOT and xEdit. I've created a separate folder away from Steam and my games where I place all my tools: D:\Games\Utils\ Under which I install LOOT, in a folder called LOOT and one copy of xEdit in a folder called xEdit. In my Skyrim Special Edition instance of MO2 I have those tools with the following arguments for LOOT and xEdit: "--game=Skyrim Special Edition" -sse In my Skyrim instance they are: --game=Skyrim -tes5 After changing your settings to these, please run MO2 for Skyrim and start both LOOT and xEdit and then paste the contents of the "logs" folder here. Change to Skyrim Special Edition and paste those logs also. nb. The logs folders are under your main MO2 folder in %appdata% and there should be separate folders for each game. Each folder should have at least 2 logs.

I don't know why you can't install Timing is Everything, it's just a simple archive with no FOMod script or anything! The best thing to do is to remove it from your Data folder because it does use scripts and you will need to ensure the correct ones are being overwritten, as it is now you can't do that. If worse comes to worse and you still can't install from inside MO just navigate to your "Mods" folder in explorer and create a new folder called: Timing is Everything. Use an archive extraction tool like 7Zip and extrract the contents into that folder. When you start MO it will appear as a mod in the left pane.

Just to get things clear, MO/MO2 is handling your installed mods properly, you're just not seeing LOOT function correctly? Could you post your modlist and also a screenshot of LOOT please?