GrantSP

What's the exact name of the texture and the supplying mod? @RoyBatty also says he sees this sort of behaviour in his Fallout games but I can't seem to track the reasons down. Off the top of my head if a mod with greater priority has a plugin that references another texture explicitly or a *.nif has a hardcoded path to another texture are the only reasons that might contribute to this, otherwise there may be a serious flaw in MO that 1000's of users have just missed. Possible, I don't take nearly as much care in noticing what textures are loaded whilst in game.

They're not actually patches, from what I can see, they are replacement plugins. This means you will install the main files from the English version and then replace the *.esp with that from the German equivalent. e.g. Install the main file from the English Nexus page and then from the German page install the BS Bruma Patch file and replace the plugin. In MO you can either "Merge" when prompted if installing into a mod with the same name, or install it after the original in a mod named differently and when it is activated MO will replace the plugin with the later one. On a side note sine these are all mods for the original Skyrim I'm assuming you are modding that game in which case you should really use MO 1.3.11 instead. More stable and less likely to bug out. P.S. No idea about the T'Skyrim Riverwood mod, couldn't find it anywhere.

Perhaps a brief refresher course in the basics of MO is in order. Try watching the great @Gamerpoet's series on MO as well as reading the manual.

Have you activated it in the left-hand pane?

Holy necro post Batman!

Check to see that ALL masters are correctly sorted.

... and move it out of Program Files while you're at it. UAC issues will be a problem if you leave it there.

After running SSE from the desktop launcher does it still not load from MO2? It appears Bethesda may have pushed out some updates in the last few days and this will mean you will need to run it to update the registry settings again.

Make sure you enter the "Extra HUD" menu and check all the boxes to enable them.

I have no idea about your specific issues, sorry. I have however moved your posts to the F&LNV Support forum where they may see some more attention.

SKSE64 isn't even out of alpha yet! Best to let that team iron out any bugs in their code before looking for a "fix" in MO2.

@Ewookie1 If you now install Chrome and use that as your default browser the NXM protocols will no doubt work. There isn't anything wrong with Chrome or any other browser with regards to these things, it's just a case of the protocol handler being messed up and how to go about rectifying it. The method described above no longer works due to a Chrome change in format for that settings file, however the underlying principle still holds true: ModOrganizer uses your systems default browser's protocol system so if you cannot download files from Nexus, then the issue is with your system, not MO's code.

The method described above is no longer current. Google's Chrome uses another format now to store that information and trying to edit 'Local State' will be pointless. Any issues you may face with regard to MO downloading files from Nexus are likely due to Nexus server issues.

Yes it was down and it should now be back up.

The wiki server was offline for sometime, but it should now be back up.

The link you posted is for MO2 which should only be used if you're modding SSE or FO4. If you're trying to mod old Skyrim then use MO 1.3.11. On the other hand if you're trying to sort SSE plugins install the LOOT program and use that instead of MO/MO2's internal sort. In fact I suggest using the full LOOT in all cases over the internal sort. For me MO2's internal sort has never worked.

AMD has "ReLive", nVidia has "GeForce Experience" other companies like Steam also try to force an overlay onto your game so you can: chat, take screenshots/videos easier, etc. Yeah the wiki is down, one of the admins needs to give it a kick to restart. MO is a so-called "portable" executable in that it makes no changes to the registry and all the configuration files are within its own structure. It 'knows' where the game is by reading the registry setting that game makes, but not write to it. This is why all the guides say you MUST start the game at least once from the desktop before using MO, otherwise the correct registry entries are not set.

I know you've posted in GitHub as this being a MO2 issue but it still falls into the problem of the Windows update breaking something. I have Win10 version 1607 and WB works perfectly fine inside MO2.

You can change a lot of the UI settings once in game via the MCM for the appropriate mod, ie. iHUD - Extras. Make sure all those settings are what you are expecting to see. The whole UI process is much simpler now with the use of UIO, so if you follow the guide step-by-step it will work. If you haven't already, move MO away from any Steam folder or other UAC folder and work from there. MO does not need to be in proximity to either the game or Steam to function. Yes the only INI files you need change are those in the profile you are currently using. These can be edited either via MO's tools or manually with a text editor. All NVSE plugins can safely be installed via MO, so if that is what you have done that is fine. Black screen --- make sure all the plugins are correctly checked and ordered as missing masters will break the game. Additionally check to see that MO's Archive management is on AND all BSAs are correctly checked in the UI. Lastly ensure no 3rd party software such as Steam's chat or your graphics driver's overlay software is on. All such 'addon' software are known to mess with the game when run through MO. Lastly whenever catastrophic situations like this occur simply create a new profile and add things back in small batches to see if you can see what you have missed. You can also use these new profiles as stages of the entire process, once you get to a working stage create a new on profile from the last working one and proceed from there, this way you will always have a working game to fall back to.

hmm... I think there may be underlying issues here with your system. Never seen a 'fast-exit exception' error with regard to MO/MO2 before so I can't give you any specifics on why that occurred. Has MO2 ever worked on your machine?

I commend you on your inventiveness but I think you may need to consider another path than that you have proposed. Also I'm not sure many players will be as enthusiastic about waiting around for the full effect of "reading" to kick in, I may be wrong. Firstly skill books are different to other "consumables" in that they do not have an effect applied to them, they simply contain data variables that are applied directly to the player when the book is 'read'. Secondly you will probably need to read up on all the scripting functions and see if there is something you can use. This a link to an updated GECK wiki maintained by the TTW team, it is far more comprehensive than any other I know of.

Have you ever been able to run MO2 from that address? I'd suggest moving it out of the Steam path and into a folder of its own, e.g. G:\Tools\MO2\ or even G:\MO2\ Also if you are currently on Win10 you may have the issue the Creator update introduced and therefore you will have to wait for the Windows update that fixes it. There is one in the pipelines at the moment.

Can you please post the full pathname. Errorcode 161, and the message itself, refer to an invalid pathname. You might also try and check to see that the path you are expecting to see actually is correct.

Oooh goody, though if it was as convoluted as last time I may pass.