Windows symlinks require admin

[GeopJr]

trafficstars

On a previous issue, Windows caused problems with symlinks. In fact it refused to even untar due to them. As a workaround, generateSymlinks.js was made, which, as the name implies, generates the required symlinks. Unfortunately, Windows also has an issue with that as they can only be made with admin privileges.

Currently, the script stops and asks the user to re-run it with from an admin terminal, An attempt to spawn an admin terminal was made (using runas /user:Administrator) however it appears that if you don't have an admin password, you cannot proceed.

To fix this issue an alternative is required to at least run it as admin without forcing the user to do it themselves.

[ambarvm]

Symlinks work without admin permission if developer mode is turned on (Windows blog post) Though you need admin permission to turn it on once. I guess it would be helpful to suggest the user to turn on developer mode.

[GeopJr]

Thanks for the insight! I'll make sure to suggest it when displaying the error (should probably also add WSL too)!