Windows 11 Release Preview KB5065789: AI File Explorer Actions and Braille Viewer

  • Thread Author
Microsoft’s optional Release Preview package KB5065789 lands as a compact but consequential update for Windows 11, bringing AI-powered File Explorer actions, a redesigned Advanced (formerly “For developers”) settings page, expanded accessibility features — including a Braille Viewer — and a suite of taskbar and desktop usability tweaks that preview what’s coming in the broader 25H2 enablement wave. This preview is being distributed as an optional, non‑security servicing package to Release Preview insiders and is intentionally staged: many AI features are gated by region, licensing (Microsoft 365 + Copilot), and device entitlement (Copilot+ hardware). Early community and press coverage documented the user-facing changes; Microsoft’s support notes and the Windows Insider Blog provide the authoritative rollup and install guidance.

Background / Overview​

Windows update delivery in 2025 continues the model of enablement packages layered onto existing servicing branches (24H2 and 25H2). KB5065789 is a Release Preview package that carries both the cumulative LCU and the servicing stack (SSU) components that, once installed, change the servicing baseline on a device. Microsoft has published a formal KB article for the package listing feature additions, fixes, and known limitations; the Windows Insider Blog posted companion release notes explaining the staged rollout and the builds seeded to Release Preview. These official posts confirm that the package is optional and that the most visible items are being rolled out gradually rather than appearing on every machine at once.
Windows Report’s early writeups captured many of the user‑visible additions and gave practical context for how the features behave in the wild. Their coverage highlights the taskbar and desktop changes and digs into the redesigned Advanced Settings and Voice Access upgrades that Microsoft is previewing to testers. Those writeups are useful for user-facing descriptions and community feedback, but the definitive technical details and licensing gates come from Microsoft’s own KB and Insider blog entries.

What’s in KB5065789 — Headline Features​

Below is a condensed, verifiable list of the highest‑impact items in the preview package, with the technical conditions and limits you need to know up front.
  • File Explorer AI actions (context menu) — image edits and Copilot Summarize for OneDrive/SharePoint documents. Supported image types: .jpg, .jpeg, .png. The Summarize action requires an active Microsoft 365 subscription and a Copilot license. Availability is not universal — the EEA is explicitly excluded at rollout.
  • Redesigned Advanced settings page (Settings > System > Advanced) — this replaces the legacy “For Developers” area, consolidates developer and system toggles, and surfaces Git/Version control details directly in File Explorer for repository folders.
  • Voice Access and dictation upgrades — natural language commands for Voice Access and improvements to on‑device dictation, with expanded support for Intel and AMD Copilot+ PCs. Some voice improvements are tied to Copilot+ hardware entitlements and on‑device AI models.
  • Accessibility improvements — Narrator gains a Braille Viewer (enables paired refreshable Braille displays), improved reading/navigation in Word tables/lists, and smoother Narrator feedback overall.
  • Taskbar and desktop polish — easier pinning to the taskbar without restarting explorer.exe (pinning policy takes effect within hours), moveable on‑screen hardware indicators (volume, brightness, airplane mode), an improved Windows Share window with pinning for favorite targets, and minor taskbar UX fixes and clock options.
  • Miscellaneous: Emoji 16.0 glyph updates, keyboard shortcuts for inserting en‑ and em‑dash, Xbox controller Task View behavior, enterprise features such as Administrator Protection Preview and plugin support for passkeys.

File Explorer’s AI actions — closer look​

What the new context menu exposes​

The File Explorer context menu now contains an AI actions entry. For images (.jpg/.jpeg/.png) Microsoft ships four initial AI image edits surfaced directly in Explorer:
  • Visual Search (use an image to search the web)
  • Blur Background (opens Photos to apply subject focus)
  • Erase Objects (generative erase via Photos)
  • Remove Background (opens Paint to produce a subject cutout)
For documents stored in OneDrive or SharePoint, a Summarize action invokes Copilot to produce concise highlights without opening each file — a workflow shortcut aimed at triaging large file sets. Microsoft’s KB specifically states that Summarize requires Microsoft 365 + Copilot licensing.

Practical limits and gating​

  • File types for image edits are currently limited to common raster formats (.jpg/.jpeg/.png). Expect broader support to be added later rather than immediately.
  • The Summarize action invokes cloud or service‑side Copilot processing and is license gated. Without a Microsoft 365 + Copilot entitlement, the Summarize option may not be available. The EEA is excluded from the initial rollout.

Why this matters​

Integrating AI actions into the shell reduces app‑switching friction and can accelerate common content tasks. For power users and knowledge workers who triage files from OneDrive/SharePoint, the Summarize action promises time savings — but only for accounts and tenants with the right licensing.

Taskbar and desktop customization: real changes, limited scope​

KB5065789 continues Microsoft’s iterative approach to returning or reintroducing flexibility where it was previously limited. The package includes several incremental taskbar and desktop quality‑of‑life tweaks:
  • Pinning policy no longer requires an explorer.exe restart; pins applied via policy may appear within a few hours rather than forcing a restart. This is a small but meaningful operational improvement for IT admins.
  • Moveable hardware indicators let users reposition overlays for volume, brightness, and airplane mode. This addresses persistent UX complaints about overlay placement obscuring content.
  • Windows Share improvements permit pinning favorite recipients/apps into the Share window for faster access.
Windows Report’s coverage emphasized the taskbar and desktop aspects as the most immediately visible changes to everyday users, noting that these UX tweaks are part of Microsoft’s broader attempt to soften friction in the shell. Those writeups are helpful for understanding how the features appear to testers, but the KB confirms the specific behavior and rollout limitations.

Advanced Settings: For Developers rethought​

What’s changed​

The “For Developers” page has been reorganized into a more comprehensive Advanced settings area under Settings > System > Advanced. The new page:
  • Consolidates developer and system options in one place
  • Adds a Git/File Explorer + version control card, showing branch, diff count, and last commit metadata directly in File Explorer when a repository folder is selected
  • Surfaces toggles and task‑kill integration intended to simplify developer workflows on local machines
The Windows Insider Blog and Microsoft’s KB explicitly call out Git integration and other developer‑centric settings as part of this refresh. For developers, exposing VCS state in Explorer is a convenience that reduces context switching.

Caveats​

The Git/Explorer integration is primarily cosmetic and convenience oriented; it’s not a substitute for full IDE integrations. It’s also a staged feature — you may not see it unless your device is eligible for the staged rollout.

Voice Access and dictation upgrades​

Voice Access and Windows’ dictation stack have both been extended in this preview.
  • Natural language commanding in Voice Access now accepts more conversational phrasing (filler words, synonyms) rather than rigid, template commands. This aims to reduce the training time required to speak naturally to the system. Microsoft notes this is available for Intel and AMD Copilot+ PCs, which signals a hardware entitlement in some scenarios.
  • On‑device dictation improvements and “fluid dictation” features reduce reliance on cloud services for basic punctuation and grammar insertion, improving responsiveness and privacy in certain cases. Some advanced voice features remain gated to devices with on‑device AI acceleration.
These upgrades are meaningful for accessibility and productivity, but the Copilot+ hardware and licensing gates mean availability will be uneven across the installed base.

Accessibility: Braille Viewer and Narrator enhancements​

KB5065789 advances Windows’ accessibility story with tangible additions:
  • Braille Viewer: Narrator now includes a Braille Viewer that mirrors on‑screen text to a paired refreshable Braille display, opening a new floating window that updates dynamically as the user navigates. Microsoft provides setup guidance (Narrator + Braille support package) in the KB.
  • Improved Narrator behaviors for Word documents (tables, lists, footnotes), as well as more reliable continuous reading and selection feedback. These changes aim to make Windows a more robust platform for screen‑reader and Braille users.
For accessibility advocates, the Braille Viewer is a substantial step — it’s practical, device‑oriented, and addresses real workflow needs for blind and low‑vision users.

Deployment, installation, and enterprise considerations​

How KB5065789 is delivered​

  • The package is published as an optional preview in Windows Update; administrators can acquire it via Windows Update for Business, WSUS, or the Microsoft Update Catalog. If you’re enrolled in Release Preview, the builds were first seeded on or around mid‑September 2025 and subsequently updated with micro revisions. Microsoft emphasizes that the combined SSU+LCU is applied as a single package; removing the LCU later requires DISM and careful operations.

Build numbers & staging complexities​

Community reporting and Microsoft’s Insider blog referenced multiple micro‑revisions as the package rolled: initial builds 26100.6713 / 26200.6713 and then small follow‑up revisions (26100.6718 and later 26100.6725). Some community sources reported different micro builds; Microsoft’s official KB and Insider notes are the authoritative record and should be used when documenting exact build numbers. Treat conflicting community build claims as unverified until Microsoft’s update history confirms them.

Enterprise risk notes​

  • The SSU portion of combined packages is persistent; rollbacks are nontrivial. Microsoft’s KB notes the LCU can be removed with DISM, but the SSU remains. Test pilot devices before broad deployment.
  • Many AI features are license and hardware gated. Enterprises should audit Copilot/Microsoft 365 entitlements and plan for controlled pilots if these features are relevant to workflows.
  • Privacy and data flow: Summarize and other Copilot actions may process content via cloud services and require account entitlements. IT teams must map how Copilot integrations will interact with data governance policies and regulatory constraints. Microsoft’s staged rollout and EEA limitations reflect both regulatory considerations and deployment caution.

Strengths: Why this preview matters​

  • Practical shell integrations: The AI actions in File Explorer and the Click to Do refinements meet users where they work — the shell — reducing friction and app switching. This is exactly the kind of practical integration that can yield daily productivity wins for knowledge workers.
  • Accessibility progress: The Narrator Braille Viewer and improved reading and table navigation are substantive, usable gains that advance Windows’ accessibility baseline.
  • Developer convenience: Exposing Git status in Explorer and consolidating developer toggles into an Advanced page reduces cognitive overhead for developers and power users.
  • Operational niceties for admins: Taskbar pinning without requiring explorer restarts is a small but meaningful operational improvement that will reduce helpdesk tickets and awkward restart requirements after group policy changes.
  • Thoughtful staged rollout: By gating AI features by license, region, and device capability, Microsoft reduces risk of broad privacy or regulatory missteps and gives admins time to plan entitlements.
These strengths are well documented in Microsoft’s support notes and Insider blog and reflected in the community testing reported by outlets and technical blogs.

Risks, uncertainties, and things to watch​

  • Fragmented user experience: Licensing and Copilot+ hardware gating will create an inconsistent experience across the installed base. Two users on identical builds may see different capabilities, complicating support and documentation. Expect confusion in mixed environments.
  • Privacy and data governance: File Summarize and some image edits may send content to cloud services or rely on online models. Organizations must verify whether these workflows meet internal data handling policies and regulatory obligations. Microsoft’s licensing and regional gating are partial mitigations but not a complete solution for enterprise data governance.
  • Rollback complexity: The combined SSU+LCU packaging model makes clean rollback harder. Enterprises should pilot the update on representative hardware and keep tested rollback procedures ready.
  • Third‑party tooling collisions: Shell-level AI and Explorer integrations increase the chance of conflicts with third‑party customization tools (ExplorerPatcher, StartAllBack, Windhawk). Power users who rely on those tools should test for interaction effects before broadly adopting the preview. Community reporting has already shown interplay between Microsoft’s shell changes and third‑party mods.
  • Uneven availability and documentation lag: Staged rollouts often outpace public documentation and may spawn conflicting community reports about build numbers and feature behavior. Rely on Microsoft’s KB and Insider blog for the canonical details.

Recommended actions — for power users and admins​

  • Check your current build: run winver or visit Settings > Windows Update before making deployment decisions. Confirm whether your device is on 24H2 or 25H2 and which build number is present.
  • Pilot on a small, representative cohort: include Copilot+ and non‑Copilot devices and vary licensing profiles. Evaluate both feature availability and policy implications.
  • Validate data flows: test the Copilot Summarize and image actions with representative (non‑sensitive) documents to confirm where data is processed and whether log/audit trails meet your governance needs.
  • Prepare rollback/runbook: document DISM removal steps for the LCU and confirm restoration plans for the servicing stack if recovery is needed.
  • Update support docs: because the experience will be inconsistent, maintain a short matrix mapping which features require Copilot licensing, Copilot+ hardware, or are blocked in the EEA.
  • Communicate with users: make it clear that KB5065789 is optional and preview-only; explain expected benefits and limitations. Encourage users to report unexpected behavior to centralized IT channels.

Final analysis — incremental but strategic​

KB5065789 is not a single, dramatic UI overhaul. Instead, it’s a strategic bundle of incremental improvements that collectively point to Microsoft’s current roadmap: embed generative and assistive AI deeper into the shell, make the system easier to operate and manage, and improve accessibility and developer productivity. The package demonstrates a pragmatic approach — roll small, verify, and gate features behind hardware and licensing requirements to reduce blast radius.
For individual users, the most tangible gains will be the convenience of File Explorer actions, hardware indicator control, and taskbar pinning fixes. For enterprises, the package is a prompt to revisit Copilot licensing, data governance, and update rollout policies. Accessibility advocates should welcome the Braille Viewer and Narrator refinements, while power users and modders should test for compatibility with third‑party customization tools.
Microsoft’s KB and Insider blog entries are the authoritative references for this preview; community reporting and hands‑on writeups (like those published by Windows Report) help illustrate real‑world behavior. When planning to adopt these changes, base decisions on Microsoft’s official guidance, run controlled pilots, and prepare clear policies around Copilot entitlements and data handling — because the promise of shell‑level AI is compelling, but the rollout will be uneven until gating and licensing converge across the ecosystem.

KB5065789 is a clear signal: Windows’ next iterations will be less about large visual redesigns and more about embedding small, intelligent productivity features into the places users already work — the taskbar, the desktop, and File Explorer. The tradeoffs are straightforward: convenience and accessibility on one side, complexity of rollout, licensing entanglement, and governance concerns on the other. Deploy thoughtfully, test comprehensively, and expect the experience to mature over the next months as Microsoft widens the staged rollout.

Source: Windows Report KB5065789 brings new taskbar and desktop customization options in Windows 11
Source: Windows Report KB5065789 revamps Advanced Settings & adds Voice Access upgrades in Windows 11