Historically, the Windows installer required administrative privileges and could configure the host with the virtualization provider (WSL or Hyper-V). With this latest release, we have refactored the Windows installation experience to prioritize convenience for enterprise users and simpler code for maintainers.

No Admin? No Problem.

The headline feature for Windows users in Podman 6 is the ability to install Podman without administrative privileges.

In previous versions, the installer was a machine-wide bundle that required elevated permissions to extract files to protected directories such as C:\Program Files. This was a significant barrier for corporate environments.

The new installer supports per-user installation. It installs directly into the current user’s folder and uses the HKCU registry instead of HKLM, allowing unprivileged users to get up and running independently. Per-machine installation is also supported, although per-user is the default.

From EXE Bundle to Dual-Purpose MSI

We have transitioned from distributing a complex .exe bundle to a streamlined Dual-Purpose Package (.msi).

The previous bundle was primarily used to orchestrate the automatic installation of WSL2 or Hyper-V, a feature that was hard to test automatically and broke a few times. By moving to a single .msi package, we’ve simplified the codebase and provided a standard installation format that better aligns with modern Windows management tools.

Note on Upgrading: Because this is a fundamental change in the installer architecture, the new MSI package cannot perform a “seamless” in-place upgrade from the old exe-based versions. You will need to uninstall your previous Podman version before installing Podman 6. Don’t worry, your Podman data and machine configurations will survive the uninstallation process.

Simplifying the Installation Logic

We’ve removed the automatic installation of virtualization providers (WSL2 and Hyper-V). While this might sound like a reduction in features, it is actually a major improvement in reliability:

• Logic where it belongs: The complex logic for setting up virtualization has been moved from the installer code into the podman machine init command, where the Podman team can better maintain it in Go.
• Reduced friction: Removing that logic from the installer eliminates a category of bugs that were impossible to test in our CI/CD environments.

Support for Community Package Managers

We recognize that many Windows users don’t use the standalone installer at all, preferring tools like Scoop, Chocolatey, or WinGet. As part of our refactoring efforts, we have ensured that the new installer works well with these third-party tools.

As always, we want to hear your feedback. If you encounter any issues or have ideas for further improvements to the Windows experience, please join the conversation on GitHub by participating in a discussion or opening an issue.

References

https://github.com/podman-container-tools/podman/issues/25723