The *.appxbundle installer does not automatically add the installation directory for winget.exe to the PATH environment variable in Windows 10

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

Install winget from the v0.1.4331-preview release, using the *.appxbundle installer.
View the systems PATH environment variable to confirm whether the installation folder for winget was added.

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

[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.0

Any other software?

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

I just installed the appxbundle and I could not immediately run winget even 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.

aslze

winget 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 alises

It 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 winget even 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 winget by joining the "Microsoft Package Manager Insiders Program" and installing through the Windows Store.

I installed winget.exe from the Windows Store as a standard user, Dave, and winget.exe was 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.836

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.

This MUST be part of your $PATH variable:

%userprofile%\AppData\Local\Microsoft\WindowsApps

without 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?

My 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?

I 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 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

I've the same issue the last four people above me have been facing.

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\WindowsApps in 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 winget even 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 22621

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\WindowsApps in 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.

Squashed 'src/SfsClient/sfs-client/' changes from be733af9..44d81dc8

Squashed 'src/SfsClient/sfs-client/' changes from be733af9..c639a506

Squashed 'src/SfsClient/sfs-client/' changes from be733af9..0e27525d

Windows: Windows.Desktop v10.0.18362.778
Package: Microsoft.DesktopAppInstaller v1.0.41331.0

Any other software?

Windows: Windows.Desktop v10.0.18362.778
Package: Microsoft.DesktopAppInstaller v1.0.41331.0

Any other software?

v1.12.350...

%userprofile%\AppData\Local\Microsoft\WindowsApps

I just had to do this today - it this still broken!!

Navigation Menu

Repository navigation

The *.appxbundle installer does not automatically add the installation directory for winget.exe to the PATH environment variable in Windows 10 #210

Brief description of your issue

Steps to reproduce

Expected behavior

Actual behavior

Environment

37 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

The *.appxbundle installer does not automatically add the installation directory for winget.exe to the PATH environment variable in Windows 10 #210

Description

Brief description of your issue

Steps to reproduce

Expected behavior

Actual behavior

Environment

Activity

LuanVSO commented on May 19, 2020

aslze commented on May 19, 2020

jwheeler88 commented on May 19, 2020

davefollett commented on May 20, 2020

JHentges commented on May 20, 2020

M2vH commented on May 20, 2020

MisinformedDNA commented on May 20, 2020

b3n-h4il commented on May 20, 2020

MisinformedDNA commented on May 20, 2020

b3n-h4il commented on May 20, 2020

MisinformedDNA commented on May 20, 2020

Pentao commented on May 21, 2020

nirinsanity commented on May 21, 2020

37 remaining items

Sparx2 commented on Jan 18, 2022

Sparx2 commented on Jan 18, 2022

Masamune3210 commented on Jan 18, 2022

argha2000 commented on Apr 17, 2022

kaerez commented on Jul 28, 2022

botsama commented on Jun 13, 2023

storrer commented on Aug 30, 2023

aliGabre commented on Aug 16, 2025

aliGabre commented on Aug 16, 2025

andrew-allen-work commented on Dec 5, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions