WARNING!!! BACKUP YOUR 32bit/x84 Flash.ocx IN CASE THE ONE IN THIS THREAD DOESN'T WORK FOR YOU.
(I'm looking into this problem seriously now, waiting for a few flash devs to get back with me. I'm tired of all these plebs complaining about the same shit)
Previous thread: https://www.mpgh.net/forum/showthread.php?t=1170564
The reason why trainers are crashing when loading SWFs is because the shockwave flash has a security update that messes with the ability to write memory in the base swf from other swfs. There's a few ways to fix this depending on your OS, and version. I've recently came up with a solution that should work for everyone. Visual Studio's shockwave flash control references Flash.ocx, all you have to do is use a Flash.ocx without the security patch.
1) Go to C:\Windows\System32\Macromed\Flash
2) If "Flash.ocx" exists then
Right click > properties > security > Advance > Change Owner > Advance > Find Now > Select your Windows Username > OK > OK > Apply > OK.
Now click Edit then select your Users/Admins and check Full Control.
Remove/Delete Flash.ocx
3) Download Shockwave Flash Fix from this thread, and extract the Flash.ocx to your Macromed\Flash folder.
Now you should be able to use SWFs in trainers again. If this doesn't work then try to uninstall the Adobe Flash security update or install an archived flash version(https://www.mpgh.net/forum/showthread...5#post12680335).
Virus Scans
https://virusscan.jotti.org/en-US/fi...job/xoo5qwwi25
https://www.virustotal.com/#/file-an...UwNDMyMjU1NQ==
@Silent Don't sticky until can get more people to confirm this works. Pretty sure it'll work for everyone.
(May need to recreate thread once more information is gathered, so please post any results here!)
Edit: Apparently some trainers reference C:\Windows\SysWOW64\Macromed\Flash as well. Still looking into this.
Okay so this is what's going on for me (on my computer) Legit DragonFable Trainer is referencing the sysWOW64 folder for Flash.ocx, but even though AEDAB says it's referencing the same folder, it's actually referencing System32. I'm not sure why this is happening, but I'm going to need to get some feed back before I can figure out how to resolve this. Hopefully we can come up with a perm solution to adobe's shit software.