Find installation steps, troubleshooting tips, and the most common fixes for PowerToys before you contact support.
When a release behaves unexpectedly, start by checking the download source, your Windows version, and the system runtime requirements. Reinstalling or restarting after a failed update often resolves the most common issues.
If PowerToys is not launching correctly, try restarting Windows, reinstalling the latest update, and checking that the app has the required permissions to run. If the issue persists, use the contact page to share your details and the exact error message.
These are recurring problems real PowerToys users have reported in community discussions and the official issue tracker, along with the fixes that have worked for most people.
A common complaint is that dragging a window while holding Shift no longer snaps it into a configured FancyZones layout, especially right after an update.
Confirm FancyZones is enabled in Settings and that the drag activation option (hold Shift, or "always on" if you turned the modifier key off) matches how you're dragging. Restarting PowerToys often clears a stuck state. If zones still don't appear, delete the current layout and recreate it, since a corrupted layout file is a frequent cause.
Some users notice the PowerToys Run process gradually using more CPU or RAM over time, particularly with several plugins enabled.
Open Settings → PowerToys Run and disable plugins you don't actively use, especially indexing-heavy ones like Windows Search. Keeping PowerToys updated helps too, since performance issues like this are regularly patched. Restarting PowerToys from the system tray clears the problem temporarily if it comes back.
Remapped keys or shortcuts can silently stop functioning after the PC wakes from sleep, restarts, or when PowerToys auto-starts in the background at boot, with the remap only working again after PowerToys is manually restarted.
Reopen PowerToys from the system tray to reapply the remap, or toggle Keyboard Manager off and back on in Settings. If this happens often right after startup, try adding a short delay before Keyboard Manager loads, or check for a newer PowerToys version that addresses the timing issue.
Store, winget, and standalone installers can occasionally fail with a generic error code, often caused by a stuck Windows Installer process or a conflict with the currently installed version.
Close any running installer-related processes in Task Manager before retrying, download the standalone .exe from our download page instead of the Store, and right-click it to Run as administrator. If a specific release is known to be broken, install the previous version from the Older Versions list and update again once a fix is out.
After an update, a PowerToys shortcut can suddenly conflict with a shortcut Windows itself now reserves (for example, for Copilot or Snap layouts), which makes the PowerToys action silently stop firing.
Open PowerToys Settings and check the Shortcut Conflicts panel on the dashboard, which flags any clashing hotkeys, then reassign the affected shortcut to a key combination Windows isn't using.
Some users report PowerToys showing a "PowerToys ran into an issue" message, not launching at all, or not starting automatically at boot even though "Run at startup" is enabled.
End any existing PowerToys process in Task Manager, then relaunch it from the Start Menu. If it still won't open, reinstall using the latest installer from the download page, and re-enable "Run at startup" in General Settings afterward. Checking Windows Event Viewer for a PowerToys crash log can help pinpoint the cause if the problem repeats.