Microsoft shipped PowerToys 0.100.0 on June 10, 2026, officially graduating the Command Palette Dock from its March preview and giving every connected display its own customizable toolbar instance. That per-monitor independence makes the Dock a genuinely useful workspace companion, not just a secondary launcher — but an unresolved defect that sends menus to the wrong screen means anyone building a mission-critical multi-monitor layout should proceed carefully.

What changed in PowerToys 0.100.0

The Dock itself isn't new. It first appeared as a preview in PowerToys 0.98.0 on March 17, 2026, offering a persistent toolbar along one screen edge that could host pinned commands, widgets, and launchers. Back then, it was a single-instance experiment: you got one Dock, period.

PowerToys 0.100.0 turns that into a properly multi-monitor feature. According to the official documentation on Microsoft Learn, every display now gets its own Dock instance with an independent set of pinned bands. You can assign different commands to different screens, and you can drag a band from one monitor's Dock to another to move it across displays.

That's a significant leap. Instead of duplicating the same launcher on each monitor, the Dock can now reflect the actual work happening on that screen. A sysadmin might put monitoring widgets on a secondary display and keep general navigation commands on the primary. A developer could pin build shortcuts to the monitor running an IDE and leave email and chat shortcuts elsewhere.

The update also benefits from the stability work delivered in PowerToys 0.99.1, which fixed popup crashes, cleaned up Dock window disposal, and eliminated an obnoxious visual flicker that followed settings changes. Those corrections addressed the sorts of reliability problems that make a persistent on-screen toolbar feel untrustworthy. Microsoft's own documentation describes the Dock as using the Windows AppBar API to reserve screen space so other windows don't overlap it, and now it should stay visible without randomly crashing or leaving ghost windows behind.

What the Dock actually does — and how to set it up

Enabling the Dock requires Command Palette to be running (it's a subset of that utility). Flip the “Enable Dock” toggle in Command Palette settings, and a toolbar appears on your screen edge — top by default, though you can choose left, right, or bottom. The toolbar splits into three regions: Start, Center, and End. Start holds primary commands and launchers; Center is a flexible middle section you fill yourself; End contains utility widgets like a performance monitor and date/time.

Pinning commands works from multiple directions. You can right-click any item in the full Command Palette and select “Pin to Dock.” You can enter Dock edit mode (right-click the Dock background, then “Edit Dock”) to add items via a flyout and drag bands between regions. You can even drag a file or URL from File Explorer onto the Dock, which automatically creates a bookmark band for it.

Appearance tweaks are extensive: acrylic or transparent materials, light/dark/system theme, background colorization with a custom color tint, and even a background image with brightness, blur, and fit controls. For a utility that occupies permanent screen real estate, that degree of personalization matters.

On multi-monitor rigs, each display's Dock is separately configurable. You can enter edit mode on any monitor's Dock and build a unique layout there. Dragging a band from one monitor's Dock to another moves it. The documentation explicitly notes you can keep a performance monitor on the primary display and work bookmarks on a secondary one.

The wrong-monitor problem

This is where the rollout advice gets conditional. A GitHub issue filed against PowerToys 0.99.1 on June 1, 2026, reports that the Dock or its quick-access context menu can appear on the wrong monitor in a multi-display configuration. One open report doesn't prove everyone will hit it, but the bug touches the exact capability that makes per-monitor Docks attractive: predictable display targeting.

If a context menu meant for monitor three pops up on monitor one, the physical separation of tools you spent time arranging breaks down. For users who treat the Dock as a handy convenience — just a few pinned items on each screen, none of them critical — a misplaced menu is an annoyance. For anyone who has built a workspace where certain commands live only on certain monitors for efficiency reasons, it undermines the entire point of the feature.

Microsoft hasn't issued a public timeline for a fix, though the PowerToys team generally moves quickly on reported defects. The issue remains open as of the 0.100.0 release.

How we got here

The Dock's evolution has been fast. PowerToys 0.98.0 launched the preview with basic pinning and a single-monitor mindset. Early adopters immediately saw potential for what the forum community called a “second taskbar” — modular, extensible, persistent. But the preview's rough edges were apparent: crashes, visual glitches, and no real multi-monitor story.

PowerToys 0.99.1 landed in late May 2026 with targeted fixes. The release notes addressed “Dock popup crashes,” “DockWindow cleanup,” and “visual blinking after settings changes.” Those aren't headline features, but they are the kind of housekeeping that transforms a novelty into something you might actually keep visible all day.

Now, with 0.100.0, Microsoft has baked in the full per-monitor model and documented it on Microsoft Learn as a permanent feature. The number of available bands has grown as extensions have matured, meaning you can pin not just built-in commands but third-party items from things like the Web Search or System Monitor extensions.

Practical advice for different audiences

Home users on a single monitor: Adopt it now. The worst that can happen is a popup crash, and 0.99.1 made those far less frequent. Start by pinning a handful of frequently used items — the Home command, a few settings shortcuts, maybe the Date/Time widget — and see if the persistent toolbar earns its screen space. You can always turn it off with one toggle.

Enthusiasts with two or three displays: Light usage is fine, but don't go all-in immediately. Enable the Dock on each monitor, pin a few non-critical bands, and run it for a week. Watch for context menus that appear on the wrong screen. If you can live with that occasional glitch, per-monitor Docks do add real value: weather on one display, system resources on another, quick-launch bookmarks on the third. Just keep your layouts simple until Microsoft closes that targeting defect.

Power users designing monitor-specific command centers: Stage it. The Dock's potential — truly independent toolbars on every screen — is precisely what the open bug threatens. Build your ideal layout on a test machine, or enable it on only one monitor at first. After each addition, verify that context menus open on the display where you clicked, that popups survive repeated interaction, and that dragging bands between monitors leaves them on the intended screen. If the wrong-monitor bug shows up, wait for a fix before deploying it across your real workspace.

Extension-heavy setups: Extensions multiply the possible failure points because they add new band types, context menus, and popups. Even if the Dock itself is stable, an extension could interact poorly with per-monitor independence. Introduce extensions one at a time, testing Dock behavior on every connected display after each installation. The same checks apply: menu placement, popup stability, visual consistency.

IT and managed fleets: Keep Dock adoption separate from a broader PowerToys rollout. Updating to PowerToys 0.100.0 to get other fixes and features is fine, but don't push a standardized Dock layout through Group Policy or MDM yet. Run a pilot with a handful of users whose workflows aren't disrupted by a misplaced menu. Collect feedback specifically about multi-monitor behavior. Only when Microsoft confirms the targeting bug is fixed, or when you've validated it doesn't appear in your specific hardware/driver configs, should you consider making the Dock part of a standard image.

What to watch next

The PowerToys team hasn't signaled exactly when the wrong-monitor bug will be patched, but given the pace of recent releases and the public attention the issue has received on GitHub, a fix in the next incremental update wouldn't be surprising. Once that lands, the Dock will be ready for the ambitious multi-monitor setups it was clearly designed to support. Until then, it remains a useful tool best approached with a measure of caution — treat it like a reliable co-pilot, not an autopilot.