Windows 11 Insiders in the Beta Channel just got another serving of polish and productivity smarts with the release of Build 26120.5770 (KB5064089). This cumulative update, part of the 24H2 servicing stream, lands as a near-final proving ground for features that may ship broadly—delivering new Copilot+ experiences, a long‑awaited accessibility tool, and a suite of fixes that smooth out rough edges reported in earlier flights.

Microsoft’s Beta Channel for version 24H2 operates as an enablement‑style train: builds arrive as 26120.xxxx cumulative packages and are often split into two deployment buckets. One bucket is reserved for features that roll out gradually to Insiders who flip the “get the latest updates” toggle; the other delivers fixes and universally available improvements to every device that installs the update. Build 26120.5770 continues that pattern, blending new AI‑powered interactions, a fresh Braille viewer inside Narrator, and under‑the‑hood graphics alignment with the Agility SDK.

Copilot+ and Click to Do gain real productivity chops

The headliner in this flight is unquestionably Click to Do. Microsoft’s on‑screen AI action surface now sports two new capabilities that inch it closer to a genuine productivity tool.

Convert to table with Excel is the standout. Click to Do can now detect simple tables in the UI—whether they appear in a screenshot, a video conference share, or a static document—and offer an action to convert that visual data directly into an editable Excel spreadsheet. You can capture, copy, or share the resulting table without manually retyping a single cell. Table detection is still in early preview and will improve in later builds, but the promise is clear: raw visual data becomes structured, transferable information in seconds. This feature requires a Microsoft 365 subscription and the latest Excel install for the full experience, and it is currently blocked in the European Economic Area. Rollout begins on Snapdragon‑powered Copilot+ PCs, with AMD and Intel Copilot+ support to follow.

Microsoft 365 profile cards inside Click to Do bring contextual collaboration details directly into the flow. When Click to Do recognizes an email tied to a work or school Entra ID tenant, it surfaces an inline profile card—no need to switch to Outlook or Teams to fetch contact info or organizational context. A work/school account and a Microsoft 365 subscription are required. For enterprise users, this is a subtle but powerful productivity accelerant: the information you need appears right where you are working.

These two additions signal Microsoft’s determination to turn Click to Do from a lightweight action bar into a capture‑and‑transfer engine deeply intertwined with Microsoft 365 entitlements.

Narrator gets a Braille viewer for sighted instructors and testers

Accessibility receives a meaningful bump with the introduction of a Braille viewer inside Narrator. This floating window displays the textual and Braille representation of output from a connected refreshable Braille display—or a default 40‑cell view when no display is present. Teachers of students with visual impairments, assistive‑technology trainers, developers, and QA testers can now see what a Braille user is reading, verify formatting, and debug Braille output without needing to read Braille themselves. The viewer includes controls to adjust the number of displayed cells and to reposition the window, making it equally handy in a classroom or a lab.

Microsoft positions this as a tool for sighted allies who support Braille users, and that framing is spot‑on. It fills a long‑standing gap in Windows’ assistive technology stack and will likely be welcomed by education and enterprise accessibility teams.

Small but welcome OS tweaks

Two additional improvements, both gradually rolling out, deserve mention:

  • Windows Share – Find Apps: The Share UI now surfaces locally installed and Microsoft Store apps directly when you search within the share dialog. Finding the right target for a file or link is now much faster.
  • Direct3D 12 parity with Agility SDK 1.616.1: Developers can rely on the OS‑level Direct3D12 matching the latest Agility SDK, simplifying graphics pipeline testing and ensuring consistent frame‑pacing behavior across different build configurations.

Fixes tackle real‑world regressions

Build 26120.5770 ships a batch of targeted fixes that respond to user‑reported bugs from prior 26120‑series flights. These become active only when the “get the latest updates” toggle is on, but they address pain points that daily‑driver Insiders have been vocal about:

  • Taskbar & System Tray: Incorrect flyout behavior when clicking date/time on a secondary monitor is fixed, and duplicate preview thumbnails no longer appear when switching desktops after minimizing apps.
  • Windowing: An explorer.exe crash triggered by Alt+Tab in the previous build is resolved.
  • Display: HDR no longer toggles itself off spontaneously—a bug that had prevented re‑enabling HDR in Settings.
  • Audio: Casting audio to a TV no longer cuts out after a few seconds.
  • Other platform fixes: Smart card driver error 31 is corrected, a diskusage help text typo is cleaned up, and a PIN confirmation issue when casting from Quick Settings is squashed.

These fixes mirror the Beta Channel’s current posture: quality and polish over splashy new features. Community reports from earlier 26120 builds have consistently called for better dark‑mode consistency, File Explorer context‑menu stability, and taskbar/Start reliability—and this build delivers on many of those asks.

Known issues and installation caveats

No Insider flight is without wrinkles, and Build 26120.5770 carries a handful of known issues that testers should weigh:

  • File Explorer may show a Shared section even when no content is available.
  • Settings can get stuck scanning Temporary files under System > Storage.
  • Audio device errors: A newly reported class of audio driver failures shows yellow exclamation marks in Device Manager; manual driver update is the current workaround.
  • Xbox Controllers: Bluetooth‑connected Xbox controllers may trigger a system bugcheck (blue screen). Microsoft provides a Device Manager workaround—uninstalling the oemXXX.inf XboxGameControllerDriver.inf driver package—until a proper fix ships.

These cautions echo continuing community reports about update rollbacks (error 0x80070005) and device‑specific regressions. The Beta Channel remains pre‑release software with real deployment risk, and Microsoft’s official guidance is unchanged: enable it only on machines you can restore quickly, and consider flipping the “get the latest updates” toggle only if you want to maximize exposure to staged experiments—and accept the accompanying instability.

The strategic calculus behind Build 26120.5770

1. Incremental AI feature gating on Copilot+ hardware

Microsoft’s 2025 insider strategy has been to gate the most sophisticated on‑device AI experiences to Copilot+ certified hardware, then broaden support to AMD and Intel platforms later. Build 26120.5770 uses this playbook: the Convert to table with Excel action debuts on Snapdragon‑powered Copilot+ PCs, with AMD and Intel support promised downstream. This approach lets the company collect real‑world telemetry from NPU‑accelerated devices while minimizing risk during early AI model validation. For testers, however, it creates a fragmented experience: some machines get the full suite, others wait. IT pilots must include diverse hardware classes in their evaluation fleets to avoid surprises.

2. Microsoft 365 as both enabler and lock‑in

Both the Convert to table with Excel and profile card features require a Microsoft 365 subscription. This deepens the value proposition for enterprise customers while embedding subscription entitlements directly into core OS interactions. The flip side is a two‑tier experience: users without a subscription see reduced functionality, even though the underlying AI processing likely runs on the same hardware. As these capabilities inch toward broad availability, the licensing dependency will be a sticking point for some organizations.

3. Accessibility gains traction, but regional gating remains

Braille viewer is a genuine advance for inclusive classrooms, but the update also underscores a recurring theme: several Copilot and Click to Do features are not rolling out in the EEA. Accessibility tools must be globally available to serve diverse education and enterprise deployments; regional delays during preview can hinder international pilot programs and teacher training. Testers should verify what is actually available in their region before drawing up deployment plans.

4. Focused stability work yields real productivity gains

The sheer number of small fixes—duplicate thumbnails, explorer crashes, HDR toggling off—shows Microsoft is listening. These are the kinds of daily friction points that erode user confidence, and addressing them head‑on in the Beta Channel raises the quality bar for eventual production releases. Yet persistent issues like the Xbox controller bugcheck and audio driver fragility remind us that device diversity still challenges update reliability. IT shops must continue to treat Beta builds as test‑only, not as pre‑production rollouts.

How to test Build 26120.5770 responsibly

For power users, testers, and IT pilots who want to kick the tires, a structured approach reduces risk:

  1. Back up important data and create a full system image or recovery drive.
  2. Install on non‑production hardware (or VMs) that reflect your target device classes—Copilot+ hardware for AI tests, standard Intel/AMD devices for baseline behavior.
  3. Enable the gradual rollout toggle (Settings > Windows Update > Windows Insider Program > Get the latest updates as they are available) if you want to see CFR features early.
  4. Exercise the scenarios that matter:
    - Click to Do: highlight a visual table, invoke Convert to table with Excel, and verify content fidelity in Excel.
    - Narrator: connect a refreshable Braille display and check Braille viewer output.
    - Gaming/peripherals: test Bluetooth Xbox controller stability and audio casting to a TV.
  5. Log issues in Feedback Hub with clear reproduction steps; include diagnostic traces when possible.
  6. Monitor Flight Hub and the Insider blog for updated known‑issue notes, and follow Microsoft’s workarounds if you hit rollbacks or blue screens.

What this means for enterprise IT

  • Beta Channel builds are validation platforms, not deployment candidates. Use them to check software compatibility, telemetry behavior, management policies, and Copilot‑related controls.
  • Hardware variance is real. Copilot+ capabilities differ by chipset and enrollment status; pilot programs must mirror your production fleet’s hardware diversity.
  • Privacy and compliance must be front and center. AI features that capture screenshots or surface profile data should be assessed under your organization’s data‑handling rules. Confirm whether snapshots are processed on‑device or routed to cloud services, and map that behavior to your compliance framework.
  • Rollback readiness is essential. Maintain system images, restore points, and test recovery steps for common pitfalls like update rollbacks and driver regressions.

The bottom line

Build 26120.5770 (KB5064089) is a polish‑meets‑capability update that nudges Click to Do closer to a real productivity engine, delivers a practical accessibility tool with Braille viewer, and irons out a dozen user‑reported annoyances. It is not a dramatic pivot in Windows’ roadmap, but it is a visible, methodical step in weaving AI into everyday workflows while preserving a measured, telemetry‑driven rollout.

For Insiders willing to accept the Beta Channel’s pre‑release risks, this flight offers a meaningful preview of where Windows productivity and accessibility are headed. Enterprises should continue to treat it as an early validation platform, paying close attention to hardware gating, Microsoft 365 dependencies, and the known update fragilities that persist across the 26120 series. As Microsoft refines table detection, profile‑card behavior, and Braille integration, the feedback loop from this build will help shape the polished features that eventually land on production desktops.