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

App execution aliases in %LOCALAPPDATA%\Microsoft\WindowsApps don't launch through interop #4969

Closed
DHowett-MSFT opened this issue Mar 13, 2020 · 4 comments

Comments

@DHowett-MSFT
Copy link

DHowett-MSFT commented Mar 13, 2020

This is particularly problematic with Windows Terminal's wt.exe alias -- launching it yields no response and no new terminal. This happens on Vibranium w/ WSL1 or WSL2.

This applies even to console app execution aliases like python.exe and DesktopAppConverter.exe.

@benhillis
Copy link
Member

/fixed 20190.

@ghost ghost closed this as completed Aug 12, 2020
@ghost ghost added the fixedininsiderbuilds label Aug 12, 2020
@ghost
Copy link

ghost commented Aug 12, 2020

This bug or feature request originally submitted has been addressed in whole or in part. Related or ongoing bug or feature gaps should be opened as a new issue submission if one does not already exist.

Thank you!

@korpa
Copy link

korpa commented Sep 9, 2020

@benhillis When will this be fixed in Win10 2004?

@zachsiegel-capsida
Copy link

This does not seem to be fixed in Windows 10 21H2, 19044 (I have 19044.1526). Am I missing something?

This issue was closed.
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

4 participants