-
Posts
3 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by rubjonny
-
-
As title. Spent hours and hours trying to figure out why Fallout NV wouldn't even launch. Uninstalled, Reinstalled, verified local files in steam, UAC is switched off, installed on my D: drive etc etc. Gave up. Reinstalled Fallout 3, checked it loaded which it did. Spent hours and hours installing a large mod list, only to find FOSE wouldn't work. More hours checking all the usual, no joy.
I finally figured out the issue just now, its Windows Exploit Protection. To resolve:
Right click start menu -> click settings
Update & Security
Windows Security
Virus & Threat detection
App & browser control
Exploit protection settings
Program settings
Add program to customise -> Choose exact file path
Browse to Fallout.exe
Scroll down, Tick 'Force randomisation for images (Mandatory ASLR) and make sure its set to Off.
Repeat for FalloutNV.exe, enjoy!
-
As title. Spent hours and hours trying to figure out why Fallout NV wouldn't even launch. Uninstalled, Reinstalled, verified local files in steam, UAC is switched off, installed on my D: drive etc etc. Gave up. Reinstalled Fallout 3, checked it loaded which it did. Spent hours and hours installing a large mod list, only to find FOSE wouldn't work. More hours checking all the usual, no joy.
I finally figured out the issue just now, its Windows Exploit Protection. To resolve:
-
Right click start menu -> click settings
-
Update & Security
-
Windows Security
-
Virus & Threat detection
-
App & browser control
-
Exploit protection settings
-
Program settings
-
Add program to customise -> Choose exact file path
-
Browse to Fallout.exe
-
Scroll down, Tick 'Force randomisation for images (Mandatory ASLR) and make sure its set to Off.
Repeat for FalloutNV.exe, enjoy!
-
Fix found for FOSE and New Vegas not working on Windows 10 20H2
in Mod Troubleshooting
Posted
That's the thing, on my machine there were no error messages of any kind. The event logs were clean, no crashes, nowt, zilch, naaathing.
It was a hunch based on something that popped up on one of the machines I support at work, it wasn't exactly the same since it actually crashed and gave an error message but it was a package which put a hook into the winsock stack or something along those lines. It got me thinking that FOSE must launch some kind of hook into the FO3 exe maybe I was dealing with the same issue. Though that doesnt explain why even the standard FONV executable wouldnt run, I guess theres some kind of magic going on under the hood.
Anyway, if it helps even 1 person avoid the 12 hours of messing about I went to I'll be happy :D