BreakinBenny96

Well, I have Control Flow Guard, Data Execution Prevention, Forced Randomization for images, randomizing memory allocations, validate exception chains and heap integrity all enabled. I wound up exceptioning Arbitrary Code Guard to OFF, blocking images with low integrity as well, remote images, fonts that "aren't trusted", Code Integrity Guard, the CFG, DEP, disabling deactivation of addon-mechanisms allowing for DLL injections, Win32k calls, subprocesses, EAF, forced randomizaion, hardwarebased stack protection, IAF, memory allocation, and SimExec. You can experiment as well.

I've found the solution!!! I have to toggle a number of vulnerability settings for Lithtech.exe that are active by default for the system. Say that you have all the vulnerability settings for your whole machine enabled by default, you have to add exceptions to Lithtech.exe so it can run the latest edition of Modernizer (by this point). (I am a broken record by this point, oh frick I did it again.)

And I did... Unfortunately, nothing changed. Neither did excluding NOLF and Lithtech.exe from DEP... but it was worth a try.

Howdy! How do I do that? Anyway, disabling Data Execution Prevention on lithtech.exe and NOLF.exe didn't do a thing either. I had to do that for Rune, Unreal Gold, and Harry Potter and the Philosopher's Stone.

Yep... similar on my end. Not even the first two PC Harry Potter games play this dirty, particularly not with the unofficial upgrade Metallicafan212 made for HP2.

Yes. After installing the 2015-2019 64-bit one it still doesn't let Modernizer play. And again, I am sorry for sounding like a broken record, but the Modernizer patch needs updating and there's no question about that with this issue, especially if I'm to stay on these specs. Then it's a good thing me using Inspection mode and doing a "hacky hack" partly fixes it.

I did that too, and FOX.REZ had definitely nothing to do with it. Is this a case of me being an unlucky sod whose machine the last version of Modernizer refuses to run on before Haekb took off with no idea Visual C+ 2019 Redist could no longer be obtained easily on its own?

You probably know about my specs already, but I might specify them again. My Windows 10 Pro machine is on version 22H2 with an Intel Core i5-2500K processor at 3.30 Ghz, 8 GB RAM and on 64-bit OS with an NVIDIA Geforce GTX 460. The latest version of Modernizer that works for me is the one with "Patch 1", unlike the latest one that was seemingly abandoned by its creator. I don't have any additional mods sans the FOX.REZ which contains GOTY multiplayer maps.

It took me quite the effort to reply, but I've done it now. Compatibility mode didn't do anything at all, I got the exact same results. I can't tell if it's because of the Intel HD graphics fix Haekb tried implementing or something else, but I still believe this calls for emergency updating by someone other than Haekb (such as DanielGibson) because the former has mysteriously vanished and their GitHub is no longer maintained, with no way to contact them.

In the past, Modernizer worked well for me when I went back to play No One Lives Forever 1. I did miss out on multiplayer, but it wasn't a significant loss... but with the latest version that was last updated three years ago, and even with Visual C++ Studio 2019 Redist, Haekb's creation doesn't work at all on my Windows 10 PC. How many of you people have had this issue? Only a few, or many? Even then, I feel this calls for updating like DanielGibson on GitHub's currently doing. What can I do to solve NOLF1 never getting to the main menu without a black screen and then crashing? Thanks in advance!