UniGetUI
A graphical package-management interface that brings WinGet, Scoop, Chocolatey, PowerShell Gallery, pip and npm discovery, installation, updates and removal into one place.
One interface for several package managers
UniGetUI can discover, install, update and remove packages through WinGet, Scoop, Chocolatey, PowerShell Gallery, pip and npm. It exposes package IDs, publishers, versions, sources, update controls and import or export tools.
The interface does not unify trust
Each package still comes from its underlying repository and publisher. The same application may appear through multiple managers, so compare package ID, source, publisher and install path before changing it.
Batch changes need a recovery plan
Installation, updates and removal change the system and may request administrator rights. Exporting a package list does not back up application data, licenses or every setting; create a recovery point and test one low-risk package first.
Save to your cloud drive
Open the cloud drive to get the file directly, or save it for convenient access on another device.
Quark Cloud Drive
RecommendedSave UniGetUI to this cloud drive
Baidu Netdisk
Save UniGetUI to this cloud drive
UniGetUI source checks and staged updates
Start with one detected package manager and one low-risk update, verify the source and recovery plan, then process categories in small batches.
Before you start
- Use an installer from the current trusted maintainer and review the package managers detected on the device.
- Create a system restore point or reliable backup and close applications with important unsaved work.
- Know which repositories and managers already own the software on this device.
Installation steps
- 01
Install the x64 build
Verify UniGetUI 2026.2.7 and the installer, then confirm detected managers, versions and configured sources at first launch.
- 02
Scan installed and pending packages
Wait for each manager to refresh, compare duplicate entries and review publishers before selecting any batch action.
- 03
Export the current package list
Save package IDs and install parameters before changes, while separately backing up application data, licenses and configuration.
Quick start
- 01
Test one low-risk update
Review package ID, source, publisher, current and target versions and install parameters, then update one application only.
- 02
Verify before batching
Launch the updated application and check core functions, then update by category; handle drivers, security software and development tools separately.
- 03
Configure ignores and notices
Skip or ignore versions with known compatibility issues and enable update notices; use automatic updates only for recoverable packages.
Usage tips
- UniGetUI is not a guarantee of package safety; verify the package ID and publisher for every source.
- Custom parameters, batch removal and administrator prompts make real system changes, so review the final selection.
- Similar names and old domains may represent third-party copies; keep the trusted source and maintainer visible.
Troubleshooting and uninstall
Why does one application appear more than once?
Compare manager, package ID, install path and version, then keep one source responsible for updates instead of alternating managers.
What if an update fails or the application stops launching?
Save UniGetUI and manager logs, stop the batch queue, restore from the backup or restore point and retry the package alone after checking dependencies.
- Export the list and remove the interfaceSave the package list and ignore rules, then uninstall UniGetUI; installed applications and underlying managers remain and need separate handling.
Frequently asked questions
Does UniGetUI host the software packages itself?
No. It calls the selected package managers and displays their metadata; the repository and publisher provide the actual package.
Can UniGetUI install or update several packages together?
Yes, but review every source and package first, keep a recovery point and process low-risk groups before sensitive software.
Is an exported package list a full system backup?
No. It usually records packages and some parameters, not application data, accounts, licenses, drivers or all manual settings.
Why should duplicate package entries be reviewed?
Different managers may target the same application, and alternating sources can create version, path or update conflicts.