Allow user-context installation on Windows (no admin rights required)

[SableRaf]

Since Processing 4.4, the Windows release uses an .msi installer, which installs in the system context by default.

This means people without admin access on their machine cannot install Processing. As reported by this Reddit user

We should provide an option to install in user context, so that admin rights are not needed.

This would make installation easier for students, schools, and others using restricted machines.

Reference

https://stackoverflow.com/questions/14339372/wix-non-admin-installer-tutorial

[Stefterv]

Looks like installing to Program Files is what causes the escalation to Admin, maybe we can install Processing in a different location?

[SableRaf]

Oops, I shared the wrong reference link I meant to post this https://www.advancedinstaller.com/per-user-per-machine-msi-installation.html

It says:

Compared to per-machine installations, a per-user application gets installed in a user profile location, usually in AppData\Local or AppData\Roaming.

[Stefterv]

No, I edited it because we don't use advanced installer

[SableRaf]

I see! I read that page a little too quickly and missed that it wasn't about regular .msi installers.

maybe we can install Processing in a different location?

Is there a way we can leave it to the user to choose between a simple installation and an administrative installation? Is this page relevant?

If technically possible, then maybe the options could be labeled like this to keep it clear:

• Simple install (recommended for most users)

• Admin install (for administrators and shared machines)

[jdebou]

Hello, I have looked into this today. here are my findings.

The first thing is that we can configure the Wix package to allow both per-user and per-machine installation with the Scope property.

Then we can then set a ALLUSERS variable to conditionnaly choose between the different installation paths.

I have built an installer that can do both installations, with the variable set from the command line when running msiexec.

Adding the dialog to pick between the two options is a little trickier. We are using WixUI_Mondo for the ui sequence, which does not support picking between different scopes. From there, it appears we can either :

• rewrite that sequence, adding a custom dialog into the sequence;
  or
• swap WixUI_Mondo for WixUI_Advanced, which defines a built-in InstallScopeDlg.

My feeling is that going for the advanced installer would be preferable, since it is the built-in solution offered by Wix, but I could be wrong since I don't know the reasons WixUI_Mondo was picked in the first place.

I could start working on a PR, and would like some feedbacks on those solutions.

Cheers