Package Managers for Windows? Yes!

Windows used to be the land of .exe installers, random download buttons, browser toolbars, mystery update services, and “next-next-finish” wizard hell.

To be fair, a lot of that still exists.

But modern Windows is not as bad as it used to be. Today you can install and update a serious amount of software from the command line. You can also script new machine setup, keep developer tools updated, install libraries, and manage apps without opening twenty vendor websites.

The annoying part is that Windows does not have one clean equivalent of apt, dnf, pacman, or Homebrew.

Instead, Windows has several package managers, and they solve different problems.

Some are for normal desktop apps. Some are for developer tools. Some are for Python or C++ environments. Some are not really package managers, but they are useful enough that people use them like package managers.

So this article is not about finding one magical winner. It is about knowing which one to use and when.

Quick Answer

If you just want one package manager for a normal Windows 10/11 machine, use WinGet.

If you want the cleanest command-line tool setup, use Scoop.

If you manage Windows machines professionally, learn Chocolatey and WinGet.

If you hate terminals, install UniGetUI.

If you are doing C/C++ work, use vcpkg.

If you are doing Python/data/ML work, use Mamba or Conda.

---

1. WinGet

Official site/docs: https://learn.microsoft.com/en-us/windows/package-manager/winget/

WinGet is Microsoft’s official Windows Package Manager command-line tool.

It lets you search, install, upgrade, remove, and configure apps from the terminal.

Example:

winget search firefox
winget install Mozilla.Firefox
winget install Microsoft.VisualStudioCode
winget upgrade --all
winget uninstall Mozilla.Firefox

For a modern Windows 10 or Windows 11 machine, this is the default recommendation.

It is built around real Windows desktop apps, not only developer tools. Browsers, editors, utilities, communication apps, media tools, VPNs, terminals, and lots of everyday software are available.

Why it is still active

WinGet is actively maintained by Microsoft and is now part of the modern Windows software management story. It is not some abandoned side project from 2012.

Pros

Cons

Best for

Use WinGet for general Windows software:

winget install 7zip.7zip
winget install Git.Git
winget install Microsoft.PowerToys
winget install VideoLAN.VLC
winget install Google.Chrome
winget upgrade --all

This is probably the closest Windows has to a normal built-in package manager.

---

2. Chocolatey

Official site: https://chocolatey.org/

Chocolatey is one of the oldest serious Windows package managers that people still actually use.

Before WinGet became useful, Chocolatey was the answer if you wanted something like apt-get for Windows.

Example:

choco install git
choco install googlechrome
choco install vscode
choco upgrade all

Chocolatey is especially popular with sysadmins, automation scripts, internal package repositories, and business environments.

Why it is still active

Chocolatey still has an active package ecosystem, current documentation, business products, and a large community package repository.

Pros

Cons

Best for

Use Chocolatey if you are:

• managing many Windows machines
• scripting lab setup
• building Windows VM images
• working with old internal workflows
• maintaining older automation scripts that already use Chocolatey

For personal use, I would usually start with WinGet now. But Chocolatey is absolutely not dead.

---

3. Scoop

Official site: https://scoop.sh/

Scoop is a command-line installer for Windows, but it has a different vibe than WinGet and Chocolatey.

It is less about big GUI apps and more about developer tools, portable apps, command-line utilities, and a cleaner user-space install experience.

Example:

scoop install git
scoop install curl
scoop install nodejs
scoop install python
scoop install ffmpeg

Scoop usually installs into your user directory, which means fewer UAC prompts and less system pollution.

Why it is still active

Scoop is actively maintained on GitHub, still has current releases, and still has an active bucket ecosystem.

Pros

Cons

Best for

Use Scoop when you want a clean Windows dev machine:

scoop install git
scoop install nodejs-lts
scoop install python
scoop install ripgrep
scoop install fd
scoop install ffmpeg

For command-line tools, Scoop often feels better than WinGet.

---

4. Ninite

Official site: https://ninite.com/

Ninite is not a traditional package manager, but it deserves to be here because it solves a real Windows problem: installing common apps quickly without babysitting installers.

You go to the website, pick apps, download one installer, run it, and Ninite installs everything in the background.

It can also update apps by running the same installer again.

Why it is still active

Ninite is still available and still focused on silent install/update workflows for common Windows applications. Ninite Pro is also still offered for managed environments.

Pros

Cons

Best for

Use Ninite when you need to set up a basic Windows machine fast:

• Chrome or Firefox
• 7-Zip
• VLC
• Zoom
• Discord
• Steam
• Notepad++
• LibreOffice
• Dropbox

For a family laptop or a fresh Windows install, Ninite is still very useful.

---

5. UniGetUI

Official site: https://www.marticliment.com/unigetui/

UniGetUI is not exactly a package manager by itself.

It is a graphical frontend for multiple package managers.

It can work with tools like:

• WinGet
• Chocolatey
• Scoop
• pip
• npm
• .NET Tool
• PowerShell Gallery
• and others

So instead of remembering different terminal commands, you get one UI for discovering, installing, updating, and uninstalling packages.

Why it is still active

UniGetUI is actively maintained, has a current GitHub project, and is widely used as a GUI layer over the Windows package manager mess.

Pros

Cons

Best for

Use UniGetUI if you like the idea of package managers but do not want to manage everything manually from the terminal.

It is also useful on a personal machine where you might have WinGet, Scoop, and Chocolatey installed at the same time.

---

6. MSYS2 / pacman

Official site: https://www.msys2.org/

MSYS2 gives Windows a Unix-like development environment and uses a port of Arch Linux’s pacman package manager.

This is not the same thing as installing normal Windows desktop apps.

MSYS2 is for build tools, compilers, shells, Unix-style utilities, and native Windows development environments.

Example:

pacman -Syu
pacman -S mingw-w64-ucrt-x86_64-gcc
pacman -S mingw-w64-ucrt-x86_64-cmake
pacman -S git

Why it is still active

MSYS2 is still maintained, still updates its package repositories, and still tracks modern Windows support changes.

Pros

Cons

Best for

Use MSYS2 if you build native Windows software, especially C/C++ projects using Unix-ish tooling.

It is not a replacement for WinGet. It is a developer environment with a package manager.

---

7. vcpkg

Official site: https://vcpkg.io/

vcpkg is a C/C++ package manager maintained by Microsoft and the C++ community.

It is not for installing desktop apps.

It is for project dependencies like:

• Boost
• OpenSSL
• zlib
• fmt
• SDL
• Qt
• curl
• SQLite
• OpenCV

Example:

vcpkg install fmt
vcpkg install openssl
vcpkg install sqlite3

Modern vcpkg can also work with manifest files, which makes it better for reproducible project dependency setup.

Why it is still active

vcpkg is actively maintained by Microsoft and the community, with regular registry updates and new ports.

Pros

Cons

Best for

Use vcpkg if you are building C++ projects on Windows.

For example, if you are trying to compile a tool and it needs OpenSSL, zlib, SQLite, or Boost, vcpkg is often the least annoying way to get there.

---

8. Conda and Mamba

Conda site: https://conda.org/

Conda is a package and environment manager, mostly used for Python, data science, machine learning, scientific computing, and cross-platform native dependencies.

Mamba is a faster replacement/reimplementation of much of the Conda workflow.

Example:

conda create -n qa-tools python=3.12
conda activate qa-tools
conda install requests pandas pytest

With Mamba:

mamba create -n data python=3.12 pandas numpy jupyter
mamba activate data

Why it is still active

Conda remains widely used in Python/data science environments, and Mamba is actively maintained as a faster alternative with current package releases.

Pros

Cons

Best for

Use Conda or Mamba for Python projects where dependencies are more serious than a tiny script.

For example:

• data science notebooks
• ML experiments
• scientific libraries
• cross-platform Python environments
• tools that need native compiled dependencies

For simple Python CLI tools, I would usually use pipx or uv instead.

---

9. Language-Specific Package Managers

These are not Windows package managers in the normal desktop-app sense, but they are still part of a real Windows development setup.

JavaScript / Node.js

Official npm site: https://www.npmjs.com/

Common commands:

npm install
npm install -g typescript
pnpm install
bun install

Use these for JavaScript and TypeScript projects.

Do not use npm to manage your whole Windows machine. Use it for JS dependencies and JS-based global tools.

Python

pip docs: https://pip.pypa.io/

Common commands:

pip install requests
pipx install poetry
uv venv
uv pip install pytest

Use pip inside project environments. Use pipx for isolated Python CLI tools. Use uv if you want a fast modern Python workflow.

.NET

Official docs: https://learn.microsoft.com/en-us/dotnet/core/tools/global-tools

Example:

dotnet tool install --global dotnet-ef

Use it for .NET global tools, not for normal desktop software.

---

What About Microsoft Store?

Microsoft Store is not exactly the same thing as a full package manager, but it does matter.

Some apps are easiest to install and update through the Store. Windows also updates Store apps automatically in many normal setups.

The problem is that the Store catalog is not the whole Windows software universe.

A lot of real desktop software still lives outside the Store.

So the practical setup is usually:

• Store for Store apps
• WinGet for normal desktop apps
• Scoop for CLI/dev tools
• Conda/Mamba for Python/data environments
• vcpkg for C/C++ dependencies

That sounds messy because it is messy. Welcome to Windows.

---

What I Would Actually Install on a Fresh Windows Machine

For a normal power-user/dev setup, I would do this:

Step 1: Use WinGet first

winget install Microsoft.PowerToys
winget install Microsoft.WindowsTerminal
winget install Microsoft.VisualStudioCode
winget install Git.Git
winget install 7zip.7zip
winget install Mozilla.Firefox
winget install VideoLAN.VLC

Step 2: Add Scoop for CLI tools

scoop install git
scoop install curl
scoop install wget
scoop install ffmpeg
scoop install ripgrep
scoop install fd
scoop install jq

Step 3: Add language managers only when needed

For Python:

winget install Python.Python.3.12
pipx install poetry

For Node:

winget install OpenJS.NodeJS.LTS
npm install -g pnpm

For C++:

git clone https://github.com/microsoft/vcpkg.git
cd vcpkg
.\bootstrap-vcpkg.bat

For data/ML:

Install Miniforge or Miniconda, then use Mamba/Conda environments.

---

Which Ones I Would Avoid or Not Recommend as Main Picks

Fallback manual .exe installers

Sometimes you still need them. But they should not be your default workflow anymore.

If an app exists in WinGet, use WinGet.

Random “driver updater” package managers

Hard pass.

Most of these are shady, ad-heavy, or unnecessary. Get drivers from Windows Update, the OEM, Nvidia/AMD/Intel, or the hardware vendor.

Abandoned Windows package managers

There have been many attempts over the years. If the repo is stale, docs are old, or Windows 11 support is unclear, skip it.

Package managers are infrastructure. Dead infrastructure is worse than no infrastructure.

Using one tool for everything

This is the classic mistake.

WinGet is great, but it is not vcpkg. Scoop is great, but it is not Conda. Conda is great, but it is not for installing Chrome. MSYS2 is great, but it is not your normal app store.

Use the right tool for the job.

---

Comparison Table

---

Final Recommendation

If you are a normal Windows user, install and learn WinGet.

If you are a developer, add Scoop.

If you are a sysadmin or you maintain Windows automation, keep Chocolatey in your toolbox.

If you want a GUI, use UniGetUI.

If you do C/C++, use vcpkg.

If you do Python/data/ML, use Mamba or Conda.

If you just need to set up a family laptop in 15 minutes, use Ninite and move on with your life.

Windows package management is still not as clean as Linux, but it is no longer hopeless.

You do not need to download every installer manually like it is 2008.