Windows 11 Canary Build 27959 Adds Moveable Indicators and Dash Shortcuts

Microsoft’s latest Canary-channel flight lands with a handful of practical UI tweaks and quality fixes: Build 27959 introduces movable on‑screen hardware indicators, an OS‑level en/em dash typing shortcut, the ability to pin favorite apps in the Windows Share UI, and a raft of under‑the‑hood corrections aimed at File Explorer, Windows Hello, Voice Access, and Arm64 stability. This update is targeted at Windows Insiders in the Canary Channel and continues Microsoft’s pattern of iterating UI refinements and developer fixes early in the development cycle.

Background / Overview​

The Canary Channel serves as Microsoft’s earliest, most experimental Insider stream — a place for platform-level experiments that may never ship to the broader Windows population. Builds in this branch are often used to test concepts, collect early feedback, and exercise internal plumbing across OS subsystems. Because of that, feature behavior is intentionally fluid: options may appear, disappear, or change form as Microsoft refines the user experience. The release notes for Build 27959 reiterate this stance and remind Insiders that leaving the Canary Channel requires a clean install of Windows 11.
This flight is primarily a quality-and-polish update with a few small, immediately visible usability improvements. The three items most likely to be noticed by everyday users are:

• A setting to reposition hardware indicators (volume, brightness, airplane mode, virtual desktops).
• New keyboard shortcuts to insert an En dash (–) and Em dash (—) system‑wide.
• Pinning support in the Windows Share window for faster share targets.

Each of these touches addresses a long-standing friction point—either ergonomics or typing efficiency—while the rest of the build focuses on stability and compatibility fixes across File Explorer, the taskbar, accessibility subsystems, and developer tooling.

---

What’s new in Build 27959​

Moveable hardware indicators: a small setting, a big UX win​

Windows 11 now lets you change where hardware indicator flyouts appear on screen. Insiders can choose from three positions:

• Bottom (legacy Windows 11 position, default)
• Top left
• Top center

You can change this via Settings > System > Notifications by selecting the dropdown labeled Position of the onscreen pop‑up. The intent is simple: make the flyouts less intrusive during full‑screen apps, presentations, video calls, or when you frequently interact with controls near the screen center. Microsoft highlights the option in the Canary release notes and has been testing it across channels.
Why this matters: the on‑screen volume and brightness indicators have been a frequent point of feedback since Windows 11 centralized them at the bottom of the screen. Restoring choice — particularly the traditional top‑left position — respects users who prefer a less centered indicator or who use apps that occupy the middle of the display. Independent coverage of this change confirms Microsoft is rolling it out to Insiders and testing different placements before any broader deployment.
Practical how‑to (Insider Preview)

• Open Settings.
• Go to System > Notifications.
• Use the dropdown labeled Position of the onscreen pop‑up and pick Bottom, Top left, or Top center.

New OS‑level keyboard shortcut for en and em dash​

Build 27959 adds two simple, system‑wide shortcuts for typographic dashes:

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

That mapping brings Windows closer to macOS conventions and removes the need for numeric Alt codes or the emoji & symbols picker for common punctuation. Microsoft documents the change in the Canary release notes, and multiple independent outlets and community threads have validated the behavior in recent Insider builds.
Accessibility caveat: if Magnifier is running, WIN + Minus remains mapped to Magnifier zoom‑out, so the En dash shortcut will not take effect while Magnifier uses that key. Microsoft calls this out explicitly in the release notes; it preserves existing accessibility hotkeys while adding the new typographic convenience to the broad population that does not rely on Magnifier.
Why this matters: writers, editors, and anyone who types frequently will appreciate fewer context switches. The new shortcut is a clear productivity win — but the Magnifier interaction demonstrates how keyboard shortcuts must be balanced against accessibility requirements.

Pin your favorite apps in the Windows Share window​

Sharing in Windows is getting a small organizational improvement: you can now pin apps inside the Windows Share UI so frequently used targets appear more quickly. This reduces friction when sharing content to messaging apps, note apps, or collaboration tools and is particularly useful on machines used for frequent social or collaborative workflows. The feature is documented in the build notes and is already visible in Insider test builds.

---

Fixes and platform improvements: what’s addressed​

Build 27959 includes multiple bug fixes and performance improvements across core areas:

• General / Stability: Microsoft fixed a regression causing increased bugchecks (IRQL_NOT_LESS_OR_EQUAL) on some Arm64 devices. This had been flagged in earlier Canary releases and is explicitly addressed in this flight. Given the risk of kernel‑mode crashes, Arm64 users were warned to avoid running unstable Canary builds on production machines.
• File Explorer:
• Removed the accent-colored backplate behind packaged app icons in the Open With list, improving icon legibility.
• Made underlying changes to improve the performance of launching cloud files and loading context menus.
• Fixed mirroring issues for Arabic/Hebrew display languages and problems where increased scaling caused icons and text to overlap on the desktop.
• Taskbar & System Tray: corrected battery icon desynchronization (the icon showing a different plugged/charging state than actual hardware) and a focus bug when using app preview thumbnails.
• Start menu: fixed a bug where the Start menu dismissed when using WIN + Shift + S to take a screenshot.
• Display & Graphics: addressed an artifact where parts of an app’s rendered content could appear stuck on screen when another maximized or full‑screen app updated in the background. This partially stuck content was especially noticeable while scrolling.
• Windows Hello: resolved a setup failure for Windows Hello PIN (error 0x80090010) on Entra‑joined devices.
• Voice Access: fixed an issue that caused Voice Access to show error 9001 and not work.
• For developers: fixed playback of GPU captures in PIX on Windows via a PIX update—critical for graphics developers and driver teams.
• Windows Security: corrected apostrophe rendering in parts of the app.

These fixes combine targeted user-facing UX polish with important developer and platform health corrections that keep the Canary pipeline useful for engineering validation.

---

Known issues and risks: what to watch for​

Sleep and shutdown problems (NEW)​

Microsoft is investigating reports that sleep and shutdown aren’t working correctly for some Insiders after recent Canary builds. This is a new, active known issue called out in the 27959 release notes. Because sleep and shutdown touch firmware, drivers, and power frameworks, the bug can be disruptive and potentially harmful for unsaved work or for systems used as daily drivers. Insiders experiencing this should roll back to a more stable channel or avoid using affected machines for critical tasks.

Arm64 bugchecks (IRQL_NOT_LESS_OR_EQUAL)​

Earlier Canary flights saw an uptick in bugchecks on some Arm64 machines. Microsoft flagged the issue and noted it in release notes for recent Canary builds; Build 27959 lists fixes addressing similar Arm64 regressions, but Arm64 users should continue to exercise caution. Frequent BSODs on Arm64 testers were reported across community forums and prior Canary releases, and Microsoft has indicated it is tracking and addressing those regressions. Running test builds on production Arm64 hardware is not recommended.

Accessibility and shortcut conflicts​

The new WIN + Minus shortcut collides with the Magnifier zoom-out hotkey. Microsoft intentionally preserves Magnifier behavior, but this means users who rely on Magnifier cannot use WIN + Minus for En dash insertion unless they remap or disable Magnifier’s keys. This trade‑off highlights the complexity of evolving global OS shortcuts while keeping accessibility intact.

Canary unpredictability and channel switching​

A general reminder: Canary builds are experimental. Features may be rolled out in waves, localized translations may lag, and functionality can change unexpectedly. If you want to get off the Canary Channel, Microsoft requires a clean install of Windows 11 — there’s no downgrade path to a lower‑numbered channel without wiping the device. This barrier makes Canary unsuitable for machines where time and uptime matter.

---

Practical guidance for Insiders and IT pros​

If you’re already on Canary, here’s how to get the most out of 27959 while protecting your work:

• Back up before installing: create a restore point, an image backup, or a full system backup before applying Canary builds.
• Avoid installing Canary on production machines: Canary builds may introduce regressions that affect productivity.
• Report issues early: use Feedback Hub (WIN + F) and file feedback under the suggested categories (Desktop Environment > MTC controls and audio for the hardware indicator change). Microsoft relies on structured feedback to shape final behavior.
• If you need to revert to a stable channel: prepare for a clean install — export settings, save product keys, and ensure you can reinstall apps and drivers. The release notes explicitly remind Insiders about the clean‑install requirement to move off Canary.

For developers and support teams:

• If you reproduce the PIX playback issue during GPU capture debug, update PIX to the latest release Microsoft referenced; the release notes say a PIX update addresses playback problems. Test capture/restore in a controlled environment after updating PIX.
• If your app relies on precise timing or low-level graphics behavior, test under Build 27959 for the display and stuck-frame fixes—some rendering inconsistencies have been addressed.
• Arm64 device owners should log kernel dumps and file Feedback Hub traces if experiencing IRQL_NOT_LESS_OR_EQUAL bugchecks — dumps accelerate root cause analysis.

---

Deeper analysis: user impact, accessibility, and enterprise considerations​

User impact and ergonomics​

The movable indicator setting is an example of incremental UX re-empowerment. It’s not flashy, but it addresses a recurring complaint: indicators should not obstruct content. Allowing the top‑left or top‑center options restores classic Windows behavior while keeping Windows 11’s modern visual language intact. For people who present their screen frequently, share during meetings, or use apps that center critical UI elements, this small change reduces friction.
From an SEO perspective, phrases like volume flyout position, Windows 11 hardware indicators, and move volume indicator Windows 11 are now relevant search terms; users troubleshooting or seeking to customize their flyouts will likely search with those keywords. The change is therefore both user‑centric and discoverability‑friendly.

Accessibility tension: convenience vs. assistive tech​

The new en/em dash shortcut is a huge convenience for typists but collides with Magnifier. Microsoft’s choice to preserve Magnifier behavior shows an appropriate prioritization of assistive tech, but it also creates a differential experience depending on whether users rely on Magnifier. Accessibility advocates should watch for additional options — for instance, a Preference toggle that lets Magnifier users remap its zoom keys — because consistent input affordances are especially important for users with disabilities. The current behavior maintains accessibility but at the cost of shortcut uniformity.

Enterprise risk profile​

Most enterprises do not deploy Canary builds broadly by policy. Two enterprise‑facing notes here are relevant:

• The Windows Hello PIN fix for Entra‑joined devices addresses a domain‑join login issue that could block new PIN provisioning in managed environments. Enterprises testing sign‑in flows should validate the fix.
• The File Explorer and cloud‑files improvements reduce friction for hybrid storage scenarios (OneDrive and other cloud providers). IT should validate cloud file launch performance in test rings before broader deployment.

Overall, Canary remains an engineering and experimentation channel; organizations should continue to gate feature releases via controlled flighting and avoid Canary for production use.

---

Cross‑verification of key claims​

• The release notes and screenshots for Build 27959 are published on Microsoft’s Windows Insider Blog; the blog enumerates the movable hardware indicators, the en/em dash shortcuts, the Windows Share pinning, the fixes for File Explorer and Windows Hello, and the new known issue about sleep and shutdown.
• Independent reporting confirms the moveable indicator change and documents the UX rationale. Coverage from The Verge and Windows‑focused outlets captured the feature as it arrived in Dev/Beta/Canary test flights, noting the top‑left and top‑center options specifically. These independent writeups corroborate Microsoft’s description and show community interest.
• The en/em dash shortcuts have been validated by multiple technical news outlets and community tests. Reports and community threads describe the new WIN + Minus / WIN + Shift + Minus mapping and highlight the Magnifier interaction. Additional reports show that some early adopters used tooling such as ViVeTool to enable related feature flags in earlier builds, underscoring the experimental rollout path.

When a claim could change quickly — for example, whether a Canary feature will ship to stable Windows 11 — there’s no definitive public confirmation; Microsoft’s blog emphasizes that Canary features are experimental and may never ship, so any forward projection about general availability is speculative. Flagging that uncertainty is necessary: the fact that this feature exists in Canary today is verifiable; whether and when it appears in stable releases is not.

---

Quick reference: what to try in Build 27959​

• Change hardware indicator position:
• Settings > System > Notifications
• Dropdown: Position of the onscreen pop‑up → choose Bottom, Top left, Top center.
• Insert En / Em dash (system‑wide):
• Type WIN + Minus (-) → En dash (–)
• Type WIN + Shift + Minus (-) → Em dash (—)
• Note: If Magnifier is active, WIN + Minus will zoom out instead.
• Pin apps in Windows Share:
• Open the Share window (via Share option in app/Explorer).
• Pin frequently used apps to the top of the Share UI for faster access.
• Report issues: Feedback Hub (WIN + F) — use the categories suggested in the release notes (e.g., Desktop Environment > MTC controls and audio for flyout positioning feedback).

---

Conclusion​

Build 27959 is a tidy, user-first Canary flight: it adds practical, discoverable features (moveable flyouts and dash shortcuts) that fix small but persistent irritations, while delivering important stability and compatibility fixes across File Explorer, Hello sign‑in, and developer tooling. For Insiders the update is worth testing — especially if you’ve wanted to move the volume/brightness indicator back to a classic position or if you are a heavy typist who will benefit from the new dash shortcuts. However, the Canary channel’s experimental nature means the cautious approach remains correct: don’t deploy Canary builds on production hardware, back up before installing, and use Feedback Hub to report any regressions you encounter. Microsoft’s blog and independent reporting both confirm the features and the tradeoffs; follow the known‑issues list closely if you experiment with this build.

---

Source: Microsoft - Windows Insiders Blog Announcing Windows 11 Insider Preview Build 27959 (Canary Channel)

 

[ChatGPT]

Microsoft has pushed Windows 11 Insider Preview Build 27959 to the Canary Channel, delivering a small but user-focused wave of changes — most notably a new setting to reposition on-screen hardware indicators, a system-wide keyboard shortcut for inserting en and em dashes, and the ability to pin apps in the Windows Share UI — along with a batch of stability fixes and a new known issue affecting sleep and shutdown on some devices.

Background​

Microsoft’s Canary Channel is the earliest preview ring for Windows Insiders, where platform-level experiments and concept work appear before they’re vetted for Dev, Beta, or public release. Builds in Canary are intentionally exploratory: features may be heavily revised, rolled out via controlled feature rollouts, or removed entirely. That makes Build 27959 important for watching the direction of small-but-impactful usability changes, even if those changes are still in trial phases for wide release.

---

What’s new in Build 27959 — quick summary​

• New positioning control for hardware indicator flyouts (brightness, volume, airplane mode, virtual desktops): bottom (current), top-left, and top-center.
• New system-wide keyboard shortcuts to insert an en dash (–) and em dash (—): WIN + Minus (-) and WIN + Shift + Minus (-) respectively. Note the Magnifier conflict: if Magnifier is active WIN + Minus will continue to zoom out.
• Pin apps in Windows Share: you can now pin favorite targets to the top of the share sheet for faster access.
• Visual refreshes to more dialogs to match Windows 11 styling and multiple fixes across File Explorer, taskbar, graphics rendering, Windows Hello, Voice Access, and developer tools like PIX.

The build also lists a new known issue: reports that sleep and shutdown may not work correctly for some Insiders after these Canary builds — Microsoft is investigating.

---

Overview: moving hardware indicators out of the way​

What changed​

Windows 11 has historically shown hardware flyouts — small overlays that appear when you change volume, brightness, or toggle airplane mode — in a fixed area that can sometimes obstruct content. Build 27959 introduces a setting to choose where those flyouts appear: the current bottom (default), or two new positions: top-left and top-center. The setting is exposed at Settings > System > Notifications via the Position of the onscreen pop-up dropdown.

Why it matters​

These flyouts frequently appear during media playback, presentations, or full-screen apps; being able to move them reduces interruption and improves the visual experience. Because the positions avoid the top-right corner — where window controls and many app UI elements live — Microsoft appears to be balancing visibility and non-intrusiveness. Independent coverage earlier in the year and community testing shows this change has been in testing across channels before its appearance in Canary, which indicates Microsoft is progressively making it available to gather feedback.

How to test it now​

• Open Settings > System > Notifications.
• Find Position of the onscreen pop-up and choose Bottom, Top-left, or Top-center.
• Adjust volume or brightness to confirm the indicator appears where expected.

Caveats and rollout​

• This setting is being rolled out via the Canary experimental pipeline, so not every Insider will see it immediately. Controlled feature rollouts are common for UI changes to let Microsoft monitor compatibility across hardware and apps.
• Some layout and localization adjustments may still be pending; if flyouts intersect with app UI on specific apps, file feedback via Feedback Hub under Desktop Environment > MTC controls and audio.

---

Typographic convenience: en dash and em dash via WIN + Minus​

The new shortcuts​

Build 27959 adds two system-wide shortcuts for typographic dashes:

• WIN + Minus (-) → en dash (–)
• WIN + Shift + Minus (-) → em dash (—)
  This insertion is available while typing anywhere in Windows, which means it works across editable text fields in browsers, native apps, and many third-party programs. Microsoft explicitly notes that if Magnifier is running, WIN + Minus retains its Magnifier zoom-out behavior rather than inserting an en dash.

Why this is meaningful​

Typing proper dashes on Windows has historically involved:

• remembering Alt codes (numeric keypad required),
• using the Emoji & Symbols picker (Win + .) and navigating to Symbols, or
• relying on app-specific auto-corrects (e.g., Microsoft Word converting two hyphens).

A dedicated, mnemonic system shortcut solves a real productivity friction, especially on laptops without numeric keypads and for writers who need frequent access to typographic punctuation. Coverage from multiple outlets and community threads confirms the shortcut’s arrival in Insider builds and shows the change is already being positively received.

Accessibility intersection and concerns​

This shortcut intersects with accessibility tooling: Magnifier reserves WIN + Plus/Minus for zoom controls. Microsoft’s decision to preserve Magnifier behavior when it’s active prioritizes accessibility over typographic convenience, which is a defensible choice but introduces limitations for users who both depend on Magnifier and type dashes often. Potential mitigations include remapping keys via PowerToys or third-party utilities, but altering accessibility bindings should be done with caution.

Tips and caveats​

• If you don’t see the shortcuts yet, expect a staged rollout — some Insiders see experimental features earlier than others.
• Third-party utilities such as ViVeTool have been used by enthusiasts to enable hidden features in Insider builds, but such tools are unsupported and can risk instability; use them only if you understand the trade-offs.

---

Windows Share: pin your favorite apps​

What changed​

The Windows share UI now supports pinning favorite apps to the top of the Share using list, making the share flow faster and less noisy. The feature surfaces as a pin control when hovering over share targets. This functionality began appearing in earlier Insider builds across Dev/Beta and is now noted in the Canary build 27959 release notes.

Why it’s useful​

Modern workflows rely on sharing content between apps frequently. Pinning reduces friction for users who repeatedly send files to the same services or contacts, similar to the convenience found on many mobile platforms’ share sheets. The change is small but measurable: fewer clicks and less hunting for the right app in the share list.

Notes on behavior​

• Pinning behavior historically applies only to Store-aware or modern share targets; classic Win32 apps that do not register as share targets may not appear. Microsoft documentation and community testing indicate pinned targets are limited to compatible apps.

---

Fixes and stability improvements​

Build 27959 contains a series of platform fixes aimed at reliability and rendering consistency across modern Windows 11 configurations. Key fixes called out in the release include:

• ARM64 bugcheck (IRQL_NOT_LESS_OR_EQUAL): Microsoft fixed an issue that caused some Arm64 devices to experience increased bugchecks (green screens) in recent Canary builds. This reduces the incidence of system crashes on affected hardware.
• File Explorer: visual cleanup in the Open With list (removed accent backplates behind packaged app icons for clearer readability), performance improvements launching cloud files and loading context menus, fixes for icon/text overlap at increased text scaling, and correct mirroring behavior in Arabic/Hebrew display languages.
• Taskbar and system tray: corrected battery icon sync issues where the icon could show an incorrect plugged/unplugged state, and fixed focus problems with app thumbnail previews.
• Start menu: fixed dismissal when attempting a screenshot with WIN + Shift + S.
• Display and graphics: resolved partially stuck-onscreen content in apps or browsers while other full-screen apps updated in the background — a rendering glitch noticeable during scrolling.
• Windows Hello: addressed PIN setup failures (error 0x80090010) on Entra-domain joined devices after recent updates.
• Voice Access: fixed an error (9001) that could prevent Voice Access from working.
• Developer tooling: PIX on Windows playback for GPU captures is restored via a PIX release, resolving compatibility regressions for graphics developers.
• Windows Security: corrected display issues with apostrophes in some app text.

These fixes speak to Microsoft’s dual focus on ergonomics and platform stability — addressing both visible polish and deeper reliability issues surfaced by the Insider community.

---

Known issues and risk assessment​

Sleep and shutdown regression​

The release notes list a new known issue: reports that sleep and shutdown may not work correctly for some Insiders after the latest Canary builds. Microsoft is actively investigating. This is noteworthy because sleep/shutdown regressions can be disruptive to daily use; Insiders running Canary should weigh the risk before installing on machines they rely on.

Other risk considerations​

• Canary builds are not matched to a final Windows release and can include experimental code paths. Expect bugs, potential data loss in edge cases, and the possibility that features may never ship. Controlled feature rollouts mean that behavior can differ wildly between machines and accounts.
• Accessibility trade-offs: the en/em dash shortcut prioritizes Magnifier functionality when active; users relying on assistive tech may not be able to use the new typing shortcut without remapping.
• Enterprise environments: Canary builds are strongly discouraged on production devices. Insiders who manage enterprise deployments should avoid Canary and prefer Beta/Release Preview channels for safer testing cadence and better parity with shipping builds.

---

Practical advice: who should install, and how to report issues​

Who should try Build 27959​

• Enthusiasts and power users who enjoy testing early UI/UX changes.
• Developers and accessibility testers who need to validate behavior across language layouts, Magnifier interactions, or GPU tooling compatibility.
• Users who can tolerate instability and have a recovery plan (system backups or spare machines).

Who should not​

• Enterprise users, or anyone who needs guaranteed sleep/shutdown behavior or uncompromised uptime.
• Users who cannot perform a clean reinstall if they later decide to exit the Canary Channel — leaving Canary normally requires a clean Windows install to return to a lower-channel build number.

How to send useful feedback​

• Use Feedback Hub (WIN + F).
• File under the relevant category (e.g., Desktop Environment > MTC controls and audio for hardware indicator positioning).
• Attach repro steps, screenshots, and system information.
• For crashes and bugchecks, include a memory dump if available and the precise build number from Settings > System > About.

---

Developer and enterprise implications​

For developers​

• The PIX playback fix restores a vital tool in graphics debugging workflows; developers who rely on PIX should update to the latest PIX release that addresses the playback regression. The release notes and separate PIX updates indicate Microsoft coordinates tool releases in tandem with OS changes.

For IT admins​

• Canary channel bits can diverge significantly from production Windows servicing. IT admins should not use Canary builds for compatibility validation in mass deployments; instead, target Beta or Release Preview channels and consult Flight Hub and Release Health for official servicing guidance. Canary remains a sandbox for concept validation rather than a compatibility baseline.

---

User experience and accessibility analysis​

The changes in Build 27959 illustrate a pattern: Microsoft is focusing on small refinements that reduce friction in daily interactions — dashes for writers, flyout positioning for visibility, and share-pin convenience for faster workflows. These are the sort of micro-UX improvements that compound into a better daily experience for power users and productivity-focused people.
However, the en/em dash shortcut’s conflict with Magnifier underscores an important tension: system-level shortcuts must balance discoverability and accessibility. Preserving Magnifier behavior when the tool is active is the accessibility-first choice, but it means the typographic improvement is not universally available to users who may benefit from both. Microsoft’s note on the controlled rollout shows awareness, and the Feedback Hub is the correct channel to push for refinements such as configurable shortcut priorities or alternative bindings that don’t collide with accessibility features.

---

Step-by-step: enable and validate the headline features (quick checklist)​

• Join the Windows Insider Program and pick the Canary Channel (not recommended for production devices).
• Update to Build 27959 via Settings > Windows Update.
• To move hardware indicators: Settings > System > Notifications > Position of the onscreen pop-up. Confirm by changing volume/brightness.
• To try the dash shortcuts: focus any editable text field and press WIN + - for en dash, WIN + Shift + - for em dash. If Magnifier is active, expect WIN + - to act as zoom out instead.
• To pin apps in Share: invoke the Share UI from a file or link and look for the pin control when hovering over a share target.

---

Conclusion​

Build 27959 is a concentrated bundle of user-focused refinements and important fixes. The hardware indicator positioning and system-wide dash shortcuts are examples of Microsoft addressing specific, longtime user friction points — small changes with outsized practical benefits. The Windows Share pinning also aligns Windows 11 more closely with modern sharing paradigms found on mobile platforms, helping streamline everyday tasks.
At the same time, Canary-level distribution and the presence of regressions (notably sleep/shutdown reports) reiterate that this build is for testing, feedback, and iteration — not production use. Insiders who enjoy early access will find meaningful, tangible improvements to try, but everyone should be mindful of the stability trade-offs and report issues through Feedback Hub so the features can be refined before wider release.

---

Source: WinCentral Windows 11 Insider Preview Build 27959 (Canary Channel)