If you still have the problem afterwards I need to know about your AV (name, version, licensed or freeware). Uninstall FNIS, and make sure that tools/GenerateFNIS_for_Users is completely removed. So don't be fooled when seeing the files.
Some AVs not only send false positives, they also remove execution rights from the. GenerateFNISforUsers.exe does not start on double-click / Error 53 (without file name): run as administrator! If the error persists, then almost certainly it's an issue with your AntiVirus software.
Note: the generator result is NOT affected by this warning.
We've yet to understand what's causing this issue, because there's a UAC-messing-with-me check inside NMM that is not triggering in this case, looks like something may have changed on Windows 10 or in a recent OS patch. Here is the comment by DuskDweller (the NMM developer):This is a completely new issue where Windows UAC is preventing NMM from creating any link file (save for a few), this is usually fixed by running NMM as admin the proper way. ERROR(2021) ("Language file(s) missing in Data\Tools\GenerateFNIS_for_Users\languages"): this is an NMM issue.The only know way to RELIABLY solve this issue is to move Steam and Skyrim away from "C:\Program Files(x86)". After installation go to GenerateFNISforUsers.exe -> Click Right-Mouse-Button -> Properties -> Compatibility -> Tick "Run as Administrator" -> OK. Remove "Data/tools/GenerateFNIS_for_Users" first.
To make FNIS work you can try to install FNIS manually. It seems to be caused by the Windows UAC (User Account Control), by which the Microsoft tries to protect "C:\Program Files(x86)" from the users wrong doing. Usually it is NMM which creates the issue as you can see from DuskDweller's response posted as part of the known issue "ERROR(2021)" (or 2001) below.
It has to do with authorization issues on your PC, and even the usual running as admin does not help. Usually (not always) these users - use NMM, and - have Steam, NMM, Skyrim all installed under "C:\Program Files(x86)". is denied: Recently there is a rising number of users who get this error trying to run FNIS. Nope im blind, the solution is on the fnis nexus page:ĮRROR(5): Access to the path.