From 95dc83724e540767b77f2e13133ee8aa3fde6613 Mon Sep 17 00:00:00 2001 From: Lewis Cowles Date: Sun, 9 Jan 2022 18:23:40 +0000 Subject: [PATCH 1/4] Adds experiment to know if PATH is common issue. Was the solution to #1840. With thanks to @ItzLevvie --- doc/troubleshooting/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/troubleshooting/README.md b/doc/troubleshooting/README.md index d8a0321b87..86995f38e9 100644 --- a/doc/troubleshooting/README.md +++ b/doc/troubleshooting/README.md @@ -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. 4. Apps deployed on the machine are registered per user by default. If App Installer was installed on a different user account than the one you are trying to run it on, you will have to reinstall it again on this account and try again. If the above guidelines do not resolve the problem, please open an issue with details of the Windows version and App Installer version you are using. From 2e79b972671aa1f3663504a38ba3124b0737b459 Mon Sep 17 00:00:00 2001 From: Lewis Cowles Date: Mon, 10 Jan 2022 00:38:06 +0000 Subject: [PATCH 2/4] Update command. --- doc/troubleshooting/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/troubleshooting/README.md b/doc/troubleshooting/README.md index 86995f38e9..b1fc61454f 100644 --- a/doc/troubleshooting/README.md +++ b/doc/troubleshooting/README.md @@ -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". 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. +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 command-prompt or `& "$env:LOCALAPPDATA\Microsoft\WindowsApps\winget.exe"` from an administrator powershell. If the command runs then, but not before, then you very likely have a missing PATH environment component. 4. Apps deployed on the machine are registered per user by default. If App Installer was installed on a different user account than the one you are trying to run it on, you will have to reinstall it again on this account and try again. If the above guidelines do not resolve the problem, please open an issue with details of the Windows version and App Installer version you are using. From d6826d910f655c81db4150bda0f3e12d59395574 Mon Sep 17 00:00:00 2001 From: Lewis Cowles Date: Mon, 10 Jan 2022 00:39:58 +0000 Subject: [PATCH 3/4] Remove extension that is not needed --- doc/troubleshooting/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/troubleshooting/README.md b/doc/troubleshooting/README.md index b1fc61454f..f3168881bb 100644 --- a/doc/troubleshooting/README.md +++ b/doc/troubleshooting/README.md @@ -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". You can verify this by running `%LOCALAPPDATA%\Microsoft\WindowsApps\winget` from an administrator command-prompt or `& "$env:LOCALAPPDATA\Microsoft\WindowsApps\winget.exe"` from an administrator powershell. If the command runs then, but not before, then you very likely have a missing PATH environment component. +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 command-prompt or `& "$env: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. 4. Apps deployed on the machine are registered per user by default. If App Installer was installed on a different user account than the one you are trying to run it on, you will have to reinstall it again on this account and try again. If the above guidelines do not resolve the problem, please open an issue with details of the Windows version and App Installer version you are using. From 9ead387d1a19afb6b81f0477085021462c183241 Mon Sep 17 00:00:00 2001 From: Lewis Cowles Date: Mon, 10 Jan 2022 22:25:07 +0000 Subject: [PATCH 4/4] Remove administrator from instructions --- doc/troubleshooting/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/troubleshooting/README.md b/doc/troubleshooting/README.md index f3168881bb..b4d1efefeb 100644 --- a/doc/troubleshooting/README.md +++ b/doc/troubleshooting/README.md @@ -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". You can verify this by running `%LOCALAPPDATA%\Microsoft\WindowsApps\winget` from an administrator command-prompt or `& "$env: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. +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 a command-prompt or `& "$env:LOCALAPPDATA\Microsoft\WindowsApps\winget"` from a powershell. If the command runs then, but not before, then you very likely have a missing PATH environment component. 4. Apps deployed on the machine are registered per user by default. If App Installer was installed on a different user account than the one you are trying to run it on, you will have to reinstall it again on this account and try again. If the above guidelines do not resolve the problem, please open an issue with details of the Windows version and App Installer version you are using.