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] - Remove dummy aliases for Python #1020

Open
agowa opened this issue Jan 18, 2024 · 7 comments
Open

[FEATURE] - Remove dummy aliases for Python #1020

agowa opened this issue Jan 18, 2024 · 7 comments
Labels
enhancement New feature or request help wanted Extra attention is needed low priority Small problems that does not require a fix immediately workaround avaliable Where a temporary workaround/fix is available for an issue

Comments

@agowa
Copy link

agowa commented Jan 18, 2024

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

@agowa agowa added the enhancement New feature or request label Jan 18, 2024
@Ast3risk-ops
Copy link

This is a problem on windows in general, Microsoft sucks ass

@agowa
Copy link
Author

agowa commented Jan 18, 2024

@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.

@he3als
Copy link
Contributor

he3als commented Jan 18, 2024

Might be difficult to do, but a good suggestion.

@he3als he3als added the low priority Small problems that does not require a fix immediately label Jan 18, 2024
@CodingMadness
Copy link

Might be difficult to do, but a good suggestion.

Just for curiosity, do you guys plan to add it to next release?

@he3als
Copy link
Contributor

he3als commented Mar 10, 2024

Not currently, I can't find an official way to programmatically manage app execution aliases.

@agowa
Copy link
Author

agowa commented Mar 14, 2024

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:

@he3als
Copy link
Contributor

he3als commented Mar 15, 2024

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.

@he3als he3als changed the title [FEATURE] - remove app execution aliases of App Installer [FEATURE] - Remove dummy aliases for Python May 27, 2024
@he3als he3als added the help wanted Extra attention is needed label May 27, 2024
@he3als he3als added the workaround avaliable Where a temporary workaround/fix is available for an issue label Jun 12, 2024
@he3als he3als moved this to Fixed for next release in Atlas Playbook Jul 4, 2024
@he3als he3als moved this from Fixed for next release to Low priority in Atlas Playbook Jul 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed low priority Small problems that does not require a fix immediately workaround avaliable Where a temporary workaround/fix is available for an issue
Projects
Status: Fixed for next release
Development

No branches or pull requests

4 participants