FNW Win10 RS3 patch crash

[dubiousintent]

Please, do keep us informed of any solution. Good luck.

 

-Dubious-

[Derialund]

I have sent an e-Mail to the NVSE team, but I didn't get any answer. Considering that adding the main executable (nvse_loader.exe, FalloutNV.exe and FalloutNVLauncher.exe) on the DEP exception list that can be edited on the System tab, didn't produced any appreciable solution, I have decided to go directly at the Root of the Problem. The Anti-Exploit (old EMET) integrated inside Win10, with the RedStone 3 (1709) "service pack" (I think is called Windows Defender Exploit Guard, but I'm not sure of that, for the language I use on the system is Italian).

It can be configured inside the Windows Defender Security Center, on the "App & browser control tile", "Exploit protection settings". Inside there, there's two main configuration voices "System settings" and "Application settings". To solve the problem it is necessary to add an entry for FalloutNV.exe and NVSE_loader.exe (to be sure, I don't have do any test to see if only FalloutNV.exe is needed, but after adding it and launching the game, the NVSE problem was solved, but if removed it and then launched the game again, have caused the "Could not inject DLL" error message to appear again, so the override entry related to FallouNV.exe is mandatory). There, every security option must be override and superimposed on deactivate.

Now the game launch quickly and NVSE is working again. Probably the last MS patch have solved something related even with the Exploit protection feature, for I can assure you that before its installation I haven't any problem with NVSE.

At the moment, I'm supposing if even SKSE could be affected by this issue.

[Derialund]

I don't think that placing a mass-override on the Exploit Guard feature, for FalloutNV.exe and NVSE loader could lead to some security problems. These processes are not dangerous as a browser or else.

 

This situation has also proven that the Exploit Guard feature take over any other configuration placed on the system. Probably even the DEP entries made on the old Windows System settings section.

[dubiousintent]

Interesting. Nice detective work. Logically I agree with your conclusions.

 

Just a little clarification, please, as I don't have Win10 or EMET myself (still on Win7). You say "every security option must be override and superimposed on deactivate." However, from what I have been able to determine searching the web, it is not clear if "override" and "superimposed on deactivate" are "exploit mitigations" you enable or setting choices you make under the various other mitigations. Would it be possible for you to link an image example of such for either app; and might I have permission to use that image to illustrate this solution in the wiki?

 

Now we just have to see what impact the "out of band" patch on the 5th: "2018-01 Security Monthly Quality Rollup" (for Meltdown) will have. It already forced me to roll it back because it shrunk my "borderless windowed mode" FNV screen down to a one inch square. Looks like January is going to be a bumpy ride for games. "This article" lists the related KB articles for the various versions of Windows.

 

-Dubious-

Edited January 7, 2018 by dubiousintent

[Derialund]

I have tried to reduce the override entries for FalloutNV.exe and NVSE_loader.exe, but it didn't went right.
Leaving just FalloutNV.exe and removing NVSE_loader.exe, caused the game to finish in a loading endless loop. So to have the game working, you need both FalloutNV.exe and NVSE_loader.exe inside the Windows Exploit Guard.

Pratically you have to

 

1) Open the Windows Defender Security Center
2) Go to "App & Browser control"
3) Scroll down the page and go to "Exploit Protection" section. Then click on "Exploit Protection Settings"
4) Inside the result page, pressing over "Program Settings"
5) Click on "Add program to customize"
6) Click on "Choose exact file path" and search on the root the location of FalloutNV main executables, where FalloutNV.exe and NVSE_loader.exe should be
7) In the "Program Settings" page should appear the entry with all the path (for ex: D:\Fallout\FalloutNV.exe)
8) In such entry click over it and then on the button "Edit"
9) Inside the setting page resulting, there's various entries like:

- Arbitrary Code Guard (ACG)
- Block low-integrity images

etc.

then under it there's a check box for every entry with the description: "Override system settings". Under it there's a "lever-box" with On/Off

That checkbox must be checked for every entry and then every "lever-box" must be turned to OFF.

21 System override should be indicated under the Fallout Executable entry list, that means that everythings is turned off.

Edited January 7, 2018 by Derialund

[Derialund]

This must be done for both FalloutNV.exe and NVSE_loader.exe

It can be necessary even for Skyrim and Fallout4 in case, for who play such games under Win10 RS3 (1709).

I have found that the game "response" is more quick.

 

PS: Yes, you can use the images but it would be better to be done from an english language Windows, for mine are in Italian.

Edited January 7, 2018 by Derialund

[Derialund]

Thank you to make me aware of the Meltdown patch issues.

PS: Yesterday night I have put the PC on Hibernate. The PC closed and turned off. So I decided to have a look at my smartphone. The PC was silent but still powered and connected to a working router (that I use to connect).

Then suddenly the PC decided to turn on again, without me pressing the hardware start button. I thought about it could have received a bogus Wake Up on LAN packet, but I don't really know. There wasn't any other PC connected, nor other computer tools that could have been sent such packed on the LAN.

Really spooky.

Edited January 7, 2018 by Derialund

[dubiousintent]

Thanks for the details and clarification on the WDEG configurations. I agree about the images (English is the language of the forums), so hopefully someone else will provide some. (Your English is good enough I lost track that it isn't what you are using in your system. :laugh: )

 

As for the PC "waking up" in the middle of the night: most likely that was the "Background Transfer Service" (BTS) which is Windows way of checking for and downloading updates. That is an "internally initiated" process as opposed to the "externally initiated" "Wake On LAN" packet that you speculated. Anti-virus (and who knows what else) can also trigger such a "wakeup" as long as the system has power, even when not logged in.

 

-Dubious-