Mod Organizer

Legacy (32 bit) Version of Mod Organizer with support for Skyrim Legendary Editions and some other 32 bit games.

Reached End of Life

Last Updated Version: 1.3.15

Application Details:

Version: 1.3.x
License: Free to use and share
Votes: 0
Latest Rating: Platinum
Latest Wine Version Tested: 4.19-staging

Maintainers: About Maintainership

Link Source Code Free Download Skyrim SE Nexus Mod Page

Test Results

Old test results
The test results you have selected are very old and may not represent the current state of Wine.
Selected Test Results

What works

  • OverlayFS injection (and therefore mod loading)
  • Mod reordering
  • Adding mods to the list
  • Launching custom executables (for other mod tools)

What does not

  • Throws errors about not being able to save some settings (may be a configuration error on my end)
  • Previous versions had "random" issues with not exiting when it was supposed to. This may be resolved already.
  • Built in INI editor is mostly non-functional, instead use your preferred plain-text editor on ModOrganizer_directory/profiles/default/skyrim.ini (changing "default" and "skyrim" for profile and game name respectively)


What was not tested

  • Downloading mods from the Nexus
  • Profiles (though they likely work)

Hardware tested


  • GPU:
  • Driver:

Additional Comments

"Installs?" is N/A because program is distributed in a compressed archive.

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
ShowArch Linux x86_64Nov 29 20194.19-stagingYes Yes NoPlatinumZenAnonX 
ShowUbuntu 18.04 "Bionic" amd64 (+variants like Kubuntu)Jan 27 20194.0Yes Yes YesGarbageEonfge 
ShowArch Linux x86_64Mar 24 20183.4Yes Yes YesSilverZenAnonX 
CurrentGentoo Linux x86_64Jun 22 20151.7.44N/A Yes SilverNicholas O'Connor 

Known Bugs

Bug # Description Status Resolution Other apps affected

Show all bugs

HowTo / Notes

Downloading using NXM Links

Follow this method to make nxm links("Download with Manager" button) work with MO. Thanks to @Joe Davison for this how to.

Requires XDG.

1. Create a script called with the following contents 

  • #!/bin/sh
  • export WINEARCH=win32 export
  • WINEPREFIX="/path/to/your/wine/prefix"
  • export WINEEXE="/path/to/your/wine/binary" 
  • "${WINEEXE}" "/path/to/ModOrganizer/nxmhandler.exe" "$@" 

2. Create a nxmhandler.desktop file in ~/.local/share/applications with following contents,

  • #!/usr/bin/env xdg-open
  • [Desktop Entry]
  • Exec=/path/to/ %u
  • Icon=application-x-ms-dos-executable
  • Type=Application
  • StartupNotify=true
  • GenericName=nxmhandler
  • Name=nxmhandler
  • Path=/path/to/ModOrganizer
  • MimeType=x-scheme-hander/nxm

3. Mark BOTH files as executable (chmod +x), make sure nxmhandler.desktop is in ~/.local/share/applications.

4. Next time you click an nxm link your browser(browser should support setting handlers for custom links, firefox,palemoon,icecat etc) should ask you what you want to do. Choose nxmhandler. Mod Organizer should then launch and commence downloading.

Making FNIS Work

FNIS sometimes encounters problems when running through STEP method, do following to make it work

  1. Download 32 bit version of FNIS from nexus.
  2. Extract and rename "Meshes" to "meshes" and "scripts/sources" to "scripts/Sources".
  3. Copy over extracted files to Skyrim's data directory.
  4. Under MO go to Data tab and navigate to "tools\GenerateFNIS_for_Users".
  5. Right click on "GenerateFNISforUsers.exe" and Add as executable. This should create a shortcut in game launcher.

Always launch FNIS through this shortcut if you want it to see your installed mods.

Fixing Fonts

Enable subpixel font smoothing

  • winetricks fontsmooth=rgb

Disable render extension for client side fonts

  • Open wine regedit, and inside HKEY_CURRENT_USER\Software\Wine\X11 Driver make an entry for "ClientSideWithRender"="N"

Reference -

Making TES5Edit and TES5Edit based patchers(Real Shelter) work

This how to is designed with Real Shelter Patcher in mind, if you are using any other TES5Edit patch change "Start In" and "Arguments" accordingly.

  1. Copy over TES5Edit to Data folder of Skyrim
  2. Under Data tab in MO find TES5Edit.exe and select Add as Executable. (This will be shortcut to run TES5Edit in future)
  3. To make Real Shelter Patcher work, first install mod normally through MO and enable it.
  4. Next, open <Edit> in your executables and add a new executable with,
    • Title: Real Shelter Patcher
    • Binary: <Same as TES5Edit>
    • Start In: <Directory containing Real Shelter Mod, if MO is installed to Program Files this will be something like "C;\Program Files\Mod Organizer\mods\Real Shelter\R.S. Patcher" without quotes>
    • Arguments: <Path to tes5pas file, if MO is installed to Program Files this will be something like "C;\Program Files\Mod Organizer\mods\Real Shelter\R.S. Patcher\RSPatcher.tes5pas" WITH quotes>
    • Done!

Making Skyproc Patchers work

This was tested with jre1.8.0_161

  • Download jre x86 from oracle.
  • Install jre using wine, "wine jre1.8.0161"
  • Installer will get stuck but no worries, go to "WINEPREFIX/drive_c/users/username/AppData/LocalLow/Oracle/Java/jre1.8.0_161" and copy "jre1.8.0_161.msi" to someplace safe.
  • Ctrl+C or kill installler process.
  • Run, "wine msiexec /i jre1.8.0_161.msi". This should install java.
  • Now install any skyproc mod in MO and enable it.
  • Go to "Data" tab and navigate to "SkyProc Patchers/mod name".
  • Right click on mod's jar file and "Add as Executable".
  • Patcher could now be run from custom executable created in MO anytime.


The following comments are owned by whoever posted them. WineHQ is not responsible for what they say.

NXM Linking through XDG
by ZenAnonX on Tuesday December 3rd 2019, 0:32
Noticed something recently, xdg-open automatically detects nxm handler as long as there is a ".desktop" file in "~/.local/share/applications" with "MimeType=x-scheme-handler/nxm;" set.

To check whether xdg-open detected it run,

$ xdg-mime query default x-scheme-handler/nxm
$ xdg-settings get default-url-scheme-handler nxm

output of both commands should point to same desktop file.
Setting Exec to something like this 'Exec=WINEPREFIX=$HOME/.wine wine nxmhandler.exe "%u"' in that desktop file starts download in Mod Organizer without problems.
Best part about this, no longer a script needed to run nxmhandler and many browsers natively support it. Checked it in falkon and its working :).
RE: NXM Linking through XDG
by Jarrard on Tuesday January 7th 2020, 7:47
was trying to make this so the desktop file launched the mo2 via nxmhandler.exe for proton run command but it didn't work out.

In the end I had to make this somewhat complicated bash script which runs with the nxm x-scheme handler like normal but checks if process is running and execs the correct command.

Why do this and NOT just run the basic nxm command by itself, well it would fail to launch modorganizer.exe for me, I dunno why but it does.

Anyway the OTHER methods worked on Ubuntu but it seems my Arch install doesn't like how some things are run, I even had RUNTIME errors with the other methods which is bizarre but that is what happened.

HOPEFULLY the solution I have posted here is basically FAILSAFE and will work no matter what distro is used.

(mind the auto wrap formatting of this website, the STEAM.... commands are 1 line)

ps -aux | grep "[M]odorganizer" > /dev/null 2>&1
if [[ "$?" == "0" ]]; then
STEAM_COMPAT_DATA_PATH="/home/theriddick/WINE/F4_SSE_MO2" /home/theriddick/.steam/steam/compatibilitytools.d/Proton-TKG-5rc4/proton run /mnt/GamesSSD/Games/MO2/nxmhandler.exe "$@"
STEAM_COMPAT_DATA_PATH="/home/theriddick/WINE/F4_SSE_MO2" /home/theriddick/.steam/steam/compatibilitytools.d/Proton-TKG-5rc4/proton run /mnt/GamesSSD/Games/MO2/Modorganizer.exe

RE: NXM Linking through XDG
by Jarrard on Tuesday January 7th 2020, 17:39
My system is very strange when it comes to nxm handling. Its impossible to run MO2 from firefox basically, it will runtime error fault, but nxmhandler can pass nxm links to mo2 if run outside and DIRECTLY via the proton command (note I said directly, I can't use lutris unless its to just exec the, using lutris blocks nxm handler somehow).
NXM Linking under Plasma with Chrome browser issues
by Jarrard on Saturday November 23rd 2019, 1:45
I've had some issues linking NXM to Brave browser and also linking with Proton launched MO2.

I discovered in the end I can enable WINEESYNC=1 in my and it will work but loads up a new instance of MO2 instead of using any existing prelaunched version (it will open the links up inside this instance fine).

I don't know what Steam is doing to create the proton mo2 instance but it must differ enough to cause it to trigger a separate wineserver.exe, anyone have input?

Also only FIREFOX has the ability to open NXM links to a handler, Brave browser does not and will just spit the usual unknown NXM:// handler (I tried endless fixes).

So this isn't quite how I wanted to handle things, anyone got some input overall? All I want is the MO2 instance from steam to work when opening a NXM link via browser, not a whole new instance loading up which appears to have faults (still uses same prefix but fails to load some fixes).

PS. I also had to manually set a API key because if MO2 tries to open a browser it crashes.
RE: NXM Linking under Plasma with Chrome browser issues
by ZenAnonX on Friday November 29th 2019, 18:30
1. Use firefox, don't if know brave supports nxm, it might even be failing even in windows.

2. It all boils down to running that nxm link with nxmhandler.exe in MO or MO2 folder. So for a link like this "FalloutNV/mods/..." we will have to run `wine nxmhandler.exe "FalloutNV/mods/..."`. This starts my download for that mod in MO instance, didn't test in MO2 yet. Simple way for this would be to make a desktop file that executes nxmhandler.exe and link that desktop file to nxm link open since firefox gives us that option.

3. Unless proton is running MO2 from a different prefix altogether the download should start in same MO2. Can you open a shell with all env variables set for that proton prefix and then try running both MO2 and nxmhandler from that same shell?
RE: NXM Linking under Plasma with Chrome browser issues
by Jarrard on Friday November 29th 2019, 18:38
In the end (Exec=sh /home/theriddick/ %u) did it for me in the nxm.desktop file, yep just had to state sh app. It works in firefox because it has its own inbuilt handler and bypasses this file or something..
RE: NXM Linking under Plasma with Chrome browser issues
by Jarrard on Friday November 29th 2019, 18:40
Also to get MO2 to open up links into the Steam Proton container you need to run it via the proton script or something. I haven't quite figured out the exact command yet. (I'll get around to it sometime).
Downloading from Nexus
by Joe Davison on Monday July 17th 2017, 14:35
For anyone interested, I've managed to get Firefox to handle nxm links through Mod Organizer meaning I can click NMM links on Nexus and have Mod Organizer go. Requires XDG.

Here's what I did:
Create a script called with the following contents

export WINEARCH=win32
export WINEPREFIX="/home/joe/GOG Games/Fallout New Vegas/prefix"
export WINEEXE="/home/joe/GOG Games/Fallout New Vegas/wine/bin/wine"

"${WINEEXE}" "/home/joe/GOG Games/Fallout New Vegas/prefix/drive_c/Program Files/Mod Organizer/nxmhandler.exe" "$@"

And an nxmhandler.desktop file with the following, which is then placed in ~/.local/share/applications
#!/usr/bin/env xdg-open
[Desktop Entry]
Exec=/home/joe/GOG\ Games/Fallout\ New\ Vegas/ %u
Path=/home/joe/GOG Games/Fallout New Vegas/prefix/drive_c/Program Files/Mod Organizer

Mark BOTH files as executable (chmod +x), make sure nxmhandler.desktop is in ~/.local/share/applications.

Next time you click an nxm link your browser should ask you what you want to do. Choose nxmhandler. Mod Organizer should then launch and commence downloading.
RE: Downloading from Nexus
by Jarrard on Sunday April 29th 2018, 7:59
Couldn't get this working for the new Vortex mod manager, with nxmhandler and direct to vortex. Not sure whats wrong.

NMM had crash issues on load up which is why I'm using Vortex (works). Haven't tried MO2 but from what I hear the virtual file-system component does not work correctly which is effectively 99% of MO2! so kinda pointless.
RE: Downloading from Nexus
by ZenAnonX on Sunday April 29th 2018, 15:23
Its basically a two step procedure,

First, having an application to handle nxm links(nxmhandler.exe) and a desktop file to send that link to that application.

And second, to have a browser which could send link to same desktop file on opening nxm links, this being firefox or any firefox variant(Icecat, Palemoon etc) works.

This procedure works fine with mod organizer since opening any nxm link with nxmhandler.exe starts download in mod organizer. Vortex's nxmhandler might handle this differently. So you might need to first find out command line arguments of vortex's nxm handler and then tweak desktop file accordingly. Try opening nxm links directly with wine to check.

wine nxmhandler.exe nxmlinktomod
RE: Downloading from Nexus
by Jarrard on Sunday April 29th 2018, 19:05
Yeah some fiddling is probably required.

Vortex makes these registry entries when you enable it
"C:\Program Files\Black Tree Gaming Ltd\Vortex\Vortex.exe" -d "%1"

So perhaps the -d is required, I have got it setup so when clicking on NXM links it opens vortex but it appears to not grab the link. Could need that -d.

I also tried using windows iexplorer and firefox inside the prefix but for some reason it fails to open the nxm link even when nxmhandler has been ran and set.
RE: Downloading from Nexus
by Jarrard on Sunday April 29th 2018, 19:09
ok the following line works but metadata isn't capture? perhaps that isn't working on vortex yet. I will need to test it under windows to see.

"${WINEEXE}" "/home/theriddick/.wine64/drive_c/Program Files/Black Tree Gaming Ltd/Vortex/Vortex.exe" -d "$1"
RE: Downloading from Nexus
by Jarrard on Sunday April 29th 2018, 19:13
Ok well $1 and $@ works so I dunno whats with that.

Unfortunately Vortex goes to a white-screen when you attempt to install. Maybe I should just create a windows VM for these apps, seems like their just not designed to function under wine at all.
RE: Downloading from Nexus
by ZenAnonX on Sunday April 29th 2018, 21:30
Yeah, NMM had broken compatibility with wine too due to dotnet, I assume vortex follows same pattern. I would suggest shifting over to MO as it works flawlessly for mod management and much more.
RE: Downloading from Nexus
by Jarrard on Monday April 30th 2018, 0:00
But Mod Organizer 2 does not work with VFS function? and the VFS is basically all of MO2.

I can't use MO1 for Fallout4 and SkyrimSE which is why I am going down this route. I dunno if Vortex is a dotnet issue as everything pretty much works until you goto install a mod and it has a white screen/box like some graphics is missing. Could be a simple fix.

I'll look into MO2 working but if the VFS can't initialize then its pretty useless.
RE: Downloading from Nexus
by A.J. Venter on Monday April 30th 2018, 2:31
Vortex is in public alpha - the problem you're facing may not even be wine related.

That said there may be an easy work-around to be able to use MO2 anyway. The only missing functionality is the VFS - and while MO has to do that with library injections - Linux supports it natively at the filesystem layer with tech like unionFS, AuFS etc (pick your poison really).

So you could, conceivably, write a script to read the data files from MO2 and determine the order in which the mods are meant to go, then move your skyrim directory out of the way and mount it back to the proper location, with the mods mounted overlayed on top of it in the same order.

It should give you a working setup - and may even have the bonus that you may not need to keep MO running to see the mods. I'm not sure exactly how the profiles directory would need to be mounted (you may have to ignore it's ini layer).

Sorry I can't test this myself at the moment, I'm one of the NVidia users who is affected by the current rendering issues on SSE so I cannot run it under wine.
That said, if you manage to make it work - maybe have the script take a parameter for the MO (and data) directories and stick it on github, that way other people can use it as a work-around until MO2's VFS is functional / or Vortex works. I'm sure people would appreciate that.
RE: Downloading from Nexus
by Jarrard on Monday April 30th 2018, 3:09
I did not have any rendering issues with SSE when I tested with my 1080ti 396.18 drivers last week. It ran at 55-60fps with high-ultra 4k. I did have a custom wine 3.6 staging package installed which apparently fixes fallout4 from the blackscreen issue, could also be why I did not have the graphics issues on SSE.

I had the new compiler disabled flag set btw.

As for vfs methods under linux, what's really needed is a decent mod organizer for Linux now that we have wine/dxvk at a stage where the games are running good. I'ts surprising to find almost all I have come across are some dotnet or something. I can't even get dotnet to work correctly (can't get past the select game mod folder stage, crashes with trace).
RE: Downloading from Nexus
by Jarrard on Monday April 30th 2018, 3:17
So my solution for now will be at some point I'll make a virtualbox windows install container and just use my mod tools through that. No virtual file system method but at least NMM and Vortex SHOULD work fine.

Quite surprising no progress has really be made to get these mod managers working under wine.

Latest NMM does this at present after selecting game/folders. (just putting this here for reference, I think this is just dotnet failing like always).

Tracing an Unhandled Exception:
Object reference not set to an instance of an object.
Full Trace:
System.NullReferenceException: Object reference not set to an instance of an object.
at Nexus.Client.Games.Fallout4.Fallout4Launcher.SetupCommands()
at Nexus.Client.Games.GameLauncherBase..ctor(IGameMode p_gmdGameMode, IEnvironmentInfo p_eifEnvironmentInfo)
at Nexus.Client.Games.Fallout4.Fallout4GameMode.get_GameLauncher()
at Nexus.Client.MainFormVM..ctor(IEnvironmentInfo p_eifEnvironmentInfo, GameModeRegistry p_gmrInstalledGames, IGameMode p_gmdGameMode, IModRepository p_mrpModRepository, DownloadMonitor p_dmtMonitor, ModActivationMonitor p_mamMonitor, ModManager p_mmgModManager, IPluginManager p_pmgPluginManager)
at Nexus.Client.Bootstrapper.RunMainForm(String[] p_strArgs)
at Nexus.Client.Program.Main(String[] p_strArgs)

Running Threads (0)
RE: Downloading from Nexus
by A.J. Venter on Monday April 30th 2018, 3:32
The issue doesn't affect everybody, but it does affect me, since I can't run the game anyway - I haven't really bothered to try and get a working mod setup for it.
There is an open bug about it:
RE: Downloading from Nexus
by Jarrard on Monday April 30th 2018, 3:36
Ironically Nexus Mod Manager 0.56 and earlier work provided you CANCEL the check for update on launch (and disable in settings). But no FO4 or SSE support in those sadly. Seems dotnet works but maybe NMM crashes due to some sort of internet access error.
RE: Downloading from Nexus
by HeroCC on Sunday August 11th 2019, 11:08
You may need to run `update-mime-database ~/.local/share/mime` after making the desktop file, I needed to.