winget-cli: winget is not pre-installed on Windows App Installer.

The client is distributed within the App Installer package. While this package is pre-installed on Windows, the client will not be made generally available during the Preview period.

Hmm… No… I just downloaded Windows Terminal through Microsoft Store but it cannot run ‘winget’ command. It says

+ CategoryInfo          : ObjectNotFound: (winget:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

What should I do?

About this issue

  • Original URL
  • State: closed
  • Created 4 years ago
  • Comments: 24 (15 by maintainers)

Most upvoted comments

Why is the App Store the encouraged installation method in the documentation if you can just install it without running a special OS build or seeking access to a special program by just installing it from the releases page here on GitHub? Until it becomes a mainstream thing in the App Store, it’s the least practical way for someone to use it.

At very least, the documentation currently has a link to the App Store before the link to the prerequisite steps. If you have to do those things first, it would be more obvious if the documentation started by talking about how to do the prerequisite steps before giving a link to the app store.

Sorry but I signed up for the preview flight ring using the MSA I login as, over a week ago, and I’m still not getting winget via app store on two different PCs

@Karl-WE Keep sending the feedback reports. Sometimes these things are tricky to diagnose and fix, but we want the best experience possible. I hope most of these challenges go away when we ship App Installer including the Windows Package Manager as the default. I’m counting the days.

The “Windows Package Manager Insider” sign up form results in a request. We have to manually add your e-mail address to the flight group. That happens in batches. We generally try to get this done daily, but sometimes we may miss a day or two. After your address has truly been added to the flight group, the “App Installer” with the Windows Package Manager becomes available as an update from the Microsoft Store.

I think this should be included in readme or the email? It is very confusing, since it is not stated anywhere in the guide, or the email about the this delayed time. I think everybody must think it’s automatically.

Good luck Den. The user ratings for App Installer on the Store are not representative 😃 I will try to catch it and open a new issue if I can repro it.

@Karl-WE thanks for the clarity here. Do you know if the experience is different based on the version of Windows? I’d like to be able to reproduce this so I can determine if there is a process to resolve this consistently. It may be an issue with the Microsoft Store, Windows 10 version, or the App Installer version.

@denelon thank you for the quick change. I think it’s much clearer now for new users.

@vietvudanh, I’ll take a look and see if I can find a good place to put a small note 👍

@Karl-WE thanks for pointing this out. I’ll see if I can get in touch with the right team to figure out what is causing this behavior.

@denelon I am seeing the following behaviour with the store based App Installer and suspect this is not intended.

App Installer is installed on a system, listed in Settings > Apps Searching for App Installer on the Store, it shows up as if it is not installed.

Basically a user could install it from store over and over again. Affects all release builds of Windows 10, aka 20H2.

image

Same here. Default microsoft account. Signed up for the preview but nothing happending. Btw. - why isn’t winget used to update winget?