Repository navigation
The *.appxbundle installer does not automatically add the installation directory for winget.exe to the PATH environment variable in Windows 10 #210
Description
Activity
winget uses an "execution alias" to add itself to path. it should be in
C:\users\<username>\AppData\Local\Microsoft\WindowsApps
if it is enabled in windows settings->aplications->app execution alises
Reacted by Lemmingh, Soumya Ranjan Mahunt, Violet Giraffe, AZ9tumas, Arno Gobbin, juner, Murugappan M, Halano and lrichertReacted by SimonReacted by Mikey, Simon and Samuel AndrésI just installed the appxbundle and I could not immediately run
wingeteven spawning a new console. I thought it was not added to the PATH. I had to log out and log in for it to work.Reacted by Mikey, Violet Giraffe, Jonty1111 and pic0owinget uses an "execution alias" to add itself to path. it should be in C:\Users%userprofile%\AppData\Local\Microsoft\WindowsApps
if it is enabled in windows settings->aplications->app execution alisesIt did seem to activate it's alias correctly, but yet it still did not add to the PATH variable--however aslze mentions he needed to log out and back in for it to work.
I just installed the appxbundle and I could not immediately run
wingeteven spawning a new console. I thought it was not added to the PATH. I had to log out and log in for it to work.
I seemingly had the same or similar PATH problem. I installed
wingetby joining the "Microsoft Package Manager Insiders Program" and installing through the Windows Store.I installed
winget.exefrom the Windows Store as a standard user, Dave, andwinget.exewas installed to: "C:\Users\Dave\AppData\Local\Microsoft\WindowsApps\winget.exe".When trying to run
winget, I got an executable not found error. Looking at the PATH environment variable, I did have "C:\Users\Admin\AppData\Local\Microsoft\WindowsApp" set for the administrator account not for the Dave user or system wide. I also had the execution alias as mentioned above and logging out/in nor a reboot fixed things.In order to make it work I had to add this to my system environment variable for PATH:
%userprofile%\AppData\Local\Microsoft\WindowsApps
As shown in this screenshot:
UPDATED: Added operating system Info
Windows 10 Pro (not insiders)
Version: 1909
Build: 18363.836Reacted by Philip Colmer, pesansiviero, Helmer, Licínio Mendes, Ian Yates, Project-Magenta, Johnson Lee, Chayim Refael Friedman, Nizzal Gurung, Mikey and 26 moreReacted by LorVC, Rohit Malik, Andrei Georgescu, Ross Danby, Crong and Tahir MalikReacted by Marco M. von Hagen, Luan Vitor Simião Oliveira and Steven Kalinke- pinned this issue
on May 20, 2020 I installed via the via the *.appxbundle installer a few minutes ago and was able to open a CMD and "winget show firefox" immediately: no problem found. I am logged into Windows as an administrator, in case that's pertinent.
Reacted by Victor Alves and shtau1This MUST be part of your $PATH variable:
%userprofile%\AppData\Local\Microsoft\WindowsAppswithout the above in $PATH NONE of the Apps installed in WindowsApps can be executed from shell.
Don't know, if the above directory is part of $PATH by default?
Reacted by Mat, Irtiza Babar, vijiboy, Lyrixxx and AbdelMy path is set correctly, but the alias didn't get setup.
Is there a way to manually add it? Or something else I can try?
Well, i do have the correct PATH setup for the Windows Apps folder. But inside of it there isn't a Winget.exe file, so i get the same error with the winget command. I don't have a Windows Insider Build, used the link to use the App Installer through the Windows Store. I reseted the App Installer app in the configurations, then tried to install it again. But there in't any alias for Winget.exe nor an executable file. Any ideas?
Reacted by Humberto Jorquera, Ian Yates, Jacob, Max Perraudin, Tyler Mandry, goyzhang, Joseph Poncy, Marlene Mayr, James Ross, Alvin Thompson and 9 moreI joined the "Microsoft Package Manager Insiders Program", but it looks like I'm not getting the latest version:
Hmmm... I just noticed something. The project readme file says "Windows 10 1709 (build 16299) or later" and the email says "Windows 10, version 1809 (or later)". Which one is it?
Reacted by nirinsanity and Yisroel TechI joined the "Microsoft Package Manager Insiders Program", but it looks like I'm not getting the latest version:
Hmmm... I just noticed something. The project readme file says "Windows 10 1709 (build 16299) or later" and the email says "Windows 10, version 1809 (or later)". Which one is it?
I'm having the same issue, and i used the same installation method. I couldn't notice any change in the Installation App.
BTW: I'm on v1803. (Need to get IT to upgrade me.)
Having the same issue here,
I'm on version 1903.
The app store confirms that the product is installed.
I restarted the machine, but not App execution alias is added for winget.
Winget is not in my path:
%userprofile%\AppData\Local\Microsoft\WindowsApps
Reacted by Ian Yates, Bowen Cao, Yisroel Tech, Lynden, Chayim Refael Friedman, Yuechuan Xue, Joseph Poncy, Chris Feijoo, Toothbrush, Alvin Thompson and 5 moreReacted by Kelly Hwong, Steven Kalinke, Chenguang and Facundo I. LattandiI've the same issue the last four people above me have been facing.
Reacted by Paolo, Yisroel Tech, Caltor, Lynden, Chayim Refael Friedman, Chris Feijoo, Toothbrush, Andrew Mitchell and Alvin Thompson37 remaining items
- unpinned this issue
on Oct 1, 2021 winget uses an "execution alias" to add itself to path. it should be in C:\users<username>\AppData\Local\Microsoft\WindowsApps if it is enabled in windows settings->aplications->app execution alises
Oh, my mind ! Its a my computer and profile and I can't login .I am a bit angry
I think you are confused, a execution alias is basically a shortcut to a program, a alias is another word for nickname or alternate name. They weren't referring to you by name
After updating manually, Winget did not work. The solution that worked for me was to add an absolute address path to the enviromental variable of PATH
C:\Users\%USERPROFILE%\AppData\Local\Microsoft\WindowsAppsin addition to what was already there%USERPROFILE%\AppData\Local\Microsoft\WindowsApps, then log out and log back in to resolve issue.Following the instructions from the automated email did not work, the manual install has a better success rate overall after installing on three machines.
I was facing the same issue for the last 1 month. Following these steps worked for me
Issue still alive and well. How long does it take to fix the path? This is a store wide issue.
I just installed the appxbundle and I could not immediately run
wingeteven spawning a new console. I thought it was not added to the PATH. I had to log out and log in for it to work.Thank you for this tip. Just had an issue trying to use kubeconfirm that I installed with winget and it did not see binary when I opened a new cmd console, but logging out and back in has the path sorted now.
Adding OS for context:
OS Name: Microsoft Windows 11 Pro
OS Version: 10.0.22621 N/A Build 22621After updating manually, Winget did not work. The solution that worked for me was to add an absolute address path to the enviromental variable of PATH
C:\Users\%USERPROFILE%\AppData\Local\Microsoft\WindowsAppsin addition to what was already there%USERPROFILE%\AppData\Local\Microsoft\WindowsApps, then log out and log back in to resolve issue.
Following the instructions from the automated email did not work, the manual install has a better success rate overall after installing on three machines.I was facing the same issue for the last 1 month. Following these steps worked for me
This worked for me on Windows 11 in August 2023.
- added 3 commits that reference this issue
on Dec 6, 2024 [winget --info]
Windows Package Manager v0.1.41331 Preview
Copyright (c) Microsoft Corporation. All rights reserved.Windows: Windows.Desktop v10.0.18362.778
Package: Microsoft.DesktopAppInstaller v1.0.41331.0Any other software?
[winget --info]
Windows Package Manager v0.1.41331 Preview
Copyright (c) Microsoft Corporation. All rights reserved.Windows: Windows.Desktop v10.0.18362.778
Package: Microsoft.DesktopAppInstaller v1.0.41331.0Any other software?
v1.12.350...
%userprofile%\AppData\Local\Microsoft\WindowsApps
I just had to do this today - it this still broken!!
Brief description of your issue
When installing winget via the *.appxbundle installer, the installation directory for winget.exe is not automatically added by the installer to the PATH environment variable; this should have been added automatically so that the CLI commands can work out of the box.
Steps to reproduce
Expected behavior
The installation folder for winget is added to the system PATH environment variable.
Actual behavior
The installation folder for winget is not added to the system PATH environment variable.
Environment