GrantSP

Well, yeah, 18kb is small but the blank template is only 1kb so it definitely is your creation.

Is your copy of Windows 10 the so-called "Creator" update? Reports are starting to come in that it is breaking the functionality of MO/MO2.

Check your settings. Make sure the path to the copied profiles matches that in the settings.

There's no problem really, all that is happening is the report file (the HTML) is still under MO2's control when WB tries to release it to be viewed in your browser. The actual patch is still being created so your game should be fine. I guess there is a slight timing error in the 64bit code compared to the 32bit code of the original MO, but that's not going to fixed anytime soon, as there is no longer any active development of this tool.

What version of Win10? Many reports of the so-called "Creator" update (v1703 I believe) breaking MO's functionality. Your report is more to do with MO than LOOT as these sort of reports are almost never heard of with non-MO users.

Is this a legitimate copy of Skyrim?

Sounds like you may be having permissions issues. The INI should be saved when you close the dialogue but if it is being reverted either Windows, or another process, is stopping the file from being correctly saved. This may also be the cause of the modlist not reflecting the correct list.

Previously you said you re-installed both MO & LOOT into folders directly off the root, that screenshot shows them as still sub-folders of your Steam install.

That's not the question you should be asking. Although MO's built-in LOOT is the same api as that from LOOT, the real question is why your MO install isn't working properly. Any tool you run from MO may suffer the same fate.

NAS software, firewalls, AV software, game overlays, ingame chat apps or anything that interferes with the files currently in use.

So are you now saying LOOT doesn't even load? Even if it does start and shows the incorrect plugin list there should be a log to show this. Are you sure you have no other software running that is interfering with MO's functionality, as per my link referred to earlier? If there are none please try this. Uninstall both MO and LOOT and install away from your Steam library. Just place them in their own folders off the root directory, or off the "Games" folder. e.g. C:\Games\MO, C:\Games\LOOT

Okay so it looks like you're modding Fallout 4. There are still a few issues with MO2 and FO4, one of which is the need to close the programme after each tool is called otherwise a crash happens. Sadly I don't see any resolution for MO2's issues as there are no developers actively working on it anymore.

Please post your logs.

In the log you posted above there is an entry saying it is also creating the: usvfs-2017-08-19_16-37-34.log. Please delete ALL logs and then post the contents of ALL the new ones created. There should be at least 2.

Just edit it in the 'Settings' dialogue, much easier to do. If you must edit the INI this is what you will have: 4\binary=D:/Games/Utils/LOOT/LOOT.exe 4\arguments="--game=\"Skyrim Special Edition\" --single-process" Of course the paths will be different, but you get the idea. The entire argument is encapsulated in quotes, but this is an internal MO setting to tell it to read these things "as is". The actual text string "Skyrim Special Edition" needs the slashes before each quote so that the "" are read as part the string, otherwise the spaces will break it.

Yes it's clean. If LOOT says so then you're okay to proceed.

If you're looking at the INI it will appear as this: arguments="--game=\"Skyrim Special Edition\"" However as I said the blank screen issue is resolved by others by placing the: --single-process argument in the settings.

@alt3rn1ty Excellent! Could not have put it better myself.

Don't use MO2 for FNV. Just install MO 1.3.11 and use that instead, it's much more stable and you will have less trouble with it.

If you are still getting the blank screen try adding this to the arguments: --single-process Also the "" can be like either @GSDFan or I described it, the important thing to remember is that you need them after the argument processor: -- this is so the spaces are viewed as part of the argument, not a terminator. Thus "game=Skyrim Special Edition" is identical to game="Skyrim Special Edition"

Add the argument to the LOOT entry in the INI: "--game=Skyrim Special Edition"

This is a more in-depth discussion on this matter. The most likely culprit is the 'Gamebar' in the latest update of Win10, scroll to the last few posts and follow the steps there or go to the "Tricky software" link in my signature. In any case. in the future, please post your logs so we can diagnose those, they are designed for that purpose and are much better than screenshots.

Yes.

Just to clarify something. Any issues you may face with editing plugins with the CK via MO are NOT the fault of MO. It is just a tool to provide a set of mods to either the game engine, or in this instance, the Construction Kit. Crashes are just part and parcel of the crappy tools Bethesda supplies the user and any "unwanted" overwrites are due to the user not being aware of what files are being saved and where.

I can't test it at the moment, I'm still version 1607 of Win 10 and the so-called 'Creator' update is 1703. However from the few reports I've gotten so far I think it may be a setting that can be turned off. Failing that I hae reached out to a few coders that may be able step in and do "fix" if necessary, still in the discussion phase at the moment. The big difference with MO and any other manager is the hooking process that @Tannin developed, he expanded on his thesis project about malware and hence the underlying code looks to Windows as malicious and may be turned off somehow. Having the ability to keep a clean 'Data' folder, and the use of multiple profiles is a good selling point of MO/MO2 but if that fails it may be time to call it a day and look elsewhere. As for Windows 7, I doubt there are any concerns with it. Microsoft has just as much wiped their hands of it and have stated they will no longer support it in newer CPUs so I can't see any fancy patches or updates coming along that render MO broken on that platform.