Keeping all of the programs on your computer up to date is important for security reasons; just ask LastPass, the disgraced password manager that got hacked because an employee's personal computer was running an old version of Plex Media Server. The particular vulnerability that the hackers exploited had been patched almost 3 years earlier, but because the employee never bothered to update Plex, he never got the fix.
Every month that you leave software on your computer un-patched is time in which hackers may discover the vulnerability and start using it to attack computers. But how on earth can you even figure out which of your programs need updates? Doing that one by one takes forever, and THEN you still have to actually install those updates.
This is where software updaters are essential. On Windows, SUMO used to be among the best programs for the job, but it was discontinued in early 2024. I've been searching for a replacement for a while now, and I finally settled on WinGetUI (soon to be known as UniGetUI). A LOT more detail and some tips are under the readmore!
Details:
Purpose: Provide a unified frontend for multiple package managers on Microsoft Windows to simplify installing and updating software
OS Supported: Windows 10, 11
Installer Size: 76 MB
Country of Origin: Catalonia/Spain
Languages Supported: 16 languages fully, 24 partially
A LOT more detail and some tips are under the readmore!
Winget ("WIN-get") is the name of Microsoft Window's new-ish package manager, a program that itself takes care of installing and updating other software for you. Linux and Unix have had built-in package managers for decades, but Windows has been sorely lacking on that front until just recently. Winget provides the ability to install and update software, but it's a command line utility, meaning you have to type text into a command prompt in order to get winget to do anything for you.
WinGetUI is essentially just a nice interface using winget in the background; it shows you which programs you have installed, which ones have updates available, and it will even install the updates for you. That last part was a game changer for me personally as it saves me a lot of time (I have a LOT of programs and libraries installed on my computer).
The best part is the developer has added support for other package managers too. Computer language SDKs often come with their own package managers for downloading the little libraries that you can bundle with code that you write, and WinGetUI now supports most of them: npm, pip, .NET Tool, Chocolatey, scoop, Powershell Gallery, and it can even list software installed from the Steam shop or the Microsoft Store (though it can't update those ones for you). Incidentally, this is why the name is changing from WinGetUI to UniGetUI; it now supports a lot more package managers than just winget.
WinGetUI can even help you migrate software to a new computer. Simply install WinGetUI on your old computer, export a list of all of the software you have installed, then install WinGetUI on your new computer and import that list and then click install. You'll probably have to babysit it for a while because Windows will prompt you to give admin access to the installers that need it, but hey. At least you don't have to write down all the software you have and download and install each one by hand.
I do want to highlight that Microsoft is still working out the kinks in winget. Windows has existed for a long time and provided a lot of freedom in how you could install software. Multiple companies have made their fortunes just by providing custom installer software for Windows (InstallShield and NSIS being prime examples), so Microsoft has their work cut out for them trying to get all the different software manufacturers to list their software in the winget directory AND standardize their installers.
As such, you may run into issues like these:
WinGetUI lists a program you installed manually and tries to update it via winget; the installer succeeds, but because those installation methods are different, you end up with 2 copies of the software installed in different locations
WinGetUI fails to update a program because the hash of the downloaded installer doesn't match the hash that winget says it should have. This is usually a developer error
WinGetUI fails to determine whether some programs have updates available or not
WinGetUI downloads an installer/updater but it fails to run because it detects that the installation methods for that program are different (manual install vs. winget install)
Almost all of these can be resolved by uninstalling the manually installed version and reinstalling it using winget, either from the command line or just from WinGetUI. Once you do that one-time operation, the winget package manager (and by extension WinGetUI) should be able to handle everything from there on out. It will only get better too as winget usage becomes more common among software developers.
Master Silent Winget Updater with 12-Hour Timestamp & 30-Day Auto-Cleanup
The Start
OVERVIEW: THE SILENT DAEMON
Standard Windows operating environments suffer from high-frequency telemetry interrupt flags and constant update notifications (Steam, Discord, Adobe, core drivers). Left unmanaged, these updates introduce friction, trigger User Account Control (UAC) prompts, and clutter the system directory with fragmented log files.
To achieve absolute operational autonomy, we engineered a headless PowerShell deployment. The architecture requires a completely invisible background execution loop: zero pop-ups, zero UAC interrupts, and automated log rotation. The script executes on a weekly cron-equivalent schedule, generating cryptographic-grade 12-hour timestamps for runtime forensics, and enforces a strict 30-day retention policy to prevent drive bloating.
THE BLUEPRINT & LOGIC TREE
1. Preemptive Process Termination (The Clean Slate)
Before registering the updated daemon, the initialization sequence must nuke any legacy instances of the scheduled task. This ensures a zero-state baseline, unregistering conflicting triggers rather than allowing overlapping execution logic to corrupt the task runtime.
We isolate execution to a low-impact window when system resources are unutilized. Sunday afternoons at 14:00 hours represent our operational sweet spot—allowing the hardware to catch up on patches and stabilize its baseline environment before the standard work week cycles in.
This is the heart of the operational loop. We encapsulate the native Windows Package Manager (winget) inside an isolated script block tasked with three low-level instructions:
Silent Bulk Upgrades: Enforces global application upgrading (--all), captures untagged dependencies (--include-unknown), and forces silent execution while auto-accepting EULAs and source manifests to bypass standard user-input blockages.
Temporal Logging: Calls Get-Date with a structured yyyy-MM-dd_hhmmtt format string. This yields unique, chronologically scannable filenames, ensuring exact timeline diagnostics if an application deployment experiences a fatal error.
Automated Garbage Collection: To prevent local filesystem bloat within C:\Logs, the daemon executes a parity check on the directory, identifying any .txt outputs with a LastWriteTime delta older than 30 days and purging them from the sector.
To achieve true invisibility, the task must run beneath the window-manager abstraction layer. We pass the -WindowStyle Hidden and -NoProfile arguments directly to the PowerShell executable execution string, suppressing the instantiation of a visual console window.
Finally, the daemon is written to the system registry. We explicitly set the execution token to -RunLevel Highest. This satisfies the necessary security permissions for winget to perform system-wide package deployment without hanging on elevation errors, while -Force ensures an atomic overwrite of the active task profile.
The beauty of this architecture is its absolute silence. The local interface remains untouched, holding the perimeter without demanding cognitive energy. Yet, every Monday morning, a quick look into C:\Logs reveals a clean, chronological record of the system's maintenance history (e.g., winget-update-2026-05-24_0200PM.txt).
If a dependency breaks or an application updates unexpected behavior, we have full audit capability to isolate the root cause. It’s a set-it-and-forget-it subsystem—exactly the kind of operational efficiency required to keep our local forge clear of corporate background noise.
Pre-requisite Check: Ensure the physical path C:\Logs is provisioned on the root drive before spinning up the daemon, or map the target variable to an active local directory.
If you are experiencing fork sync issues with WinGetCreate, synchronize your fork of winget-pkgs to fix them!
#WinGet #TechNews #TechUpdates #programming #WinGetCreate #Packaging #Software #Computers #Laptops
Installing applications on Windows has often been a frustrating experience for many users, involving searching multiple websites and navigating complex installers. While the Microsoft Store offers some convenience, it doesn’t cover everything—leading to potential security risks and unwanted software. Fortunately, there’s now a powerful alternative: Winget, Microsoft’s command-line package…
These Winget Hacks Transformed How I Use Windows 11
Anyone who uses computers often knows how quickly some tasks can become repetitive and boring. For someone like me, constantly troubleshooting or fixing PCs, having a Windows feature for easy software installation is always a handy tool.
What is Winget and Why Should You Care?
Windows Package Manager, or Winget, might not be the first thing that springs to mind when you think of Windows…
