Then expand the GenerateFNISforUsers folder. Mods can cause conflicts and crashes if the load order isn't sorted properly, and conflicts aren't checked for. Fix crashes, errors and mods not loading by following this guide for PC, Xbox One and PS4. Disregard this mod if was not installed.USERSSince you must launch FNIS through Mod Organizer in order for it to recognize your mods, add FNIS to the list of executables by doing the following. For STEP, this applies to, which is listed in the Patches section of the Guide. Notice: Users only need to run this mod if also using the, or other mods that support/require it. The main cause is probably because I only configured the custom paths after finishing MO2 installation, thus creating 2 Base folders for MO2 and it went to the folder first created.I already manually placed the DLCs' esm's into the data folder before fixing this but now I don't have to worry about running FNIS in the future.Doesn't seem like a common issue but hope anyone who might run into the same issue can get through it faster than i did. I deleted them and started MO2 again and the files are now shown both in the folder in my game directory and in MO2.

The paths for my folders are as in the picture and that is where I went to find the overwrite folder to check for the files.Your reply (Thanks!) did make me go back to the default location in appdata to check if anything's there, and there were, all the subfolders. Thing is I already located the overwrite folder and the cleaned files were there, but MO2 didn't seem to detect it and so the files didn't show in MO2. Fixed (I should have replied sooner) The first thing I tried in order to troubleshoot this was checking that.

Mod organizer how to fix conflicts