GrantSP

These are how the arguments should look for those tools: nb. my paths are different, this is just to show which tool is referenced. 4\binary=D:/Games/Utils/LOOT/LOOT.exe 4\arguments="\"--game=Skyrim Special Edition\"" 6\binary=D:/Games/Utils/WryeBASH/Wrye Bash.exe 6\arguments=-g \"skyrim special edition\" 7\binary=D:/Games/Utils/xEdit/xEdit.exe 7\arguments=-sse(technically the last one is not needed as you already have it named in the binary field. This is just if you use the name 'xEdit' instead of 'SSEEdit') This sentence: makes me think you added the arguments to the 'binary' field. As for FNIS, is this the SSE version or are you using the version for classic Skyrim? Is this computer used by two or more users? Your xEdit logs show paths to 2 different user paths and one of them is to an OneDrive folder. That may cause issue if software is needed to create that folder. MO, and MO2, often are flagged as malware by certain tools and refused access to those locations. All other logs show no issues.

Without any diagnostic material to work from there is very little we can do, whatever logs you have will suffice and a copy of your INIs to see how you have setup those tools.

All the other columns may be moved around except for the 'Mod name'. You can however sort the columns by categories via the menu at the bottom of the window.

This is incorrect. The code used to launch the game is exactly the same as that to run tools. Do the tools run outside of MO2?

Logs and INIs please.

Considering this is the thread for 'classic' Skyrim, @Vakarlan better be using the original FNIS on his game or use the SSE version of FNIS on SSE!

All looks good now.

Have you run SSE at least once from its launcher, outside of MO2, to set the registry settinsg?

Are you able to change the instance to SSE from within MO2? ie. after you start MO2 open the 'Game selector' dialogue via the far left icon of the toolbar.

Win 7 compatibility mode on Win 7!!

Doing this from within the MO GUI has, at times, been a bit finicky. If all else fails just move the files into a newly created folder with Windows Explorer.

As for May 2017 @Brumbek has officially resigned from modding. This means this and the SSE version will be the last.

When MO was being developed Oblivion was not used extensively as a game in its support regimen, so I'm not really sure what will happen. Try and let us know.

Again, whilst I'm glad that you managed to get that to work, running it in compatibility mode isn't the true answer, it's just masking the culprit from being spotted. I have a Win10 machine and the full F&LNV plugin list (~127 plugins) and LOOT functions just fine. Without more diagnostic evidence to figure out what is happening, we can't determine what the true solution is.

Add that line to your Oblivion.ini, not the Oblivion_default.ini. After you can delete the profile_tweaks.ini if that is all it contains. Note this description of what that setting does as described here.

Never seen anything like that before. Check the main MO for stickied threads about software that may interfere with MO. Perhaps something is interfering with the execution of NVSE, though I highly doubt it. Aside from that your logs and mo.ini will be useful.

Try saving the empty file and then exit and restart. Quite possible MO2 is hanging on the save function and not releasing control correctly to Windows.

Check to see that no AV software is stopping the execution of the FNIS exe from MO. Check the sub-forums for the thread about what software can interfere with it.

Are you sure it is actually freezing and not just taking a long time? Whenever I close the CK it usually says it is "Not repsonding", but give it a few minutes and it will close and exit cleanly. In your case the 'hooking' code in MO2 needs to trick the CK, and also Windows, into saving the file correctly in the correct place. Depending on systems this may take some time.

Without some evidence to support your view, I'd have to say your conclusions are in error. It is impossible to install and activate a texture mod and it not show up in game. Checking the "Data" tab in MO will show you which textures are overwriting the default textures, and these are the ones used in game.

If that's all the logs that are being generated then there is a serious flaw with your MO2 install. Remove and re-install. Take note of the stickied threads in the MO sub-forum about software that may interfere with it.

Are you running the game via MO or are you still using the default Skyrim shortcut on the desktop, or even from Steam? The modded game MUST be called from MO as the mods are dynamically loaded on runtime.

Are there any logs or crashdumps generated? Logs we can help with but crashdumps, not so much. Sounds more like some issues with Windows or possibly some other software preventing those dialogues from accessing your system.

Those are general Windows file-selector dialogues, it would be good to also know what version of Windows you are running.

@Greg's description of what to do pertains to the left pane of MO, not the right. Once you activate the "Cleaned" versions in the left pane there will be ONLY one version of each DLC in the right. Therefore your question on disabling them is moot.