GrantSP

So all the DLC's plugins and BSAs are back where they should be? If you still have the cleaned DLC in their own mod there will be nothing you need to redo. If they need cleaning again, do so and be sure to keep the result in their own mods afterwards.

Adjust your INI to look something like this: 4\title=LOOT 4\custom=true 4\toolbar=true 4\ownicon=false 4\binary=D:/Games/Utils/LOOT/LOOT.exe 4\arguments="\"--game=Skyrim Special Edition\"" 4\workingDirectory= 4\steamAppID=

Hmm... don't worry about your INI for now. Reacquire the files by verifying your game via Steam as @Nozzer66 suggests. Somewhere along the line you've removed those files.

Skyrim will need to be run at least once from it's own launcher to set the registry entries. 0kb logs mean MO2 has been unable to 'hook' the game or tool. It would have been good if you told us that you did a clean re-install of everything before you posted these files. Nevermind, we can work from the state you currently have it.

Welcome to STEP @Vuulgar According to your INI you are trying to run SkyrimSE in a Skyrim instance of MO. SkyrimSE should be run from MO2 in it's own instance that has specific settings for that different game.

We always prefer to have posts remain up so if you could outline what your small snafu was that would be helpful. PS. We all make stupid mistakes from time to time, don't worry about it, it's part of the learning process.

The plugins will exist in the right-hand pane because the cleaned versions are either still in 'Overwrite', most likely, or you have moved them into a new mod, not likely with your experience so far. This however does not explain why the DLCs are not shown as "Unmanaged" in the left-hand pane. Post your MO INI and a screenshot of your MO UI so we may see the error. Additionally provide as much detail as possible about your Skyrim install.

Welcome to STEP @Jaquavius Question: why are you going through all that rigmarole to enable archive invalidation? Just open MO and press the 'Configure Profiles' button and then check the "Automatic Archive Invalidation" selector. That's all you need do. MO will now, on runtime, add the BSA it uses to perform this task.

MO wiki section called: Overwrite. Summary of that section is this: do not leave files in the 'Overwrite', decide if they are temporary or needed and either delete them or move them into existing mods or create new mods from the contents.

CTD's are most likely due to missing masters. What master files does the mod you installed require? Check this thread as to common causes of CTDs.

Was there not another log called something like: usvfs-2016-12-28_17-31-26.log? Possibly more than one with differing timestamps? I see no entries in your INI other than LOOT. How did you call SSEdit and Wrye Bash? The drive that you have your mods and LOOT installed to, is that a NAS device or somehow controlled by software?

In a personal conversation with him it was discussed to remove for the following reasons: as described above a few users have errors the internal sorting lacks the reporting features and thus you are unable to edit metadata @Tannin was initially going to incorporate all the LOOT features into MO at a later stage, that's now not going to happen it makes more sense to have an essential tool developed by the original developers it's just as easy to call LOOT as it is to press 'Sort'.

Welcome to STEP @Zanoth Nice to hear more are trying to work on the repo. As for the 'Sort' button, it is going to be removed in favour of using the full LOOT program so your edits may be rendered useless. :confused:

Post your INI and the logs so we may examine them.

Marketing! Most users won't look for an editor for TES5 on a FO4 page or a LOD generator for TES4 on a FO3 page. So a different tool is named and released on each game's forum. I'd also add most users will find adding game switches to their arguments a bit confusing. I may be downplaying the IQ of a lot of users here but that's my take on it. Of course they could just rename them, but that too may be too much for the genaral punter.

Okay, that's good. That's the same release I'm on. Only thing left I can suggest is to post a report on his issue tracker. I'm all out of ideas, sorry.

Last idea I have. Are you using this release or one of the last from @Tannin?

Well sad to say, I'm out of ideas. Especially since MO runs FNV from that drive! I see you've got your Steam details entered in MO (don't worry, there encrypted in the INI so no-one can steal them.), try closing down Steam and see if MO2 will start it for you. It works for me without hassle.

Hmm... is your "I" drive a network attached device or perhaps controlled by software? Since we've ruled out everything else I can only assume there is another layer of software that MO is being hindered from accessing. If it is try and add it to your anti-virus exceptions list or check to see if that software has full admin access rights. If it isn't a NAS there still must be some thing interfering with MO's 'hooking' of the Steam game, perhaps an overlay program from your graphics card or similar. My AMD install tried that with Raptr and it messed with me similarly.

You'll need to start the game from the desktop at least once to have the launcher set the registry values.

I had these values set with the previous version of LOOT and after updating to the latest, these values have been automatically changed to 127. This is the value I have been changing the STEP guide to use. I missed this mod's page and have now changed it.

ALL tools need to be called from within MO to 'see' the current profile's list of mods.

Open the ini in an editor and remove the extra entries here: [customExecutables] 1\title=Skyrim 1\custom=true 1\toolbar=false 1\ownicon=false 2\title=Skyrim Launcher 2\custom=true 2\toolbar=false 2\ownicon=false 3\title=LOOT 3\custom=false 3\toolbar=false 3\ownicon=false size=3 1\binary=I:/GAMES/STEAM/SteamApps/common/Skyrim Special Edition/SkyrimSE.exe 1\arguments= 1\workingDirectory=I:/GAMES/STEAM/SteamApps/common/Skyrim Special Edition 1\steamAppID=489830 2\binary=I:/GAMES/STEAM/SteamApps/common/Skyrim Special Edition/SkyrimSELauncher.exe 2\arguments= 2\workingDirectory=I:/GAMES/STEAM/SteamApps/common/Skyrim Special Edition 2\steamAppID=489830 Everything in that block starting from: 1\binary=I:/GAMES/STEAM/SteamApps/common/Skyrim Special Edition/SkyrimSE.exe can be deleted. MO should recognise the default executables and call them without explicitly adding the paths as the registry will hold the correct game paths.

Herein lies the issue. Depending on how you had NMM setup you probably have masses of files strewn throughout your Skyrim installation. All of which need to purged to avoid conflicts with MO managed files. Specific to FNIS, you will need to remove the NMM installed version completely and then install it via MO if you want to use it. It is probably easiest to do that with ALL your NMM installed mods and re-install them via MO. @GamerPoets has a lot of tutorial videos on all manner of MO related stuff and I strongly urge you to watch some of those. Also the MO wiki contains all you need to answer most of the common questions about MO.

As this has progressed from a basic MO related question to a more generalised STEP install question, I'll move the tread. @GrantSP