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.
• .NET Core 3.1.22 Desktop Runtime or a newer 3.1.x runtime. The installer will handle this if not present.

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.53.1-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 winget

There 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.

We hope everyone has had a wonderful December 2021. The PowerToys community has been busy with a bunch of improvements. We're still working on improving the installer but this should drastically improve things. 3 things you will want to check out are G-code support in file explorer preview pane and thumbnails, the new web search plugin from PowerToys Run via ?? action phrase, and the new Always on Top utility via Win+Ctrl+T.

@Aaron-Junker also has done some great progress on implementing developer file preview pane via the Monaco engine from Visual Studio Code.

• The new installer currently has a visual quirk when upgrade if you have a custom install path. It will show the default install path but it will actually overwrite the current location. We are investigating how to fix this.

• Welcome to the family! With a quick Win+Ctrl+T, the window in focus is toggled to be on top. Toggle again, and it reverts back to normal.

• HEX input improvements for adjust color menu including support for hex code without hashtag and short hex code like #CF0. Thanks @htcfreek!
• Better bottom right screen detection for overlay

• Increased negative space margin
• Fix for not snapping child windows
• Fix for clearing keyboard focus on editor launch
• Fix to improve overlays to reduce brightness and hide numbers. Thanks @davidegiacometti

• Added G-code support for thumbnails and preview pane. Thanks @pedrolamas

• Fixed regression from Metadata tag removal of ColorSpace. Thanks @CleanCodeDeveloper

• Row highlighting + preview support now implemented. Thanks @niels9001
• Fixed AltGR input issue
• Improved folder renaming support
• Opens on active monitor

• Web searching has been added! ?? What is the answer to life will go to your favorite search engine via your browser. You can change the default action key too! Thanks @cyberrex5 for primary implementation and @franky920920 and @htcfreek for supporting
• VS Code workspace improvements. Thanks @ricardosantos9521
• Binary and Hex number support. Thanks @gsuberland
• Ability to use factorials in calculations
• PT Run will not show in Window Walker results anymore. Thanks @davidegiacometti
• Fix log / ln calculations
• Fix to make previous results clear
• Fix to detect symlinks and prevent recursive loops
• Fix for trackpad scrolling being too fast
• Removed unneeded nuget package. Thanks @ChaseKnowlden
• Better detection for if a packaged app can be elevated
• Improve crash resiliency for Program plugin. Thanks @davidegiacometti
• Improved Windows setting results. Thanks @htcfreek
• Fixed a bug where some similar activation phrases aren't working as expected. Thanks @htcfreek and @cyberrex5.

• Disabled by default as this requires elevation to register the virtual camera.
• Changed (default) hotkey for mute camera & microphone from Win+N to Win+Shift+Q to not conflict with a Windows 11 keyboard shortcut

• Multiple accessibility, layout, image, string and icons fixes. Thanks @niels9001

• Improved mutex support to prevent multiple PT Run instances from running

• NOTE: The new installer currently has a visual quirk when upgrade if you have a custom install path. It will show the default install path but it will actually overwrite the current location. We are investigating how to fix this.
• Large progress toward user based installing vs machine wide. Upgrade scenario still needs additional work.
• Removed custom bootstrapper and now are using a WiX bundle.
• Removed unused image assets that were still being shipped. Thanks @niels9001

• Setting WinUI3 proof-of-concept and validate we do need at least one more feature, elevation support from WinUI 3 unpackaged applications.

• New YAML based pipeline for building our signed installer. This will allow us to consolidate our CI to use same file. This was critical for us to unblock ARM64 and .NET 6 migration.
• Our submodules will no longer auto fetch to prevent locking issues. If you want a refresher on how to do this, head to our dev docs
• Localization system shifted to Touchdown from CDPx. This should remove many of the loc issues.
• Consolidated a lot of the naming of EXEs and DLLs along with projects
• Update to spell checker. Thanks @jsoref
• /dup response has been added
• /reportbug /bugreport will ask for a "report bug" zip

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, @ChaseKnowlden, @CleanCodeDeveloper, @cyberrex5, @davidegiacometti, @franky920920, @gsuberland, @jay-o-way, @jsoref, @niels9001, and @ricardosantos9521

For v0.55, we'll work on adding more stability in with VCM and getting dev file preview pane added in so we get 150 file types :)

• We are working to heavily reduce / remove the UAC prompt over the next few releases on install. This is a big shift so it is spanning multiple releases so we can isolate issues if they do occur. Work is tracked in #10126
• Getting the dev file preview pane work integrated. (Monaco Editor)
• .NET 6 upgrade to all available surfaces
• Find my mouse feature, accessibility cross-hair

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.