GrantSP

Going back to your opening post, just how exactly did you install FOSE? The actual DLL must be installed manually outside of the MO environment, only plugins that rely on FOSE may be installed via MO. Since that is the only variable in your setup that is yet to be examined closely we'd like to know more about that. MO works "out of the box" with Fallout3/NV.

I got nothing else apart from the fact Steam is in Program Files (x86). Do you have old Skyrim? If so does the same thing happen when you try to run WB on that setup?

Okay I now have a clean temp folder and these are the folders created on running WB: \AppData\Local\Temp\comtypes_cache\Wrye Bash-27\ And this is what is created after building the patch: comtypes_cache\WryeBash_btapp5\WryeBash_temp\WryeBash_temp_backup\Bashed Patch, 0.esp, Bashed Patch, 0.espf On closing WB only \AppData\Local\Temp\comtypes_cache\Wrye Bash-27\ remains so the files under process that get locked are the actual bashed patch and the other temp folders. Note: these are tests I'm doing outside of MO2 to ascertain exactly what files/folders the WB process creates, I'll redo these from MO2 to see what the extra layer of code does to the naming schema. EDIT: No change. The random name for the fist WryeBash_ folder is different each time but nothing else significant changes.

Nope, even after a system restart all the files created by WB in the %AppData%\Local\temp folder are still flagged as being used. Hmm... well would you believe Google Drive was stopping the process? I had that uninstalled ages ago but there still must be services running in the background. But why are they trying to backup temp folders?! Anyway that was a wild goose chase as far as this problem goes... let's keep thinking.

Thanks. Actually the logs I'm looking for are from MO2 and they are named similarly to this one: usvfs-2017-07-07_23-50-55.log However your BashBugDump also shows me that UAC is still an issue for some reason in your execution of WB. See how there is a test of UAC made and then a 'tree' is removed (presumably the files/folders created in the temp folder). That's when the Windows error shows saying the process can't continue because another process is accessing the files/folders. In my educated guess the process is UAC controlling the temp folder in your %AppData%. Interestingly on my system if I try and clear that temp folder the entire folder/file structure created by WB when I ran it earlier is still flagged as under control of a process despite it now being several hours since WB and MO2 were closed. Even executing an "Admin level" delete will not clear it. In my mind this an error. There should be no reason why those files are still being accessed long after the tool is closed. Standby I'm going to do hard reset and see if they free up.

Can all of you please do me a favour and: Delete your current logsSetup a profile with minimal mods, perhaps just vanilla + FNIS + one other modRun FNISRun Wrye Bash and create a bashed patchPost only the "usvfs-*" log here or in PasteBinAlso let me know if anyone has Steam installed into a folder called "Program Files (x86)" regardless of the drive it is on. Lastly advise if the WB you are using is the standalone version or not. These are the things that we all are, I believe, have in common: Win10MO2 installed as portableNo AV software other than Windows DefenderThat being the case there must be a commonality between you three that I am not seeing that is also different to my setup. @Tabris Your BashBugDump.log is significantly different to mine as all my logs records is "Testing UAC". This makes me believe that despite your deactivating UAC on your system it still is playing an effect on your install. I have seen other reports of Win10 playing silly-buggers with UAC folders despite the user stating UAC was disabled. Your Steam install location includes a name that is perhaps tricking Windows into believing it is in fact inside a UAC folder.

Are you absolutely sure SkyUI is not installing? The fomod (the script that handles the installation) requires no user input so it just installs the mod and it should appear in the left hand pane. The fomod dialogue progress bar may be hidden behing the main MO UI so you don't see it. If on the other hand it truly is not installing then there may be an issue with your .NET installation as that is specifically required to run that code, check the MO manual page for the the links to the needed requirements.

Make sure you have no other processes running that might try and access those files, specifically AV software or firewalls. Windows errors, though notoriously vague, are never wrong so there is some software trying to access that temp file or the temp folder. Temporarily deactivate your AV and similar software and try again. I have just done some tests on my setup with SSE and MO2 using both WB versions 306 & 307 with no issues. I will make this note though: it is never a good idea to run MO/MO2, or tools from within it, as admin. Doing so may make the files you create or even the process itself unreadable by other software that is run at a user level. Only run as admin when specifically instructed to by the mod authors.

Yes fine. MO is a complete standalone executable that leaves no mess in the registry or other areas, all you need is in the install folder.

This is the very first question in the MO FAQ.

The fomod makes a check to se if the DLC are active, the only reason it would be greyed out is if they were not active. Check the Archives tab in the right pane.

Nice dogtag!!

What happens if you set Edge as your default browser temporarily and then revert to Firefox later? Just thinking about how Windows sets default handling for webpages because that's all MO is doing here, using whatever Windows is telling it to use. There is no specific MO code to handle webpages except for the minuscule code snippets used to render Nexus pages in the "Information" dialogue.

You can use an online hosting service like PasteBin to show large text files.

Logs please. If possible logs with OBSE on and then off.

If this the original Skyrim, not Skyrim SE, then you should be using MO 1.3.11 not MO2. Also MO/MO2 isn't causing any issues when the game is started as once the game is running there is practically no code from MO/MO2 left running, any issues are due to INI settings, mods, ENB issues or some other factor.

No, don't try and fix this "issue" by using symlinks. Remove your current MO2 installation and install it to a folder away from Steam and other UAC folders. Something like: C\Games\MO2\ would be fine. Perhaps the Skyrim SE path may be causing issues due to spaces in the name. Perhaps. In any case the number of users that are having difficulties are minuscule compared to the entire MO2 userbase.

Without logs it is very hard to say what you are doing wrong. FNIS 7.0 works with MO2 perfectly well. Install it, activate it in the left pane, ensure the executable is properly set and then run it.

Logs and INIs please. We can't help if we don't know your setup.

Correct. UNP Texture Blender is not a mod but rather a tool. Because of that its path has no relevance to Skyrim's assets. Think of it like you would any other tool like LOOT, xEdit or even MO. None of which need to be installed anywhere near the games they work on.

No, both FNIS and DynDOLOD must be setup properly with accurate paths as they both contain assets that are called inside the game.

I picked up: "Middle Earth - Shadow of Mordor" for $4. (The 42 Gig of download though is a real nightmare to install if your internet is flaky.)

Nope, don't think there is one. In all the time of I've used I haven't found it. If there is then it is hiding very well!

Welcome to STEP @echosend You will see that message appear because this install is actually NOT a mod, in the strictest sense of the term. It is in fact a tool that should be able to installed anywhere and the executed to allow it to "do its thing". Install it with or without MO and add the executable to MO's 'Executable list' and then run it.

That was my mistake. I've edited my post to show what I really wanted to say. In essence the errors you are seeing are of no consequence, just ignore them.