Home

Known Issues:

• MO2 does not work with Windows insider preview builds. (Finally fixed! Thanks Silarn) (**)
• If Windows Event Logs are cleaned/removed (for example with CCleaner) MO will stop virtualizing the mods and the usvfs logs will result empty. Restarting the PC should fix it.
• There is a bug with the vfs that makes the game not see the mods if using SKSE in some rare cases. (**)
• Programs can't see the mods if MO is installed inside the game folder for some users.
• Wrye Bash (non python version) can fail to launch if MO is installed on a different drive than the game. (**)
• Quick access cache is cleared after WB or TexGen are run through MO. (**)
• BSA extractor does not support new Archive types.
• Generate files in mod instead of overwrite does not work. (**)
• When uninstalling MO, prompt asks if you want to keep instance files, but removes them either way.
• The IniTweaks that MO allow to add to mods through the modInfo dialog are not actually used by the game.
• If a tool is set to run as administrator while MO is not (MO will ask the user if he wants to start the program elevated), all the tools launched after that one will not be able to see the virtualized files (If mo was started as admin this does not happen).

(**) A fix for these issues is available and undergoing testing on the discord server. If you experience those issues, please visit the server to report if they are effectively fixed and test if they break something else.

Common Fixes

• Windows could be blocking MO's files after download without telling you and MO could behave incorrectly, to avoid this, right-click on the downloaded MO2 zip, open properties and check the Unblock checkbox if present.
• Many antivirus can flag MO as a virus. Make sure nothing is blocked or deleted by your AV. If your programs can't see the mods, there is a good chance some Mo files where blocked or deleted by the AV
• If you have any kind of problems download and repair the vcRedists found on the MO2 nexus description, especially if you have problems after updating windows or something similar.
• If you are on Windows 10 make sure you have the latest official version (1709 specifically, Insider builds were reported to not work!), or Mo will not start applications or will give all kinds of problems. (To see what version you are on, run winver).
• If your mods don't get loaded in the game it could be caused by a faulty or modified steam api dll, verifying game files with Steam will fix that.
• Body Slide gives an error when batch building: create an empty mod and set BS to output to that custom folder by pressing CTRL when clicking batch build.
• Download with mod manager from nexus does not work: In MO settings there is a button to associate with nexus links. If that does not work, manually run nxmhandler.exe that can be found in the MO2 installation folder, click the Register Active button and select yes when asked.
• When attempting to open a link on nexus, the MO2 shows a popup that claims that nxmhandler.exe cannot find the Qt5QuickWidgets.dll: copy the Qt5QuickWidgets.dll from the dlls folder to the main application folder.
• xEdit gives errors and can't see the virtualized files: your windows could be missing the Visual C++ 2015 runtime x86. You can find it here: https://www.microsoft.com/en-us/download/details.aspx?id=48145

Additional Notes

When installing a new MO stanalone build don't just overwrite an existing installation, you should first remove the old files as they could cause issues, you can keep your settings and setup by leaving/backupping: ModOrganizer.ini, profiles, mods, downloads, overwrite and stylesheets folders. These can be found in MO's install folder if you have a portable instance, or in Appdata\Local\ModOrganizer|, if you have a global instance. An alternative is to simply keep the new build in a different directory and, in MO's settings, point to the old mods, profiles, downloads and etc folders.

Please report issues here: https://github.com/Modorganizer2/modorganizer/issues

When reporting an issue, log files (and crash dumps in case of a crash) can be found in: \logs and \crashDumps inside the ModOrganizer folder, or in: appdata\local\modorganizer\<game>\logs and appdata\local\modorganizer\<game>\crashDumps if you have a global instance of MO. Make sure you have log level set to "debug" in MO settings.

To anyone interested in contributing, or simply checking out the code, Mod Organizer is subdivided into multiple github repos that can be found here: https://github.com/LePresidente?tab=repositories If you intend to set up a build environment on your end, you should follow the instructions provided here: https://github.com/LePresidente/modorganizer-umbrella Be aware that much of the original documentation is incomplete and outdated. If you have any questions, feel free to ask them in the #umbrella-dev channel of the Devs discord server.

To anyone wondering, although MO2's known issues with 32bit games are solved, there is no real reason to switch to MO2 for the old games. MO1 is solid as a rock and MO2 does not come with new feature as of 2.1.0. So it's up to you to decide, but be warned that the old games obviously received less testing and issues with them might have lower priority.