On July 15, Devolutions shipped UniGetUI 2026.2.3, a milestone release that compiled the package manager front-end into native code. Within 24 hours, the team had released 2026.2.4 to patch a critical bug: WinGet sources vanished, turning the dashboard into an empty shell for many users.

The upgrade that promised speed but broke a key connection

The 2026.2.3 release aimed to transform UniGetUI’s performance. Before this update, the app ran like most .NET desktop software—its code was compiled just-in-time as you launched it. The switch to NativeAOT (ahead-of-time compilation) promised a leaner, faster startup by turning the whole program into machine code before it ever hits your desktop. That means less CPU grind on low-powered laptops, a smaller memory footprint, and a reduced attack surface because there’s less runtime for malware to hijack. For anyone who opens UniGetUI daily to check for updates, the benefit was meant to be obvious, especially on older hardware.

But the transition wasn’t seamless. WinGet, Microsoft’s own command-line package manager, is UniGetUI’s most popular back end. After upgrading to 2026.2.3, a significant number of users discovered that the “Discover Packages” tab was empty when WinGet was selected. No matter how often they refreshed, the list stayed blank. The app couldn’t see any software to install, update, or remove—effectively rendering its most essential feature useless.

Inside the NativeAOT switch and its unexpected fallout

To understand why this happened, you don’t need to be a developer. NativeAOT compiles .NET code directly into a standalone binary, stripping away the layer that normally interprets code at runtime. That layer, called the JIT compiler, also handles many behind-the-scenes interactions with Windows components like COM objects—the glue WinGet uses to expose its package data.

UniGetUI talks to WinGet through a COM interface. Under the old compilation model, the .NET runtime managed these interactions smoothly, handling data marshaling and error recovery. With NativeAOT, the app must handle those details more explicitly. The empty-source bug suggests a failure in that handshake: UniGetUI thought it queried WinGet successfully, but the data never made it to the interface. The bug didn’t crash the app or throw an error; it simply showed zero packages, which is far more confusing for a user who doesn’t know what to look for.

The developer’s GitHub release notes call out “WinGet sources empty regression” as the headline fix, alongside a second issue where PowerShell module installs ignored the user’s chosen installation scope (machine-wide vs. current user). Both are classic consequences of retooling the compilation pipeline without exhaustive integration testing across every supported package manager.

A one-day hotfix: what version 2026.2.4 repairs

UniGetUI 2026.2.4 lands exactly one day after its broken predecessor. It doesn’t roll back NativeAOT; it patches the specific pain points while preserving the performance gains. The release notes list three targeted fixes:

  • Empty WinGet sources restored: The primary repair. After updating to 2026.2.4, switching to WinGet in the Discover tab should immediately show your usual list of packages, including Microsoft Store, msstore, and any custom sources you’ve added.
  • PowerShell module installs now respect scope: When you choose to install a module for all users or just the current user, the setting now sticks.
  • NativeAOT startup stability: Additional safeguards prevent crashes during the critical first seconds when the app initializes its services.

These fixes arrive on top of everything 2026.2.3 introduced—the dockable navigation pane, toast notifications, manual package operation modes, remembered sorting, and GPU-friendly interface tweaks—all intact.

Who’s affected and how urgently you should act

The short answer: if you installed 2026.2.3, update now. If you’re on an older release, jump straight to 2026.2.4 to avoid the bug entirely. Here’s how the impact breaks down by user type:

  • Home users and enthusiasts: You likely use UniGetUI to keep browsers, media players, and development tools current without opening a terminal. An empty WinGet source means you’re blind to updates. Automatic checks might silently fail, leaving you on vulnerable versions of software. The fix is quick and non-disruptive.
  • IT administrators and power users: If you manage a fleet of Windows machines or maintain a community repository, you depend on UniGetUI’s visibility. The regression could have caused help-desk calls from users who thought their package manager was broken. The rapid hotfix is reassuring, but it highlights the need to test such foundational changes in a sandbox before pushing to production.
  • New UniGetUI users: If you downloaded the tool for the first time on July 15 and saw a blank WinGet page, don’t abandon it. That was a one-day glitch. Install 2026.2.4 and you’ll see the full catalog you were expecting.

Beyond the bug: the quieter quality-of-life gains in 2026.2.3

Because the hotfix bundles all of 2026.2.3’s improvements, it’s worth calling out the features that got overshadowed by the WinGet failure:

  • Dockable navigation pane: A much-requested return of the resizable, floating panel that gives quick access to package lists, updates, and settings.
  • Toast notifications: Now you’ll get a system pop-up when a package operation completes, so you don’t have to keep the UniGetUI window open.
  • Manual modes for install, update, and uninstall: For users who want more control, you can now step through operations interactively, approving each action.
  • Persistent column sorting: Package list sorting (by name, version, source) is remembered per page, so you don’t have to re-sort every session.
  • Scroll-stable log windows: As new output streams in, the log view retains your scroll position, making it easier to watch a specific line during long downloads.
  • Performance tweaks: Icon loading and memory management were optimized, DataGrid scrolling is smoother, and indeterminate progress bars were removed to cut GPU usage. The last one might save a few milliwatts on a tablet or extend battery life on a laptop that keeps UniGetUI running in the background.

All of these are present and working in 2026.2.4, as long as WinGet sources are cooperating.

How to update and confirm your WinGet sources are back

Updating takes less than a minute:

  1. If UniGetUI is open: Go to Help > Check for Updates. The app should find 2026.2.4 and offer to download it. Confirm and restart when prompted.
  2. If it’s not open or the updater fails: Download the installer directly from the project’s GitHub Releases page (look for version 2026.2.4) or wait for the Microsoft Store to push the update—though the direct GitHub download is the fastest.
  3. After updating: Launch UniGetUI, click on the Discover tab, and select WinGet as the source. The package list should populate within seconds. If it doesn’t, try clicking the Refresh sources icon (circular arrow) next to the source selector. In rare cases, a cold reboot or running winget source update in a Command Prompt can realign things, but the hotfix should resolve it directly.

For administrators deploying via scripts or MDM tools, replace any existing 2026.2.3 packages with 2026.2.4 immediately. Verify by launching the app on a test machine and confirming the WinGet source is populated before broader rollout.

The bigger picture for UniGetUI and Windows package management

UniGetUI’s rapid patch demonstrates the strength of open‑source responsiveness: a critical bug gets reported, reproduced, and fixed within hours. But the incident also exposes a tension in the Windows package‑management ecosystem. As more tools adopt aggressive optimization techniques like NativeAOT, they must contend with dozens of underlying package managers, each with its own quirks and rarely updated interop contracts.

WinGet itself is still maturing; its COM API isn’t as battle‑tested as, say, the Windows Shell’s. UniGetUI’s reliance on that API means future WinGet updates could similarly break things until stability improves on both sides. The developer’s willingness to ship a same‑day hotfix is commendable, but users who want absolute stability might wait a few days before installing major UniGetUI releases in the future.

For now, the takeaway is clear: UniGetUI 2026.2.4 is the version you want. It delivers the speed boost of native compilation without the show‑stopping bug, and it adds a handful of interface refinements that make package management on Windows feel less like a chore. Install it today, and you’ll be back to updating, installing, and removing software with a single pane of glass—the way it was meant to work.