Windows 11 Canary Build 27959: Moveable Onscreen Indicators and En Dash Shortcuts

Microsoft’s latest Canary-channel build for Windows 11, Build 27959, brings a collection of small but widely requested user-facing tweaks and a raft of stability fixes — most notably a new setting that lets you reposition the on‑screen hardware indicators (volume, brightness, airplane mode, virtual desktops), system‑wide keyboard shortcuts for inserting en and em dashes, and the ability to pin favorite apps inside the Windows Share window. These changes are rolling out to Insiders as experimental, controlled flights and are accompanied by several bug fixes and at least one newly reported known issue affecting sleep and shutdown behavior. The new flyout positioning, in particular, has been described by Microsoft and independent observers as a “highly requested” tweak that restores choice and reduces overlay obstruction during full‑screen work and presentations.

---

Background / Overview​

The Windows Insider program uses multiple channels (Canary, Dev, Beta, Release Preview) to stage platform experimentation and incremental changes. The Canary channel, where Build 27959 is being flighted, is Microsoft’s earliest testing lane for platform-level experiments and quality fixes; features there are intentionally fluid and may never reach broader Windows releases. That experimental posture is important context for how to interpret and test the additions in Build 27959: they’re ready for hands‑on feedback, not blanket deployment.
Microsoft’s announcement for the relevant Beta/Canary waves documented the repositionable hardware indicators under the Settings > System > Notifications path (dropdown: “Position of the onscreen pop‑up”), and clarified that the supported positions are Bottom (existing default), Top left, and Top center. The company asked Insiders to file feedback in Feedback Hub under Desktop Environment > MTC controls and audio.
Why this matters: Windows 11 centralised many on‑screen popups to the bottom center for a consistent aesthetic, but that placement frequently obstructs centered content in games, video players, creative software and during screen sharing. Giving users a choice — especially the traditional top‑left location — is a low‑risk change with high perceived value. Independent coverage and community testing confirm the change is rolling out to Insiders and is visible in Canary builds.

---

What’s new in Build 27959​

Moveable hardware indicators: small setting, large UX effect​

• New setting: Settings > System > Notifications > Position of the onscreen pop‑up.
• Supported positions: Bottom (default), Top left, Top center.
• Applies to hardware flyouts for: brightness, volume, airplane mode, and virtual desktops.

This option is precisely the kind of friction‑reducing tweak that accumulates into a noticeably smoother daily experience. By allowing users to move the flyouts away from the center, Microsoft reduces accidental content occlusion during presentations and creative workflows. Insiders are encouraged to file feedback via Feedback Hub under Desktop Environment > MTC controls and audio.
Practical note: the UI is a discrete dropdown with three fixed positions rather than a free‑form drag. That simplifies testing and avoids layout edge cases while covering the most common user preferences.

System‑wide En dash and Em dash shortcuts​

• WIN + Minus (‑) inserts an En dash (–, U+2013).
• WIN + Shift + Minus (‑) inserts an Em dash (—, U+2014).

This is a tiny but powerful productivity shortcut for writers and editors who previously had to rely on Alt codes, character maps, or the emoji & symbols picker. The mapping is mnemonic (minus → dash) and brings Windows closer to the convenience macOS users enjoy. However, Microsoft explicitly notes an important accessibility caveat: if Magnifier is running, WIN + Minus remains the Magnifier zoom‑out hotkey and will not insert an en dash. That preserves existing assistive workflows but creates a conditional behavior that users should be aware of.

Pin favorites inside Windows Share​

• The Windows Share UI gains the ability to pin frequently used apps to the top of the sharing targets list.
• This reduces friction when sharing content frequently to the same set of apps and is especially useful for collaboration workflows and fast messaging/sharing use cases.

The Share pinning addition streamlines the share flow and reduces the time spent hunting for targets. Microsoft’s release notes and community reports show the pin affordance inside the Share flyout in Insider builds.

Quality and stability fixes​

Build 27959 also includes a broad set of fixes across core subsystems:

• General: Fix for increased Arm64 bugchecks (IRQL_NOT_LESS_OR_EQUAL) in prior Canary builds.
• File Explorer: Removed accent colored backplates behind packaged app icons in “Open with”, performance improvements for cloud file launches and context menu loading, fixes for RTL mirroring in Arabic/Hebrew locales, and desktop icon overlap at large text scaling.
• Taskbar & System Tray: Battery icon desynchronization fix and focus‑related fixes for app preview thumbnails.
• Start Menu: Fixed a dismiss issue when capturing screenshots with WIN + Shift + S.
• Display & Graphics: Fixed partially stuck onscreen content when maximized/fullscreen apps update in the background.
• Windows Hello: Resolved PIN setup failure with error 0x80090010 on Entra‑joined devices.
• Voice Access: Addressed error 9001 that prevented Voice Access from working.
• For developers: PIX on Windows playback issue fixed in a new PIX release.

These reliability patches are the sort of under‑the‑hood work that makes Insider builds safer to test and prepares platform components for downstream channels.

Known issue to watch: sleep and shutdown investigation​

Microsoft acknowledged reports that some Insiders on the Canary channel have experienced problems with sleep and shutdown after recent Canary builds; the company is investigating. This is a significant operational issue — sleep/shutdown regressions can be disruptive — and underlines the Canary channel’s experimental nature. Do not deploy Canary builds on production machines without backups and test devices.

---

How to try the new features (Insider steps)​

• Join the Windows Insider Program and set your device to the Canary channel (be aware Canary often requires a clean install to switch back from higher channels).
• Update to the latest Insider build (Build 27959 or the Canary build number reported on your device).
• To move hardware indicators:
• Open Settings > System > Notifications.
• Use the dropdown for Position of the onscreen pop‑up and choose Bottom, Top left, or Top center.
• To insert En/Em dash anywhere in Windows:
• Press WIN + Minus for En dash; WIN + Shift + Minus for Em dash.
• If Magnifier is active, WIN + Minus will remain mapped to Magnifier’s zoom‑out function.
• To pin apps in the Share UI:
• Open a Share dialog (e.g., right‑click a file > Share), then pin your frequently used targets.

These steps reflect Microsoft’s documented release notes and Hands‑On guidance appearing in Insider commentary and community testing.

---

Critical analysis — strengths and tradeoffs​

Strengths: practical polish and user empathy​

• Low friction, high benefit: The repositionable hardware indicators are a high‑value tweak because they remove a daily annoyance without changing the overall visual language of Windows 11. It’s the kind of incremental polish that improves perceived quality disproportionately to engineering effort.
• Writer productivity: OS‑level En/Em dash shortcuts are a thoughtful addition for people who write frequently and prefer keyboard-first workflows. They reduce context switching and are easily discoverable.
• Share UX: Pinning in the Share window addresses a real workflow friction — frequent targets are now a single click away.
• Stability focus: The build bundles a number of important fixes (Arm64 bugchecks, File Explorer performance, Windows Hello PIN on Entra domains) which reduce support load and increase confidence for those testing later channels.

Tradeoffs and risks​

• Experimental channel volatility: Canary builds are inherently unstable; features and fixes may change, regress, or never ship to stable Windows 11. Organizations should not treat Canary builds as stable releases.
• Accessibility tension: Preserving Magnifier’s WIN + Minus behavior protects assistive workflows but produces inconsistent behavior for the new en dash shortcut. Users who rely on Magnifier cannot access the WIN + Minus en dash mapping without remapping keys; Microsoft may need to provide remap options or alternate shortcuts to reconcile this.
• Fragmentation risk: Controlled feature rollouts and hardware/licensing gating (seen with AI features in other Insider builds) increase variability across environments. Two devices on the same OS build may have different feature sets depending on server activation, hardware (e.g., Copilot+ NPU), or licenses, which complicates support and documentation.
• Potential multi‑monitor/DPI edge cases: Moving flyouts to top‑left or top‑center must behave sensibly on multi‑monitor systems with differing DPIs and scaling. Early flights may expose alignment or clipping bugs in exotic configurations; Microsoft’s staged approach reduces exposure but does not eliminate the possibility.
• Known sleep/shutdown problem: The reported issue affecting sleep/shutdown is operationally serious and a reminder that Canary builds can introduce regressions that impact productivity and hardware power management. Test before adopting.

---

Enterprise implications and recommendations​

For IT administrators and enterprise pilots, the short answer is: test selectively, document thoroughly, and do not deploy Canary to production.

• Pilot groups: Use a small cohort of non‑critical test devices to validate the Flyout position change, Share pinning, and the Windows Hello PIN fix for Entra‑joined devices. The Hello fix may be particularly relevant to managed fleets that previously experienced PIN setup failures.
• Update support documentation: Note that flyout position is now configurable and document the new setting path so helpdesk personnel can guide users.
• Verify accessibility: Ensure assistive technologies (Narrator, Magnifier, third‑party screen readers) behave correctly with relocated flyouts; confirm that the flyouts announce correctly and do not impede focus order.
• Policy and manageability: Check the impact of feature gating and server‑side activation on standardized images; admin teams should validate that expected features are present for pilot users and that rollout controls (Intune, Group Policy) still behave as intended.
• Avoid Canary for production: Microsoft explicitly intends Canary for experimentation; for enterprise validation, prefer Beta or Release Preview channels and controlled feature rollouts that mirror production cadence.

---

Developer and accessibility notes​

• Developers building overlay UIs (streaming, creative tools) should be aware that users can now relocate system flyouts. Apps that intentionally place UI elements near the top center or top left should detect system flyout position where possible or offer user settings to avoid conflicts.
• Accessibility APIs: Microsoft must ensure relocated flyouts remain visible and announced correctly through platform accessibility APIs. Early testing in diverse assistive setups (screen readers, Braille devices) is recommended.
• Keyboard mappings: The en/em dash shortcuts are globally available but contingent on localization and keyboard layout. Developers of input method editors (IMEs) and international keyboard layouts may need to verify behavior for non‑US layouts.

---

Verification and cross‑checking of claims​

Key claims in the Build 27959 notes — the repositionable hardware indicators, WIN + Minus dash shortcuts, Share pinning, and the list of fixes and known issues — are present in Microsoft’s Insider release notes and corroborated by multiple independent outlets and community testing. Microsoft’s official Insider blog and the Beta/Canary release announcements document the hardware indicator setting and the control path in Settings. Independent reporting and community threads also validated the shortcuts and the Share pinning affordance. When a claim could change quickly — such as whether a Canary feature will reach general release — the correct posture is cautious: the feature’s presence in Canary is verifiable; its broader availability and timeline are not guaranteed.
Where public documentation or deterministic timelines are absent, this article flags such items as speculative or evolving. For example, the precise roll‑out cadence across Dev/Beta/Canary and stable channels depends on Microsoft’s staged activation and telemetry, which can change between flights; therefore any statement projecting general availability beyond the Insider builds is inherently uncertain.

---

Practical advice — what to do next​

• If you’re an Insider and you want the feature now: install Build 27959 in the Canary channel on a test device and try Settings > System > Notifications → Position of the onscreen pop‑up. Report any layout or accessibility issues through Feedback Hub (WIN + F).
• If you rely on Magnifier: note that WIN + Minus remains mapped to Magnifier while it’s active; consider whether you want to remap keys or wait for Microsoft to provide alternate shortcuts.
• If you manage an enterprise fleet: pilot the build in a limited ring, validate Windows Hello behavior for Entra‑joined devices and test cloud file performance improvements in File Explorer before wider deployment. Document known issues (sleep/shutdown) and hold Canary out of production.
• For developers and UI overlay authors: test multi‑monitor and high‑DPI scenarios against relocated flyouts and adapt overlay positioning logic as needed.

---

Conclusion​

Build 27959 is a pragmatic Canary release: it delivers several small, high‑impact UX wins (moveable hardware indicators, en/em dash shortcuts, Share pinning) alongside important stability work across File Explorer, Windows Hello, and Arm64 reliability. These are the types of incremental refinements that meaningfully improve day‑to‑day use without altering Windows 11’s core visual language.
At the same time, Canary’s experimental nature and the newly reported sleep/shutdown investigation underscore why Insiders use this channel — to surface issues early and shape the product — and why enterprises should remain conservative about adoption. The repositionable flyouts are an especially welcome nod to user feedback, restoring choice and reducing visual obstruction for full‑screen scenarios; the en/em dash shortcut is a thoughtful productivity addition. Both demonstrate Microsoft’s continued focus on polishing small pains and making the OS more adaptable to real‑world workflows.
Try the features on a test device, file feedback if you encounter regressions, and treat Canary as a lab rather than a deployment lane — the changes are valuable, but measured validation remains the responsible path forward.

---

Source: Neowin Microsoft confirms a "highly requested" Windows 11 feature is coming with new Build 27959