How to use PowerToys | Downloads & Release notes | Contributing to PowerToys | What's Happening | Roadmap
| Architecture | Solution (Main) | Solution (Stable) | Installer (Main) |
|---|---|---|---|
| x64 | |||
| ARM64 | Currently investigating | Issue #490 |
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 docs.microsoft.com!
- Windows 11 or Windows 10 v1903 (18362) or newer.
- Our installer will install the following items:
- .NET Core 3.1.22 Desktop Runtime or a newer 3.1.x runtime. This is needed currently for the Settings application.
- .NET 5.0.13 Desktop Runtime or a newer 5.0.x runtime.
- Microsoft Edge WebView2 Runtime bootstrapper. This will install the latest version.
Microsoft PowerToys GitHub releases page, click on Assets at the bottom to show the files available in the release and then click on PowerToysSetup-0.55.0-x64.exe to download the PowerToys installer.
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 are continuing our progress toward getting PowerToys ARM64 ready, fix some top issues and new utilities. Work from last month helped us enable us to upgrade the code base to .NET 5 and next month onward to .NET 6. This will provide stability and speed improvements.
We're also extremely excited to bring on 3 new PowerToy utilities.
- File Explorer add-on: Developer files for preview pane. This should add about 150 file extensions total. We are using the Monaco Editor to power this experience. Thanks @aaron-junker!
- File Explorer add-on: STL file format thumbnail generation! Since STL is a common 3D file format, this allows a quick visual check. Thanks @pedrolamas! Preview pane support is already in Windows.
- Mouse Utility: Crosshair over pointer via Ctrl+Alt+P. This feature was co-developed with the accessibility team at Microsoft. When the team told us about the idea and described trying to find your cursor by looking through a straw, we knew we could leverage code from the other mouse utilities to quickly enable this feature. Below is a quote from one of the testers with a rough validation build:
"This will change my life and allow me to use any PC without constantly losing the pointer. This is huge! I will be able to work at my normal speed again. It is a total game changer for people with visual field impairments!" – Joanna A.
- We would love to directly say THANK YOU. Filing issues and feature requests takes time and we greatly appreciate it. You help us quickly diagnose, spot trends, and prioritize. We love when people fix bugs and develop new PowerToys every little bit does really help.
- @edwinzap really helped us validate translation issues when our localization system was in transition.
- @bdoserror quickly pointed out a release note error
- .NET runtime is now on 5, our next release will be upgraded to .NET 6. Moving to .NET 5 and then 6 helped reduce our moving parts in a single release so we went this route. Why this is important is this is one of the major work items needed for ARM64 support. In addition, this should help provide a speed boosts once we are on .NET 6.
- @jsoref's spelling plugin help
- Fixed one of two borders showing incorrectly bugs.
- Border defaults to OS accent color now. Thanks @davidegiacometti
- Reduced CPU / GPU activity. Not done improving, we know we can do better.
- Bug fixed to not lose zones after update
- Fixed editor margin issue for Chinese language. Thanks @niels9001
- GCode thumbnails now have transparency. Thanks @pedrolamas
- New Utility - Developer files for File Explorer preview pane. This should add about 150 file extensions total. We are using the Monaco Editor to power this experience. Thanks @aaron-junker!
- New Utility - STL thumbnails added! Preview pane support is already in Windows. Thanks @pedrolamas!
- Fixed bug with too much meta data. Thanks @CleanCodeDeveloper
- Fixed bug resizing bug for constant height while maintaining aspect ratio. Thanks @CleanCodeDeveloper
- New Utility - Crosshair over pointer via Ctrl+Alt+P. This feature was co-developed with the accessibility team at Microsoft. Thanks @niels9001 for helping with the icon!
- Files are sorted now how File Explorer sorts.
- Improved speed and fixed bugs with Window walker plugin. Thanks @htcfreek
- Window Walker will now show path of elevated apps. Thanks @davidegiacometti
- Added UEFI command to system commands. Thanks @htcfreek
- Fixed crashing bug in EnvironmentHelper class. Thanks @htcfreek
- Fix URI plugin bug with
^:. Thanks @franky920920 - VS Code plugin not showing workspaces with latest Code version was corrected. Thanks @ricardosantos9521
- Fixed bug that caused plugins to not load. Thanks @davidegiacometti
- Fixed crash in Uri plugin and Web search plugin. Thanks @cyberrex5!
- Fixed a regression with settings being reset when moving from admin to non-admin
- Fixed crashing bug with Zoom and other clients. We found someone we could remotely debug with and identify the actual crashing part.
- Change of behavior: When leaving a meeting, VCM will now leave your microphone in the state it was. This mimics behavior of applications if VCM was not present.
- Change of behavior: When you exit PowerToys, your current microphone state will remain.
We'd like to directly mention certain contributors (in alphabetical order) for their continued community support this month and helping directly make PowerToys a better piece of software. @Aaron-Junker, @bdoserror, @CleanCodeDeveloper, @cyberrex5, @davidegiacometti, @edwinzap, @franky920920, @jay-o-way, @jsoref, @niels9001, and @ricardosantos9521
For v0.56, we plan on finishing up the .NET upgrade path to 6. This will require development to migrate to Visual Studio 2022. We are also shifting back to a continuous version number system versus Odd for main and Even for experimental releases.
- .NET 6 upgrade to all available surfaces
- A Dialog on update making you aware of what has changed.
- 'Shake to activate' find my mouse
- PowerToy Run plugin improvements
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.
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.