GrantSP

You installed the MO2 on top of the existing installation and those are ver 1.3.11 related files that MO is trying to load. Either perform a fresh, clean install of MO2 and migrate your existing mods over to that or simply delete those files in your current installation. I'm glad you now have a carefree install. Keep in mind MO2 is a working beta release and since @Tannin has now been employed as Nexus' new head of NMM development, it will likely stay in beta stage forever. This will mean in the future NMM will be the new MO and possibly the de facto manager for everyone.

Don't try and run that executable as is, it is a secondary executable that is called from MO and MO will pass on the correct game details itself. This particular error message is one of the more obscure and hence more difficult to fix so please don't get your hopes up too high. We know where it comes from and theoretically where the fix should go but it doesn't always apply in every system. If you don't mind trying something, @Tannin applied a fix that may be specific to MO version 2 or it may also work for 1.3.11. Grab that zip file and extract it, overwriting everything in the installation with the same name. It seems to work for MO2, maybe it will also be backward compatible.

Can you check the MO wiki and see if you have implemented the prerequisites for .NET? Although Microsoft would have us believe .NET is backward compatible, specific versions need to be available for full functionality.

Hey @Onichu, welcome to STEP and thank you for your files. Did the actual mod get installed, although you received no notification, or is it a completely broken installation? The logs show everything happening with one exception, the line: 12:10:21 [D] Installation successful Additionally as per my update on the Frostfall comments page, is your system Win7, 7 updated to 10, or a fresh Windows 10 system?

That's how @Tannin responded to one query about what this new manager will be like. I'm both glad and sad, in the same way a father would be when his child grows up and get's married. :O_o: Not that I'm anyway the father, but the feeling is similar. So here's hoping it all works out for the best and let's get ready to create new wikis and tutorials! Woohoo!

That's an indicator of missing textures. Fast travel will no effect on that. Best bet is to check thoroughly your installation to see you haven't omitted a step.

Welcome to STEP @Drahnier016 Sorry to hear about your troubles in modding Skyrim, but let me firstly set matter to rest. The problems you describe sound like nothing that MO is doing and rather more to do with an incorrect step with on of the guides you followed. As such I have moved this thread to the General section as I see no reason for it to specific to MO, this will also allow users with a wider knowledge of testing to see it. I have also provided a link to the sub-forum in the General section that specifically deals with crashes and the like.

I'll let @Greg answer your question directly, but I'll make an observation about the way you have your system installed: The paths are needlessly long. e.g. Firstly I'd move MO out of the Steam directory as there may be issues with exceeding path lengths with some tools, such as FNIS, if you keep MO installed that way. Keep Steam and any games you have in its own directory and install MO somewhere else and lose the sub-folder structure. Just "ModOrganizer", or similar, is recommended, not:

I'd generally advise against installing onto an external drive any system files such as Steam. The same would probably apply with the games as well. Since you're using MO there is an easier way to keep storage problems under control. In MO's settings point the 'Mods' storage to your external drive, or your largest internal drive. I have 3 drives, 2 SSD's @240Gb and a HDD@2Tb. I have a ton of games installed and all the mods from all the guides hosted here on STEP installed and stored and I am nowhere near getting close to a drive limit. All my downloads and game mods are on the HDD and Steam, MO and all my games are on a SSD.

Ahh... well... that shoots that theory down.

Hmm... AMD driver users aren't seeing crashes and NVidia driver users are, that's not good. At least it narrows the field a bit as to where the issue lies.

I always update everything so I'm on AMD's 16.9.2 and Windows latest updates and everything is working perfectly.

Welcome to STEP @Vermithraxxx There is a guide to follow with regards to migrating from NMM to MO, it is linked via the MO wiki, which is also the default help system accessed through the MO UI. As the guide describes, using NMM means the 'Data' folder will now be in a mess and just adding mods with MO will not be as easy as you may want. The 'Data' folder will need to be restored to a "vanilla" state. Read through that guide, and the MO wiki in full and feel free to ask any question you like that isn't answered there, we will happily step you through anything that is not clear to you.

Ooohh! Nasty. Didn't even think to look at your sig. Doh!

Out of curiosity, what sort of SSD did you have and how did it fail?

No, not really!

Welcome to STEP @gawakamy If you are referring to MO's built-in 'Sort', then, yes, there is no report function with that tool. However STEP recommends installing LOOT as an executable and calling it from inside MO.

Yeah, that's what I mean.

None of the current games that are used with MO run with DirectX 12. Skyrim uses v.11 and most of the earlier games will use v.9. .NET software is also very finicky and you will need to ensure your system has either enabled or installed the correct versions. The MO guide has a section describing how to do this.

I've never heard of VorpX before so I can only speculate. If that software is trying to hook into the game executable and add features to it, that process may be slowing down due to MO first hooking the game to add the mods. Purely speculation on my part. The upshot is though any software that is running in the background, if it isn't absolutely necessary, should be disabled.

There are many tools you could use to check on your running processes, Google will help you find one you want, but the point remains: those running processes are still active regardless of whether you start the game with MO or not. MO is not adding any load to your system and thus causing lag.

Take note of the comment #21 just further up the page. That is the author of the programme, @Tannin. I think it is a safe bet that he would know what is and isn't possible with regard to any portion of his code remaining active in memory.

Welcome to STEP @dps_kane. If you are referring to statements such as: please note that ENBSeries and ENBoost are two different things. The former is a set of graphical configuration settings and the latter is a management system for memory. STEP does not ask you to make changes to your graphical settings needlessly.

Welcome to STEP @Miki. Check that Steam Overlay or perhaps your graphics card manufacturer's software isn't active. As this thread has already shown there is NO OVERHEAD involved with MO once the game is started, any issues you see are not related to MO.

...or click the left-most icon of the group of three in the top-right of the left pane and choose: "Check all for updates". Remember to consult the manual.