GrantSP

The ONLY way MO2 will have any impact on your MO1 install is if you told MO2 to use the exact same profile(s) as used by MO1. There are no other mechanisms in which either MO can "talk" with each other and possibly mess things up for the other. There are no registry settings or anything system wide that either tool uses that may have become mixed up. All of the settings that determine what MO (1 or 2) does with your mods are just text files stored in the folders in your MO profiles folder.

The reason the install process is failing is, as @GSDFan instructs, the downloads from any other servers are not complete but most likely they are 0Kb long, thus MO2 cannot do anything with them.

Create a new profile, or switch to another one if you have it, and enable just one additional mod and let's see that set of logs. This doesn't make any sense as you say both MO1 and MO2 yield the same result. This indicates to me that there is no fault with the code, but rather either an error in that specific profile or you are in fact missing those DLC. However as you say you can run the game from Steam and they appear that would seem unlikely.

GamerPoets has a series of videos describing MO2 in detail. There is a section in one of them showing how easy it is to migrate from MO1 to MO2.

Please read the pinned topics before posting. https://forum.step-project.com/topic/13336-mo-cant-connect-to-nexus/

Yes there are a couple of ways to do it. From within the MO2 UI you just open the "Information" dialogue and on the 'Nexus Info' tab change the game via the dropdown menu labelled "Source game". Or if you want to you can change the entry in each "meta.ini" file in each installed mod folder in MO2's mods folder. The entry is: gameName=Skyrim for Skyrim and it is: gameName=skyrimse for Skyrim Special Edition. You could do a mass edit with a tool like Notepad++. It has the ability to search through all files including sub-folders and make the change in each.

I see your report there and I'll respond in Discord.

Assuming your Skyrim install is not a crack, and assuming you have all the DLC installed all you need do is start MO and it will see all the files for the vanilla game. Now if the above is correct, to test just create a new profile and see if you can enable just the base game files and start the game. This will tell us if your current profile is broken somehow. Regardless of whether the game starts or not post the last created USVFS log here.

As I mentioned in your TTW thread your issues are totally unrelated to these changes by Nexus.

Clearly you have not been using MO2 as it is far from a "buggy and unstable mess".

Let's see your MO_interface.log and your INI.

You have MO2 installed into the game folder, it can not be installed there as weird errors result due to recursion of the VFS. Move your MO2 install.

Windows 10 completely broke some of the core functionality of NVSR. You must set the ini to these settings: bHookCriticalSections=0 bHookLightCriticalSections=0 I've added a section in the guide to make mention of this fact.

Perhaps you should acquaint yourself with MO more fully by watching the numerous YouTube videos and ensure you have set it up correctly.

Without your logs and your MO.ini it will be almost impossible to diagnose.

MO2 works very well with FNV. Have you checked to see that update.bsa is actually active?

Not sure without your logs but since MO 1.3.11 is on its last legs you may consider switching to MO2.

The MO2 devs may be able to look further into this at a later stage. There are reported hacks to get around this limitation but the underlying process seems to be different with regards Oblivion, obse and Steam compared to the other supported games.

Make sure you have updated correctly because there is this in the log: 18:55:31 [D] update available: 2.1.2 -> 2.1.3 If you are 100% sure you are on the latest go to settings and change the server to CDN as there are reports that Nexus is having difficulties with the other servers.

Functionally MO2 is identical to MO1 as far as setting up your F&LNV install. You can simply copy the profiles, mods and, if you want, downloads folders from MO1 to MO2. Setting up the executables is exactly the same.

Update your MO2 install

Please read the pinned threads before posting. This non-issue is covered in this pinned thread.

This usually happens if you have installed the 2.1.2 version into the default location and then are calling MO2 from the shortcut that is the previous version. You need to install 2.1.2 over the previous version to have just the one installation.

I'm sorry to hear you say that. It is, of course, your choice but I think you're making a mistake. The resultant installations of your mods will always be harder to maintain with NMM, that's just the nature of that beast.

From what you've provided there is no clear reason why your install is crashing on game load so the best thing to do is nuke your MO2 install and start afresh. Your already downloaded mods DO NOT NEED TO BE DELETED so there is that saving grace. Simply backup the "downloads" folder and save it somewhere. Completely remove the install including the settings stored in %AppData% that relate to MO2, and get the latest release and re-install. Use an "instanced" install and point it to your SkyrimSE game. Firstly ensure that MO2 can start a vanilla game with just the game itself then with SKSE. Once that is done copy in your downloaded mods to the new MO2 "downloads" folder and install a few mods at a time and test. The best option is to create new profiles at each stage so that you have a failsafe to fall back to if one of the last installed mods breaks the game. If you haven't already watch the series of MO2 videos by @GamerPoets.