On July 15, 2026, the developers behind UniGetUI pushed out a rapid hotfix—version 2026.2.4—to repair regressions that appeared barely 24 hours after the application’s ambitious 2026.2.3 performance overhaul. The update addresses a trio of bugs that left some users staring at empty WinGet source lists, PowerShell modules installing in the wrong scope, and the new NativeAOT builds failing to launch reliably. If you updated to 2026.2.3 yesterday, you’ll want to grab this hotfix immediately.

What actually changed

Version 2026.2.3, released a day earlier, was a milestone: it moved UniGetUI’s shipped builds to NativeAOT compilation, scrapped GPU -hungry indeterminate progress animations, and reworked memory handling, icon loading, and list scrolling. The goal was a snappier, more efficient management console—especially for machines with long package lists, older hardware, or users who keep the app open all day.

But the architectural leap exposed three critical flaws that weren’t caught in testing:

  • Empty WinGet sources. After upgrading to 2026.2.3, some users found that WinGet—the built‑in Windows package manager—showed no available sources. That effectively broke UniGetUI’s core function of aggregating applications from multiple repositories.
  • PowerShell scope ignored. When installing PowerShell modules through the interface, the installation scope (CurrentUser vs AllUsers) selected in the UI was disregarded. The actual scope depended on default behavior, which could scatter modules unpredictably and create permission or maintenance headaches for admins.
  • NativeAOT startup crashes. The new native builds, while faster in principle, sometimes refused to start. Issues with WinGet and COM initialization surfaced, prompting Devolutions to add extra safeguards in the hotfix.

Hotfix 2026.2.4 addresses all three. It restores WinGet source visibility, forces PowerShell installs to respect the chosen scope, and patches the NativeAOT boot sequence so the app starts as reliably as it did before the conversion.

Taken together with 2026.2.3’s gains, the 2026.2.4 build represents a net win for most users. The underlying performance upgrades—faster startup, fewer garbage‑collection pauses, less GPU chatter—remain intact. The hotfix simply sweeps away the regressions that slipped through.

What it means for you

The impact depends on how you use UniGetUI.

For everyday Windows users

If you rely on UniGetUI as a software discovery and update hub, the most visible symptom of the bug would be an empty “WinGet” section. With 2026.2.4, that catalog reappears. You’ll also notice smoother scrolling and a slightly lighter feel thanks to the 2026.2.3 rewrites—provided the hotfix installs cleanly. The dockable navigation pane and toast notifications that arrived in 2026.2.3 add a welcome layer of polish, and the manual operation mode gives you finer control over installs and updates. If you never touched PowerShell modules, the scope bug likely didn’t affect you.

Power users and developers

If you frequently install PowerShell modules (from the PSGallery provider, for example), the scope regression was no minor glitch. A module installed in the wrong context might be invisible to scheduled tasks or scripts that expect it in a system-wide location. With the hotfix, your scope choice is respected again. The same goes for Node.js packages (npm), Python packages (pip), and .NET tools: the 2026.2.3 performance improvements make package‑list navigation more responsive when you have hundreds of entries. Just make sure to verify that your WinGet sources repopulate after the update.

Administrators and IT pros

For admins managing fleets or using UniGetUI in a controlled deployment, the startup reliability of NativeAOT builds is the headline risk. A tool that won’t launch breaks workflow. Version 2026.2.4 adds safeguards you can’t see but that should prevent silent failures. If you deploy UniGetUI via winget or Chocolatey, consider pushing an update or at least validating that version 2026.2.3 is not present on critical machines. The application also now retains log scroll positions and remembers per‑page sorting—small things that add up when you’re troubleshooting across multiple systems.

How we got here

UniGetUI (formerly WingetUI) has grown rapidly as the de‑facto graphical wrapper for Windows package managers. It currently supports Winget, Chocolatey, Scoop, Pip, npm, .NET Tool, and PowerShell Gallery. The project, maintained by Martí Climent and contributors, aims to give Windows a unified software store‐like experience for terminal‑oriented tools.

The 2026.2.x line is part of a post‑3.0 rewrite that focuses on performance and architecture. Version 3.0 itself had already modernized the UI. The move to NativeAOT—a compilation technique that produces a fully native executable instead of relying on the .NET runtime—promised startup times sometimes halved and memory footprints reduced. It’s a strategy Microsoft’s own teams have been exploring for PowerShell and other command‑line tools.

However, AOT compilation is notoriously tricky: code that worked under the JIT can fail when stripped of reflection, dynamic loading, or late‑bound COM calls. The empty WinGet sources and COM initialization failures are classic symptoms of NativeAOT edge cases. The PowerShell scope issue appears unrelated to AOT but likely stemmed from a refactoring alongside the performance work.

Devolutions’ rapid 24‑hour turnaround suggests the team had monitoring in place and treated the regressions as top priority. The hotfix didn’t roll back NativeAOT; it patched around the pain points, which signals confidence in the underlying technology.

What to do now

If you’re already on 2026.2.3

Upgrade immediately. The quickest path is through UniGetUI itself: open the app, go to the settings (cog icon), navigate to the “Updates” tab, and click “Check for updates.” The tool will fetch 2026.2.4 and walk you through a silent install. Alternatively, download the latest installer from the official GitHub releases page.

After the update, verify the fixes:
- Open the “Discover Packages” tab and confirm that WinGet sources populate.
- Install a small PowerShell module with a specific scope (e.g., -Scope CurrentUser) and check that it lands where you intended.
- Restart UniGetUI several times to ensure NativeAOT reliability stays solid.

If you’re still on an older UniGetUI version

You can jump straight to 2026.2.4. The performance improvements from 2026.2.3 will be included, and you’ll avoid any exposure to the regressions. The safest route is to download the latest installer from GitHub rather than relying on an in‑app upgrade that might chain through 2026.2.3. The project’s release notes recommend a clean install if you encounter any upgrade oddities.

If you use winget to manage UniGetUI

If you installed UniGetUI via winget, run winget upgrade --id UniGetUI.UniGetUI to pull the hotfix. The package is already updated in the winget repository.

General housekeeping

  • If you ever see an empty source list after a future update, open the UniGetUI logs (from the settings) and look for entries mentioning WinGet or COM initialization. You can reset sources via the “Settings > Package Sources” panel as a temporary workaround.
  • The 2026.2.3 release added a “manual mode” for operations; enabling it (in Settings > General) gives you a step‑by‑step view of installs and updates, which can help diagnose scope or source issues.
  • The window‑size drift bug is fixed in 2026.2.3+, so if you’d previously avoided maximizing UniGetUI, you can now do so without it growing on every restart.

Outlook

The quick‑fire hotfix suggests the project remains in active, responsive development. NativeAOT is clearly the future for UniGetUI, and the team is willing to iron out wrinkles at speed. For users, the lesson is as old as software: ground‑breaking releases sometimes break ground they shouldn’t. The 2026.2.4 patch is small, safe, and restores full utility. If you haven’t already, grabbing it now will ensure you get the speed boost without the hassle.

Looking ahead, the next feature‑sized release can build on a stable NativeAOT foundation. Pay attention to the project’s GitHub issues and the UniGetUI changelog; the developers have shown they take regressions seriously. For now, 2026.2.4 is the build you want—and it’s ready when you are.