Trying out the Windows Package Manager


There’s a ton of stuff I miss when I have to use Windows for something, but package managers would be among the biggest. For all the new problems they can introduce, they still make setting up systems so much easier. My Mac and *nix machines are up and running with a few commands.

Windows has had the Chocolatey package manager for years, but like my dance moves I’ve always found it clunky and brittle. Wait, what? Package managers will always give you just enough rope, but Chocolatey also supplies an unlocked Acme supercar, and a handy cliff to drive it off from. Scoop is much nicer, but I’ve also run into integration problems. Not to rag on the developers of these tools, they’re doing the best they can with the toolchains and frameworks available.

The news slipped by me last year that Microsoft released an official Windows Package Manager, so I thought I’d give it a try. I went to the Microsoft Store and downloaded the App Installer, which provides the winget binaries. Hey, it’s better than calling it Windows Console Application Installer Enterprise Corporate for Teams, SP1 RU2.

I did a search for Firefox, and installed:

Screenshot showing winget in operation. I did a search with winget search firefox, then winget install Mozilla.Firefox. The final line shows 'Starting package install...'.

Again, the syntax is just a little bit clunkier than what we have elsewhere, but already it felt like an improvement. It downloaded Firefox and ran the MSI automatically without user interaction, albeit with the mandated installer popups. It even detected and installed the correct version based on my locale.

After installing though, the prompt sat at Starting package install… for the rest of the day until I turned the VM off. The same thing happened with a few other packages, and on two separate machines. Maybe the installers aren’t handing off properly, or the package manager itself isn’t properly detecting when tasks are finished. It is a bit weird using software that the package manger claims it’s still only starting to install. The verbose IDs are also tedious to write out, and these shenanigans sour me on it.

At the end of the day, is a phrase with six words. Maybe if I were a full-time Windows Server sysadmin, I’d invest more time in it. But I can’t shake the feeling that all of these feel like a kludge on top of a system that wasn’t designed to be maintained this way, like attaching turbines and wings to a dump truck. I’ll probably stick with just installing MSIs the old fashioned way.

Author bio and support


Ruben Schade is a technical writer and infrastructure architect in Sydney, Australia who refers to himself in the third person. Hi!

The site is powered by Hugo, FreeBSD, and OpenZFS on OrionVM, everyone’s favourite bespoke cloud infrastructure provider.

If you found this post helpful or entertaining, you can shout me a coffee or send a comment. Thanks ☺️.