There was a news article that ASLR is not used correctly in Windows 8 and 10, and to have ASLR you have to Force ASLR for all .exe's. https://it.slashdot.org/story/17/11/17/207239/windows-8-and-later-fail-t... - Forcing ASLR breaks all portableapps apps causing them not to run with error code 7B. The apps work if I download them from their web sites and run without portableapps. It might be worth looking at and fixing considering the problem Windows 8 and 10 have, as right now you have to choose between running securely *or* using portableapps, you can't have both afaik. (I searched and saw other topics on ASLR but this seemed to warrant a separate thread.)
The problem can be easy solved by enabling ASLR in all PortableApps.com's executables.
I applied the ASLR registry hack to two Win10 laptops and it had absolutely no effect on any of my portable applications.
I can confirm this problem. I applied the registry modification (https://blogs.technet.microsoft.com/srd/2017/11/21/clarifying-the-behavi...) and all except a few portable apps (Firefox, Chrome) failed with error code 0xc000007b. The apps that work seem to have been built with a newer version of NSIS (3.x), according to their embedded manifests.
Undoing the registry patch solved the problem for me after a reboot.
John T. Haller has confirmed the problem in this thread.
So we'll have to wait until all apps have been rebuilt with PAL 3.x.
Unfortunately, this problem also hits other, non-PAF, programs as well (e.g. integrated older Java-Launchers). So I'll just have to turn off Force-ASLR for now.
FYI, workaround example:
Do the same for all exes effected.
No more crashing.
God Bless America
Hi, I posted this reply on another topic: https://portableapps.com/comment/235980#comment-235980
This way you don't have to change each application's settings.