Table of Contents

Why Do My Mods Keep Disabling Themselves in Fallout 4?

Quick answer

This page answers Why do my mods keep disabling themselves Fallout 4? quickly.

Fast answer first. Then use the tabs or video for more detail.

Watch the video explanation below for a faster overview.
Game mechanics may change with updates or patches.
Use this block to get the short answer without scrolling the whole page.

Read the FAQ section if the article has one.
Use the table of contents to jump straight to the detailed section you need.
Watch the video first, then skim the article for specifics.

▶

The frustrating issue of Fallout 4 mods inexplicably disabling themselves is a common headache for players who love to customize their wasteland experience. The most frequent culprit is a “Read-only” setting on your user_settings.config file. This prevents the game from properly writing and saving your mod preferences. When this file is set to “Read-only,” the game cannot save that the mod is enabled and therefore, it is disabled upon restarting.

However, there are several other potential causes. These include issues with load order, mod conflicts, problems with your mod manager, and even conflicts with Windows Security features. Let’s dive into each of these possibilities to help you diagnose and fix this annoying problem.

Troubleshooting the Disappearing Mod Mystery

Here’s a comprehensive breakdown of the most common causes and their solutions:

1. The “Read-only” Culprit

Problem: Your user_settings.config file is set to “Read-only,” preventing the game from saving your mod preferences.
Solution:
1. Locate the file. The file is typically located within your Documents/My Games/Fallout4 folder.
2. Right-click the file and select “Properties.”
3. In the “General” tab, uncheck the “Read-only” box.
4. Click “Apply” and then “OK.”

2. Load Order Chaos

Problem: Mods need to load in a specific order to function correctly. Incorrect load orders can lead to conflicts and disabled mods.
Solution:
1. Use a mod manager like Nexus Mod Manager (NMM) or Mod Organizer 2 (MO2) to manage your load order. MO2 is generally considered superior due to its virtualized mod installation, which keeps your Fallout 4 directory clean.
2. Look for any conflicts indicated by your mod manager. Many managers can identify potential issues between mods.
3. Experiment with different load orders. A general rule of thumb is to load core mods (like bug fixes) first, followed by smaller mods, and then texture packs.
4. Use a tool like LOOT (Load Order Optimization Tool). LOOT automatically sorts your load order based on community-maintained rules, significantly reducing conflicts.

3. Mod Manager Meltdown

Problem: Your mod manager is outdated, misconfigured, or experiencing errors.
Solution:
1. Ensure your mod manager is up to date. Download the latest version from the official Nexus Mods website.
2. Run your mod manager as administrator. This gives it the necessary permissions to modify game files.
3. Verify that your mod manager is correctly configured to point to your Fallout 4 installation directory.
4. Reinstall your mod manager if problems persist.

4. Windows Security Interference

Problem: Windows Security (including Windows Defender and third-party antivirus software) may be interfering with the mod installation or execution.
Solution:
1. Add your Fallout 4 installation directory, your mod manager, and the Fallout4.exe file to the exceptions list in Windows Security.
2. Temporarily disable your antivirus software (with caution) to see if it’s the cause of the problem. If disabling it resolves the issue, you’ll need to configure your antivirus to allow Fallout 4 and your mod manager to run without interference.

5. Corrupted Mods

Problem: A downloaded mod file is corrupt, leading to installation issues and disabled mods.
Solution:
1. Re-download the mod from the Nexus Mods website. Ensure the download completes successfully.
2. Check the mod’s comments section on Nexus Mods. Other users may have reported similar issues and potential solutions.
3. Completely remove the mod (including any files left in your Fallout 4 directory) and then reinstall it.

6. Multi HD Install

Problem: Fallout 4 and your mods are installed on different hard drives, causing issues with accessing the mod files.
Solution:
1. Try installing the game in the same drive the mods are installed.
2. Create a symbolic link, can be done from the command prompt.

7. Plugin Limit

Problem: Fallout 4 has a 255 plugin limit. If you exceed this limit, mods will not load.
Solution:
1. Use a merging tool (like Merge Plugins) to combine smaller mods into larger ones, reducing the plugin count.
2. Disable unnecessary mods. Carefully evaluate which mods are essential to your gameplay experience and disable those you can live without.

8. INI Files

Problem: The .ini files are not configured for modding.
Solution:
1. Go to your Documents/My Games/Fallout4 folder.
2. Modify the Fallout4Custom.ini file as such:

[Archive] bInvalidateOlderFiles=1 sResourceDataDirsFinal=

9. BethINI Tool

Problem: Using this tool with an incompatible INI setting.
Solution:
1. Ensure the “Basic” preset is selected.

10. Archive Invalidation

Problem: Not having proper archive invalidation.
Solution:
1. It is necessary to have Archive Invalidation set up correctly. Most mod managers should handle this, however, some may need this to be set up manually.

11. Game version

Problem: Having an older game version incompatible with a mod.
Solution:
1. Update the game to the latest version.
2. Downgrade the mod to an older version.

12. Missing Masters

Problem: Some mods require other mods to function (these are master files). If these master files are missing, the dependent mod will fail.
Solution:
1. Read the mod description carefully. The mod author should list any required master files.
2. Install all required master files before installing the dependent mod.
3. Check your mod manager for warnings about missing masters.

13. Script Extender (F4SE) Issues

Problem: Many advanced mods require the Fallout 4 Script Extender (F4SE). If F4SE is not installed correctly or is outdated, mods that rely on it will fail to function.
Solution:
1. Download the latest version of F4SE from the official website.
2. Follow the installation instructions carefully. Typically, this involves extracting the F4SE files into your Fallout 4 game directory (where Fallout4.exe is located).
3. Launch Fallout 4 through the f4se_loader.exe file.

14. Game Cache

Problem: Having a corrupt or old cached game files.
Solution:
1. Verify the game files through Steam.

15. Conflicting Settings

Problem: Some mods may have incompatible settings.
Solution:
1. Read the mod descriptions carefully.
2. Use the mod configuration menu.

Fallout 4 Mods FAQ