GrantSP

The game loading outside proves nothing regarding AV interference. The very method used by MO to 'hook' these executables is the same as that used by some viruses and malware. MO reads the code in memory and tricks it into using the paths to mods as found in its setup and then allows it to continue its original execution with these new paths. That's the boiled down, simplified version anyway. For this reason using MO will ALWAYS be a tricky matter as the more levels of software that are loading all need to be tricked in the same manner. If Steam just updated for you make sure you haven't got its overlay running in the background, likewise for any other software that sometimes bundles "helpful" tools like those. Your graphics driver software may also try to install some game overlays and these should either be removed or turned off. The log is showing MO failing at the time SKSE loads TESV so something on your system is stopping that process from continuing. If none of the above helps you may need to examine the location of Steam and Skyrim to ensure UAC is also not enabled there. If you have another drive Steam might be better installed there, though this should be considered a last choice as I can't see the folder you created as being at fault, but you never know with Windows!

How do you have the SKSE scripts installed? STEP recommends having them as a mod installed via MO which would mean your log would finish with something like this from one of mine: DEBUG (13:45:07.0808): all hooks installed INFO (13:45:07.0808): injection done DEBUG (13:45:07.0808): first access to SKSE Scripts v1_07_03 DEBUG (13:45:07.0808): get file attributes: D:\steam\steamapps\common\Skyrim\Data\SKSE\skse.ini -> D:\Games\ModOrganizer\TES5\mods\SKSE Scripts v1_07_03\SKSE\skse.ini: 20 DEBUG (13:45:07.0808): create process (a) D:\steam\steamapps\common\Skyrim\\TESV.exe - null (in null) - hooking DEBUG (13:45:07.0983): hooks removedThe log should then begin again but this time using TESV.EXE as the 'hooked' executable.

Welcome to STEP @Wombler Please create a new blank MO profile and see whether it will start with no mods loading. Although you haven't changed anything in these runs, clearly something has changed, software just doesn't refuse to work for no reason. If the new blank profile works you will have to work your way through your list and see which mod isn't working properly and fix that.

I'm led to believe the GOG version of both the Fallout games just released have LAA enabled by default, so there's one bonus right there. You should see no issues regarding not using Steam when following this guide.

Major backend rework is in the wind for sometime soon. Also the entire structure is going to have a site re-structure to try and compensate for these sort of things. Sadly all we can do for now is grin and bear it.

Yeah, like Tech says, check your install. Those BSAs are definitely not from Skyrim but rather from SSE.

Yes, very good catch. I think we all missed something.

Select SKSE from the list of executables in MO and then run that. Any mod that requires SKSE to function will of course fail if it is not loading. ps. The 'access violation' is, I believe, a result of poor exit code handling. Could be improved but it doesn't affect the game as it only occurs on game exit when nothing can go wrong with your saves.

Okay so I've re-read your posts and I now see that we talking about a specific set of mod conflicts and not a general MO issue. Check what masters Convenient Horses needs and then ensure they are active and loading before its plugin. Also since you are trying to load a save game, make sure all mods that were active during that save are still active.

That last line in the log is nothing to worry about, it occurs in almost every run and is not an error as such, hence the INFO header for it. Open your 'Settings' in MO and ensure your "Log Level" is set to 'Debug'. Run Skyrim again and post that log please. However the entire block of your log is regarding: TESV.EXE and not SKSE_LOADER.EXE. Are you sure you are running the game by calling SKSE from MO and not the game itself?

Create a new post and post your log there, but before that remove all the lines in your MO ini that I have highlighted in your post. Explicit entries for the basic executables are not needed as MO reads these from the registry.

Can I see your MO ini please? Your log is calling the SKSE dll in the last part and this doesn't usually happen Also where did you get your copy of SKSE? From Silverlock.org or Steam? There is an error in your log that is looking for 'translation.cpp' which I have not seen before. Related to that have you installed the scripts for SKSE as per instruction in STEP?

Logs please. Also a copy of your INI. To clarify, you are trying to call SKSE from MO, not the Skyrim executable?

By the "latest" version I hope you mean 1.3.11 and not any variant of MO2 as that is very much a beta release and is prone to error at this stage. (Probably will never make it out of beta to full release.) If you are using MO2 then remove it and use 1.3.11. Even if you believe you have full UAC rights over Program Files (x86) there is still the likelihood that Windows is messing with you, best option is to create a new folder structure away from that folder and install Steam, any games or tools and MO there. e.g. C:\Games\Steam\Skyrim C:\Games\Tools\LOOT C:\Games\MO Whatever the current situation post your INI and logs here in spoiler tags or use PasteBin.

I'm not sure why users continue to place games and game-tools in My Documents?! They are not documents. The same issues with UAC may be faced here, just to a lesser degree. I use a structure like this: C:\Games, and then place my Steam, games and tools in sub-folders off that. Downloaded mods are fine to be in Documents as they are only read once when installing them, you could easily delete these afterwards. The 'Mods' folder, or any other MO folder is called quite often on execution so any folder that Windows deems as 'mine, so hands off', may be problematic. Now I'm assuming you followed Steam's instructions on moving it and Steam games. The CK also needs to be moved in the same manner. Remember after they have been moved you need to run them once from their own launchers to set the registry settings.

Post your logs and your MO INI. Modded Skyrim must be launched from MO, as does the tools like xEdit or LOOT. If you are getting permission errors when calling SKSE then you will probably need to move your Steam/Skyrim install away from the current location. UAC errors are due to Windows control over certain folders which is why STEP recommends installing Steam/Skyrim into a folder system of your own making, not a Windows controlled one.

@Drbigt & @bukanaku Please use 'spoiler' tags for long lists.

Okay, couple of points you should look at: Your Steam/Skyrim install is Program Files (x86). This is not a good place to install it as it is a UAC folder and Windows permissions stuff up a lot of things in gaming/modding. Move it with Steam's move tool. You have a SKSE entry in your INI that doesn't need to be specifically set. SKSE, Skyrim and the CK are all automatically set by MO based on your registry settings. You also have your mods stored on a OneDrive folder. This 'may' be an issue if there is a software component involved inside explorer to set and manage that folder. Every level of extra software that MO needs to navigate through causes issue.

Links don't work because PasteBin and ImgUr both say those pages are removed. Regardless of the method I link to them. Don't run the MO, or any executable called from it, unless explicitly asked to by support or an author. Permissions will be messed up for other tools or mods that then try to find those created files, e.g. saves or patches etc. Run Skyrim's launcher at least once from the desktop to initialise the registry entries. Afterwards only use MO.

If this is for "regular" Skyrim I suggest you use MO 1.3.11 and not MO2. As for the reasons why some of your mods aren't installing I can't tell without more diagnostic information such as INIs and full logs.

Your links are all broken. This looks more and more like you are trying to start the game from the default game launcher, perhaps from the desktop, instead of via MO.

Post your MO ini because your screenshot shows the Skyrim launcher starting and if you call SKSE from MO it will not call that but rather go straight to the game. Your link to your directories screenshot is invalid.

According to your screenshot your installed mods are indeed loading! How exactly are you determining that they aren't?

None of the tools you are trying to run are 64bit so it makes no difference.

I don't use Win7 so I can not be categorical in my assessment but since no one else on Win7 has posted anything about this, and the updates you linked to would have no bearing that I can see, it looks to me like some other issue(s) is/are at play. Since you aren't providing anything else to work with you'll be left on your own. However since you've circumvented the system by using symlinks the entire question is now moot. Hope you get the answer you're looking for somewhere and you can continue to play the game.