Open agowa opened 10 months ago
This is a problem on windows in general, Microsoft sucks ass
@Ast3risk-ops true, but as Atlas already fixes a lot of other annoyances it kinda would be nice if it was added to the playbook.
Might be difficult to do, but a good suggestion.
Might be difficult to do, but a good suggestion.
Just for curiosity, do you guys plan to add it to next release?
Not currently, I can't find an official way to programmatically manage app execution aliases.
They are managed within: $env:LOCALAPPDATA\Microsoft\WindowsApps
, HKCU:\Software\Microsoft\Windows\CurrentVersion\App Paths
, and HKLM:\Software\Microsoft\Windows\CurrentVersion\App Paths
Also see https://learn.microsoft.com/en-us/windows/win32/shell/app-registration#using-the-app-paths-subkey
I'd call this the official way as that documentation states:
To register and control the behavior of your applications with the App Paths subkey:
App Execution Aliases don't seem to be managed in those keys. Deleting the file from WindowsApps works but it's a hacky solution that I'd rather not implement, especially as it doesn't update the toggle in Windows Settings.
What is your feature request regarding to?
Atlas Playbook
Is your feature request related to a problem? Please describe.
The App Installer has two annoying app execution aliases registered. Namely "python.exe" and "python3.exe", could you just disable them within the Atlas playbook? They do not execute python and can cause the windows store to open, even though python got installed. Also they're unnecessary and bloated.
Describe the solution you would like.
Set the App execution alias of "App Installer" to "Off". This setting can be found within "App > Advanced app settings > App execution aliases" of the settings app.
Describe alternatives you have considered.
does not apply
Additional context.
No response