Microsoft dropped Dev Channel build 26220.6682 (KB5065782) on September 12, 2025, and it’s packed with three distinct threads: a locally inferred Copilot prompt box inside Click to Do, a hand-picked seven-glyph Emoji 16 rollout, and sweeping accessibility enhancements for Narrator. The matching Beta build 26120.6682 confirms this isn’t just an experimental spike—it’s part of the steady, enablement-package cadence that’s defining Windows 11 version 25H2.

Insiders who rely on assistive tech, content creation, or just daily productivity will find material improvements here. But the build also carries a set of known hardware quirks and regional restrictions that remind everyone why Dev Channel flights stay on secondary devices.

The Big Three: AI, Emoji, and Accessibility

Click to Do Gets a Local Brain

The most consequential AI addition is a Copilot prompt box grafted directly into Click to Do. On Copilot+ PCs, after selecting text or content, you can now type a custom prompt that ships off to Copilot along with that selection. Beneath the text field, suggested prompts appear—but crucially, those suggestions are generated on-device by Microsoft’s Phi‑Silica model stack, not fetched from the cloud. For English, Spanish, and French text selections, the inference stays local, cutting both latency and privacy exposure.

This is more than a convenience tweak. By moving suggestion generation to the edge, Microsoft sidesteps the need to send potentially sensitive selection context to servers, a design choice that will resonate with enterprises and privacy-conscious users. The feature is strictly gated by region: the EEA and China do not receive it at this time, and only Copilot+ hardware qualifies. That segmentation complicates testing but aligns with a growing pattern of intelligent, device-conditional rollout.

Visual polish accompanies the functional upgrade. A new right-edge swipe animation makes the Click to Do gesture feel deliberate, and “action tags” now surface popular AI actions in contextual menus, helping newcomers discover what Copilot can actually do. These small discoverability nudges matter because the feature’s promise hinges on users remembering it exists.

Meanwhile, the Start menu’s Recommended section is dabbling in prompt examples. Some Insiders will see phrases like “create an image with Copilot” tucked among recent files. It’s a lightweight nudge meant to bridge the gap between passive awareness and active use—and it’s rolling out gradually, so not everyone will spot it yet.

Emoji 16: Curated, Not Comprehensive

Windows 11 has never been a platform that rushes to adopt every new Unicode glyph, and this build reinforces that philosophy. Instead of the full Emoji 16.0 set, Microsoft cherry-picked seven new emoji:

  • Face with Bags Under Eyes
  • Fingerprint
  • Root Vegetable
  • Leafless Tree
  • Harp
  • Shovel
  • Splatter

The choices span expression, objects, food, and nature, clearly aiming for cross-cultural appeal rather than encyclopedic coverage. Notably absent is the flag emoji that headlined many platform rollouts; community reports confirm it’s excluded from Windows for now. Early adopters are already noting rendering inconsistencies—some apps and websites won’t display the new glyphs immediately, and the system emoji panel sometimes lags behind. For a feature that touches messaging, social media, and design apps, this fragmentation can frustrate users who expect platform parity. Still, the curated approach keeps the update lightweight and avoids bloating the font payload in an enablement package already freighted with other changes.

Narrator: Document Interaction Finally Gets Attention

The most under-hyped but arguably most impactful set of improvements lands in Narrator. Microsoft has clearly placed a bet that robust document reading will win over users who depend on screen readers for productivity. The build targets Microsoft Word specifically, but the behavioral fixes ripple across all text-heavy navigation.

Here’s what changed:

  • Natural-voice smoothness: Pitch jumps when announcing headings, grammar errors, and spelling mistakes are ironed out. This makes long reading sessions less fatiguing.
  • Footnote navigation: Narrator now clearly announces footnote numbers and moves in and out of footnote content without losing context.
  • Continuous reading reliability: The infuriating bug where reading would stop dead mid-passage is fixed.
  • Comment pane tracking: When focus moves to the comments pane, Narrator now follows correctly, reading comments without extra key mashing.
  • List coherence: Items that wrap across multiple lines are fully read, and navigation through lists no longer truncates or repeats content.
  • Table muscle: New Scan Mode commands jump to the beginning or end of rows and columns. Boundary announcements prevent accidental row additions, and selection across non-uniform table cells now behaves predictably.

For assistive tech testers and anyone who lives in Word documents, these are foundational fixes. The improvement to table navigation alone removes a frequent source of friction. Microsoft’s own release notes spell out the exact key combinations, signaling that they expect power users to adopt these commands quickly.

Gaming, Settings, and Audio Fixes

Xbox controller behavior gets a modest but welcome remap. A short press of the Xbox button now launches Game Bar; a long press opens Task View. Holding the button still powers off the controller. For streamers and multitaskers who flip between game overlays and window management, this reduces friction. It’s a tiny tweak that acknowledges how many PC gamers use controllers not just for play but as a nexus for their streaming workflow.

Advanced Settings is tentatively returning to the Settings app in both Dev and Beta. Microsoft removed the long path and virtual workspaces options temporarily to chase down issues, but the broader restoration signals that the feature will survive. Meanwhile, a SCOOBE (Second Chance OOBE) reminder now prods users about Microsoft 365 subscription or payment hiccups during setup—a subtle monetization touch that some will find helpful, others intrusive.

For creators, a targeted fix for audio stutters when using NDI with Display Capture in OBS Studio is included for everyone in the Dev Channel. This issue had plagued streamers whose setups relied on OBS for scene composition while piping audio via NDI. The fix arrives as a direct response to community feedback and represents a rare instance of Microsoft prioritizing third-party interoperability for a niche but vocal user segment.

Under the Hood: Fixes That Matter

The build’s reliability work is extensive. The highlight is a resolved bugcheck—a green screen—that could trigger during hibernation in recent flights. That same bug likely caused shutdowns that appeared to hang. For Insiders who’d grown accustomed to unpredictable restarts, this is a significant relief.

File Explorer gets three distinct corrections: an errantly visible Shared section that appeared even when empty, broken thumbnails for video files with specific EXIF metadata, and a context‑menu interaction that could freeze the main window. The Start menu fixes are smaller but welcome: it no longer dismisses when you take a Win+Shift+S screenshot, and random scrolling jank is reduced.

Other targeted fixes include:

  • Taskbar: Automatic hide/unhide is more reliable, and animations are smoother.
  • Windows Sandbox: The vmmemCmFirstBoot process no longer consumes runaway CPU cycles.
  • Search: Work has gone into reducing cases where the search pane hangs on “loading.”
  • Voice Access: Error 9001 is squashed.
  • Windows Hello: PIN availability in Safe Mode is restored, and 0x80090010 errors on certain Entra‑joined devices are resolved.

These are the kind of quality-of-life fixes that accumulate across flights and eventually make the difference between a build that feels polished and one that feels prototype-grade.

Known Issues: What’s Still Broken

No Dev Channel build is without thorns. Microsoft lists several known problems that Insiders should check before installing:

  • Click to Do’s right-edge gesture visuals may appear on the wrong display when launched on a primary monitor.
  • Media controls sometimes vanish from the lock screen.
  • Windows Studio Effects can fail on certain external webcams due to firmware incompatibility; toggling them off in Camera settings is the workaround.
  • Audio device drivers in Device Manager may sport yellow exclamation marks; a manual driver roll procedure is provided.
  • A particularly nasty bug causes Xbox controller Bluetooth usage to trigger bugchecks; uninstalling the XboxGameControllerDriver.inf driver via Device Manager is the stopgap.
  • PIX on Windows cannot play back GPU captures on this OS version until a PIX update ships; Microsoft expected that fix by end of September.

For streamers, the controller bugcheck and Studio Effects hiccup are the most likely tripwires. Developers relying on PIX for GPU debugging will need to wait or use an alternate OS install.

Analysis: Strengths and Cautions

Privacy-First AI That’s Worth Watching

The decision to power Copilot prompt suggestions locally via Phi‑Silica is a strong privacy signal. It reduces reliance on cloud roundtrips and limits the data surface area. For enterprises navigating compliance frameworks, on-device inference simplifies risk assessments. However, it’s not blanket protection: the local model still receives updates over the network and may emit telemetry. Security teams should audit the update mechanism and any telemetry logs before certifying these features for highly regulated environments.

Accessibility as a Differentiator

Narrator’s improvements are substantive, not cosmetic. By targeting document-heavy workflows, Microsoft is carving out a productive niche for its screen reader that rivals third-party solutions. The table navigation enhancements alone move Narrator from “functional” to “powerful” for professionals who spend their days in Word. Accessibility advocates and enterprise assistive-tech testers should exercise these changes across web apps and alternative office suites to ensure the fixes hold beyond Microsoft’s own ecosystem.

The Emoji Gap and User Frustration

The curated Emoji 16 approach invites cross-platform confusion. When a Windows user sends a “Face with Bags Under Eyes” to an iPhone user, both see the intended glyph. But when a missing flag emoji appears as a square placeholder, it disrupts communication. This isn’t a new problem, but the selective rollout accentuates it. Users who expect emoji to “just work” may not appreciate the nuance of a conservative font update.

Controlled Rollouts: A Double-Edged Sword

CFR and per-device gating keep blast radius small, but they make testing a logistical headache. An IT department that wants to validate Copilot prompts may have to provision specific Copilot+ hardware outside the EEA and China, then hope they fall into the rollout group. For the broader Insider audience, the gating can feel arbitrary and breed resentment. Microsoft needs to provide clearer transparency about which features are active on which devices at any given time.

Practical Guidance for Insiders

  • Back up before you fly. Dev Channel builds remain fundamentally experimental.
  • If you stream with OBS: Test the audio stutter fix in a controlled session. Verify controller Bluetooth stability by running Game Bar with the Xbox controller connected wirelessly. Have the driver uninstall workaround ready.
  • If you rely on Narrator: Dive into Word documents with complex tables, footnotes, and comments. File feedback immediately if you see regression, as these improvements are likely to ride into Release Preview soon.
  • If you’re in enterprise IT: Stage all tests in isolated labs. Do not deploy Dev Channel builds to production endpoints. Document on-device model update frequency and telemetry options for compliance review.

Quick Fixes for Known Issues

  • Audio device yellow exclamation: Right-click the device in Device Manager, Update Driver → Browse my computer → Let me pick from a list → choose the most recent dated driver → Next.
  • Xbox controller bugcheck: Open Device Manager → View → Devices by driver → find oemXXX.inf (XboxGameControllerDriver.inf) → right-click → Uninstall.
  • Studio Effects camera failure: Camera settings → Advanced camera settings → toggle Use Windows Studio Effects off for the affected webcam.

What Comes Next

The trajectory is clear: Microsoft will gradually expand Emoji 16 to full Unicode coverage, push Copilot features beyond Copilot+ hardware, and validate Narrator enhancements across third-party apps. The PIX update timeline is critical for game developers, and the Xbox controller driver fix will need to graduate from workaround to permanent solution. Meanwhile, the on-device model strategy signals a larger shift: Windows is increasingly leaning on local inference for AI features, which could reshape the privacy conversation around Copilot.

The Bottom Line

Build 26220.6682 isn’t a spectacle; it’s a surgical update. It fixes real pain points—hibernate crashes, OBS audio stutters, Narrator’s document-reading gaps—while cautiously layering AI capabilities that respect privacy boundaries. The Copilot prompt box and Emoji 16 set are modest but practical, and the accessibility work is some of the best to hit the Dev Channel in months. For Insiders who value utility over flash, this build is worth installing on a test rig. For everyone else, it’s a preview of a steadier, more thoughtful Windows 11 that continues to inch toward 25H2.