• Thread Author
Microsoft’s latest Insider flights deliver a compact but meaningful set of refinements — from a new Copilot prompt box inside Click to Do to a curated Emoji 16 rollout and deep accessibility fixes for Narrator — packaged in Dev build 26220.6682 (and matching Beta build 26120.6682), signaling another step in the company’s incremental 25H2 enablement strategy. (blogs.windows.com)

A modern desk setup with a curved monitor showing AI Ethics in Content Creation and a to-do panel.Background / Overview​

Windows 11, version 25H2 continues to be delivered as an enablement package layered on the existing servicing branch, so Microsoft is shipping frequent, incremental flights rather than a single mass upgrade. The Dev Channel build 26220.6682 (KB5065782) is part of that ongoing cadence and is intended primarily for Insiders who opt into the latest feature toggle; many new experiences are gated by Controlled Feature Rollout (CFR) and by device entitlement (for example, Copilot+ PCs). The official Windows Insider blog post announcing the update summarizes the changes and known issues and underscores Microsoft’s cautious rollout model. (blogs.windows.com)
Community and independent coverage suggests Microsoft is focusing this flight on three converging priorities: AI/productivity polish (particularly Copilot integrations), accessibility improvements (major Narrator fixes), and stability/bug remediation across core subsystems such as File Explorer, the Start menu, and audio capture workflows used by streamers. That interpretation is consistent with both the official release notes and community summaries circulating among Insiders. (windowscentral.com)

What’s new — headline features​

Click to Do: Copilot prompt box and interaction polish​

  • New Copilot prompt box in Click to Do: Users on Copilot+ PCs can now type a custom prompt directly into a text box that is sent to Copilot along with the selected on‑screen content. Suggested prompts appear beneath the box and — importantly — those suggestions are generated locally by Microsoft’s on‑device model stack (Phi‑Silica) for supported text selections in English, Spanish, and French. The feature is regionally gated and not rolling out to the EEA or China at this time. (blogs.windows.com)
  • Gesture and discoverability updates: New visual animations for the right‑edge swipe gesture make the Click to Do gesture feel more intentional and easier to follow, while new “action tags” in contextual menus surface popular AI actions to help discovery.
Why this matters: the prompt box reduces friction for quick, context-aware prompts and brings a more conversational Copilot experience into conventional right‑click workflows. Local suggestion generation is a privacy‑friendly touch because it reduces the need to send selection context to cloud endpoints, although the exact telemetry and retention behaviors of local models should be verified for enterprise deployments.

Start menu prompt examples​

Microsoft is trialing prompt examples in the Start menu’s Recommended section to nudge users toward Copilot-assisted tasks (for example, “create an image with Copilot”). This is a small UX nudge designed to drive awareness and help users learn how prompts map to Copilot features. The experiment is being rolled out gradually. (blogs.windows.com)

Emoji 16: a curated set, not a full dump​

Windows 11 gains a curated set of Emoji 16.0 glyphs in this build — deliberately small and cross‑category rather than the entire Unicode set. The included glyphs are:
  • Face with Bags Under Eyes
  • Fingerprint
  • Root Vegetable
  • Leafless Tree
  • Harp
  • Shovel
  • Splatter
This is a conservative inclusion compared to some platform rollouts that ship the full Unicode addition; Microsoft’s choice is framed as deliberately curated for cross‑cultural utility. Independent coverage notes slight platform disparities — for example, some apps may not render the new glyphs immediately while the system picks them up — and that one flag emoji from the original Emoji 16 list may not be shown on Windows. (blogs.windows.com) (windowscentral.com)

Gaming controller behavior​

Xbox controller ergonomics gained a tiny but useful tweak: a short press of the Xbox button opens Game Bar, while a long press opens Task View. Holding continues to power off the controller. This change improves controller integration for PC multitasking and streamers who switch between windows frequently. (blogs.windows.com)

Narrator and accessibility improvements (substantial)​

This build contains a broad set of improvements to Narrator, targeted specifically at reading and interacting with documents (notably Microsoft Word):
  • Smoother natural‑voice announcements (less pitch jumping when announcing headings, grammar/spelling errors).
  • Better footnote navigation with clearer footnote number announcements.
  • Reliable continuous reading that no longer stops unexpectedly during long passages.
  • Improved comment reading where focus is tracked correctly when moving into the comments pane.
  • More coherent list announcements and navigation; full list items are read even when they wrap across lines.
  • Enhanced table navigation commands (beginning/end of rows and columns in Scan Mode) and clearer boundary announcements to avoid accidental row additions.
  • Better selection feedback when selecting across table cells and awareness of non‑uniform tables.
These changes aim to make Narrator far more usable in professional, document‑heavy workflows and reduce the friction experienced by assistive technology users. The Windows Insider announcement spells out the command keys and behaviors. (blogs.windows.com)

Settings and Other UI changes​

  • Advanced Settings is returning to Settings (Dev and Beta), though Microsoft temporarily removed the long path and virtual workspaces options while they address issues.
  • A new SCOOBE (Second Chance OOBE) reminder surfaces subscription/payment issues for Microsoft 365 during setup, simplifying renewal or payment updates.
  • A targeted fix addressing audio stutters in apps using NDI when Display Capture is active in OBS Studio is included for everyone in the Dev Channel. That fix is particularly important for streamers and content creators who rely on OBS. (blogs.windows.com)

Fixes and reliability work​

The build includes a long list of targeted fixes; of particular note:
  • Resolved a bugcheck (green screen) that could occur during hibernation in recent flights, which also may have been responsible for shutdowns that appeared to hang. (blogs.windows.com)
  • Taskbar: improved reliability of automatic hide/unhide behavior and smoother animations.
  • File Explorer: fixed erroneous visibility of the Shared section with no content, thumbnails for certain video files with EXIF metadata, and context‑menu interactions causing the main area to become unresponsive.
  • Start menu: fixed dismissal when taking a screenshot (WIN + Shift + S) and random scrolling issues.
  • Windows Sandbox: resolved runaway CPU usage by the vmmemCmFirstBoot process.
  • Search: work to reduce cases where search is stuck loading.
  • Voice Access: a fix for error 9001.
  • Windows Hello: fixes for PIN availability in Safe Mode and 0x80090010 errors on certain Entra‑joined devices.
The build also provides guidance on a handful of currently known issues where Microsoft is still investigating root causes. (blogs.windows.com)

Known issues to watch​

Microsoft lists several known problems in this flight; Insiders should read them carefully before updating a production machine:
  • Click to Do right-edge gesture visuals may appear on the wrong display when launched on a primary monitor.
  • Media controls sometimes do not display on the lock screen.
  • Windows Studio Effects can fail on some external webcam models due to firmware compatibility; turning the Studio Effects off in Camera settings is the suggested workaround.
  • Audio device driver issues in Device Manager can show yellow exclamation marks on some systems; Microsoft offers a driver roll procedure as a workaround.
  • Some Insiders reported Xbox controller Bluetooth usage causing bugchecks; Microsoft outlines an uninstall method for the implicated XboxGameControllerDriver.inf entry as a workaround.
  • PIX on Windows cannot play back GPU captures on this OS version until a PIX update is released (Microsoft expected a fix by the end of September at the time of the announcement).
These will remain important for Insiders who rely on specific hardware or workflows (for example, streaming with OBS, developer GPU debugging, or accessibility testing). (blogs.windows.com)

Technical verification and cross‑checks​

The official Windows Insider blog post (the canonical source for the flight notes) documents the changes and the exact build number and KB identifier. The blog post was published on September 12, 2025 and contains the full release notes for Dev build 26220.6682. (blogs.windows.com)
Independent coverage from Windows Central and other outlets confirms the Emoji 16 additions and notes platform differences in rendering and exclusion of certain emojis (for example, flags) on Windows — a useful reality check that the Windows rollout is selective rather than comprehensive. Those reports also highlight differences between what appears in the system emoji panel and what third‑party apps display immediately. (windowscentral.com)
Community reporting and aggregated Insider commentary emphasize the balance Microsoft is striking: incremental AI surface expansions (Click to Do and Copilot prompts) plus substantive accessibility work for Narrator and stability fixes that matter to streamers and enterprise admins. Those community syntheses provide additional operational context for the patch, including practical recommendations and troubleshooting steps.
Note on verifiability: any claim about region‑gating, exact telemetry behavior of on‑device models (Phi‑Silica), or firm timelines for PIX fixes derives from Microsoft’s blog and public statements and should be considered accurate as of the announcement date. Enterprises or security teams that require absolute confirmation should validate those details in controlled lab tests or consult Microsoft support for contractually enforceable assurances. (blogs.windows.com)

Critical analysis — what’s notable, what’s risky​

Strengths and positive signals​

  • Focus on accessibility: The breadth of Narrator updates is notable and represents a material quality‑of‑life improvement for assistive‑tech users. The addition of robust table navigation commands and more natural voice feedback addresses long‑standing pain points for professional document workflows. This is a solid PR and product win for accessibility advocates. (blogs.windows.com)
  • Local model inference for prompts: The use of Phi‑Silica to power suggested prompts locally is a privacy‑forward move that reduces cloud dependency and supports on‑device responsiveness. For enterprises, on‑device inference is often preferable because it minimizes data exfiltration risk. (blogs.windows.com)
  • Targeted fixes for streaming workflows: The OBS NDI/Display Capture audio stutter fix directly addresses a real, cross‑community pain point and demonstrates Microsoft’s willingness to triage and prioritize third‑party interoperability issues that affect creators. (blogs.windows.com)
  • Incremental, controlled rollouts: By continuing to ship features via CFR and per‑device gating, Microsoft reduces blast radius and gives engineers a chance to respond to real‑world feedback before broad availability. This approach benefits stability and quality when executed well.

Risks, edge cases, and enterprise impact​

  • Dev Channel instability: As always, Dev Channel flights can introduce regressions and should not be installed on primary or mission‑critical machines without a rollback plan. The build explicitly fixes some high‑impact issues (hibernate bugcheck) but also introduces new regressions and hardware compatibility edge cases (audio device driver errors, Xbox controller bugchecks). Organizations should stage tests in representative environments.
  • Fragmented emoji and rendering parity: The selective Emoji 16 rollout is user‑facing but inconsistent across apps and platforms, which can create cross‑platform communication confusion. Messaging apps, browsers, and web services may show different glyphs or missing glyphs until they adopt the update. (windowscentral.com)
  • Hidden telemetry and model lifecycle: While on‑device suggestions are better for privacy in principle, any local model still requires updates and may emit telemetry. Enterprises should validate update mechanisms and retention policies for on‑device models before certifying Copilot features for regulated or highly controlled environments. This is a governance task for security teams.
  • Device and regional gating: Copilot+ exclusivity and regional exclusions (EEA, China) mean many Insiders won’t see the features even if they install the build. That complicates testing plans and can create perception problems among users who expect parity. (blogs.windows.com)

Practical recommendations​

For individual Insiders​

  • Back up your system before installing Dev Channel builds.
  • If you rely on OBS or streaming workflows, test the build in a non‑critical environment to verify the audio stutter fix and any controller behavior changes.
  • If you use Narrator, exercise document workflows (Word documents with footnotes, tables, comments) and file bugs/feedback for any regressions via Feedback Hub.

For IT administrators and accessibility testers​

  • Validate Narrator improvements against your standard compliance scenarios and assistive tech stacks. Include web apps and third‑party document editors in test matrices.
  • Keep Copilot feature tests in a lab and document on‑device model update cycles and telemetry options for compliance audits.
  • Do not deploy Dev Channel builds to production endpoints. Use Release Preview or staged deployments after Microsoft graduates these features and fixes.

For content creators and streamers​

  • Run rehearsal sessions on the build with your streaming setup (OBS, NDI workflows, external webcams) before going live. Verify the Xbox controller Bluetooth behavior if you use controllers as input devices.

How to test or roll back specific issues (quick guides)​

  • Fixing yellow exclamation audio devices in Device Manager
  • Right‑click the problematic device, choose Update driver → Browse my computer → Let me pick from a list of drivers on this computer → select the most recent dated driver → Next. Repeat for each affected device. If Device Manager shows generic hardware types instead of specific drivers, that device likely isn’t related to this known issue. (blogs.windows.com)
  • Resolving Xbox controller Bluetooth bugcheck
  • Open Device Manager → View → Devices by driver → find oemXXX.inf (XboxGameControllerDriver.inf) → right‑click on that driver and choose Uninstall. This is the workaround Microsoft provides until a fix ships. (blogs.windows.com)
  • Workaround for Windows Studio Effects camera preview failure
  • Open Camera settings → Advanced camera settings → toggle Use Windows Studio Effects off for affected external webcams until Microsoft’s firmware compatibility update arrives. (blogs.windows.com)

What to watch next​

  • Whether Microsoft expands the Emoji 16 set to full parity with Unicode and how quickly third‑party applications adopt the new glyphs. (windowscentral.com)
  • The pace at which Copilot Click to Do features move beyond Copilot+ hardware and leave regional restrictions behind.
  • Validation that Narrator’s improvements remain stable across multiple app ecosystems (web apps, third‑party office suites) after broader rollouts.
  • PIX playback and GPU capture playback fixes: developers relying on PIX should monitor the PIX release cadence; Microsoft indicated a PIX update was expected to address playback by the end of September at the time of the announcement. (blogs.windows.com)

Conclusion​

Build 26220.6682 (Dev) and its Beta sibling represent a pragmatic, incremental push: Microsoft is layering measured Copilot integrations, shipping a small but meaningful Emoji 16 set, and — crucially — addressing substantive accessibility shortcomings in Narrator. The flight underscores a multi‑track development strategy that privileges controlled rollouts and device gating to limit risk while iterating quickly. For Insiders and testers, this build is worth exploring especially if you focus on accessibility or creative workflows, but it remains ill‑suited for primary devices until these changes graduate to Release Preview or General Availability. (blogs.windows.com)
The path forward should be watched closely: local model inference and Copilot integration are coming into everyday Windows contexts, and the priorities shown in this build — privacy‑friendly local AI, assistive technology robustness, and targeted stability fixes — reflect sensible engineering tradeoffs for a platform with a broad and diverse user base.

Source: Neowin Windows 11 25H2 gets Emoji 16, accessibility improvements, and more in build 26220.6682
 

Back
Top