-
Notifications
You must be signed in to change notification settings - Fork 165
Troubleshooting
This page is an attempt to dive deeper into some common issues and solutions listed on the wiki homepage. Please refer to that page for for other issues.
Click things with arrows to expand them
Note: If you see this without clicking on something, this page does not support your browser. Chrome or Firefox is recommended.
Failed to start process (the parameter is incorrect [87])
My mods don't show up in LOOT / Wrye Bash / xEdit!
Bodyslide failed to load setup.xrc / BodySlide.xrc file!
Disable anti-malware and anti-virus programs
USVFS hooks into the programs you run through MO2. To many anti-malware programs, this can look like a nefarious action. Many of these program will interfere with MO2 or USVFS with absolutely no indication to the user. Adding exclusions or exceptions to the entire MO2 installation folder, not just the executable, may allow MO2 and USVFS to work correctly. Some particularly stubborn programs seem to not respect exclusions and may need to be completely uninstalled.
Note: Not all users will be affected by this in the same way.
Note: This list is non-exhaustive. This only includes programs we've seen interfere.
Acronis
Some versions of Acronis backup software include anti-ransomware protection. Adding an exclusion for ModOrganizer.exe should work. Last reported: 2018-08-03.
Avast
No details available.
Bitdefender
Adding exclusions for the entire MO2 installation folder works for some users. Other users have had to completely uninstall Bitdefender. Last reported: 2018-08-01.
Malwarebytes
No details available.
Windows Defender
No details available.
Check the options for the executable
In the Modify Executables dialog, double-check the "start in" and "arguments" fields for the executable having problems. The possible problems are too numerous to list here. If you're not sure what they should be, maybe ask in the Discord channel.
Check the Windows Event Log service
For currently unknown reasons, the Windows Event Log service can be critical to properly hooking some programs like LOOT, Wrye Bash, and xEdit. As of version 2.1.4, MO2 will warn the user of a busted event log service when running an executable.
To check the state of the service, open the Windows start menu and type "Services". Find the "Windows Event Log" service in the list. The status should be "running" and the startup type should be "automatic". If they are not in this state, double-click the service to bring up the properties. Change the startup type in the drop-down menu, hit apply, and then hit the start button.
If the service refuses to start, something could be wrong with Windows logs. Fixing this is out of the scope of this wiki. One user has reported success by deleting the logs located somewhere in the C:\Windows folder.
Do not clear the Windows system log
For currently unknown reasons, the Windows system log can cause problems if it has been cleared. This can happen if it's done manually with the Windows Event Viewer or if it's done automatically with a tool like CCleaner. Any time the system log is cleared, your PC must be restarted for MO2 to work properly.
In the case of CCleaner, this should be able to be avoided by disabling the "Advanced > Windows Event Logs" option.
Update or uninstall Alienware/Dell software
A crash in this manner is usually caused by a program that creates overlay icons on files. This is an incompatibility between these programs and Qt, the GUI framework used by MO2.
A known offender of this is software for Alienware or Dell computers that may be called Alien Respawn or Dell Backup and Recovery. This comes stock on many of their computers. Installing the most recent version of this software should resolve the issue. Alternatively, uninstalling the software should also fix the issue.
Hopefully useful information: https://www.dell.com/support/article/us/en/04/sln297423/dell-backup-and-recovery-18-overview-and-install?lang=en
Block Skyrim SE in your firewall
Skyrim SE has an annoying bug where it can crash when able to connect to the internet. For some reason, launching the game through MO2 can cause this issue to occur, even if it doesn't occur when the game is launched outside of MO2. To confirm this is an issue, I suggest you disable your entire internet connection and try again. Pull the Ethernet cable. Disable your WiFi antenna.
If the game launches successfully in that state, block anything remotely related to the game from the internet. That includes the game itself (SkyrimSE.exe), the Creation Kit (CreationKit.exe), and even SKSE64 (skse64_loader.exe). You can do this with Windows Firewall. On Windows 10, you'll want to use the app "Windows Defender Firewall with Advanced Security."