What you need to know
- Windows Package Manager is a command line tool you can use to install and upgrade apps from sources all over the web as well as the Microsoft Store.
- The latest addition to its arsenal is the ability to upgrade itself, removing the need to leave the command line to do it.
- This feature will only apply to stable versions for the time being until Windows Package Manager has support for channels.
My favorite tool on Windows 11 is the Windows Package Manager. I've written before about Windows Package Manager is so good I won't use anything else, but it continues to get better all the time.
The latest goodness, as communicated by Microsoft's Demitrius Nelon, is that the Windows Package Manager can now upgrade itself.
✅ winget upgrade wingetWinGet can now upgrade itself. Only stable versions will be published this way until we have support for channels.December 5, 2023
The addition of this feature also means that the winget upgrade --all command will now incorporate Windows Package Manager if there is a new version of the App Installer available.
Only stable versions will be published this way for the time being, since there's currently no support for channels. But that said, reading between the lines, it would seem that support for channels is something planned for the tool.
The best Windows 11 tool you should be using
The number one reason I recommend the Windows Package Manager to anyone who will listen is speed. It's so fast. Fast to find your apps, fast to install them, you can set it going and mostly leave it alone.
Sure, the Microsoft Store can do that to some degree, but if you install as much software from outside the Store as I do, Windows Package Manager is the way to do it. This quote from my previous piece linked above demonstrates how it's fit into my workflow.
The terminal doesn't have to be scary, and Windows Package Manager is actually very simple when you learn the basic commands. There's a built-in help option to guide you, but trust me when I say it doesn't take long to get the hang of.
The beauty is that because Windows Package Manager doesn't actually host the packages itself, as you would find on a Linux package manager, you're essentially just downloading your apps from source. So instead of going to a website, downloading a .exe file, opening it, running through the installer, you can tell Windows Package Manager to do it for you. The same applies to upgrading all those apps, you can do them all at once with a single command, wherever they came from.
And now you don't even need to manually update the Package Manager tool itself, it's getting closer and closer to being perfect. Hit the GitHub repo to get yourself rolling for the first time and give it a try!
Get the Windows Central Newsletter
All the latest news, reviews, and guides for Windows and Xbox diehards.
Richard Devine is a Managing Editor at Windows Central with over a decade of experience. A former Project Manager and long-term tech addict, he joined Mobile Nations in 2011 and has been found on Android Central and iMore as well as Windows Central. Currently, you'll find him steering the site's coverage of all manner of PC hardware and reviews. Find him on Mastodon at mstdn.social/@richdevine
Woow... Inovation much cool and such original!Reply
Oh, wait! Linux package managers were doing this for ages...
Ctrl+F "innovative" - "innovate" - "original"Reply
No results :D
The so-called "package manager" in Winodws 11 is nothing but a wrapper around existing installers. This makes it difficult to use with certain programs, especially on machines with more than one user.Reply
Another great example of Microsoft copying a feature that Linux or macOS had first and doing a P155 Poor job.
The underlying problem seems to be that since Microsoft doesn't (and likely won't) force software companies to use the MSIX format. So long as winget is just a wrapper around EXE and MSI installers, it will be just another poor imitation of a package manager. Better than nothing, but alternatives do exist.
"The underlying problem seems to be that since Microsoft doesn't (and likely won't) force software companies to use the MSIX format."Reply
But that's because Microsoft is in no position to force developers/software companies to do anything these days. There are way too many alternatives to Windows now.
2005 was a long time ago. Developers no longer follow Microsoft. Microsoft now follows developers.