Mandatory ASLR causes apps/games to crash (including FFVII “97 launcher on start)

[J1327]

FF7 "97 original. No mods or alterations. Game doesn’t start via launcher while M-ASLR is on. This is caused due module, which isn’t “shipped”/compiled with /DYNAMICBASE option.


Inspecting (launching .exe) with-in cheat engine’s windows debugger,
Static addresses 548BAEC there it should lead to -> "FF7_Launcher.exe+148AEC" (or as section address to -> FF7_Launcher.exe.bind+1AEC) leads to “??”...
While "FF7_Launcher.exe.bind+1AEC" exist but in different location than expected "0015BAEC” ...
So, process base address starts from 0x10000 instead from (expected/preferred) 0x400000.


Even AV is turned on, Windows Security still protects. It is not a bad thing when working in high-risk environments -- have additional security.
So, in this situation, game launcher (aka. for Final Fantasy VII “97) crash is caused due (following) security setting.
This Windows Security setting: “Force randomization for images (Mandatory ASLR)”, which reallocates process else there and
Causes program instability.

To “resolve” this, switch that option off – reboot machine – try launching app/game again.
Alternatively add program to exception.
(notes: if this would become mandatory ASLR as default option (its a far shot))

[satandidnowrong]

Came here interested to read about the problem and glad there is a solution. Thanks!