You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
The text was updated successfully, but these errors were encountered:
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 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 theirglobal_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
The text was updated successfully, but these errors were encountered: