You are here

Home » Forums » Support Forums » PortableApps.com Platform

Force ASLR breaks portableapps

7 posts / 0 new
Log in or register to post comments
Last post
November 19, 2017 - 12:51am
#1
JamesG76
Offline
Last seen: 5 years 4 months ago
Joined: 2017-11-19 00:40
Force ASLR breaks portableapps

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.)

Top
November 23, 2017 - 11:45am
Holman
Offline
Last seen: 3 years 8 months ago
Joined: 2017-11-23 06:22
The problem can be easy

The problem can be easy solved by enabling ASLR in all PortableApps.com's executables.

Top
November 23, 2017 - 2:08pm
(Reply to #2)
pbr
Offline
Last seen: 2 months 6 days ago
Joined: 2009-06-21 09:23
I applied the ASLR registry

I applied the ASLR registry hack to two Win10 laptops and it had absolutely no effect on any of my portable applications.

Top
November 23, 2017 - 4:27pm
Herrminator
Offline
Last seen: 1 year 6 months ago
Joined: 2011-04-04 11:23
Confirm!

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.

Top
November 24, 2017 - 3:43am
Herrminator
Offline
Last seen: 1 year 6 months ago
Joined: 2011-04-04 11:23
Confirmed.

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.

Top
December 2, 2017 - 8:54pm
war59312
Offline
Last seen: 1 month 1 week ago
Joined: 2007-08-18 17:10
FYI, workaround example:

FYI, workaround example:

  1. Search in Windows for: "windows defender Security Center"
  2. Click on the second icon from the bottom: "App & browser control"
  3. Scroll to the bottom and click on: "Exploit protection settings"
  4. Click Program settings and then the "Add program to customize" button
  5. Click Choose exact file path
  6. Pick ExampleApp.exe - Pick the app crashing
  7. Scroll down to: Force randomization for images (mandatory ASLR)
  8. Check: "Override system settings" and se t to "Off" and click Apply

Do the same for all exes effected.

No more crashing. Smile

Enjoy,

Will

God Bless America

Top
March 24, 2018 - 9:46am
(Reply to #6)
gvlx
Offline
Last seen: 8 months 3 weeks ago
Joined: 2014-04-15 07:47
scripted solution

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. Wink

While most apps are not recompiled to NSIS 3, running this command on a elevated PowerShell windows will allow you to run most applications:

ForEach ($filename in (Get-ChildItem -Filter "Portable.exe" C:\PortableApps\*\*).FullName) { Set-ProcessMitigation -Disable ForceRelocateImages -Name $filename }
Top
Log in or register to post comments