UniGetUI and WinGet
WinGet is the package manager Microsoft ships with Windows. UniGetUI is the window you drive it from — here is how the two fit together.
What WinGet Does on Its Own
WinGet is a command-line client for the Windows Package Manager. It is installed with Windows 11 and current Windows 10 builds as part of App Installer, and it reads from two default sources: the community winget repository and msstore, which covers Microsoft Store listings.
Everything UniGetUI shows for WinGet packages comes from that client. No separate catalogue, no repackaged installers — the graphical layer only decides what to ask for and how to display the answer.
What the Interface Adds
The parts of WinGet that are awkward to run by hand.
Visible Update List
winget upgrade prints a table; UniGetUI turns it into a checklist you can act on selectively.
Mixed Sources
WinGet packages sit next to Chocolatey and Scoop results, so you can compare versions before choosing.
Store Packages
The msstore source is exposed in the same search box as everything else.
Bundles
Export a WinGet selection to a file and reinstall it on another PC without writing a script.
When Another Manager Fits Better
WinGet is the sensible default, but not for everything.
Developer Tooling
Scoop keeps CLI utilities in your user profile and rarely needs admin rights.
Wider Catalogue
Chocolatey still covers some older or niche desktop software that WinGet does not.
Scripts and Modules
PowerShell Gallery handles modules, which WinGet is not designed for.
The WinGet Command Behind the Button
winget install --id MartiCliment.UniGetUI --exact --source winget
This is what UniGetUI runs when you install it through WinGet.
Set It Up in a Few Minutes
The installation guide covers WinGet, the installer and the portable build side by side.