What about non-admin (standard user) ?

[rwasef1830]

Hello,
The script works well for admin user, but it fails with non-admin user. It writes some errors and creates the context items but they are non-functional. Running the script as admin, installs the context menu items but for admin only.

Could you make it work for non-admin user as well ?
@lextm

[lextm]

It is intentional to require administrator permissions, as one of the Windows Terminal folder is locked down.

[rwasef1830]

Hello,
Can you explain a little bit ? Running Windows terminal doesn't need admin permission! I can run it fine under normal user... why can't the context menu open it as normal user if it is installed by current user from windows store ?

[lextm]

The function GetProgramFilesFolder accesses the WindowsApps folder,

https://github.com/lextm/windowsterminal-shell/blob/master/install.ps1#L150

That folder can only be read by administrators.

It is possible to modify the install script to skip that folder, but a lot of features won't work then, so I don't plan to work on this.

Pull requests are welcome.

[ghost]

Related to this question - if I have a main non-admin account (my.name) and a local admin account (my.name2), can I use my admin priveleges to add the context menu for the non-admin user?

[lextm]

@p2r2 that requires a very complex mechanism, splitting the install steps to two parts (script files) so that they can be run under two accounts.

While I fully understand that many enterprise users are forced to use two such accounts, it is rather complicated to rewrite the script to achieve that level of control.

Pull requests are welcome though, in case anyone wants to contribute.

[peter1rhodes]

#50 I have opened a PR for this issue