GrantSP

While it is true the FNV engine is a more stable one than the FO3 engine, installing TTW is not just a case of playing FO3 in FNV. There are a LOT of cosmetic and gameplay changes, some away from vanilla, that needed to be made. Balance, gun/ammo choices, creature strengths, armour ratings etc. that are very different from vanilla FO3.

Chrome with UBlock Origin and I have never experienced this. Also been running Windows 10 for many months now.

A few things to mention, one is not that important but needs to be addressed, the others are probably the cause of your issue. You have an explicit reference to SKSE's executable in your INI that doesn't need to be there. Delete the section that starts with "1\" immediately after the ones for listing "5\". MO doesn't need to be told of the location of that as it is automatically recognised. Your logs make mention of a mod "camp" that no longer exists in your default profile. Either resolve that by restoring that mod or delete your INI and profiles and start afresh. Additionally you have a ton of mods that are installed directly into the Data folder and not via MO. This will make conflict resolution a bit problematic and you should consider moving all of those into MO's management.

Post your logs and your MO INI. Please use spoiler tags.

Tale of Two Wastelands is an amalgam of FO3 and FNV data into the Fallout New Vegas engine. I only mentioned it as @D1Z4STR mentioned he was following a FO3 guide.

I may be branded as bit heretical for this but... I don't really think it is as necessary as it has been made to be. Yes there are a few cases where "wild edits" may have been left behind, in which case they should pose no problem if removed, but there may just as well be the same number of seemingly pointless records left behinf that also pose no threat if left alone! So, it comes back to the user. If the guide/video/friend's advice is to do "such and such" I don't think you will ruin your system if follow that advice. There is one special case I know of where cleaning is actually not a good idea because the mods NEED to have those vanilla records in tact: Tales of Two Wastelands. There it is specifically instructed to NOT clean your DLC otherwise their plugins may not work.

Glad you have it sorted now, in a fashion anyway. Yeah admin rights can be confusing with Windows implementing them in so many odd ways. If you can run MO as admin all the time then that's fine, all the tools called from it "should" also inherit the admin status for the output they produce so running MO at any future date without admin rights may be a problem, but I don't see you doing that if the only way to get your mods now is to run as admin. So in short, just do everything from now on as admin and you should be good to go.

Windows 10 has been known to push some very restrictive account permissions even on users with admin access. Not sure if you're on Win10 but be aware that it is very odd in this matter.

Okay i may have tracked it down. The log says the process falied to start and gives a Windows error number: 740. This is due to the process requiring higher access privileges than that you are now running. To simplify this further, the installation of Steam on your E: drive must have been done under Administrator privileges and you are now trying to call it as a user with lower privileges. You will need to: Fix the access status of that installation (Best option, but will require a bit of work) Give yourself Admin rights for your Windows logon account. (This is what I have and if you are careful it will be no issue.) Run MO as Admin each time. (I generally advise not doing this as if there are times when you run tools from MO, such as FNIS, etc., the resultant files may not be read properly.)

Can you run me two more tests? Run the Skyrim Launcher from MO and post the log then disable all mods and run SKSE from MO and post that log. Also, probably not related, but you have a recursive folder name scheme in your MO mods folder. You have: D:\ModOrganizer\Mod Organizer\mods You could/should remove the 2nd "Mod Organizer" from that path to be more manageable.

In any game it is best to disable Steam's overlay. Too many issues with it to mention but be assured that it, and those from other companies, messes up MO's VFS hooking mechanism.

Have you done anything odd to your Steam installation? Perhaps manually moved it? The last lines in your log show MO failing to run Skyrim correctly. DEBUG (19:24:32.0042): create process (w) E:\Steam\steam.exe - "E:\Steam\steam.exe" -applaunch 72850 (in D:\SteamLibrary\steamapps\common\Skyrim) - NOT hooking DEBUG (19:24:32.0046): process failed to start (740) DEBUG (19:24:33.0352): hooks removed

Logs please. Also you MO INI would be good to see.

Okay, the error message is not an error in this case. LOOT provides that message to alert the user about an incompatibility with the original plugin but since we are using the hotfix, and it can't tell the difference due to the same name, you need only ignore it.

1) LOOT is giving the error? What exactly is it saying? Dynamic Crosshair should come after DarNUI. 2) You need to call the game via the FOSE loader in MO's executables list. Calling the game any other way will not load FOSE and therefore you will see those errors.

You shouldn't need to do anything special to preserve both games. Just install them both, if you have the space, and they are completely separate games as far as the OS is concerned.

@Arthmoor's anti-MO stance is well known to most people and he will take any chance he can to reinforce his view of it being an inferior manager. Having said that he is quite entitled to his view when it comes to offering support for his mods. Now, the stated opinion that having MO manage the BSAs is inherently broken is just wrong. True there a few fringe situations when the order of the BSAs needs to be massaged due to this system, in fact I had to jump through some hoops in my TTW installation to fix that, but in 99.99% of cases it makes no difference. As for the second quotation, that is talking of another matter entirely, that of extracting the contents of BSAs. MO's management of BSAs is NOT equivalent to extracting them. MO has NO inherent control of the contents of BSAs, their contents are controlled only by the game upon runtime. Because of this I too concur with the advice to not extract them into your game folder. (nb. some experienced guides may advise this but will do so under strict control and you will need to follow them to a "T".) Running the launcher for any game will always initialise your INIs. To conclude, let me offer this: the user is quite free to decide whether to allow MO to manage the BSAs or not, that's why it is an option. Doing either will not break the game it just means they will need to be aware of the ramifications of either action. Informed choice is the goal here.

If you remove the bashed patch from the "Data" folder and place it in a mod inside MO2's structure, you should be able to edit that one in the future and then save it into profile specific mods after each edit. I use this method when bash patching original Skyrim.

Navigate to %AppData%\Local\ModOrganizer\SkyrimSE\ModOrganizer.ini and check to ensure the path to the game is correctly set. There should be something like this: [General] selected_profile=Tester ask_for_nexuspw=true gameName=Skyrim Special Edition gamePath=D:\\Steam\\steamapps\\common\\Skyrim Special Edition first_start=false If it isn't then you can either delete this INI and create a new instance with MO2 or simply edit it to point to the correct game.

Not an issue, it's just something that affects some users and not others. If this is original Skyrim I suggest sticking with MO 1.3.11 until MO2 matures a bit more, which is apparently happening quite quickly.

Check whether the latest driver for your graphics card is in fact the best option, sometimes a previous version works better. Are the settings in the driver software configured properly? Is it just a case of allowing Windows to restart correctly? Especially after major system updates there may be teething issues with obscure software that you may not even know is running, ethernet, router, NAS, mouse or any manner of sub-systems may now be stressing. Sorry I can't be more specific, these things are not an exact science.

No. I, and many other users, have done some testing on this when this question was first raised and we have not seen any such problem in our setups. My bet is with your drivers. A system wide update is bound to have some issue with at least one driver or sub-system.

Fomods are great and there are a few C# style ones that may cause slight issue (xml style are fine) but I agree with @Kelmych, FWE's one has always been flaky and I think it may be premature to say there's a fault in MO/Win10 because of it.

If I may butt in here with some input? This concept of "merge or not" is entirely an MO concept because of the way it handles mods. Usually with any other manager, or even if done manually, you wouldn't even think of merging because it all goes into the game's "Data" folder. Install part A and then part B goes later overriding any files that are the same. (Usually the different parts of a mod contain different files so nothing is lost.) However when it comes to optional downloads or bugfixes the files overwritten are done so on purpose. In MO the choice is entirely up to the user, there is essentially no difference to having 2 mods in the left-pane or just one. There is no loss of performance or an overhead to the system's resources, it's just a "management thing". One way of looking at the order of the left-hand pane is to view it as a timeline of installed mods that you would have done manually. ie. Top to bottom == first to last installs.

It's going to be fun in your home tonight!!