Microsoft has released PowerToys 0.100.2, a targeted patch that fixes a memory leak in Command Palette—just days after the previous update addressed a handful of other bugs in the same tool. For anyone who uses PowerToys’ rapid launcher daily, this update is a no-brainer, but its speedy arrival also signals that the 0.100 branch is still shaking off launch jitters.

What Changed in Two Consecutive Patches

PowerToys 0.100.0 introduced a redesigned Command Palette with dock support and a cleaner interface, but early adopters quickly found issues. Microsoft responded with 0.100.1, which squashed four specific bugs:

  • Run history fixes. Run history now initializes correctly, so past commands and search results appear without glitches.
  • Performance Monitor Dock glitch eliminated. The Performance Monitor Dock no longer shows “???” after a system restart.
  • Correct Hibernate icon. The Hibernate power option now has the intended icon instead of a placeholder.
  • Pin-to-Dock dialog annoyance gone. The pin-to-Dock prompt no longer appears on displays where the Dock isn’t enabled.

Yet a more insidious problem remained. Users and automated testing spotted a memory leak in Command Palette that was introduced in 0.100.1. The leak caused the Command Palette process to progressively consume more RAM the longer it ran, never releasing freed memory. Over time, this could degrade system performance significantly—especially for those who keep the launcher open all day. PowerToys 0.100.2 is a single-purpose patch that seals that leak.

What the Memory Leak Means for Different Users

For everyday users who occasionally summon Command Palette with Win+Space or a custom shortcut to launch apps or do quick math, the leak might have been subtle but cumulative. A PC left running for days could gradually feel sluggish, with no obvious culprit unless you monitored RAM usage.

For power users, the impact was more direct. If you rely on Command Palette all day to invoke scripts, extensions, pinned actions, and system commands, the leak could have forced you to restart PowerToys periodically just to reclaim memory. This interrupted workflow and undercut the efficiency that PowerToys is supposed to deliver.

IT administrators should note that the 0.100 branch is still maturing. While there’s no confirmed multi-monitor regression in this patch, the complexity of display arrangements and the number of rapid-fire fixes warrant caution. Deploying 0.100.2 to a representative pilot group—especially those with multi-monitor rigs, docking stations, or mixed scaling—is a prudent first step. The WindowsForum community has long pointed out that even small servicing releases (like PowerToys 0.97.2 earlier this year) can profoundly affect daily stability, and the same logic applies here.

How We Got Here: A Timeline of Fixes

PowerToys has been on a steady update cadence, with major versions often followed by quick bug-fixing sprints. The 0.100 release was a substantial overhaul of Command Palette, adding dock functionality and a modernized UI. But major rewrites often introduce regressions, and this was no exception.

  • 0.100.0 shipped with known rough edges. Microsoft’s open-source issue tracker lit up with reports of the four bugs later addressed in 0.100.1.
  • 0.100.1 arrived within a week, tackling those visible glitches. However, the memory leak—likely triggered by a code path in the new Palette that wasn’t excercised heavily in testing—became apparent only after extended real-world use.
  • 0.100.2 is a swift reaction, patched within days of the leak being identified. This rapid cycle mirrors the company’s response to earlier PowerToys stability issues, such as the Command Palette and CursorWrap fixes in 0.97.2.

The takeaway: the PowerToys team is actively monitoring feedback and isn’t hesitating to ship targeted fixes. For users willing to update promptly, the pain is short-lived.

How to Get PowerToys 0.100.2 Safely

For individual users:
- Check your version. Open PowerToys settings (right-click the system tray icon or search for it in Start) and look under “General.” If you’re on 0.100.0 or 0.100.1, updating is strongly recommended.
- Update from GitHub. Head to the official releases page and download the PowerToysSetup-0.100.2-x64.exe installer. Run it; it typically takes less than a minute.
- Use winget. Open a terminal and run winget install --id Microsoft.PowerToys (or winget upgrade if already installed). Let the package manager handle the rest.
- Back up your settings. If you’ve heavily customized PowerToys, navigate to the General tab and use the export feature. But be aware that settings imported from a newer version might not be fully compatible if you later need to roll back.

For IT administrators:
- Pilot first. Select a cross-section of users—single‑display, multi‑monitor, dock‑dependent, and workflow‑critical Command Palette adopters—and deploy 0.100.2 to them first.
- Capture current state. Before pushing the update, document each pilot machine’s current PowerToys version, Windows build, display topology, scaling settings, and active extensions. This makes rollback simpler if needed.
- Test extensively over a normal work cycle. Do not just verify that PowerToys launches; have pilot users run through their actual workflows, including docking/undocking, sleep/resume, and heavy Command Palette usage.
- Prepare a rollback plan. Keep a copy of the previous approved installer and a procedure for uninstalling 0.100.2 and reinstalling the prior version. Verify that settings can be restored or manually reconfigured if needed.
- Monitor the issue tracker. Check GitHub issue #45201 and newer threads for any late‑breaking reports before broadening deployment.

What’s Next for PowerToys Command Palette

The existing Dock proposal (GitHub issue #45201) shows that more refinements are on the roadmap. With the memory leak squashed, the foundation is stronger for those future enhancements. Expect further updates in the coming weeks as the 0.100 branch stabilizes. For now, installing 0.100.2 will reclaim your RAM and keep Command Palette running smoothly—whether you’re a casual user or a power-user ninja.