Windows 11 KB5065789: Narrator Braille Viewer, Click to Do Tables, File Explorer AI

Microsoft has begun seeding KB5065789 to the Release Preview Channel, delivering targeted accessibility and productivity upgrades to Windows 11 versions 24H2 and 25H2 — notably an improved Narrator with a new Braille Viewer and more natural table/list reading, and an expanded Click to Do that can detect simple on‑screen tables and export them to Excel. These changes arrive as preview builds 26100.6713 (24H2) and 26200.6713 (25H2), and Microsoft is rolling many features gradually with hardware- and region-based gating while continuing to refine detection, summary fidelity, and privacy options. (blogs.windows.com)

Background / Overview​

Windows 11’s servicing model in 2025 emphasizes staged, enablement-style updates: binaries are often staged in cumulative updates and then activated via an enablement package (eKB) to flip a device from one servicing baseline (24H2) to a new feature set (25H2). KB5065789 follows that pattern: it arrives in Release Preview so organizations and enthusiasts can validate near‑final bits ahead of general availability. The update increments 25H2 devices to build 26200.6713 and 24H2 devices to build 26100.6713 under the KB5065789 servicing package. (blogs.windows.com)
Microsoft structures these deliveries in two buckets: features that roll out gradually (server-side toggles, hardware or license gated) and items that are included in the build immediately. That distinction matters for IT: two machines on the same build may show different experiences depending on user entitlements, region, or device family. Administrators should treat Release Preview as a validation window, not a drop‑everything approval for broad deployment. (blogs.windows.com)

---

What KB5065789 adds (high level)​

The update touches several functional areas. The most user‑visible and strategic items are:

• Accessibility: significant Narrator improvements, including a Braille Viewer and improved reading/navigation of lists and tables.
• Productivity / AI surface: Click to Do table detection (Convert to table with Excel), improved action tags, and crisper Summarize outputs.
• File Explorer: new AI actions surfaced in the right‑click menu for image edits and Copilot-powered summarization for supported documents.
• Platform polish: Emoji 16.0 glyphs, a refreshed Share experience, Auto SR (automatic Super Resolution) for Copilot+ devices, and assorted security and gaming tweaks.
• Enterprise considerations: the enablement package model for 25H2 and continued removals of legacy tooling that administrators must validate before widescale rollouts. (blogs.windows.com)

These features reflect Microsoft’s twin priorities: expand accessibility tooling for users with disabilities while embedding AI-assisted, Microsoft 365‑centric productivity flows into the Windows shell.

---

Narrator: what changed and why it matters​

Braille Viewer — a visible improvement for testing and teaching​

Narrator now includes a Braille Viewer — a floating on‑screen window that displays both textual output and a Braille representation, either mirroring a connected refreshable Braille display or providing a default 40‑cell fallback when hardware isn’t present. This is designed to help sighted teachers, accessibility trainers, developers, and testers observe what a Braille user would receive in real time. The viewer updates dynamically as Narrator navigates and includes controls for cell count and window placement. To open Braille Viewer: start Narrator (Win + Ctrl + Enter) then press Narrator key + Alt + B. (blogs.windows.com)
Why this matters: refreshable Braille devices remain essential for many blind users. Previously, visual verification of Braille output required external hardware or awkward tooling. The Braille Viewer lowers the barrier for accessibility evaluation, making it easier to train, QA, and debug assistive flows in real classrooms and enterprise acceptance tests.

Naturalized reading for tables, lists, and Word workflows​

Narrator’s spoken output has been refined to be smoother and less jarring — particularly within Word documents. Microsoft adjusted voice feedback to avoid exaggerated pitch jumps and improved continuous reading, footnote navigation, and selection feedback. Crucially, Narrator now announces table boundaries and list items in a more coherent way so structured content is easier to follow. These changes reduce cognitive load for users who rely on screen readers during long editing or review sessions. (blogs.windows.com)
Caveat: while these improvements are concrete, complex document layouts or third‑party apps can still present edge cases; accessibility advocates should continue to stress‑test Narrator across the full mix of web apps, office suites, and PDF readers to capture regressions before wide deployment.

---

Click to Do: table detection and smarter actions​

Convert on‑screen tables to Excel (how it works)​

Click to Do’s new table detection recognizes simple tabular structures visible on the screen (web pages, Teams shared content, screenshots, static images). After invoking Click to Do (Win + Click, Win + Q, or touch gestures), a user can highlight a table region and choose Convert to table with Excel, which will either open the captured table in Excel for editing, copy it to the clipboard, or present sharing options. This end‑to‑end step is aimed at eliminating manual retyping and reducing context switches. (blogs.windows.com)
Important operational details:

• Hardware & license gating: the feature is rolling out first to Copilot+ PCs (initially Snapdragon‑powered devices). Support for AMD and Intel Copilot+ PCs is stated as “coming soon.”
• App and subscription requirements: to push captured data directly into Excel, the device must have the latest Excel app and the signing account typically requires a Microsoft 365 subscription.
• Regional limits: Microsoft is not rolling some Click to Do table functionality into the European Economic Area immediately; availability varies by region.

Practical implications and limitations​

• Detection quality at launch is explicitly labelled preview — simple, well‑formed tables are likely to work reliably, while complex tables (merged cells, nested tables, images embedded in cells, or irregular grids) will generate imperfect captures. Microsoft expects to refine detection models in future flights.
• The workflow ties productivity value to Microsoft 365 entitlements, which has administrative implications for organizations that want broad access without adding licenses.
• Hardware gating complicates support documentation: helpdesks will need clear troubleshooting steps and feature visibility checks to explain why two identically patched PCs might have different Click to Do options.

---

File Explorer AI actions and Copilot integration​

KB5065789 also includes the long‑anticipated AI actions in File Explorer, surfaced as a right‑click menu entry for supported files. The initial image actions supported include Visual Search (image-based web search), Blur Background, Erase Objects (generative erase), and Remove Background — capabilities surfaced via the Photos and Paint apps as part of an integrated workflow. For documents stored in OneDrive or SharePoint, File Explorer offers a Summarize action that leverages Copilot to produce short highlights without opening each file. (support.microsoft.com)
Key limitations and requirements:

• Image actions target standard formats (.jpg, .jpeg, .png).
• Document summarization typically requires a Microsoft 365 subscription and Copilot entitlement for full functionality; admin and tenant constraints may apply.
• The rollout is phased; Microsoft postponed or staged the File Explorer AI actions in earlier builds to smooth the deployment curve. Administrators should expect additional server‑side gating as Microsoft monitors telemetry. (support.microsoft.com)

---

Platform polish: emoji, sharing, Auto SR, and gaming​

KB5065789 bundles smaller but meaningful quality‑of‑life changes:

• Emoji 16.0: Microsoft added a curated set of Emoji 16 glyphs to the picker (a selective rollout rather than the entire Unicode set). This is cosmetic but notable for user expression.
• Windows Share improvements: the Share dialog can now search installed apps and suggest Store results inline, reducing friction when routing content to less‑used apps.
• Auto SR (Automatic Super Resolution): available on Snapdragon Copilot+ PCs to improve in‑game visuals with simplified toggles and potentially one‑click enabling from in‑game notifications; Microsoft intends to expand control surfaces over time. (elevenforum.com)

These smaller items compound into a more polished everyday experience, but they are the kinds of changes that often reveal device‑specific regressions — particularly with GPU drivers, HDR stacks, and controller support — so include these in pilot testing.

---

Security and enterprise considerations​

Enablement package model and migration path​

Because 25H2 is largely enabled via an enablement package (an eKB), upgrades between 24H2 and 25H2 are low‑impact from a binary distribution standpoint. That reduces update time and simplifies image management. However, this model increases the importance of feature‑level validation: when features are flipped on, scripts, agent software, or drivers that previously worked may be impacted. Administrators should focus tests on newly enabled features and any removed/deprecated components rather than revalidating the entire OS image.

Legacy tooling removals​

Recent Windows servicing notes have emphasised the removal or deprecation of legacy utilities (for example PowerShell v2 or WMIC in earlier enablement work). Any organization with legacy automation or monitoring that relies on older tooling must inventory and migrate scripts to supported APIs (PowerShell 5.1/7+, modern CIM/WMI equivalents) or risk breakages during enablement. This continues to be one of the most actionable risks for enterprise deployments.

Licensing, privacy, and regional constraints​

• Many AI-enhanced features are tied to Microsoft 365 subscriptions or Copilot licenses; organizations must confirm entitlements and tenant settings before relying on features for workflow automation.
• Microsoft has restricted some feature rollouts in the European Economic Area and may continue to regionalize capabilities while addressing regulatory or compliance concerns. Always verify availability in target markets during pilot planning.

---

Deployment guidance for IT and power users​

• Inventory critical automation and tools that might depend on legacy components (WMIC, PSv2). Prioritize migrating or testing those first.
• Create a controlled pilot ring using Release Preview devices to validate the exact combination of build, feature flags, and tenant entitlements your users will experience. Focus testing on Narrator flows, Click to Do table conversion, File Explorer AI actions, and GPU driver interactions (Auto SR/HDR). (blogs.windows.com)
• For organizations that rely on accessibility certification or procurement, exercise Narrator’s Braille Viewer with sample content types (complex tables, nested lists, PDFs, web apps) and confirm third‑party app compatibility. Document any anomalies and file feedback through the Insider channels.
• Confirm Microsoft 365/Copilot licensing and Excel app versions for users who will rely on Click to Do conversions; where Microsoft 365 licenses are not feasible, plan alternate capture/ingestion workflows.
• Communicate transparently with support teams: provide a short verification checklist (are you on build 26100.6713/26200.6713? Is the device Copilot+ and on the expected SKU? Is the user signed into a tenant with Copilot/Microsoft 365 access?). This reduces ticket churn from variable feature visibility.

---

Strengths, limitations, and risk analysis​

Strengths​

• Accessibility commitments: the Braille Viewer and overall Narrator improvements represent a genuine, practical win for assistive technology users and assessors. They make it easier to validate and teach Braille and screen‑reader workflows.
• Productivity without context switching: Click to Do’s table detection and File Explorer AI actions reduce the friction of copying data across apps and can meaningfully speed routine tasks for knowledge workers.
• Operationally sensible delivery: the enablement package approach minimizes installation impact and lets IT teams validate specific features without reimaging devices.

Limitations and risks​

• Staged, gated rollouts create inconsistent user experiences. Two machines may be patched identically but show different features because of hardware gating, tenant entitlements, or regional restrictions. This complicates documentation and support workflows.
• Licensing‑bound features tie workplace productivity gains to subscription costs. Organizations should weigh the cost/benefit of enabling Copilot/Microsoft 365 entitlements broadly versus selective deployment.
• Detection and generative features are inherently probabilistic. Early table detection is promising but will err on complex layouts; reliance on it for critical ingestion should be deferred until models mature.
• Accessibility regressions remain a risk when UI polish isn’t validated across all assistive toolchains. The Narrator enhancements are promising but must be validated widely to ensure no unintentional regressions arise.

Where claims could not be independently verified: Microsoft’s communications are clear about the features and gating model, but precise calendar timing for broader AMD/Intel Copilot+ hardware support and region‑wide availability remains subject to Microsoft’s phased rollout schedule. Treat any statements about “coming soon” as indicative but not committed dates. (blogs.windows.com)

---

Quick testing checklist (for accessibility testers and power users)​

• Confirm build: Settings → Windows Update shows build 26100.6713 or 26200.6713 (KB5065789).
• Narrator: Start Narrator (Win + Ctrl + Enter) and open Braille Viewer (Narrator key + Alt + B). Verify live updates with a refreshable Braille display or the 40‑cell fallback.
• Click to Do table capture: Invoke Click to Do (Win + Click or Win + Q), select a simple table in a web page or document, and try Convert to table with Excel; confirm Excel receives structured data. If Excel/opening fails, verify Microsoft 365 subscription and Excel client version.
• File Explorer AI actions: Right‑click a supported image file (.jpg/.png) and look for AI Actions (Visual Search / Blur Background / Erase Objects). For documents in OneDrive/SharePoint, test the Summarize action. (support.microsoft.com)
• Pilot performance tests: enable Auto SR on a Copilot+ device and benchmark a supported game to assess compatibility and visual results. (elevenforum.com)

---

Conclusion​

KB5065789 is a pragmatic update that layers meaningful accessibility and productivity improvements onto Windows 11’s 24H2/25H2 servicing baseline. The Narrator Braille Viewer and naturalized table/list reading are concrete wins for assistive technology, while Click to Do’s table detection and File Explorer AI actions promise to shave repetitive, context‑switching work from knowledge‑worker workflows. The tradeoffs are familiar: phased, hardware‑ and license‑gated rollouts create temporary inconsistency and introduce dependency on Microsoft 365 entitlements for the full experience.
For IT teams, the path forward is clear: pilot widely, validate accessibility and legacy automation scenarios early, and document feature visibility for end users. For accessibility stakeholders and power users, KB5065789 is worth testing now — but real‑world adoption should be paced to match feature fidelity, licensing plans, and organizational risk tolerance. (blogs.windows.com)

---

Source: Windows Report Windows 11 KB5065789 Release Preview upgrades Narrator and Click to Do for 24H2 & 25H2