Search Issue Tracker
Fixed in 2021.1.X
Votes
1
Found in
2017.2.1f1
Issue ID
979524
Regression
No
[Windows 10] Unity installer terminates when launching with ASLR enabled in the registry
Steps to reproduce:
1. Add attached ASLR.reg to your registry
2. Restart computer
3. Try to launch any version of the Unity installer
Expected result: Unity proceeds with the installation after clicking yes on the "Do you want to allow this app to make changes to this computer?" prompt
Actual result: the installer for Unity terminates
-
BlackGateDev
Sep 17, 2019 17:04
This issue still persists and it appears to be related to the version of NSIS used in the installer. Newer versions of NSIS (3.x) are reported to have the issue fixed. I would highly recommend support forum admins to take note of the issue so they can help people accordingly.
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Audio Mixer does not change volume when lowering volume on an Audio Mixer loaded from AssetBundles
- Error “Value cannot be null. Parameter name: key UnityEngine.GUIUtility:ProcessEvent (int,intptr,bool&)” thrown and Addressables build fails when "Include in Build" is disabled and using Addressables For Android package
- “error CS0433: The type 'CodeBinaryOperatorType' exists in both 'System.CodeDom and 'System" compilation errors are thrown when opening a specific project
- Metal Vertex Shader warning is being thrown when creating a VR Template Project
- Asset database warning is thrown when declaring font variable in the USS text file
Resolution Note (fix version 2021.1):
This is resolved in the latest 2020.2+ builds. We currently don't plan to backport to 2019.4 because the code to support this is a significant technology change.