Though This topic is quite old but I am here to mention that I am also facing this problem and someone can provide genuine solution to this.
Jump to content
Please note the date of the previous post, and see the Nexus "Terms of Service" about not resurrecting old threads. The primary reason is that the original thread participants are seldom still around, and it is unlikely that you have exactly the same setup. Details matter. Unsolved problems are usually due to vague descriptions of symptoms without any underlying details. And unless you are providing a definitive solution or significant new solid leads towards such a solution, it does not justify resurrecting an old thread. Even in the latter case you are better off starting your own thread and providing all the details requested in the wiki "How to ask for help" article.
Please provide ALL the information requested in the wiki "How to ask for help" article. Don't forget to identify things that do not appear in the "load order", such as the version of Windows, if you are using a "Steam" or "GOG" and/or "regional language version" of the game (even if you are playing it in English); using the FNV4GB Patch, NVSE and it's related plugins; replacements for textures (specifically their larger image sizes: 1024x1024, etc.), animations, or "bodies", etc.; and "post-processors" like ENB or SweetFX. It saves us playing "20 questions" and gets you a more specific answer more quickly. (The usual turn-around on post and reply in an older game forum is 24 hours.) Screenshots of the "load order" don't usually work so well because they tend to cut off or fail to display needed information and are hard to "piece together" into a complete and coherent picture.
* See "How to markup images (etc) in forum posts and comments" article for how to use "Spoiler tags". "LOOT" already includes those tags in the "load order" it copies to your clipboard, so you can just paste it's list into your post.
In the meantime, please see the wiki article "Installing a Mod With FOMM". Use the "FOMM-Forked" version of the mod.
As of 08 May 2018, the Nexus has changed some site security to come into compliance with the new "European Union General Data Protection Regulation" (EU GDPR) rules. This breaks older versions of NMM, FOMM, and other tools fetching mods using the older unsecured API. It is usually reported as being "blocked by the Windows firewall" or causing a "script" or "W3C XML Schema" error installing mods. You will need to update it from NMM on GitHub. Check the version numbers between those sites and use the latest release. Please see this Nexus site news article for details.
As of 13 May 2019 all "workarounds" that depend upon continued use of the old API will no longer function. That API has been removed, as previously announced more than two years ago. This includes but is not limited to:
* Nexus Mod Manager v0.65.11 and lower
* Mod Organiser 2 v2.1 and lower
* Mod Organizer 1
This only affects their ability to login to and automate the download from the Nexus site. You can still use them to "manage" your plugins with downloaded mods.
Bottom line: make sure you have updated your manager version.
* Did you install Steam to it's default location? (GOG is not a problem as it places the game correctly.) If so, please see the wiki "Installing Games on Windows Vista+" article for why the original default Steam behavior of installing games to the "C:\Program Files" or "C:\Program Files(x86)" folder tree was bad (they learned better, and don't do that any more but didn't change it for older games); and why "disabling UAC and running as Administrator" is NOT sufficient, with instructions how to move it. Among other things, later versions of Windows (since the game was released) force files in "system protected" folder trees to be "read only" regardless of how you set them.
Don't move it to "User\Documents" either, as "executables" are not permitted to run from there for similar "anti-malware" reasons.
This is the single most important thing you can do to fix and protect yourself against problems in the future. As much of a PITA as that is, it's never going to be any easier than now. System updates often cause issues with games installed to these folder trees. With the game moved out of the default location you will not need to be running it as an "Administrator Account", which is safer. Please see the 'Restoring to "Vanilla"' section of the wiki "FNV General Mod Use Advice" article as well.
If you did move Steam out of the default location, then likely any access privilege problem is one of "File and Folder permissions" on the parent "root" folder under which you installed the games. If this is not set correctly to allow at least "System", "Administrators", and "Users" to have "Full Control" then you can't overwrite other files or make changes. You then (while logged in as an "Administrator Account") need to enable the "Properties | Security | Advanced | Change Permissions" setting of the parent folder to enable the box: "Replace all child object permissions with inheritable permissions from this object", so those changes get applied to the existing files and sub-folders.
I recommend anyone read the entire "FNV General Mod Use Advice" article to understand the differences between this game and others you may have experience with; especially if this is your first attempt to play a modded FNV or it's been more than a year since you last did so. It is designed for someone who has never played a modded PC game before, so it tries to avoid making any assumptions, is kept "up-to-date", and covers years of "lessons learned". It is NOT a list of various mods to install that happen to work on the author's machine. It addresses fundamentals underlying how to get the basic game and mods to work together.