NMM your fallout4custom.ini is not configured corrently

[Mentholking]

I placed Archive above the Display and it fixed the problem.

YOU!!! Yes you... you saved my entire save game of 8 months into IT!!! THANK YOU !!!

[clydemcelroy1]

 

Are you sure that in your Fallout4.ini, under the [Archive] tab you have the following lines?

bInvalidateOlderFiles=1

sResourceDataDirsFinal=

(if the last one has anything after "=" you can remove it, those old entries "strings/etc" are no longer needed)

Well, this is stupid, the message (which I'm also getting) AND the documentation both say to add the lines to Fallout4Custom.ini... not Fallout4.ini...

 

 

Since custom ini overwrites fallout4 ini would it matter if you had it in both? Also just a note, the link the error message gives you goes to a malware site.

[Krigamortis]

Just a little disclaimer I recently started modding FO4, I don't have the experience or common sense for problem solving that the community has developed over the years.

 

I attempted to launch fallout 4 with F4SE, steam prevented the launch to do some kind of update. My steam settings are set to only update on launch, I launch with F4SE Loader shortcut on desktop, but it wasn't a version update guessing steam cloud or some type of sync. (sorry wasn't paying attention)

 

The original launch window before game showed (helmet pic).

 

I exited the window and launched again with F4SE this time in game I was missing custom menu and display settings but it seems the .esm, and .esl files were still working.

 

But when i attempted to reinstall a mod I got the "fallout4custom.ini not configured etc." pop up. and just like in Angardia picture I had that fallout4custom.nmm_backup file (that I don't recall being there before. Maybe it was.)

 

I tried to rearrange my fallout4.ini as others have with display beneath archive and it did not fix the problem.

 

Conclusion: Steam rewrote something and nmm doesn't like it. :) Wow right? (I warned you)

 

For now Im going to try to get my custom display settings back, I would appreciate any help one could provide.

[Ololesha]

I was helped by adding spaces after bInvalidateOlderFiles and sResourceDataDirsFinal.

It should turn out like this:

[Archive]

bInvalidateOlderFiles = 1

sResourceDataDirsFinal =

[Thisisnotmyday]

Well the Achieve above the Display worked, thx.

[deadpool0600]

I love how none of the responses are for what was being asked. I am having the same issue though, been modding for years, FO4 for a long ass time too. I have deleted and reinstalled the game maybe 20+ time over the last few years and am well versed in what I'm doing. My INI's are right, but the last two installs I've done for the game and re-initiating NMM with it have had this message popping up.

Again the INI's are correct and as they should be. I've done this enough to know. But the message keeps showing up even though it's all 110% functional in game.

[DareDevil3214]

Ive done everything in this thread, its still not working

[shadowhunter56]

Having same problem as everyone else, also for the sResourceDataDirsFinal = thing, do I have to change it within fallout4custom.ini or would I just do it under fallout4.ini cause I have seen both file types pop up and I am confused about it. Never even touched the ini files before either other than with Steam's version of FO3 which I was told not to get since it doesn't work on steam but it does with some other website though, but anyways, back to the topic at hand. for my sResourceDataDirsFinal= thing, does anyone else who hasn't done anything with it see a "STRINGS/" with "sResourceDataDirsFinal= STRINGS/" at all and is it supposed to be there or is there not supposed to be anything after the = like with what the posts before have said? Also out of all of the ini files that I have checked I never saw the bInvalidateOlderFiles = 1 at all either. Also I think I saw this one comment from somewhere but the link that the message with the "fallout4custom.ini not configured and whatnot" appears, the person said that the link sends you to a website for Malware or something like that, and I am also wondering why they haven't fixed that problem as well.

Edited March 26, 2021 by shadowhunter56

[surg23]

Does the custon.ini message even mean anything? Mods still install and play fine regardless.

[redravens13]

My issue was not only the listed error but also prevented Fallout 4 from seeing any mods even though the mods showed installed and activated in NMM.  In NMM a new profile was created labeled Creation Club Mods and overwrote my Fallout 4 profile and when I activated the original profile, NMM would crash when I tried to add, remove, enable, and disable installed mods.  What caused this?

My game suffered a catastrophic freeze and it could not be shut down in Task Manager, so I was forced to do a hard reboot.  Somehow, not only was the game bricked, NMM was bricked.  I had to delete all game files and NMM files and reinstall them and reload all mods in NMM.  That is when I could not activate any mod without the error and the game would not see any mod in NMM.  After reinstalling, I had to modify the listed files and delete the corrupted lines.

What fixed my error in NMM and get NMM to see all the mods was to fix both the FALLOUT4.INI and the FALLOUT4.CUSTOM.INI files in the location of your operating. Usually, your "C:" drive is  -  C:/Users/"the name of your user file"/Documents/My Games/Fallout4 .  The files in question will not be where Steam loads the major game files including your DLC's and Mods.  By default on the "C:" Drive - C:\Program Files (x86)\Steam\steamapps\common\Fallout 4 .  I needed to add the lines, 

bInvalidateOlderFiles=1

sResourceDataDirsFinal=

under the [Achive] tab.  I put the 2 lines at the top within the tab in the order shown in the "Fallout4.ini" file.  For the FALLOUT4.CUSTOM.INI file, I also added the two lines listed at the top in the [Archive] tab,  and moved the [ARCHIVE] tab above the [Display] tab at the top of the file above all other tabs.

I also removed the corrupt lines in both files.

I started having problems with the game after the Next-Gin Update.

This is what worked for me.