Use absolute alias path to launch utilities #2911
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
May 10, 2024 14:09
jaholme
approved these changes
May 15, 2024
EricJohnson327
approved these changes
May 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary of the pull request
AppExecutionAlias can be disabled from the Settings. This would remove exe entry from %locaappdata%\Microsoft\WindowsApps folder. Entry in %locaappdata%\Microsoft\WindowsApps<package> still exists. Hence this PR switches to using that path. However, launch as admin still fails with this approach due to OS bug.
This change also wraps Process.Start in try-catch to prevent DevHome from crashing.
References and relevant issues
Detailed description of the pull request / Additional comments
Validation steps performed
PR checklist