How to use PowerToys | Downloads & Release notes | Contributing to PowerToys | What's Happening | Roadmap
| Architecture | Solution (Main) | Solution (Stable) | Installer (Main) |
|---|---|---|---|
| x64 | |||
| ARM64 |
Microsoft PowerToys is a set of utilities for power users to tune and streamline their Windows experience for greater productivity. For more info on PowerToys overviews and how to use the utilities, or any other tools and resources for Windows development environments, head over to learn.microsoft.com!
- Windows 11 or Windows 10 version 2004 (code name 20H1 / build number 19041) or newer.
- x64 or ARM64 processor
- Our installer will install the following items:
- Microsoft Edge WebView2 Runtime bootstrapper. This will install the latest version.
Go to the Microsoft PowerToys GitHub releases page and click on Assets at the bottom to show the files available in the release. Please use the appropriate PowerToys installer that matches your machine's architecture and install scope. For most, it is x64 and per-user.
| Description | Filename | sha256 hash |
|---|---|---|
| Per user - x64 | PowerToysUserSetup-0.77.0-x64.exe | 3485D3F45A3DE6ED7FA151A4CE9D6F941491C30E83AB51FD59B4ADCD20611F1A |
| Per user - ARM64 | PowerToysUserSetup-0.77.0-arm64.exe | 762DF383A01006A20C0BAB2D321667E855236EBA7108CDD475E4E2A8AB752E0E |
| Machine wide - x64 | PowerToysSetup-0.77.0-x64.exe | 1B6D4247313C289B07A3BF3531E215B3F9BEDBE9254919637F2AC502B4773C31 |
| Machine wide - ARM64 | PowerToysSetup-0.77.0-arm64.exe | CF740B3AC0EB5C23E18B07ACC2D0C6EC5F4CE4B3A2EDC67C2C9FDF6EF78F0352 |
This is our preferred method.
Install from the Microsoft Store's PowerToys page. You must be using the new Microsoft Store which is available for both Windows 11 and Windows 10.
Download PowerToys from WinGet. Updating PowerToys via winget will respect current PowerToys installation scope. To install PowerToys, run the following command from the command line / PowerShell:
winget install Microsoft.PowerToys -s wingetwinget install --scope machine Microsoft.PowerToys -s wingetThere are community driven install methods such as Chocolatey and Scoop. If these are your preferred install solutions, you can find the install instructions there.
There is a collection of third-party plugins created by the community that aren't distributed with PowerToys.
This project welcomes contributions of all types. Besides coding features / bug fixes, other ways to assist include spec writing, design, documentation, and finding bugs. We are excited to work with the power user community to build a set of tools for helping you get the most out of Windows.
We ask that before you start work on a feature that you would like to contribute, please read our Contributor's Guide. We would be happy to work with you to figure out the best approach, provide guidance and mentorship throughout feature development, and help avoid any wasted or duplicate effort.
Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you grant us the rights to use your contribution and that you have permission to do so.
For guidance on developing for PowerToys, please read the developer docs for a detailed breakdown. This includes how to setup your computer to compile.
Our prioritized roadmap of features and utilities that the core team is focusing on.
In this release, we focused on new features, stability and improvements.
Highlights
- New utility: Command Not Found PowerShell 7.4 module - adds the ability to detect failed commands in PowerShell 7.4 and suggest a package to install using winget. Thanks @carlos-zamora!
- Keyboard manager does not register low level hook if there are no remappings anymore.
- Added support for QOI file type in Peek. Thanks @pedrolamas!
- Added support for loading 3rd-party plugins with additional dependencies in PowerToys Run. Thanks @coreyH!
- Bump WPF-UI package version to fix crashes related to theme changes. (This was a hotfix for 0.76)
- Fixed typo in version change notification. Thanks @PesBandi!
- Code improvements and fixed silenced warnings introduced by upgrade to .NET 8.
- Update copyright year for 2024.
- Added setting to disable warning notifications about detecting an application running as Administrator.
- Show notification when elevated app is in the foreground but AlwaysOnTop is running non-elevated.
- Added a new utility: A Command Not Found PowerShell 7.4 module. It adds the ability to detect failed commands in PowerShell 7.4 and suggest a package to install using winget. Thanks @carlos-zamora!
- Fixed issue causing Environment Variables window not to appear as a foreground window.
- Fixed snapping specific apps (e.g. Facebook messenger). (This was a hotfix for 0.76)
- Fixed behavior of Move newly created windows to current active monitor setting to keep maximize state on moving. Thanks @quyenvsp!
- Fixed issue causing FancyZones Editor layout window to be zoned.
- Fixed WebView2 based previewers issue caused by the latest WebView update. (This was a hotfix for 0.76)
- Fixed issue causing settings not to be preserved on update.
- Fixed crash caused by WpfUI ThemeWatcher. (This was a hotfix for 0.76)
- Do not register low level hook if there are no remappings.
- Improved icon and title showing for previewed files. Thanks @davidegiacometti!
- Added QOI file type support. Thanks @pedrolamas!
- Fixed results list UI element height for different maximum number of results value. (This was a hotfix for 0.76)
- Fixed icon extraction for .lnk files. (This was a hotfix for 0.76)
- Fixed search box UI glitch when FlowDirection is RightToLeft. (This was a hotfix for 0.76)
- Fixed theme setting. (This was a hotfix for 0.76)
- Fixed error reporting window UI issue. Thanks @niels9001!
- UI improvements and ability to show/hide plugins overview panel. Thanks @niels9001!
- Allow interaction with plugin hints. Thanks @davidegiacometti!
- Switch to WPF-UI theme manager. Thanks @davidegiacometti!
- Fixed issue causing 3rd party plugin's dependencies dll not being loaded properly. Thanks @coreyH!
- Added configurable font sizes. Thanks @niels9001!
- Changed the text color of plugin hints to improve the contrast when light theme is used. Thanks @davidegiacometti!
- Fix scientific notation errors in Calculator plugin. Thanks @viggyd!
- Add URI/URL features to Value generator plugin. Thanks @htcfreek!
- Moved Greek specific characters from All language set to Greek. Thanks @PesBandi!
- Add more mathematical symbols. Thanks @kevinfu2!
- Fixed exception occurring on theme change.
- Fix "What's new" icon. Thanks @niels9001!
- Remove obsolete UI Font icon properties. Thanks @Jay-o-Way!
- OOBE UI improvements. Thanks @Jay-o-Way!
- XAML Binding improvements. Thanks @Jay-o-Way!
- Fixed crash caused by ThemeListener constructor exceptions.
- Improved docs for adding new languages to monaco. Thanks @PesBandi!
- Update README.md to directly state x64 & ARM processor in requirements.
- Added Scoop plugin to PowerToys Run thirdPartyRunPlugins.md docs. Thanks @Quriz!
- Adopted XamlStyler for PowerToys Run source code. Thanks @davidegiacometti!
- Consolidate Microsoft.Windows.SDK.BuildTools across solution.
- Upgraded Boost's lib to v1.84.
- Upgraded HelixToolkit packages to the latest versions.
- Updated sdl baselines.
For v0.78, we'll work on the items below:
- Language selection
- Automated UI testing through WinAppDriver
- Develop support for Desired State Configuration
- Modernize and refresh the UX of PowerToys based on WPF. Here's the Work in Progress preview for "Color Picker":
- Stability / bug fixes
The PowerToys team is extremely grateful to have the support of an amazing active community. The work you do is incredibly important. PowerToys wouldn’t be nearly what it is today without your help filing bugs, updating documentation, guiding the design, or writing features. We want to say thank you and take time to recognize your work. Month by month, you directly help make PowerToys a better piece of software.
This project has adopted the Microsoft Open Source Code of Conduct.
The application logs basic telemetry. Our Telemetry Data page (Coming Soon) has the trends from the telemetry. Please read the Microsoft privacy statement for more information.