PowerToys: Backup, Diagnostics, and Plugins for Windows Power Users

PowerToys quietly hides a few genuinely time-saving features behind its polished dashboard — tools for backing up your entire configuration, automatic diagnostic logs you can read yourself, and an easy plugin system that turns the launcher into a Swiss Army knife. These three capabilities alone can save hours when moving between machines, troubleshooting odd behavior, or extending PowerToys’ reach — and they’re far easier to use than most people realize.

Background​

PowerToys has evolved from a niche utility set into a mainstream productivity toolkit for Windows power users. What started as a few small utilities is now a suite of more than a dozen modules — FancyZones, PowerToys Run (and its successor, Command Palette), Image Resizer, Keyboard Manager, Text Extractor, and more — that collectively address the gaps power users bump into every day. The project is open-source and actively maintained, which means features land fast and the community contributes plugins, bug reports, and workflow improvements.
Three “secret” features stand out because they’re small, practical, and frequently overlooked:

• A built-in backup/restore flow that exports all user settings into a .ptb backup file.
• Persistent diagnostic logs per utility that you can inspect to trace errors without reinstalling the suite.
• A plugin system for the launcher that allows third-party extensions to add commands like SpeedTest, Everything search, ChatGPT, and more.

Below is a practical, hands-on deep dive into each feature: what it does, exactly where it lives on disk, how to use it step-by-step, measurable benefits, and the caveats and risks you should consider before putting these tricks into production workflows.

---

Overview: Why these three matter​

Short version: once you know them, you stop rebuilding your environment by hand, you can diagnose problems faster, and you can make the launcher do tasks that would otherwise require separate apps.

• Backup and restore eliminates repetitive setup steps when reinstalling Windows, moving to a new machine, or syncing preferences across devices. The backup is a single file you can store in OneDrive or a shared folder and restore from anywhere. (windowsloop.com)
• Diagnostic logs make troubleshooting deterministic. Logs are generated per-module and live in local app data folders; reading them reveals stack traces, errors, and which subcomponent is failing — far easier than guessing and reinstalling everything. (github.com, windowscentral.com)
• Plugins turn the launcher from “search and run” into a programmable control surface. Install a plugin, and you can run speed tests, search Everything, query ChatGPT, control Spotify, or trigger winget installs from the same fast interface. (github.com, gilbertalgordo.github.io)

Each of these is low-friction to adopt and high-impact for daily productivity.

---

1) Backup PowerToys settings so your features are the same across all of your PCs​

What it does and why it’s useful​

PowerToys exposes a Backup & Restore control in the General settings that writes all (or most) of the suite’s configuration into a timestamped backup file — a handy single-file snapshot (.ptb). Use it to transfer your settings between machines, keep a rolling archive before you make big config changes, or place the backup in cloud storage so every PC can restore from the same baseline. This is especially valuable for multi-monitor FancyZones layouts, keyboard remaps, and other nuanced customizations that are tedious to rebuild. (makeuseof.com, windowscentral.com)

Where the backup lives by default​

When you click Backup in PowerToys, the default target directory is:
C:\Users\<username>\Documents\PowerToys\Backup
You can change this path from the General > Backup & restore area — moving it to OneDrive or another shared folder is recommended if you want truly cross-device restores. (windowsloop.com, thewindowsclub.com)

Step-by-step: Back up and restore (practical)​

• Open PowerToys (use the system tray icon or search “PowerToys” in Start).
• Click General in the left column.
• Scroll down to the “Backup & restore” section.
• (Optional) Change the backup folder by clicking Browse and selecting a OneDrive or shared folder.
• Click Backup. The app creates a timestamped .ptb file and lists the most recent backups in the UI.
• To restore: on the target PC, open PowerToys → General → Backup & restore → Browse to the backup folder and click Restore. PowerToys will restart and apply settings.

Advanced: Manual copy and per-module restore​

PowerToys stores individual utility configuration files in %LOCALAPPDATA%\Microsoft\PowerToys. If you prefer to selectively move settings (for example, only FancyZones, Keyboard Manager, or Workspaces), you can close PowerToys, copy the relevant JSON files from the local app data path, and paste them on the new machine. Be aware that some utilities maintain their own subfiles (FancyZones layouts live in zones-settings.json under the FancyZones subfolder), so manual migration requires care. (umatechnology.org, windowscentral.com)

Known limitations and gotchas​

• The built-in backup covers “most” settings, but some items (historically Workspaces or certain per-module state files) have been excluded or handled inconsistently; several GitHub issues track improvements to ensure full workspace backups. If you rely on Workspaces heavily, verify that workspaces.json or the expected files are included in your backup before wiping the original PC. Treat backup/restore as “mostly complete” and verify critical modules after a restore. (github.com)
• Version mismatch can bite: restore on the same PowerToys version when possible. Restoring a backup created by a newer release into an older client may produce partial or no effect for new settings introduced after the older release. When moving between PCs, install the same PowerToys version on both machines first. (betanews.com)

---

2) Troubleshoot with diagnostic logs — fix tools that aren’t working without reinstalling everything​

What the logs are and where to find them​

PowerToys writes module-specific logs under the local app data folder:

• Primary logs: %LOCALAPPDATA%\Microsoft\PowerToys\<ModuleName>\Logs
• Low-privilege/preview-handler logs: %USERPROFILE%\AppData\LocalLow\Microsoft\PowerToys

Each utility usually has its own subfolder and a Logs directory that collects plain-text log files you can open with Notepad. The GitHub logging docs explicitly document these locations and the BugReportTool aggregates them when needed. (github.com)

Why this matters (real-world troubleshooting)​

Rather than guessing whether FancyZones, PowerToys Run, or the File Explorer add-ons are failing, open the log files and look for:

• Recent ERROR or WARN lines
• Exception stack traces (they often include the module name and the failing code path)
• Timestamps that match your repro attempt

Logs often show whether an issue is internal to a PowerToys module, caused by a permission problem, or triggered by a third-party app (for example, antivirus or a shell extension). Reading the logs lets you escalate precisely or post a minimal reproducible report to the GitHub issues page. (windowscentral.com, github.com)

How to gather logs for a bug report​

• Reproduce the problem (e.g., try to trigger the issue in FancyZones).
• Close PowerToys to flush logs, or run the BugReport tool (PowerToys includes a “Report a bug” helper that captures logs automatically).
• Open %LOCALAPPDATA%\Microsoft\PowerToys and navigate to the module folder then Logs.
• Copy the latest log(s) and paste them into a new text file or compress them for upload.
• If asked on GitHub for logs, include the specific module logs and a short reproduction sequence.

Security and privacy considerations​

• Logs can contain file paths, usernames, and occasionally snippets of command-line arguments. Review logs for any sensitive data before sharing them publicly. Remove or redact secrets (API keys, personal file paths you don’t want to leak) when posting logs to public issue trackers. (github.com)
• Keep in mind that logs accumulate; periodically clear them or rotate them if disk space is a concern, especially in multi-user environments. Some GitHub threads show complaints about log proliferation and attention to log folder management. (github.com)

---

3) Add plugins to PowerToys for more functionality — extend the launcher into a power user hub​

What plugins do and how they change the launcher​

PowerToys Run (and its successor, Command Palette) are extensible: third-party plugins add new commands into the launcher. Community plugins already exist for:

• SpeedTest (run an internet speed test from the launcher)
• Everything search (super-fast file search)
• Browser history search
• Process Killer (kill a process by name)
• ChatGPT (query an LLM and open results in a browser)
• Spotify control and RDP quick-launch

The plugin model elevates the launcher from “quick open” to a programmable command surface that replaces multiple separate utilities. (github.com, gilbertalgordo.github.io)

Where plugins live on disk​

The recommended installation path for community/third-party Run (or Command Palette) plugins is:
%LOCALAPPDATA%\Microsoft\PowerToys\PowerToys Run\Plugins
Install procedure (official guidance):

• Close PowerToys.
• Copy the plugin folder to the Plugins path above.
• If upgrading a plugin, delete the old plugin folder first.
• Launch PowerToys and enable/configure the plugin in Run/Command Palette settings. (github.com, gilbertalgordo.github.io)

Example: install a SpeedTest plugin (generic)​

• Download the plugin ZIP from the project page (GitHub or community repo).
• Extract the plugin folder to %LOCALAPPDATA%\Microsoft\PowerToys\PowerToys Run\Plugins.
• Open PowerToys → Run (or Command Palette) → Plugins list and enable the plugin if required.
• Invoke the launcher (Alt+Space by default for Run; Win+Alt+Space for Command Palette) and type the plugin’s activation keyword (per plugin docs, often a short token).

Command Palette vs PowerToys Run — what changed (and why it matters)​

Microsoft has been consolidating Run into a richer Command Palette experience. The documentation and release notes state that the Command Palette is intended to succeed PowerToys Run, bringing more features, extension support, and a modern UI. In practice, Command Palette is available as a PowerToys utility (Win+Alt+Space by default) while Run remains available in settings for backward compatibility. You should treat Command Palette as the forward-looking launcher and verify plugin compatibility before switching entirely. (learn.microsoft.com, theverge.com)

Risks of plugins and how to mitigate them​

• Third-party plugins run code that interacts with your system. They can execute commands, launch urls, or access files. Only install plugins from reputable sources and review plugin code if possible.
• Plugins may require credentials or API keys (for ChatGPT, Spotify, etc.). Store keys securely and avoid embedding secrets in plugin folders.
• After major PowerToys updates (or when migrating from PowerToys Run to Command Palette), plugin APIs can change. Keep copies of plugin versions and test them before relying on them for critical workflows. (ghacks.net, github.com)

---

Practical checklist: how to adopt these three features safely and quickly​

• Update PowerToys to the latest stable release before migrating settings or installing plugins.
• Take a manual backup (PowerToys General → Backup) and copy the .ptb backup file to OneDrive or an external drive. Verify the backup by restoring it into a test environment (a virtual machine or secondary account).
• If you rely on Workspaces or other advanced modules, manually check %LOCALAPPDATA%\Microsoft\PowerToys and confirm the presence of relevant JSON files (e.g., FancyZones’s zones-settings.json, Workspaces’ workspaces.json).
• If you encounter a problem, collect module logs from %LOCALAPPDATA%\Microsoft\PowerToys\<Module>\Logs and review the last 1–2 files for ERROR/WARN entries before filing a GitHub issue.
• For plugins, prefer community repositories listed in the official third-party plugins doc and install them into %LOCALAPPDATA%\Microsoft\PowerToys\PowerToys Run\Plugins after closing PowerToys. Reopen PowerToys and enable the plugin in the launcher settings. (github.com, windowsloop.com)

---

Deep technical notes and verifications (what I checked and where)​

• Backup behavior and default path (Documents\PowerToys\Backup) were verified against multiple how-to guides and recent PowerToys documentation; the UI exposes a Browse control so you can change the target folder if you prefer OneDrive. If you’re running PowerToys older than v0.64.0, the backup/restore controls may not be available, so upgrade first. (windowsloop.com, betanews.com)
• Logging locations are documented in the PowerToys GitHub devdocs (logging.md): most logs live under %LOCALAPPDATA%\Microsoft\PowerToys, while low-privilege preview handlers log under AppData\LocalLow. The BugReportTool collects from both locations. That’s the authoritative source for log paths. (github.com)
• Plugin installation and recommended folder are documented in the PowerToys third party plugins doc on GitHub; the app expects plugins under %LOCALAPPDATA%\Microsoft\PowerToys\PowerToys Run\Plugins with PowerToys closed during install. (github.com, gilbertalgordo.github.io)
• Command Palette is the officially announced successor to PowerToys Run according to Microsoft’s Command Palette docs; coverage in press and release notes confirms it’s the intended future path, and many distributions now ship Command Palette as the default launcher while retaining Run as an option. Treat Command Palette as the supported, evolving launcher for future plugin development. (learn.microsoft.com, windowscentral.com)

If any of these technical paths look different on your machine, check your PowerToys version and the module changelog — PowerToys changes quickly, and features or file locations can evolve between releases.

---

Strengths and clear benefits​

• Low friction, high payoff: The in-app backup and plugin systems lower the barrier to reproducible environments and centralized tooling.
• Transparent troubleshooting: Per-module logs give you real diagnostic evidence and accelerate meaningful bug reports or rollbacks.
• Extensible launcher: A plugin-enabled launcher means you can stop context-switching between multiple utilities; single-keystroke actions become the new normal.
• Open-source ecosystem: Community contributions expand functionality quickly and provide a pool of practical plugins and real-world fixes.

---

Risks, trade-offs, and recommended mitigations​

• Risk: Plugins can execute arbitrary code or exfiltrate information.
• Mitigation: Only install plugins from vetted sources; inspect code prior to install if possible; sandbox sensitive keys and use ephemeral tokens.
• Risk: Backups may not be 100% comprehensive for niche modules (Workspaces historically excluded).
• Mitigation: Manually verify important per-module files in %LOCALAPPDATA%\Microsoft\PowerToys and include them in your own archive process if needed. (github.com)
• Risk: Logs may include sensitive paths or parameters.
• Mitigation: Review and redact logs before posting publicly; use the BugReport tool only after sanitizing.
• Risk: Forward compatibility between Run and Command Palette, and between PowerToys versions, can vary.
• Mitigation: Keep the same PowerToys version across machines for migration; snapshot backups before major upgrades.

---

Final practical recommendations​

• Add PowerToys to your standard Windows image or post-install checklist and enable automatic backups to a cloud folder so your customizations survive OS reimages.
• When experimenting with plugins, start in a VM or non-critical account and keep a copy of the plugin folder so you can revert quickly.
• If you depend on Workspaces or complex FancyZones templates, supplement the UI backup with a manual copy of the JSON files in %LOCALAPPDATA%\Microsoft\PowerToys.
• Use the logs as your first line of defense; scanning the latest ERROR entries typically yields the quickest path to a fix or a minimal GitHub bug report.

---

PowerToys is a pragmatic toolbox: the headline utilities get attention, but the little features described here—backup/restore, readable diagnostic logs, and the plugin ecosystem—are the ones that transform PowerToys from “nice to have” into a durable part of a professional Windows workflow. Enabling these features and folding them into your setup routine reduces rebuild friction, speeds up repairs, and unlocks a layer of automation that many users miss. Consider this a small operations manual: back up, read the logs, and extend wisely — and you’ll get far more value from PowerToys than most users realize.

---

Source: groovyPost 3 secret PowerToys features I wish I knew sooner