So this isn't PowerToys 0.102 yet. It's an early version of what 0.102 could look like, built from the branch that stable releases normally come from rather than the busier main branch. Testers and IT admins who track PowerToys builds should know that difference before they install it.
What "built from stable" means here
The release notes list changes relative to v0.101.2781.0, the previous published preview built from main. Microsoft also says that features already available in that preview are retained unless noted under Differences from the previous preview.
NT Compatible says the build stands out because it is the first 0.102 build built on the stable branch instead of the usual main track. In plain terms, a release branch is where features stop getting added and stabilization starts. A stable-branch preview usually means the team is checking what it plans to ship, though Microsoft hasn't given a 0.102 ship date.
Everything carried over from v0.101.2781.0 is still here. That includes the Command Palette's fuzzy Settings search, the optional Quick Access Shelf with recent commands, the new Dock focus-cycling behavior and FancyZones mouse-wheel layout switching. Those features came in the earlier preview and aren't new in this build.
Section summary: This is a preview. It's the first 0.102 build cut from the stable branch, and it keeps the features from the previous main-based preview, with one exception covered below.
Command Palette gets most of the changes
As in recent preview builds, Command Palette gets most of the work. The release highlights:
- Layout previews: Command Palette now shows visual previews when choosing full or compact layouts. The full notes say related options were also moved into settings cards to make layout settings easier to find. NT Compatible says that PR #51007, by contributor Jiří Polášek, replaces that toggle with a segmented control showing live previews of each layout.
- Settings that survive restarts: Microsoft says it made dock pins and other settings more reliable across restarts. According to the detailed notes, the cause was overlapping settings saves that could overwrite newer changes. If your pinned Dock items kept disappearing after a reboot, this is the fix to look for.
- Shell icon fixes: The build fixed missing or generic Shell icons and stale icon-cache entries. The notes say this covers concurrent icon loading and refreshing cached icons after Windows appearance-metric changes.
- Packaged-app icons: Microsoft improved packaged-app icons for language, size, and contrast variants. This should help on localized systems and with high-contrast themes.
- Shortcut icons: The update preserved shortcut icon artwork, padding, and configured fallbacks.
- Settings search highlighting: The palette kept Settings search highlights animated independently of page-transition animations. If you turn off page-transition animations, for accessibility or because you don't like motion, the search result you jumped to still flashes so you can find it.
Most of this is reliability work. The icon fixes clean up blank and generic tiles, and the settings-save fix deals with a race condition that could quietly throw away changes. Neither changes what Command Palette can launch.
Section summary: Layout previews are the one visible change. Settings persistence and icon rendering account for most of the practical improvement.
Universal CRT and a smaller PowerRename package
Two changes are under the hood. Under "General," the release notes say PowerToys reduced duplicated native runtime code by using the Windows-provided Universal CRT where supported. Two limits matter: Microsoft says static VC++ runtime linkage is still used, and New+ template behavior hasn't changed. This isn't a full change to how PowerToys links its runtime, and "where supported" is part of the claim.
PowerRename loses unused prebuilt Boost.Regex libraries from the installer. Microsoft says the "Use Boost library" option and regular-expression behavior are unchanged, so existing rename patterns should keep working. Warp2Search describes both changes together as reducing installer size by implementing a Hybrid CRT shift and removing unused Boost.Regex DLLs. NT Compatible puts the savings at about 6 to 7 MB. Microsoft's release notes don't give a size figure, so treat that number as the outlet's estimate.
Section summary: Installs should be somewhat smaller with less duplicated runtime code. Microsoft says PowerRename features don't change.
One feature is missing compared with the last preview
The stable branch doesn't include everything from main. The "Differences from the previous preview" section names one item: PowerDisplay's Copy monitor diagnostics action, added in PR #48209, isn't in this build. Microsoft says the stable branch keeps an earlier removal of that action. This isn't a new removal. It's a difference from the previous main-based preview.
If you installed v0.101.2781.0 and used that action, it will be gone after you move to this build. Warp2Search notes more broadly that this build does not include some features from the main track.
Notes for extension developers
Command Palette extension authors should watch for one behavior change. In the updated Command Palette Toolkit, calling GetThumbnail(missingPath, jumbo: true) now returns null instead of a generic unknown-file icon. That matches how small icons already behave. Microsoft says extensions built on the updated Toolkit should supply their own fallback when needed. If your extension shows large thumbnails for files that might no longer exist, add a null check.
The development section lists more changes:
- Command Palette's native Windows Run-history dependency was replaced with a managed implementation. Recent-command history is kept and packaging is simpler.
- Command dispatch now keeps the originating page and provider context. Microsoft describes this as preparation for future Dock flyouts and says no new flyout ships in this release.
- Run-page environment-variable tests and cache-rebuild tests were stabilized.
- WinRT source generation for the shared hotkey settings hook was corrected, and new CsWinRT1028 diagnostics now fail the build.
The notes also record that the checked-in release train moved from 0.101 to 0.102 with the version epoch unchanged. That change was committed directly to the stable branch (commit 5de238aab86e) rather than through a separate pull request, and it's listed under "Changes needing final review."
Installers and SHA-256 hashes
The release includes per-user and machine-wide installers for x64 and ARM64:
| Scope / architecture | Filename | SHA-256 |
|---|---|---|
| Per user, x64 | PowerToysUserSetup-0.102.2803.0-x64.exe | 1A6737004C9E57CC0FB3D02A416397383DE7FCE58F1E3986D07671C507DC01A3 |
| Per user, ARM64 | PowerToysUserSetup-0.102.2803.0-arm64.exe | 6874D6F4F5AE827E3599117FFFCF19065470AE3A1A60449F8FB07F15D5BB588A |
| Machine wide, x64 | PowerToysSetup-0.102.2803.0-x64.exe | 8FD552ACA7D2A94310F7DB1E95378C6A795370463982F6D8886394D29365B6BC |
| Machine wide, ARM64 | PowerToysSetup-0.102.2803.0-arm64.exe | A5296A96E7230231F6A359583C63A47B3C83CFA49D343F5FBC3728ED2B574378 |
To check a download before running it, use PowerShell's built-in Get-FileHash cmdlet. It uses SHA-256 by default:
- Open PowerShell in the folder where you saved the installer.
- Run
Get-FileHash .\PowerToysSetup-0.102.2803.0-x64.exe, using the filename you actually downloaded. - Compare the output with the table. If they don't match, delete the file and download it again.
That's standard Windows practice, not a step Microsoft lists in the release notes. On managed fleets, the machine-wide installer is usually the one to use. The per-user installer suits test machines where you don't want elevation.
Should you install it?
For most people, no. Wait for the final 0.102 release. If you test PowerToys on a spare machine, or you were affected by Dock pins disappearing or broken Command Palette icons, this build is a reasonable way to check the fixes before stable ships.
Don't expect the larger 0.102 plans yet. NT Compatible reports that the 0.102 milestone aims to modernize several utilities with WinUI 3 and expand Command Palette with tabs plus JavaScript/TypeScript extensions. None of those items are in this build's release notes. Whether they arrive in a later 0.102 preview or move to a later release is still open. It's also not yet known how quickly more stable-branch previews will follow, or what else might be held back from main.
Bottom line: v0.102.2803.0 is a small, reliability-focused preview. It's notable mainly as the first 0.102 build from the stable branch, which suggests the final 0.102 release is getting closer.