PowerToys 0.100.2 Fixes Command Palette Memory Leak—Pilot First

Deploy PowerToys 0.100.2 only to a representative pilot; 0.100.1 fixed several Command Palette issues and 0.100.2 fixed a memory leak. The supplied evidence does not verify an open monitor-placement or freezing regression, so multi-monitor testing is an exposure-based precaution rather than a response to a proven active defect.
Microsoft’s release notes document the servicing sequence. PowerToys 0.100.1 fixed Run history initialization, the Performance Monitor Dock showing “???” after restart, an incorrect Hibernate icon, and a pin-to-Dock dialog appearing for displays where the Dock was not enabled. PowerToys 0.100.2 then fixed a Command Palette memory leak identified in 0.100.1.
Organizations entering the 0.100 branch should therefore test the serviced 0.100.2 build rather than deploy 0.100.0 automatically. Broad approval should depend on whether representative users can complete their real workflows without recurring interruption.

Deployment Decision​

Use three deployment groups:

User or system profile	Recommended action	Approval requirement
Single display; Command Palette is a noncritical convenience	Include in the initial 0.100.2 pilot	Activation, search, launch, shortcuts, restart, and sign-in tests pass
Multi-monitor or Dock-dependent workflow	Include representative hardware in a controlled pilot	Normal display arrangements, scaling, docking, sleep, and reconnection pass
Workflow-critical launcher use	Keep on the currently approved version during the pilot	Actual extensions, scripts, shortcuts, pinned actions, and recovery procedures pass

This segmentation does not imply that 0.100.2 is known to fail on multi-monitor systems. It recognizes that a single-screen test PC cannot adequately validate Dock placement, display reconnection, mixed scaling, or laptop docking for employees who depend on those configurations.
A launcher used occasionally to open Calculator has a different operational impact from one used throughout the day to invoke administrative tools, extensions, scripts, files, and pinned actions. Pilot membership should reflect that difference.

Operational Pilot Checklist​

1. Inventory managed systems with PowerToys installed and identify employees who depend on Command Palette.
2. Record each pilot PC’s current PowerToys version, Windows build, display count, scaling settings, docking hardware, enabled Command Palette extensions, assigned shortcuts, and critical pinned actions.
3. Separate single-display PCs from multi-monitor workstations and laptops regularly connected to external displays.
4. Obtain PowerToys 0.100.2 through the organization’s approved distribution channel. For a direct package deployment, use the official PowerToys GitHub Releases page; for a managed package channel, approve the exact 0.100.2 package there.
5. Retain the package and deployment definition for the organization’s prior approved version.
6. Install 0.100.2, open the current PowerToys settings interface, locate the displayed version, and confirm on-device that it reads 0.100.2. UI labels and navigation can change, so do not rely on an unverified fixed settings path.
7. Run the workflow tests below and record the result, frequency, operational impact, and recovery required for every failure.
8. Inspect the live GitHub issue #45201 and its linked follow-up before approval. Use the live pages to determine their current status; do not infer current behavior from the supplied historical excerpt.
9. Review the newest official PowerToys release notes for any servicing build or newly documented limitation.
10. Expand deployment only if the predefined approval criteria are met and the rollback procedure has been tested.

The pilot should cover at least one normal work cycle. Confirming that PowerToys launches immediately after installation is not enough to expose restart, sleep, display-reconnection, or repeated-use problems.

Command Palette and Dock tests​

• Activate Command Palette through every assigned keyboard shortcut.
• Open and dismiss it repeatedly using the keyboard, mouse, and focus changes.
• Search for and launch frequently used applications, commands, files, and settings.
• Exercise required plugins and extensions, including rapid repeated activation.
• Test the Extension Gallery operations used by the organization.
• Run the scripts, administrative shortcuts, and custom actions employees need.
• Pin and unpin representative actions in the Dock.
• Verify Dock visibility and placement on each display arrangement used in practice.
• Open context menus for pinned and quick-access items.
• Restart PowerToys and check the Performance Monitor display.
• Check Hibernate and other power-command icons used by the pilot.
• Sign out and back in, then repeat activation and launch tests.
• Put the PC to sleep and resume it.
• Connect and disconnect external monitors.
• Dock and undock pilot laptops.
• Change the primary display where that is part of the user’s routine.
• Test mixed display scaling and laptop-lid state changes where applicable.

For each problem, record whether it is cosmetic or work-blocking, whether reopening Command Palette restores operation, whether PowerToys must be restarted, and whether the failure is repeatable. Capture screenshots or a short screen recording, the exact reproduction sequence, relevant timestamps, PowerToys logs, display topology, scaling values, and enabled extensions.
Approval should require all critical workflows to pass, no repeatable failure that blocks work, and no recurring interruption that forces users to restart PowerToys. A team may accept a documented cosmetic issue, but it should not silently treat an extension, script, shortcut, or Dock failure as a general pass.

WindowsForum User Reports Put Stability in Context​

WindowsForum users have repeatedly focused on the practical reliability of Command Palette rather than treating each PowerToys release as a simple feature checklist. In WindowsForum’s report on PowerToys 0.97.2, the update was characterized as a small but important stability-and-polish release addressing regressions from the broader 0.97 cycle, including Command Palette and CursorWrap fixes.
That report supports a narrow operational lesson: servicing releases can matter to users who rely on PowerToys every day. It does not prove that the 0.100 branch has the same defects, nor does it establish an active monitor-placement or freezing problem in 0.100.2. The current deployment decision should rest on Microsoft’s documented 0.100.1 and 0.100.2 fixes plus results from the organization’s own representative pilot.

Read the Dock Proposal Carefully​

GitHub issue #45201 is a Command Palette Dock proposal and history record. The supplied excerpt says that the Dock shipped in PowerToys 0.98/CmdPal 0.9 and directs readers to linked follow-up work.
That excerpt does not establish a current freezing defect, a current monitor-placement defect, or the present status of the linked work. Administrators should inspect the live issue and linked follow-up for current status before approval. They should not characterize either page without reading its current contents, and they should not substitute an older proposal excerpt for current release notes or pilot evidence.

Use an Explicit Rollback Procedure​

Prepare rollback before installing the pilot. Microsoft’s official PowerToys installation documentation and the official PowerToys releases page should be checked when the runbook is created and again before execution, because supported installation commands, prerequisites, and package behavior can change.
Use this procedure:

1. Identify the approved source. Roll back through the same organization-approved channel used to manage PowerToys, such as the managed software platform or a package retained from the official GitHub Releases page. Verify the package’s version, architecture, and signature under normal organizational controls.
2. Capture the failing state. Before changing the installation, record the installed version, Windows build, installer scope, enabled modules and extensions, shortcuts, display arrangement, scaling, reproduction steps, timestamps, logs, screenshots, and any relevant crash information.
3. Capture configuration. Record or export the pilot user’s PowerToys configuration using only backup or export controls confirmed in the currently installed UI and current official documentation. Do not promise that settings will survive a downgrade or that a newer configuration is backward-compatible.
4. Remove 0.100.2. Use the organization’s normal managed uninstall action or the current Windows uninstall method documented by Microsoft. Confirm that the 0.100.2 installation is no longer registered.
5. Install the prior approved release. Deploy the retained prior package through the approved channel. Do not install an arbitrary older download or mix machine-wide and per-user deployment scopes.
6. Verify the rollback. Open the current settings interface and confirm the displayed version on-device. Then test Command Palette activation, one critical launch action, required extensions, shortcuts, Dock behavior, and the affected display workflow.
7. Restore only verified settings. If settings are absent, use a backup only when the current official documentation confirms that the restore method applies. Otherwise, reapply required settings manually from the captured configuration.
8. Preserve evidence. Keep the pre-rollback logs, configuration record, package identifiers, deployment result, and post-rollback test outcome for support or issue reporting.

If the organization’s management platform supports package supersedence or a formal rollback action, administrators may use that method instead of a manual uninstall/install sequence. The deployment record must still identify the exact prior package, installation scope, settings outcome, and validation result.

Frequently Asked Questions​

Should everyone avoid PowerToys 0.100?​

No. Deploy 0.100.2 to a representative pilot first. Users for whom Command Palette is noncritical generally present lower operational risk, while workflow-critical users should remain on the approved version until their actual tasks pass.

Is PowerToys 0.100.2 known to have monitor-placement or freezing defects?​

The supplied evidence does not establish either defect in 0.100.2. Multi-monitor, Dock, mixed-scaling, and keyboard-intensive workflows should still be tested because they create additional deployment exposure.

Why not deploy PowerToys 0.100.0?​

PowerToys 0.100.1 contains documented Command Palette corrections, and 0.100.2 fixes a memory leak identified in 0.100.1. A new 0.100 deployment should start with the serviced 0.100.2 package.

What does issue #45201 establish?​

It establishes proposal and development history for Command Palette Dock and points to linked follow-up work. The supplied excerpt does not establish a current placement or freezing regression. Inspect the live issue and linked follow-up for their current status.

Are settings retained during rollback?​

Do not assume so. Capture the configuration before uninstalling 0.100.2, verify the current official backup or export guidance, and be prepared to reapply settings manually. A backup created by a newer version should not be treated as backward-compatible without official confirmation.

What should administrators check immediately before broad deployment?​

Confirm pilot results, inspect the live Dock issue and linked follow-up, read the newest official release notes, verify that systems actually show 0.100.2, and ensure the prior approved package and tested rollback procedure remain available.

---

References​

1. Primary source: github.com
   
   

   Issues · microsoft/PowerToys · GitHub

   Microsoft PowerToys is a collection of utilities that supercharge productivity and customization on Windows - Issues · microsoft/PowerToys

   github.com
2. Primary source: WindowsForum
   
   

   PowerToys Update 0.90.1: Enhanced Command Palette and User-Centric Fixes | Windows Forum

   Microsoft’s commitment to its community is on full display with the latest PowerToys update addressing pressing issues with the Command Palette—a tool that...

   windowsforum.com

 

[ChatGPT]

PowerToys 0.100.2 is the version to install on personal and other low-risk PCs because it includes two corrective releases issued after the foundational 0.100.0 update. Organizations should stage it before broad deployment if users depend on Command Palette extensions, docks, customized settings, or unattended updates, because this release cycle moves PowerToys to .NET 10, expands Command Palette into an extension platform, and changes update recovery behavior.

Why 0.100.2 is more than a routine PowerToys update​

Microsoft released PowerToys 0.100.0 on June 10, 2026. Its visible additions included a redesigned Shortcut Guide and the Command Palette Extension Gallery, but its most consequential change may be underneath the interface: the project moved to .NET 10.
That foundation change arrived alongside a more ambitious Command Palette model. Users can browse, install, update, and remove extensions through Command Palette Settings, making the feature less like a fixed launcher and more like an extensible platform.
Microsoft also reworked the update process. Beginning with 0.100.0, PowerToys should relaunch after an automatic update, provide a clearer success notification, and back up configuration files before updating. If PowerToys detects configuration corruption afterward, it can restore those files automatically.
Those are worthwhile improvements, but combining a runtime migration, extension management, and update recovery changes creates a broader testing surface than a conventional feature release. Microsoft’s two rapid follow-up patches reinforce the case for evaluating the complete 0.100.2 build rather than deploying the original 0.100.0 package.
PowerToys 0.100.1 arrived on June 24, 2026, correcting stability and behavior problems reported after 0.100.0, including issues affecting Command Palette and Shortcut Guide. PowerToys 0.100.2 followed on June 26 and fixed a memory leak in the Command Palette Performance Monitor dock extension found in 0.100.1. Version 0.100.2 is currently the latest stable release.
WindowsForum users have seen this rapid corrective pattern before. Reports on PowerToys 0.90.1 emphasized targeted stability and workflow fixes shortly after the preceding release, particularly around Command Palette behavior. Reports on PowerToys 0.92 also focused on the combination of new productivity features and performance work. Those experiences support a practical service approach: evaluate the corrected build and test the utilities that people actually use.

Should you upgrade now or hold?​

Use this decision matrix rather than treating every PowerToys installation the same way.

Environment	Recommended action
Personal, enthusiast, development, or other low-risk PC	Upgrade to 0.100.2 and complete the post-update checks
Small team with no essential extensions or docks	Upgrade a representative device first, then proceed if validation passes
Managed department or device group	Pilot 0.100.2 using the intended deployment method
Workflow dependent on Command Palette extensions or docks	Stage and test the exact extension actions and layout
Shared computers or installations with strict scope requirements	Confirm that the update preserves the existing installation scope
Devices still running 0.100.0 or 0.100.1	Use 0.100.2 as the stabilization target

A short pilot is especially useful when custom settings must remain consistent or when automation expects PowerToys to relaunch without user intervention.

How to upgrade a personal or low-risk PC​

Before updating, record the current PowerToys version and note which utilities, Command Palette extensions, pinned items, and docks you regularly use. That record makes post-update comparison much easier.

Update through PowerToys Settings​

The wording and arrangement of update controls can vary by PowerToys release, so use the update option displayed in your installed PowerToys Settings rather than relying on an unverified submenu name.

1. Open PowerToys Settings from the Start menu or the PowerToys system tray icon.
2. Open the general application settings page.
3. Locate the displayed PowerToys version and available update action.
4. Check for an update.
5. Download and install version 0.100.2 when it is offered.
6. Allow PowerToys to close while installation completes.
7. Confirm that PowerToys relaunches.
8. Reopen PowerToys Settings and verify that the displayed version is 0.100.2.
9. Run the functional checks in the verification section below.

PowerToys 0.100 introduced a success notification intended to confirm that the updated version is running. Treat that notification as useful feedback, not as the only verification. Check the installed version directly and test the features you rely on.

Update with WinGet​

Open Windows Terminal or PowerShell and run:
winget upgrade --id Microsoft.PowerToys --source winget
WinGet preserves the installation’s current scope when updating PowerToys. A per-user installation should remain per-user, and a machine-wide installation should remain machine-wide.
After the command completes:

1. Start PowerToys if it is not already running.
2. Open PowerToys Settings.
3. Confirm that the installed version is 0.100.2.
4. Confirm that the installation still has the intended scope.
5. Test the utilities and Command Palette configuration used on that PC.

Do not change installation scope during an ordinary update unless that change is separately planned and tested.

How to stage 0.100.2 before wider deployment​

The following pilot checklist is WindowsForum operational guidance, not a claim that Microsoft documents every scenario as a formal deployment requirement. Its purpose is to reproduce real user workflows rather than merely confirm that the installer exits successfully.

1. Select a small pilot group that includes both routine and heavy PowerToys users.
2. Match the production installation scope: per-user or machine-wide.
3. Record each pilot device’s current PowerToys version.
4. Record the enabled utilities and any settings important to users.
5. Inventory Command Palette extensions, pinned items, docks, and customized extension settings.
6. If your organization already has a documented PowerToys configuration-backup procedure, create a separate backup before updating. Do not assume a particular Settings page or restore control unless you have verified it in the installed build.
7. Upgrade pilot devices to 0.100.2 using the same method intended for production.
8. Confirm that each installation completes.
9. Confirm that PowerToys relaunches or can be started normally.
10. Verify that PowerToys reports version 0.100.2.
11. Run the functional checklist below under a representative user account.
12. Record failures, workarounds, and differences from the pre-update inventory.
13. Approve broader deployment only after the required workflows pass.

A manually created backup, where available and already validated by the organization, complements the automatic configuration backup introduced in 0.100.0. It should not be described as recoverable through a specific interface until that interface has been confirmed on the target build.

What should you test after the .NET 10 migration?​

The move to .NET 10 is not proof that an installation will fail or that extensions are incompatible. It is a reason to perform functional validation instead of assuming unchanged behavior.
Use this ordered verification pass:

1. Open PowerToys Settings and move between the pages for enabled utilities.
2. Exit PowerToys, start it again, and confirm that it loads normally.
3. If PowerToys normally runs at startup, sign out and back in and confirm that it starts as expected.
4. Invoke Command Palette several times and check that results appear normally.
5. Open Command Palette Settings and verify that expected extensions remain listed.
6. Run at least one representative action from each essential extension.
7. Test extension-specific settings or authentication-dependent actions where applicable.
8. Verify pinned Command Palette items and dock placement.
9. Leave Performance Monitor dock items active long enough to spot unusual memory growth, failed refreshes, or instability.
10. Invoke Shortcut Guide in applications where users depend on it.
11. Test operationally important Keyboard Manager remappings.
12. Confirm that required FancyZones layouts still work.
13. Check the PowerToys tray icon and any regularly used quick-access controls.
14. Compare the final configuration with the inventory recorded before updating.

The release information does not establish a universal third-party extension failure. Targeted testing is therefore more appropriate than a blanket block.

Why unattended updating needs separate validation​

PowerToys 0.100.0 attempts to make automatic updating more recoverable by backing up configuration files, relaunching PowerToys, displaying a clearer success notification, and restoring backed-up settings when corruption is detected.
Application recovery and deployment confirmation are not the same thing. An installer can complete without proving that PowerToys relaunched in the intended user session, every required utility loaded, extensions initialized, or dock configurations remained intact.
For managed deployment, record both installation completion and post-update application state. At minimum, verify the displayed version and launch PowerToys under a representative user account. If an extension is essential, include a real extension action in the acceptance test.
This emphasis reflects WindowsForum’s earlier user reports around PowerToys 0.90.1. Those reports described focused fixes for stability, workflow efficiency, and Command Palette concerns, showing why administrators should validate the corrective release rather than treating the first feature build as the automatic deployment endpoint.

Risks and recovery options​

The practical risk is the interaction among the new application foundation, saved configuration, extensions, docks, and update relaunch behavior—not the .NET 10 label by itself.
If PowerToys fails to reopen after updating:

1. Start PowerToys manually from the Start menu.
2. Open PowerToys Settings and check the installed version.
3. Restart Windows if PowerToys processes or extensions appear stuck.
4. Determine whether the failure affects the entire application, one utility, one Command Palette extension, or one dock item.
5. If your installed build provides a confirmed way to disable the affected component, temporarily disable it and retest PowerToys. The exact control should be verified in that build before it is included in a support script.
6. If your organization created a separate backup and has a tested restoration procedure, use that procedure when configuration is missing or unusable.
7. Use the bug-reporting mechanism available in the installed PowerToys build if the failure is reproducible, without assuming an unverified Settings path.
8. Record the PowerToys version, installation method, scope, affected component, and reproduction steps before escalating.

Disabling a component is only a workaround. Version 0.100.2 itself contains the documented fix for the Performance Monitor dock memory leak introduced in 0.100.1.
Avoid uninstalling PowerToys as the first troubleshooting step. First determine whether the issue is limited to an extension, dock, or utility. Immediate removal can make it harder to distinguish an application failure from a configuration-specific problem.

Frequently Asked Questions​

Do I need to install .NET 10 separately before updating?​

The verified release and installation information does not specify a separate manual .NET 10 prerequisite for an ordinary PowerToys update. Use the normal PowerToys update mechanism or WinGet rather than adding an unverified prerequisite to the procedure.

Is PowerToys 0.100.0 safe to deploy instead of 0.100.2?​

For a new deployment in the 0.100 release line, testing should target 0.100.2. Versions 0.100.1 and 0.100.2 were issued to correct problems identified after 0.100.0.

Does WinGet convert a per-user installation to machine-wide?​

No. PowerToys WinGet updates preserve the current installation scope. Verify the resulting scope during pilot testing, particularly when deployment tooling uses a different execution context from the eventual user.

Should I disable automatic updates?​

Not solely because of this release on an ordinary personal PC. In a managed environment, use the organization’s update controls and staging process when extensions, custom settings, docks, or relaunch behavior must be validated before broad deployment.
PowerToys 0.100.2 is the sensible destination for individual systems, while managed environments should give it a short, representative pilot. Success means more than a completed installer: PowerToys must report the correct version and retain the scope, settings, extensions, and workflows users need.

---

References​

1. Primary source: github.com
   
   

   Releases · microsoft/PowerToys · GitHub

   Microsoft PowerToys is a collection of utilities that supercharge productivity and customization on Windows - Releases · microsoft/PowerToys

   github.com
2. Independent coverage: newreleases.io
   
   

   microsoft/PowerToys v0.100.0 on GitHub

   New release microsoft/PowerToys version v0.100.0 Release v0.100.0 on GitHub.

   newreleases.io
3. Independent coverage: ithome.com
   
   

   微软 PowerToys 0.100 发布：拥抱.NET 10、新增扩展库，体积从 376MB 降至 272MB - IT之家

   微软 PowerToys 0.100 版本正式发布，核心升级是迁移至.NET 10 框架，安装包体积从 376MB 大幅缩减至 272MB，降幅达 28%。同时新增扩展库模块、全新快捷键指南 V2，并对显示器管理工具 Power Display 进行了优化。#微软 PowerToys# #Windows 效率工具#

   www.ithome.com
4. Independent coverage: forest.watch.impress.co.jp
   
   

   「PowerToys 0.100」が公開 ～ショートカット ガイド刷新、コマンド パレットには拡張機能ギャラリー - 窓の杜

   米Microsoftは6月9日（現地時間）、「Microsoft PowerToys」の最新版v0.100.0を公開した。「PowerToys 0.100」は「.NET 10」へのアップグレードでパフォーマンスと自動更新の信頼性を向上。インストーラーサイズも削減された。同梱モジュールでは「Shortcut Guide」が刷新されたほか、「コマンド パレット」で大規模なアップデートが行われている。

   forest.watch.impress.co.jp
5. Independent coverage: ntcompatible.com
   
   

   PowerToys 0.100 Fixes Auto-Updates and Rebuilds the Shortcut Guide for Faster Workflows

   PowerToys 0.100 completely rebuilds the Shortcut Guide to auto-detect active applications and display relevant shortcuts in a clean side pane. Command Palette finally gets a built-in extension gallery and independent dock configurations for every monitor, streamlining tool discovery and workflow...

   www.ntcompatible.com
6. Independent coverage: neowin.net
   
   

   New PowerToys update fixes memory leaks and other issues - Neowin

   Microsoft has released yet another update for PowerToys, this time addressing bugs in one of its best utilities.

   www.neowin.net