Windows Package Manager Preview

Demitrius Nelon

We are thrilled to announce the Windows Package Manager preview!

If you’re already familiar with what a package manager is, feel free to skip this paragraph. If you’re still reading, you’re going to love this! A package manager is designed to help you save time and frustration. Essentially, it is a set of software tools that help you automate the process of getting software on your machine. You specify which apps you want installed, and it does the work of finding the latest version (or the exact one you specified) and installing it on your machine.

Just about every developer has wanted a native package manager in Windows. That day is finally here. You are going to be able to winget install your way to bliss. One of the best parts is that it is open source. I had to pinch myself when I was able to winget install terminal, and then winget install powershell, and then winget install powertoys. You get the idea, and If you do not see an app you use, just create a new manifest, and submit a pull request.

Execute winget in Windows Terminal

When can I try it?

As of today, the Windows Package Manager preview has been made open source. You can clone, build, run and test the code from the GitHub repository ( There are other possibly easier ways to get your hands on it if that doesn’t sound appealing. Please continue reading.

What functionality is included?

You can install any app with a valid manifest (even local ones -- manifest). The command line client “winget.exe” is already pre-configured to point to the Microsoft community repository. That means you can install any package with a manifest that has been published.

Have you ever had to completely re-install all your apps and tools on your PC? How long did it take? How did you remember where to go to find, download, and install all your editors & IDEs, languages & runtimes, source control tools, etc.?


Did you enjoy it? Yeah, neither did we … which is why we created Windows Package Manager.


Now you can install all your favorite apps & tools simply by typing winget install <foo> into your command-line. Or better still, you can create a script file that installs ALL your tools while you sit back enjoy a well-earned coffee break!”

You can search for available packages and display information using the show command. There are also commands to help with manifest creation and validation (hash and validate). Once the first third-party repository is published, you will be able to add that repository as a source as well. We’re providing documentation at and both of the GitHub repositories.

Executing the winget install vscode command in Windows Terminal

How do I get it?

We have provided three different ways for you to get your hands on the Windows Package Manager. If you are a Windows Insider, you may already have it. First, you can head over to the open source GitHub repository for the client. Second, you can join any of the Windows Insider rings. Third, you can join the Windows Package Manager Insider program by providing your Microsoft Account (MSA) to Windows Package Manager Insider Program and request to be included in the preview. Either of the Insider programs will ensure you automatically receive updates as we progress from preview to general availability. After you have joined either Insider program, head over to the Microsoft Store and get the App Installer. The Windows Package manager will be available after you get the update.

The App Installer in the Microsoft Store

Why not contribute to another open source package manager?

We looked at several other package managers. There were several reasons leading us to create a new solution. One critical concern we had was how to build a repository of trusted applications. We are automatically checking each manifest. We leverage SmartScreen, static analysis, SHA256 hash validation and a few other processes to reduce the likelihood of malicious software making its way into the repository and onto your machine. Another key challenge was all the changes required to be able to deliver the client program as a native Windows application.

Which versions of Windows will be supported?

Windows Package Manager will support every Windows 10 version since the Fall Creators Update (1709)! The Windows Package Manager will be delivered with the Desktop App Installer when we ship version 1.0. If you are building software to run on Windows 10 you will have a simple way for your customers to install your software on billions of machines.

But what about…

We are expecting you have plenty of questions. What does this mean for the Windows store? It doesn’t mean anything for the Windows store. The Windows Package Manager is a command line interface, no marketing, no images, no commerce. Although we do plan on making those apps installable too.

What about insert any other package manager here? We think they are great. If they want to leverage our repository of validated packages, they can. If they want to see how we are doing it, it is open source. We’re open to feedback and suggestions.

We have already talked with a few of the well-known package manager teams. Chocolatey has a vibrant community with a massive collection of applications, and a rich history supporting both open source and enterprise customers. Scoop provides a convenient way to allow software to be installed without the UAC popups. Ninite keeps an eye on updates for all the apps it installed. There are many others like AppGet, Npackd and the PowerShell based OneGet package manager-manager.

If you are happy with your current package manager, keep using it. Our goal is to make installing software on Windows better for everyone.

What’s next?

We have a long list of features we think you will like. Take a look at the list of issues we have already created on GitHub. Be sure to +1 any issues you feel strongly about. If you do not see something, and you would like us to consider it, just create a new issue.


Discussion is closed. Login to edit/delete existing comments.

  • Yash Moon 0

    Please include “scrcpy” package.

  • Dusty Bronk 0

    This is great news. Please consider dropping the ‘get’ and just use ‘win’ install. It sounds better and is shorter.

    • Pilachii. com 0

      Men likewise happen to be wired more for unpredictable multiplication and thus, moment delight. With the appearance of the web and its cornucopia of droil , men have discovered the most advantageous path in mankind’s history to fulfill their outwardly animated requirement for discharge.

  • Sergey Kostrukov 0

    scoop package manager has been for a while and is great in all aspects.
    It’s well designed, mature and has big community.

  • Sebastian N. 0

    Can you elaborate on why you chose C++ as programming language for winget? Wouldn’t C#, Rust (for security) or Golang (for performance) be better choices?

    • Daniel Steck 0

      I’m really glad they didn’t use something like C# (although I wouldn’t have minded Rust). Using C# leads to issues like powershell which is embarrassingly slow for a shell.

      System utilities like this should be snappy and performant, and a package manager — while nontrivial — is a relatively manageable piece of software where C++ shouldn’t incur any drawbacks.

  • Mindaugas Jasiulis 0

    I hope that support for Windows store apps is not that far on the horizon, it’s quite a big pain point to reinstall stuff while navigating through the store on new machines, so far I am enjoying what you guys delivered.

  • Dimitri Luinetti 0

    Great idea !
    What about Windows Server ? No plans ?

    • Justin King 0

      Just use Choco.

      It already has dependencies, uninstall, can support private repos, works natively with CM tools like Chef/Puppet/Ansible, and basically all the basics you’d expect out of a package manager.

      I’m honestly struggling to see why they just didn’t announce chocolatey getting bundled into the OS with a formal MS repo.

  • Fawad Raza 0

    After 25 years, finally windows reached where *Nix was in 1995. lol 😂😂

    They are killing Choco now? That will be interesting, since everything might move there, still in preview but guess this is the future.

  • Phillip Patton 0


  • Anas Soulhat 0

    At the moment, there are no benefits for me to use this package manager. I’ll stay on Chocolatey for now.
    Why contribute to a new package manager when there are existing ones ?

  • William White 0

    I absolutely don’t get this. No support for server os? Why are you calling this “package manager” instead of app installer? Package manager implies you can use it in a variety of ways and point to other sources – the way that we are using choco with our artifactory instance. Can choco install apps? Sure. Can it install scripts, binaries, etc your app needs? Sure. Can this? Doesn’t seem like it, seems like it’s just an app installer. Why not acquire chocolatey? They’d benefit from pairing with nuget team. The community would benefit.

    • Joshua Scott 0

      That would be a great move for Microsoft, but how would the Chocolatey community react to an acquisition from Microsoft?

      • Justin King 0

        congratulate the choco team for the influx of money? Not sure why the community would be mad.

Feedback usabilla icon