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.
- Our installer will install the following items:
- .NET 6.0.8 Desktop Runtime or a newer 6.0.x runtime.
- Microsoft Edge WebView2 Runtime bootstrapper. This will install the latest version.
- Microsoft Visual C++ Redistributable installer. This will install one of the latest versions available.
Microsoft PowerToys GitHub releases page, click on Assets at the bottom to show the files available in the release. Please use the appropriate the PowerToys installer that matches your machine's architecture. For most people, it is x64.
- For x64 processors (most common): PowerToysSetup-0.62.0-x64.exe
- For ARM64 processors: PowerToysSetup-0.62.0-arm64.exe
This is our preferred method.
Install from the Microsoft Store's PowerToys page. You must be using the new Microsoft Store which will be available for both Windows 11 and Windows 10.
Download PowerToys from WinGet. To install PowerToys, run the following command from the command line / PowerShell:
winget install Microsoft.PowerToys -s wingetThere are community driven install methods such as Chocolatey and Scoop. If these are your preferred install solutions, this will have the install instructions.
This project welcomes contributions of all types. Help spec'ing, design, documentation, finding bugs are ways everyone can help on top of coding features / bug fixes. 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 will 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 have the right to, and actually do, grant us the rights to use your contribution.
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 releasing three new PowerToys.
Highlights
- New utility: Screen Ruler is a quick and easy way to measure pixels on your screen.
- New utility: Quick Accent is an easy way to write letters with accents. Thanks @damienleroy!
- New utility: Text Extractor works like Snipping Tool, but copies the text out of the selected region using OCR and puts it on the clipboard. Thanks @TheJoeFin!
- PowerToy Run ships with a new Plugin letting you search in past query results. Thanks @jefflord!
- The Text Extractor utility fails to recognize text in some cases on ARM64 devices running Windows 10.
- After installing PowerToys, the new Windows 11 context menu entries for PowerRename and Image Resizer might not appear before a system restart.
- There are reports of users who are unable to open the Settings window. This is being caused by incompatibilities with some applications (RTSS RivaTuner Statistics Server and MSI AfterBurner are known examples of this). If you're affected by this, please check the linked issue to verify if any of the presented solutions works for you.
- Added a new utility: Screen Ruler.
- Added a new utility: Quick Accent. Thanks @damienleroy!
- Added a new utility: Text Extractor. Thanks @TheJoeFin!
- Upgraded the Windows App SDK runtimes to 1.1.4.
- Fixed a bug causing the border to linger when closing an Outlook popup window.
- Fixed the HSB color format to correctly track HSV instead of HSL.
- Fixed an issue where the zoom factor wasn't reset when reopening the zoom window. Thanks @FWest98!
- Removed the button to open Settings from the FancyZones Editor, as it was opening behind the overlay.
- Changed the Highlight distance control to a slider in the FancyZones Editor, to address accessibility issues with screen readers.
- Fixed an issue where the FancyZones Editor would duplicate or edit the wrong layout.
- Fixed an issue that caused canvas layout width/height to be changed without even opening the layout in FancyZones Editor.
- Quality of life improvements to Developer Files preview, including a progress bar while loading, performance improvements, an improved dark mode, and logs. Thanks @Aaron-Junker!
- Fixed possible WebView related vulnerabilities in the SVG and Markdown handlers.
- Fixed some race conditions in Developer Files preview causing the loading bar to hang.
- Added localization support to the Developer Files preview messages.
- It's now possible to configure default color for Stl Thumbnails. Thanks @pedrolamas!
- Added an option to format JSON and XML files before rendering. Thanks @davidegiacometti!
- Fixed an issue that was generating a silent crash when the context menu was triggered when not selecting any file or folder. (This was a hotfix for 0.61)
- Improved performance when loading a big number of files.
- Fixed a specific case in which PowerRename tried to rename a file to an empty string.
- The UI now shows when a file can't be renamed due to its name being too long or containing invalid characters.
- Added a fix to the VSCodeWorkspaces plugin to better support portable installations. Thanks @bkmeneguello!
- The Folder plugin now expands
%HOMEPATH%correctly. - Fixed a case where a previous result was being activated when searching for new results. Added a setting to better control input throttling. Thanks @jefflord!
- Added support for port numbers in the URI plugin. Thanks @KohGeek!
- Fixed query errors when the search delay option was turned off.
- New History plugin to search for old search results. Thanks @jefflord!
- Changed the default TimeDate activation keyword to
), as queries starting by(are expected as Calculator global queries, and added information in Settings so users know that some activation keywords may conflict with normal usage of some plugins when trying to do a global query. Thanks @htcfreek! - The Unit Converter plugin updated its UnitsNet dependency and now supports plural units. Thanks @FWest98!
- Improved the validation logic in the Calculator plugin. Thanks @htcfreek!
- Improved: Clean up old install folders and logs at startup. Thanks @davidegiacometti!
- Image and phrasing adjustments.
- Icon and image updates for the new utilities. Thanks @niels9001!
- Fixed the Narrator shortcut to include the newly added Control key.
- Fixed a regression that was causing the PowerToys shortcut to be deleted on update. (This was a hotfix for 0.61)
- Updated the .NET dependency to 6.0.8.
- Fixed wrong links to installers in README. Thanks @unuing!
- Removed FXCop leftovers. Thanks @CleanCodeDeveloper!
- Added version number to missing binaries and added a CI script to verify that all binaries have their version numbers set correctly.
- Updated a dependency to fix building on Visual Studio 17.3 C++ tools.
- Fixed and reactivated the CI unit tests for FancyZones.
- Cleaned up and removed dead code from PowerRename code base.
- Added a script for verifying the solution targets match the expected CPU architectures. Thanks @snickler!
- Obsolete package Castle.Core was removed. Thanks @davidegiacometti!
- Language typos were corrected across the PowerToys assets. Thanks @pea-sys, @eltociear and @obairka!
For v0.63, we'll work on below:
- Environment Variables Editor PowerToy
- GPO policies for PowerToys
- 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 over 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.