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
Comments (1)
-
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
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.