search

Nexus-Mods / Nexus-Mod-Manager

GNU General Public License v2.0
967 stars 164 forks source link

Fallout4Custom.Ini Permanently Broken? #815

Open ItsNickValentinesWife opened 5 years ago

ItsNickValentinesWife commented 5 years ago

Describe the bug I used to have Fallout 4 running just fine with mods, but since I uninstalled and reinstalled it, I can't get it to work with NMM again. Every time I try to install mods, I get the "Fallout4Custom.ini is not set up correctly" error. I check and my ini is set up exactly like how the wiki has it. I deleted the file, remade it and I still get the error. I altered my Fallout4Prefs.ini, nothing. I reinstalled NMM, nothing. I don't know what to do at this point because I have everything set up, but NMM refuses to read the file.

Environment

Additional information https://ibb.co/Lrpkx3p https://ibb.co/9gHC3N7 https://ibb.co/j87SNVf

clydemack commented 5 years ago

This happens for me when I try to activate the 1st mod after opening nmm. If I leave it open and install another mod or mods, it won't happen again until I close nmm and restart it.

Then it offers a link to go to and learn more or whatever. That leads to a site with confirmed malware. I have scanned and rescanned my own computer for viruses, including specifically the nmm folder and the fallout4 folder.

It seems, and I am in no way an expert, that since it only does it just after launching nmm, on the 1st activation, that someone has somehow added something to the launch file of nmm that creates that popup and leads to the malware site. Am I just being paranoid?

clydemack commented 5 years ago

nmm

Just wanted to add a screenshot to show you why I was concerned about the link.

clydemack commented 5 years ago

Turns out I am probably paranoid. I saw where it was posted your security certificate expired and that's why that page comes up that way. Doesn't explain that popup coming up when I try to activate the first mod after opening nmm though. It's repeatable. Just open nmm, activate mod, get popup. And it happens with a default custom ini, a custom ini with just adding binvalidate, etc, tried putting it below the default stuff and above. tried my custom ini file I used in a previous playthrough that worked fine for months. Tried it with no custom ini. So, any suggestions beyond those?