Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Handling installation of UIAccess applications #5809

Open
lars-berger opened this issue Feb 21, 2024 · 0 comments
Open

[Feature] Handling installation of UIAccess applications #5809

lars-berger opened this issue Feb 21, 2024 · 0 comments

Comments

@lars-berger
Copy link

Feature Request

Is your feature request related to a problem? Please describe.

Assistive and accessibility software often need higher than usual permissions, which can be granted by enabling uiAccess="true" in their app manifest and installing the executable to a secure location.

From the article Only elevate UIAccess applications that are installed in secure locations:

This policy setting enforces the requirement that apps that request running with a UIAccess integrity level by marking UIAccess=true in their app manifest must reside in a secure location on the file system. Relatively secure locations are limited to the following directories:

  • \Program Files\ including subdirectories
  • \Windows\system32\
  • \Program Files (x86)\ including subdirectories for 64-bit versions of Windows

This is a pain if a user wants to use Scoop for installs. The workaround is to ask users to create a new directory within \Program Files\, and edit their global_path in the scoop config to point to this new directory.

Describe the solution you'd like

A user-friendly way to install to somewhere within \Program Files\. Perhaps a CLI flag?

Is there a particular reason why \ProgramData\Scoop was chosen as the global directory? Otherwise it could make sense to change the default global install location to eg. \Program Files\Scoop\Apps - since \Program Files\ is a more conventional install location as well as handling applications that require installation to this directory.

Describe alternatives you've considered

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant