Windows 11 Dev Channel 26220.5770: Copilot features, Excel table conversion, Braille Narrator

Windows Insiders in the Dev Channel are receiving a substantial cumulative flight: Windows 11 Insider Preview Build 26220.5770 (KB5064093), a Dev-only increment that continues Microsoft’s staged push of Copilot‑centric productivity features, expanded Microsoft 365 integration, and accessibility enhancements while chipping away at long‑running platform bugs. This release introduces a new major build identifier for Dev‑channel experimentation, expands Click to Do with a table‑to‑Excel workflow and Microsoft 365 profile cards, and adds a visual Braille viewer to Narrator — all distributed through the Insider program’s controlled feature rollout mechanism rather than a blanket push.

Background / Overview​

The Dev Channel flight to Build 26220.5770 arrives as Microsoft continues splitting development across parallel channels while maturing the near‑final Windows 11, version 25H2 codebase in Release Preview. Microsoft chose to bump the Dev Channel’s major build marker into the 26220 series to separate experimental work from the earlier 26200/26120 sequences used across other rings. That distinction signals the Dev Channel’s role as a flexible testbed where features can appear, change shape, or be removed as feedback arrives.
Microsoft packages this work as cumulative updates (KB labels) delivered through Windows Update to Insiders. Importantly, many visible experiences in this flight are being metered server‑side and exposed only to Insiders who toggle gradual rollout options in Settings → Windows Update. This gating lets Microsoft gather telemetry and limit impact while iterating on detection models, cloud entitlements, and hardware dependencies.

---

What’s new in Build 26220.5770 — At a glance​

• Click to Do — Convert to table with Excel: Detects simple on‑screen tables and offers a direct action to push the captured table into Microsoft Excel or copy/share the result. Early preview access requires the latest Excel and an active Microsoft 365 subscription. Hardware gating currently prioritizes Snapdragon‑based Copilot+ PCs; Intel and AMD Copilot+ support is stated as coming soon. The feature is not initially available in the European Economic Area (EEA).
• Microsoft 365 Profile (Live Persona) cards in Click to Do: Click to Do can now detect tenant email addresses and surface a Microsoft 365 profile card inline, showing contact details and recent collaboration context without switching apps. Requires sign‑in with a work or school account and a Microsoft 365 license.
• Narrator — Braille viewer: A floating on‑screen representation of Braille output that mirrors a connected refreshable Braille display or presents a default 40‑cell view when no hardware is attached. Aimed at sighted teachers, accessibility trainers, and developers who need a visual mapping of textual-to‑Braille output for instruction, verification, and debugging.
• Windows Share — Find apps: The Share UI can now search for installed apps and Store suggestions directly in the share surface, reducing the friction of finding a target app for sharing.
• Stability and platform fixes: A collection of targeted bug fixes across taskbar, File Explorer, HDR and display toggles, some audio recovery scenarios, and Direct3D alignment with the Agility SDK. Known issues remain, including File Explorer Shared‑section misbehavior and a potentially stuck Temporary files scan in Settings.

---

Deep dive — Click to Do: from capture to Excel​

Click to Do has evolved from a lightweight capture tool into a context‑aware productivity surface that can act on selected screen content. The Convert to table with Excel action is the most tangible example in this flight: the system attempts to recognize rendered table structures in screenshots, meeting content, images, and standard documents, then converts that capture into a structured table for Excel. The goal is simple — remove the tedious copy‑and‑paste or retyping step that consumes time after meetings or when working with static visual data.
Key practical notes:

• Detection is early preview: simple, rectangular grids are most likely to convert successfully, while complex layouts (merged cells, nested headers, irregular spacing) can produce imperfect results.
• The end‑to‑end experience requires the latest Microsoft Excel app and an active Microsoft 365 subscription on the same account you use for Windows. This ties the convenience of the capture flow into Microsoft’s cloud identity and licensing model.
• Hardware and regional gating: Microsoft is testing first on Snapdragon Copilot+ PCs and will add AMD/Intel Copilot+ devices later. The feature is initially withheld in the EEA for regional compliance reasons. Both the hardware gating and regional blocks are server‑side switches that may change without a build‑level update.

Practical workflow example:

• Invoke Click to Do (Win + Click, Win + Q, or a touch gesture).
• Select the table area using the available selection modes.
• Choose “Convert to table with Excel” from the action list.
• Send to Excel, copy to clipboard, or share the resulting table.

This workflow is intentionally frictionless, but IT teams should plan for the licensing dependency and confirm the Excel client version and Microsoft 365 tenancy behavior in their environment before promoting the feature widely.

---

Microsoft 365 Profile Cards in the shell — less context switching​

The addition of Live Persona profile cards into Click to Do is a modest UX change with outsized practical benefits for knowledge workers. When Click to Do recognizes an email address tied to an Entra (work/school) account, it can surface a Microsoft 365 profile card inline. The card consolidates contact details, recent messages and files, and shortcuts to common collaboration actions — without needing to open Outlook or Teams. This reduces context switching and keeps quick lookup tasks within the current workflow.
Caveats:

• Requires the user to be signed into Windows with a work/school account (Entra ID) and hold an active Microsoft 365 subscription.
• The card experience surfaces tenant‑aware content; organizations should validate what metadata is shown by default and consider data governance and information‑disclosure implications when rolling the capability out to employees.

---

Accessibility: Narrator’s Braille viewer and why it matters​

The Braille viewer is one of the clearest examples of pragmatic accessibility engineering in this flight. Rather than attempting to mimic tactile feedback, the viewer provides a visual mirror of Narrator’s Braille output. It can show a default 40‑cell view when no physical device is present, or expand to 80 cells for compatible hardware. Teachers, accessibility trainers, and developers who can’t read Braille can use the viewer in real time to follow what a student or user is reading on a refreshable Braille display.
How to enable (high level):

• Install the optional Braille support package via Settings → Accessibility → Narrator if your build includes the update.
• Launch Narrator (Win + Ctrl + Enter).
• Open the Braille viewer with Narrator key + Alt + B (Narrator key: Caps Lock or Insert, depending on your Narrator settings).

The viewer is intentionally a sighted companion; it is not a substitute for a physical refreshable Braille display. However, it materially reduces classroom friction by allowing sighted instructors to validate output and pace lessons without knowing Braille themselves. For AT evaluators and developers, it also offers a quicker way to debug Braille mapping and formatting issues.

---

Bug fixes, platform alignment, and targeted reliability improvements​

Beyond headline features, Build 26220.5770 includes numerous fixes and under‑the‑hood updates that matter to developers, gamers, and IT pros alike:

• Alignment of Direct3D 12 with the Agility SDK to ensure parity between OS APIs and the Agility SDK contents — important for graphics stability and driver interoperability.
• Taskbar and windowing bug fixes, including several taskbar flyout inconsistencies and ALT+Tab‑triggered crashes corrected in recent flights.
• Improvements to the Windows share experience (including Find apps) so sharing content becomes less cumbersome.
• Audio fixes for scenarios where audio stopped after casting to a TV in prior flights; a new class of device driver warnings (yellow exclamation marks) is listed under known issues and is being investigated.

These cumulative, targeted repairs are consistent with the Dev Channel’s current posture: ship experimental UX lifts while steadily reducing noise from long‑standing regressions.

---

Known issues and installation caveats​

Insiders should approach Dev Channel flights with the usual caution. Microsoft called out several items still under investigation:

• File Explorer: The Shared section may appear empty or behave unexpectedly in certain conditions.
• Settings: Scanning Temporary files under System → Storage can get stuck for some users, preventing complete storage analysis.
• Audio/Drivers: A reported audio driver class can show yellow exclamation marks in Device Manager; Microsoft has published troubleshooting steps for affected Insiders.
• Channel volatility: Dev Channel builds are experimental and may introduce regressions; avoid installing on primary production devices without a rollback plan.

If you rely on specific productivity apps, hardware drivers, or infrastructure agents, validate them in a controlled pilot before wide deployment. Insiders who encounter problems are encouraged to file feedback through the Feedback Hub so Microsoft can triangulate telemetry and reproduce issues.

---

Enterprise and IT implications — what to test and why​

Although these Insider builds are not enterprise releases, they surface changes that administrators should understand and validate before employees encounter them in production:

• Licensing and identity dependencies: Click to Do’s Microsoft 365 features require Entra sign‑in and Microsoft 365 licenses. Audit how many seats meet those requirements and whether account sync or Conditional Access policies block the intended behavior.
• Hardware gating and compatibility: Copilot+ features initially target specific hardware classes (Snapdragon Copilot+). IT should inventory Copilot+ devices and determine which staff will benefit from early feature exposure. Support documentation and helpdesk triage should account for hardware differences.
• Accessibility toolchain: The Braille viewer improves training and QA workflows for assistive technology; include this in AT test cases and classroom pilot plans, especially for special‑education deployment scenarios.
• Deprecations and tooling: The broader 25H2 enablement work flags deprecation steps (for example, retirement of older management utilities in other 25H2 notes). Organizations should plan for script and automation validation, especially where older tools or WMIC/PowerShell v2 dependencies exist.
• Update strategy: Use rings and pilot groups. The eKB (enablement package) model for 25H2 simplifies upgrades for already‑patched systems, but IT must still validate driver signing, AV/EDR agent compatibility, and large estate rollouts.

---

Security, privacy, and governance considerations​

Embedding tenant context (Live Persona) and cloud‑backed conversions (Click to Do → Excel) changes the surface area for privacy and data governance:

• Data flow: Convert‑to‑Excel uses on‑device capture plus Microsoft 365 services; confirm whether captured screen data traverses cloud services in your tenant and what retention and access policies apply. Flag any regulated data types (PHI, PII, or controlled documents) for policy review.
• Consent and disclosure: In shared devices or classroom settings, make users aware that selecting parts of the screen can trigger tenant queries or cloud actions. IT should update acceptable‑use guidance and train helpdesk staff on where to look if privacy flags are reported.
• Conditional Access: Some Click to Do M365 actions require a work/school session. Conditional Access policies, multi‑factor authentication, and device compliance checks may block or alter the inline experiences; test these scenarios in a pilot.

If your organization handles sensitive data, treat Copilot/Click to Do features as potential vectors for accidental exfiltration unless policies and tool configurations are validated.

---

How to evaluate and test Build 26220.5770 safely (recommended checklist)​

• Create a pilot ring of non‑critical machines representing typical hardware classes (Snapdragon Copilot+, Intel/AMD Copilot+, and older devices).
• Confirm Windows Update settings and flip on the “gradual rollout” toggle for Insiders if you want to replicate staged exposures.
• Validate Microsoft 365 license status, Excel client versions, and Entra sign‑in for pilot accounts.
• Exercise Click to Do selection modes and the Convert‑to‑Excel action across sample content types (simple tables, nested headers, images with tables). Record accuracy and edge cases.
• Test Braille viewer behavior with and without a physical refreshable Braille display; document the steps teachers or AT trainers need to use it effectively.
• Run a suite of regression checks: File Explorer Shared items, Settings → Storage Temporary files scan, audio device enumeration, and any previously reported WPF/Visual Studio ARM64 issues if relevant.
• File Feedback Hub tickets for any reproducible issues and follow Microsoft’s troubleshooting guidance for known driver problems.

---

Strengths, risks, and where Microsoft needs to be careful​

Strengths:

• These features remove mundane friction from common tasks: converting visual tables to Excel and surfacing contact context inline are practical productivity wins for hybrid knowledge workers.
• Accessibility investments like the Braille viewer reflect a mature, inclusive approach to assistive technology that benefits educators and testers.
• Controlled feature rollouts let Microsoft iterate on detection models and telemetry signals, reducing blast radius for early regressions.

Risks and caveats:

• Licensing and identity gating ties ergonomic convenience to Microsoft 365 entitlements and tenant configuration, which creates management overhead for enterprises.
• Hardware and regional gating may fragment the user experience; employees on unsupported hardware or in blocked regions (EEA) will have an inconsistent toolkit, complicating training and support. The timeline for Intel/AMD Copilot+ support is unspecified. Flag this as time‑gated and subject to change.
• Detection accuracy for table conversion is imperfect at present. Overreliance without verification could introduce data errors; the feature should be treated as an assist rather than authoritative extraction until detection matures.
• Privacy governance needs explicit attention: capture‑and‑send workflows that surface tenant metadata or push data into cloud apps can create accidental disclosures in regulated environments.

---

Final assessment and recommended next steps​

Build 26220.5770 (KB5064093) is a carefully staged step toward integrating Microsoft 365 into the Windows surface and improving accessibility tooling without forcing a large, risky platform change. The practical Click to Do advances and the Narrator Braille viewer are both useful and thoughtfully scoped, but they come with dependencies — licensing, hardware, and regional restrictions — that will make their enterprise adoption uneven in the short term. Pilot the features with representative user groups, update governance documentation to reflect new data flows, and ensure helpdesk teams are prepared for device‑ and region‑specific support requests.For Insiders, the build is an invitation to test real‑world workflows: share feedback through Feedback Hub, document failures for Microsoft to triage, and avoid installing Dev Channel builds on a primary production device until fixes and broader compatibility signals appear. Microsoft’s controlled rollout approach means the experience will change rapidly — expect iterations, rollbacks, and enhancements as telemetry and community feedback shape the product.

---

The release of Build 26220.5770 shows Microsoft continuing its incremental, user‑driven approach to introducing productivity and accessibility features into Windows 11. The advances are practical and meaningful today for the right users and hardware, but they also underscore the need for disciplined pilot testing, governance updates, and careful communication across IT and end users as Copilot‑enabled capabilities move from preview to broader availability.

---

Source: SSBCrack Windows 11 Insider Preview Build 26220.5770 Now Available in Dev Channel - SSBCrack News