Adds experiment to know if PATH is common issue. #1841
Conversation
Was the solution to microsoft#1840. With thanks to @ItzLevvie
doc/troubleshooting/README.md
Outdated
| @@ -95,7 +95,7 @@ These errors most commonly occur for one of following reasons. Please try out th | |||
| >`Get-AppxPackage microsoft.desktopappinstaller` | |||
|
|
|||
| 2. The App Execution Alias for the Windows Package Manager is disabled. You should enable the App Execution Alias for the Windows Package Manager. Go to `App execution aliases` option in `Apps & features Settings` to enable it. | |||
| 3. The App Installer did not automatically add the PATH environment variable. You should add the path environment variable. The value to add is "%userprofile%\AppData\Local\Microsoft\WindowsApps". | |||
| 3. The App Installer did not automatically add the PATH environment variable. You should add the path environment variable. The value to add is "%userprofile%\AppData\Local\Microsoft\WindowsApps". You can verify this by running `%LOCALAPPDATA%\Microsoft\WindowsApps\winget` from an administrator powershell. If the command runs then, but not before, then you very likely have a missing PATH environment component. | |||
There was a problem hiding this comment.
You can verify this by running
%LOCALAPPDATA%\Microsoft\WindowsApps\wingetfrom an administrator powershell.
It should be For CMD , not powershell.
For Powershell ~\AppData\Local\Microsoft\WindowsApps\winget
There was a problem hiding this comment.
My bad. I copied from the wrong window. I've given two examples. One for powershell familiar, one for command-prompt, and labelled as such.
ghost
added
the
Needs-Author-Feedback
ghost
removed
the
Needs-Author-Feedback
|
Another Note : Admin Shell is unnecessary and requiring such is problematic for MSIX packaged applications until it supports "Machine-wide install" and "Running as another users". What happens when a Standard User opens an Admin Shell via UAC only to find that winget doesn't run ?! MSIX packaged applications to this date are registered Per-User Only and doesn't support Running as another user i.e requires User Interactive Login. This is one of the major limitations of MSIX. So it's advised to remove Admin Shell requirement. |
|
Thanks for the PR! Documentation is often the unsung hero in software. |
ghost
mentioned this pull request
Was the solution to #1840. With thanks to @ItzLevvie
Apologies for my conduct on the ticket. It looks like I'd been working around this PATH entry missing with a few windows installer packages. No idea why it was not added.
Microsoft Reviewers: Open in CodeFlow