FNIS and Nemesis won't start through Mod Organizer anymore

[Nathriel]

So as the title says, my main problem is that as of yesterday both FNIS and Nemesis won't start anymore.

I have both setup properly as executables and at least FNIS worked a few days ago (Nemesis has been longer since I last tried).

 

When I launch FNIS through the executable it appears to start, but I never see a window appear. All I see is:

I have to go into Task Manager to manually shut down the FNIS process.

 

If I try to launch FNIS through the Data tab (but still within Mod Organizer), it DOES start up, but if I try to run it, it displays this error message:

 

When I try to launch Nemesis a slightly different thing happens. I get a blank Warning screen that soon after won't respond:

 

If I try to launch Nemesis through the Data tab I get:

 

As a note, I am using Skyrim SE on version 1.5.97.

All the OTHER tools that I run through Mod Organizer work just fine, by the way. It's just FNIS and Nemesis that are the issue.

 

Things I have tried so far:

• Restart Mod Organizer
• Restart PC
• Run the normal version of FNIS instead of XXL (same result)
• Make a new profile, enable just FNIS or Nemesis and nothing else and try again (same result)
• Reinstall FNIS and Nemesis
• Reinstall Skyrim and rollback to 1.5.97 again
• Re added everything to Windows Defender exception list

 

The only major thing I did yesterday that I can remember is compiling the zadBoundCombatScript according to DD 5.1 to DAR (Python script). Said compiling was done using the Papyrus Compiler App.

I doubt that would be the cause though.

 

It feels like both are having problems finding the right path or something, but from what I can see all the paths are setup correctly (nor did I change any of them recently).

 

Does anyone have any idea's what the problem might be?

 

Edited September 21, 2022 by Nathriel

[darkersteele]

In Windows 11 (and I think its the same for Win10), I had to set an exception for Windows Defender for the apps "MO2", "FNIS_Users" and "Nemesis".

I got the exact same error, because Win Defender prevented these apps to run virtualized.

I also added the \mods folder of MO2 as an exception.

 

Solved my problem.

[Nathriel]

32 minutes ago, darkersteele said:

In Windows 11 (and I think its the same for Win10), I had to set an exception for Windows Defender for the apps "MO2", "FNIS_Users" and "Nemesis".

I got the exact same error, because Win Defender prevented these apps to run virtualized.

I also added the \mods folder of MO2 as an exception.

 

Solved my problem.

Oh right, I forgot about that. I did add them all as exceptions in the past, but I'll try re adding them, see if that helps.

[Nathriel]

I removed it all from the exceptions of windows defender and then added them all back in there, including a lot of the folders themselves like \mods.

Unfortunately, that did not do anything.
I even just tried turning off both Virus & threat protection and Firewall for a moment and that did not do anything either.

 

So I doubt it's Windows Defender causing the issue.

[davisev5225]

If you are on Windows 11, the Memory Integrity Protection might also be getting in the way of the VFS.

[Nathriel]

37 minutes ago, davisev5225 said:

If you are on Windows 11, the Memory Integrity Protection might also be getting in the way of the VFS.

I'm still on Windows 10, so that won't be it either.

[Nathriel]

I managed to fix it!

Probably not in an ideal manner, but it works.

 

What was copy the tools and Nemesis_Engine folder and paste those in my actual Skyrim Data folder.

Then I pointed the Executable in MO to the exe's in there instead.

So I am still launching FNIS and Nemesis through MO. The actual exe's are just no longer located there. All the OTHER files required for both ARE still located in MO.

[davisev5225]

I don't use Nemesis, but that's how I handle FNIS.  Something about how it's coded doesn't like VFS implementations very much - it much prefers to "live" in the real directory instead of a virtual one.