Ran into this when I built a new rig and upgraded to Windows 10. It does have issues, but probably gets trashed more than it should....maybe. I ended up just fresh installing everything for my games, including validating game files on Steam. It wasn't what I wanted to do, but it kept me from breaking a window or chair. Glad I did it now.

***Windows 10 did teach me how critical backup on a separate disc for all my game stuff is....I can't overstate this enough!

Also I use MO 2, so I can't help you on the mod managers you've chosen.

Yeah, I've got all my files on a small 500gb external drive and game files on cloud storage. Learned lesson the hard way when a previous pc fried on me. Anyhoo, this was a completely fresh start DL for this cp and game runs great... just running around with invisible armor and guns atm. Only mods that seem to be working are direct DL's via the mod page in game.

So there's a missing mesh/texture path...more than likely mesh path. Is there a way to trace that path in your mod manager?

Tried, Even went and manually put the materials, meshes, scripts, and textures in manually then put the ESP's in the main data file. Still inviso armor. I'm thinking of uninstalling and reinstalling NMM again and trying that. I had better results using that loader on the last pc maybe it will work this time, maybe not. just don't know.

Just a thought before you do, have you looked for conflicts in Xedit? It is by far one of my favorite modding tools.

Nope, I don't think I have it. Will have to go download and give it a shot.

I was wondering if W10 may be blocking the files for admin use as I noticed the last time I used NMM I had to open it run it as Admin. Maybe its locking up files as read only and not allowing the mods to overwrite properly?

You actually might be onto something with that....seems like I did read somewhere about admins rights. Regardless, XEdit is a tool I wouldn't be without.

Ok, ran Xedit and cleaned up the only error that came up (load order on Armorsmith extended), ran file integrity check just to make sure all is well (it was all good), and still having same issues.

Some noted mods that are not in-game DL's that are working:

F4SE
Looksmenu
Sig MPX
Eyes of Beauty
KSH Hair
and various character presets.

Seems all other mods, even mods not dependent on Armor Keywords or Armorsmith Extended are scripted in game but are not appearing.

I've deleted all mods, and re-installed them manually again to ensure material files, meshes, scripts, and textures are in place. Still getting same results.

Maybe if I run it under compatibility with earlier windows version? I'll try that next and update. Let me know if anyone has any ideas.

UPDATE: Changing windows compatibility did not fix anything either.

Hi. Did you manage to fix this error (i hope so)? If not, let me throw in my 1$;

One of Windows 10 updates, specifically Windows 10 October update went and reset privileges set by you as a user. Uncertain if the word privileges is correct (not native english speaker). Permissions?

That means, that the file that need read/write permission suddenly gets reset to read-only. Not by you, but by WIN10. I would check the .ini file and see if Nexus actually has permission to write to that file.

Try this:
+ Go to Documents\My Games\Fallout4
+ Find Fallout4Custom.ini
+ Right click > Properties and uncheck Read-only under General tab
+ Do the same with Fallout4.ini


That said, I had a very similar problem that you describe with Nexus and mostly the same mods before WIN10 october update. I spent hours and hours trying to fix it, and unfortunately I did not document what I did properly. I did however find one tibit of information i left myself;

"Make sure your Fallout4.ini has this line in its entirety: sResourceDataDirsFinal=STRINGS\, TEXTURES\, MUSIC\, SOUND\, INTERFACE\, MESHES\, PROGRAMS\, MATERIALS\, LODSETTINGS\, VIS\, MISC\, SCRIPTS\, SHADERSFX"

I'm sorry, but I can't find the post about the line above, so I can't link or give credit.

Or - you can go the route I went.
Wipe Nexus and FO4 from registry by using regedit and try to start from scratch. Then finding out that the .ini-files was checked to read-only, uncheck that and things suddenly started to work out.

Yes, I found that I had duplicated a file in the targets. Thanks for the follow up!

Thanks! I managed to fix it. I was a knuckle head Mcspazatron and had one of the targets set to a folder inside the folder it was to go to so. once I fixed that it was fine.