Windows 11 Insider Preview: Your accounts and Copilot integrations in Build 26220.6690/26120.6690

Microsoft’s latest Insider update, delivered under KB5065786, pushes Copilot deeper into everyday workflows by adding Copilot-powered translation to the Click to Do selection surface and experimenting with quick taskbar integrations that let you share app windows directly with Copilot for visual analysis. This change, included in Windows 11 Insider Preview Build 26220.6690 (Dev, 25H2) and Build 26120.6690 (Beta, 24H2), is a concrete example of Microsoft’s strategy to turn Copilot from a separate assistant into an ambient, context-aware productivity layer inside the OS. (blogs.windows.com)

---

Background / Overview​

Microsoft has been iterating on Copilot experiences within Windows for more than a year, gradually grafting AI-driven actions into small, high-frequency UI moments such as selection menus, the taskbar, and the Start menu. The Click to Do surface—Windows’ pick-for-action tool that appears when you select text or an image—has evolved from a static list of options into a micro-composer for Copilot prompts. The changes in KB5065786 reflect this shift: small, contextual AI actions rather than a single monolithic feature. (blogs.windows.com)
Key facts verified in the official Windows Insider announcement:

• The update ships as part of KB5065786 and is available to Insiders as Build 26220.6690 (Dev) and 26120.6690 (Beta). (blogs.windows.com)
• The update enables Copilot-powered translation in Click to Do on eligible Copilot+ PCs when the new Copilot prompt box is present. (blogs.windows.com)
• Microsoft is intentionally staging the rollout using server-side toggles, and the translation feature is not being rolled out to Insiders in the EEA or China at this time. (blogs.windows.com)

These are not speculative items: they appear in Microsoft’s release notes and in independent community summaries of the flight.

---

What KB5065786 Adds: Feature Breakdown​

Click to Do — Copilot-powered translation (what it does)​

When Click to Do detects selected text that doesn’t match your Windows display or preferred language settings, the UI can now surface a translation suggestion. Choosing it sends the selected content to the Copilot app, which returns a translation inline with the rest of the Click to Do actions. This reduces the friction of copying text, opening a web translator, and pasting back—turning translation into a one-step contextual action. (blogs.windows.com)
Practical implications:

• Fast, contextual translations without leaving the current app.
• Seamless follow-up actions: after translation you can immediately ask Copilot to summarize, paraphrase, or act on the translated text.
• The feature requires the Copilot prompt box in Click to Do and may depend on Copilot+ hardware and component packages. (blogs.windows.com)

Taskbar sharing & Copilot Vision (what Microsoft is testing)​

The Dev build experiments with a new taskbar affordance: when hovering an app’s taskbar thumbnail you may see an option to share that window with Copilot. That action opens a Copilot conversation and can invoke Copilot Vision to analyze the shared content—illustrating Microsoft’s goal to let Copilot examine screen content in context, not just react to typed prompts. (blogs.windows.com)
This is an exploratory integration intended to reduce friction for tasks like extracting data from a document, explaining a chart, or diagnosing an app state, all within a Copilot session started from the taskbar.

Settings and account polish​

KB5065786 also renames and consolidates account management under a unified Your accounts page in Settings, surfacing email, subscriptions, payments, and device/account controls in one place. The move underscores Microsoft’s long-term strategy of integrating subscription entitlements into core OS surfaces. (blogs.windows.com)

---

Technical Context: Copilot+ PCs, Phi‑Silica, on-device vs cloud​

To understand availability and performance, you must grasp Microsoft’s Copilot+ and on-device AI narrative.

• Copilot+ PCs: Microsoft’s label for machines with AI acceleration hardware (NPUs or silicon validated for on-device models). Not all features are supported on all devices—some actions rely on local inference to reduce latency and preserve privacy. (blogs.windows.com)
• Phi‑Silica: The on-device small language model family Microsoft uses to generate short, low-latency suggestions in Click to Do and similar micro-interactions. The Copilot prompt box in Click to Do surfaces suggestions generated locally by Phi‑Silica for supported languages.
• Hybrid model: Microsoft is running a hybrid approach—some prompt suggestion work happens on-device while translation and deeper Copilot responses may be processed in the Copilot app (which can involve cloud processing). This hybridization is why Microsoft gates features by hardware, component availability, entitlement, and regional policy. (blogs.windows.com)

---

Why this matters — user and enterprise impact​

For everyday users​

• Speed and convenience: Quick translations inside Click to Do eliminate routine context switching, which is meaningful for frequent cross-language browsing and content triage.
• Discoverability: Embedding the Copilot prompt box into Click to Do makes AI capabilities more discoverable; casual users are more likely to try micro‑prompts when they appear in the selection menu.

For power users and creators​

• Integrated workflows: Translating a paragraph and immediately requesting a summary or localized rewrite becomes a single, coherent flow instead of multiple app hops.
• Lower latency for micro-tasks: On-device suggestion generation shortens the time between selection and actionable result.

For enterprises and IT admins​

• Feature gating complicates rollout planning: The region and hardware gating means not all workstations will get identical behavior. IT must test on representative configurations before broad deployment.
• Privacy and data flow: The translation feature explicitly sends selected text to the Copilot app. Admins evaluating compliance should treat this as a networked operation with potential cloud dependencies and verify whether on‑device-only behavior applies to their scenario. Microsoft’s blog notes the selected text is sent to the Copilot app; enterprises should review Copilot’s data-handling policies before enabling broad use. (blogs.windows.com)

---

Limitations, caveats, and known issues​

• Regional exclusions: Microsoft has explicitly excluded the EEA and China from this staged rollout for the translation feature. If you’re an Insider in those regions you likely won’t see the option yet. (blogs.windows.com)
• Hardware gating: Expect behavior differences between Copilot+ capable devices and ordinary hardware. Some features rely on NPUs or validated drivers.
• Privacy considerations: Though Microsoft positions on-device models as privacy-friendly, the translation operation sends the selected text to the Copilot app. That means content may traverse networked Copilot services depending on device configuration and Copilot component availability. Administrators and privacy-conscious users should evaluate this before enabling on sensitive machines. This nuance is documented in Microsoft’s rollout notes and reinforced by community coverage. (blogs.windows.com)
• Staged rollouts can cause fragmentation: Server-side toggles allow Microsoft to gate features and iterate quickly, but this creates a fragmented experience that can be confusing for support teams and users who expect feature parity across devices.

---

Hands-on: How Click to Do translation works (user flow)​

• Select a block of text in any app or webpage.
• Click the Click to Do action (right-edge swipe or selection menu).
• If the selected text’s language differs from your Windows display or preferred language, Click to Do may surface a Translate suggestion.
• Selecting Translate sends the text to the Copilot app and returns an inline translation in the Click to Do surface.
• Use follow-up actions in Click to Do (Summarize, Rewrite, or send to another app) or continue the Copilot conversation for deeper edits. (blogs.windows.com)

This one-by-one flow is designed to be frictionless; the most important precondition is that the Copilot prompt box is present in your Click to Do surface and that your device is eligible for Copilot+ experiences.

---

Security, privacy, and governance: what IT must verify​

• Confirm where Copilot processing occurs for translation actions on your devices—on-device only or routed through Copilot cloud services—as that determines whether selected text is exposed to remote processing.
• Validate Copilot component installation and versioning (Phi‑Silica and other AI components) on machines slated for production use.
• Review regional compliance controls: because Microsoft has excluded the EEA and China from this staged feature, legal/regulatory constraints or data residency requirements may already be influencing Microsoft’s rollout decisions.
• Establish testing matrices for representative hardware: include Copilot+ machines (Intel Core Ultra / AMD AI-capable systems / Qualcomm Snapdragon with NPU) and non-Copilot hardware to document behavior differences. (blogs.windows.com)

If a corporate policy forbids sending workplace content to cloud-based AI services, block or restrict Copilot connectivity until you confirm on-device-only behavior and retention settings.

---

UX analysis: strengths and trade-offs​

Strengths​

• Speed and context: Integrating translation into a selection action is an ergonomically smart decision—one click to translate avoids repeated context switches.
• Discoverability: The Copilot prompt box in Click to Do lowers the activation cost for micro‑prompts and may increase overall Copilot adoption.
• Hybrid model flexibility: Local suggestion generation (Phi‑Silica) combined with Copilot cloud capabilities yields a practical balance between latency and capability.

Trade-offs and potential risks​

• Fragmentation and support complexity: Server-side toggles and hardware gating mean feature availability will be uneven across users, complicating helpdesk support and documentation.
• Privacy ambiguity: The explicit transmission of selected text to the Copilot app raises questions around retention, telemetry, and corporate data exposure. Until Microsoft publishes enterprise-facing documentation clarifying retention and processing details, organizations should proceed cautiously. (microsoft.com)
• Regional restrictions may frustrate global organizations: The exclusion of the EEA and China—likely related to regulatory considerations—means global rollout will be uneven and possibly indefinite for some markets. (blogs.windows.com)

---

What to test and how to prepare (for Insiders and IT pros)​

• Confirm build and KB: ensure the target devices are on Build 26220.6690 (Dev) or 26120.6690 (Beta) and that the cumulative package KB5065786 is applied. Check Settings > Windows Update and your Insider channel toggles. (blogs.windows.com)
• Verify Click to Do prompt box: the translation feature requires the Copilot prompt box in Click to Do, introduced in earlier flights—verify you have that element visible before testing translation.
• Validate hardware compatibility: test on a Copilot+ PC and on a non-Copilot machine to compare behavior and determine whether translation is provided locally or via Copilot cloud endpoints. (blogs.windows.com)
• Exercise EEA/China checks: if you manage devices in the EEA or China, do not expect this feature to be available yet—document the affected endpoints and align on fallback workflows. (blogs.windows.com)
• Audit network and telemetry: use packet capture and endpoint logs to see where selected text is sent when invoking translation, and verify whether your organization’s data governance rules are satisfied.

---

Broader trajectory: Copilot as a productivity fabric​

KB5065786 is representative of Microsoft’s incremental strategy: weave Copilot into many small, high-frequency interactions rather than creating one large disruption. Click to Do’s new translation pairing with the Copilot prompt box is a microcosm of this approach—prioritizing discoverability, lower latency, and in-context actions.
This strategy has several predictable consequences:

• Users will increasingly expect AI actions to be available in the places they already work (selection menus, taskbar, Start menu).
• Hardware and regional gating will persist early in the rollout, creating temporary fragmentation.
• Microsoft will likely iterate rapidly via staged toggles rather than a single, global release.

Those patterns are evident across Microsoft’s release notes and community reporting on recent Insider flights. (blogs.windows.com)

---

Final assessment and recommendation​

KB5065786’s Click to Do translation is a pragmatic, useful addition to Windows 11 for users who frequently handle multilingual text. It reduces friction and folds translation into a native, discoverable workflow—an important UX win. However, the technical and governance realities mean adoption should be deliberate for organizations:

• For enthusiasts and Insiders: enable the toggle, test on Copilot+ hardware, and provide feedback through Feedback Hub to help Microsoft refine latency, accuracy, and privacy behaviors.
• For IT administrators: pilot on a small group of Copilot+ endpoints, audit the data flows when translation is invoked, and coordinate with legal/compliance to ensure Copilot’s processing aligns with internal policies.
• For privacy-conscious users: assume selected text may be routed to Copilot services; avoid sending sensitive corporate or personal data until Microsoft’s enterprise documentation explicitly confirms on-device-only handling for translation scenarios.

KB5065786 is an incremental but important step: Copilot is moving from a separate assistant into the OS’s selection and task surfaces, and Click to Do translation shows how AI can make routine tasks measurably faster. The trade-offs—regional gating, hardware dependence, and privacy considerations—are real, manageable, and should guide measured adoption and careful testing. (blogs.windows.com)

---

Microsoft’s official flight notes and community coverage provide the factual basis for this analysis; readers interested in hands-on testing should target the specified Insider builds and remember that staged rollouts mean “your mileage may vary.”

---

Source: Windows Report Windows 11 KB5065786 brings Copilot-powered translation in Click to Do

Microsoft’s latest Insider package, delivered as KB5065786, folds a fresh set of Copilot experiences into the Windows 11 shell — most notably a taskbar “Share with Copilot” affordance that lets Copilot Vision scan and analyze the content of a window you hover over on the taskbar, plus a Copilot-powered translation shortcut inside Click to Do. The changes arrive in Build 26220.6690 for the Dev Channel and Build 26120.6690 for the Beta Channel and are being distributed as staged, toggle-gated rollouts to Insiders. (blogs.windows.com)

Background​

Why this matters now​

Copilot’s role in Windows has steadily moved from a sidebar helper to an OS-level assistant that can be invoked from many contextual surfaces. The latest flight shows Microsoft continuing that trajectory by making Copilot able to see and interact with what’s already on the screen — not just take typed input. That change repositions Copilot as a workflow assistant rather than only a chat box, and it introduces new convenience and new risks that both consumers and IT teams should weigh. (blogs.windows.com) (theverge.com)

What Microsoft says the update contains​

The official Windows Insider announcement for Build 26220.6690 lists three headline themes in the KB5065786 package: (1) a consolidated “Your accounts” page in Settings, (2) Copilot-first experiences including Click to Do translation and taskbar sharing with Copilot, and (3) a collection of stability and troubleshooting fixes (File Explorer, Windows Update errors, audio regressions, etc.). Microsoft emphasizes that many items in this update are gradual rollouts controlled by server-side flags. (blogs.windows.com)

---

Overview of the new Copilot taskbar integration​

What the taskbar Share with Copilot does​

• When hovering an app’s thumbnail on the taskbar, a new option may appear: Share with Copilot.
• Selecting this option starts a Copilot conversation and invokes Copilot Vision on the contents of that specific window so Copilot can scan, analyze, summarize, or answer questions about what’s visible without the user having to copy or switch contexts. (blogs.windows.com)

The UI pattern is deliberately similar to the Teams-style window-sharing affordance users already know (hover → share), but the destination is Copilot rather than a meeting app — turning the taskbar into a direct bridge between the OS and the AI assistant. (windowscentral.com)

How it ties into Copilot Vision and Desktop Share​

Copilot Vision and the Desktop Share flows (which let Copilot view a window, a monitor, or the entire desktop) provide the underlying capability for the taskbar option. The product team previously documented opt‑in flows where users explicitly choose what to share from the Copilot composer (glasses icon) and can stop sharing at any time; the taskbar affordance is simply another, faster entry point into that same visual sharing experience. (blogs.windows.com)

---

Deep dive: UX, mechanics and gating​

UX and session mechanics​

• Activation: mouse over a running app’s taskbar thumbnail → click Share with Copilot (if the option is present).
• Session: Copilot opens a conversation panel and streams visual content for analysis; users can interact via text or voice while the session is active.
• Termination: the Copilot composer contains a clear Stop control to end the visual sharing session immediately. (blogs.windows.com)

This flow emphasizes user initiation — Microsoft’s published guidance and the Insider UI both show the feature as a deliberate action, not background monitoring. That distinction is central to how the feature is framed to address privacy concerns. (blogs.windows.com)

Gating: who will see it and when​

Multiple layers of gating mean not all Insiders — let alone general consumers — will see the taskbar option immediately:

• Microsoft uses Controlled Feature Rollouts to enable features server-side for a subset of Insiders with the “Get the latest updates as soon as available” toggle ON. (blogs.windows.com)
• Region gating: Copilot Vision and some visual features are initially restricted to specific markets (the United States appears to be prioritized). (windowscentral.com)
• Hardware / entitlement gating: Some Copilot experiences require Copilot+ PC hardware classes (or specific Copilot app versions) to access advanced features. (blogs.windows.com)

These restrictions are standard for early previews but are important for readers to understand before expecting the feature on their machine. (windowscentral.com)

---

Click to Do: Copilot-powered translation​

What changed​

Click to Do — the selection-to-action surface where users can right-click or select text and choose quick actions — now includes translation powered by Copilot on supported machines. When selected text differs from the device’s display or preferred language, Click to Do can offer a translation suggestion and send the selected text to the Copilot app for an inline translation result. (blogs.windows.com)

Limits and implications​

• This behaviour currently depends on the modern Copilot prompt box in Click to Do and is not universally available (EEA and China are explicitly excluded in the initial rollouts). (blogs.windows.com)
• Translation operations send the selected string to the Copilot service; that improves accuracy and follow-up actions but carries privacy and network considerations when working with sensitive text.

---

What’s fixed and what’s still fragile​

Notable fixes in KB5065786​

• File Explorer hang when a UNC server name is typed into the address bar.
• Resolved some Windows Update installations failing with error 0x80070002.
• Addressed cases where audio stopped working after prior updates.
• Fixed an Optional Features loading issue when Administrator Protection was enabled. (blogs.windows.com)

Known issues called out by Microsoft​

The Dev post includes a number of known issues for Insiders to watch for, including:

• Taskbar preview animations were temporarily disabled because they interfered with window sharing.
• Click to Do visual gestures can show on the wrong display under certain gestures.
• A handful of display, search, and Settings alignment issues remain under investigation. (blogs.windows.com)

Practically, that means early adopters should expect some UI rough edges and be prepared to file Feedback Hub traces for regressions. (elevenforum.com)

---

Use cases: where taskbar-to-Copilot shines​

• Research and synthesis: Share a browser or PDF window to have Copilot summarize articles, extract key facts, or reconcile figures across multiple documents without copying and pasting.
• Troubleshooting: Share an error dialog or device Settings window so Copilot Vision can highlight likely causes and suggest remediation steps, or guide a user with “show me how” highlights. (blogs.windows.com)
• Summarization and note-taking: Send a transcript, chat, or long-form content to Copilot for a concise summary or to generate action items.
• Quick translation and follow-ups: Translate on-screen strings via Click to Do and immediately ask Copilot to refine or rephrase the translation for tone or register.
• Creative feedback: Designers can share a single app window (e.g., an image editor tab) and ask Copilot to suggest layout or copy changes. (blogs.windows.com)

These examples highlight how visual context removes friction between observation and action, but they also show why caution matters when sharing sensitive or proprietary content. (windowscentral.com)

---

Privacy, security and enterprise implications​

Data flows and what to watch for​

Sharing a window with Copilot sends an image (or series of images) of the visible content to Microsoft’s Copilot backend for analysis. That enables richer responses but means:

• Visual content (screenshots of documents, internal tooling, private chats, or credentials visible on-screen) may be transmitted for processing.
• Administrators and privacy-conscious users must assume that anything visible in the shared window is being analyzed externally, unless explicit on‑device processing guarantees are provided.

Microsoft positions Desktop Share and the taskbar flow as user-initiated and provides a Stop control, but explicit enterprise governance and clear user education remain essential when enabling these features broadly. (blogs.windows.com)

Enterprise controls and admin guidance​

• Group policy, configuration profiles, and cloud content policies can affect whether Spotlight, Copilot, and related features are available or behave differently on managed devices.
• Organizations that require strict data exfiltration controls should treat Copilot Vision like any service that processes content off-device: restrict access, test behavior in a controlled environment, and update acceptable‑use policies accordingly.

Until Microsoft publishes enterprise‑grade assurances or on‑prem alternatives for visual processing, security teams should evaluate this functionality under existing data protection frameworks. If any claims about on‑device-only processing are encountered, they should be verified directly with Microsoft documentation and by reviewing network traces in a test environment. (blogs.windows.com)

---

Technical verification and cross-checks​

Build numbers and release method​

• The update is formally listed as Windows 11 Insider Preview Build 26220.6690 (Dev) and Build 26120.6690 (Beta) distributed under KB5065786. Microsoft’s announcement published on September 19, 2025, details the toggle-gated rollout mechanism for Dev Channel Insiders. (blogs.windows.com)

Copilot app and feature dependencies​

• Desktop Share and some Copilot Vision improvements require specific Copilot app versions (Insider notes previously cited Copilot app version minima like 1.25071.125 for earlier Vision rollouts). The taskbar Share flow leverages the same Vision capability, so the Copilot app version and the Store update channel matter to availability. (blogs.windows.com)

Independent confirmation​

• Coverage from major Windows outlets independently observed the taskbar share behavior and region/hardware gating, confirming that the feature is under staged testing and not yet broadly available. These outlets also highlight the same privacy and gating caveats detailed by Microsoft. (windowscentral.com) (theverge.com)

---

How to try it safely (Insider checklist)​

• Join the Windows Insider Program and enroll a test device in the Dev or Beta Channel.
• In Settings > Windows Update, turn ON the “Get the latest updates as soon as available” toggle to receive controlled feature rollouts.
• Update the Copilot app from the Microsoft Store and confirm the Copilot app version meets any preview minima reported by Microsoft.
• When the build arrives (Build 26220.6690 / 26120.6690), hover a running app on the taskbar to look for the Share with Copilot option and test only on non-sensitive windows.
• Use the Stop control to terminate a session immediately, and monitor network activity if verification of data flows is required. (blogs.windows.com)

---

Risks, mitigations, and recommended policies​

Immediate risks​

• Unintentional exposure of sensitive content: visible credentials, private chats, proprietary documents may be captured and transmitted.
• Regulatory and compliance gaps: organizations subject to privacy laws (e.g., GDPR) or sector-specific controls must assess whether sending visual content to Copilot is permissible.
• Inconsistent availability: region and hardware gating may lead to uneven user experiences and support complexities. (windowscentral.com)

Mitigations​

• Default to making Copilot Vision and taskbar sharing opt-in at the enterprise level and restrict the feature until policies and data processing agreements are fully reviewed.
• Use test labs to observe the precise network endpoints and data payloads before wider deployment.
• Educate users about the explicit meaning of “share” and include prompts or confirmation dialogs in internal documentation so employees understand what will be transmitted.

Long-term governance​

• Track Microsoft’s enterprise guidance and any forthcoming contractual or technical controls (e.g., enterprise data protection options, region-specific processing commitments).
• Consider integration of DLP (Data Loss Prevention) rules that can block visual-sharing operations for windows that display regulated data. If DLP is not possible at the image-level, place stronger restrictions on Copilot features on managed devices.

---

Critical analysis: strengths, trade-offs and what to watch​

Notable strengths​

• Real productivity gains: reducing friction between “what’s on screen” and actionable AI assistance is a meaningful UI evolution that can save time for researchers, admins, and creators. The taskbar is a high-frequency surface; embedding Copilot there makes invoking assistance fast and intuitive. (blogs.windows.com)
• Context-aware help: Copilot Vision’s ability to interpret visual context (dialogs, menus, errors) allows for targeted troubleshooting and guided highlights that traditional chat bots cannot achieve. (blogs.windows.com)

Trade-offs and concerns​

• Privacy vs. convenience: the very capability that enables richer responses (visual sharing) also increases the risk surface for accidental data exposure. The announcement and early coverage explicitly call this out; the safeguards are currently operational (user opt-in and a Stop control) but not the same as enterprise-grade on‑device guarantees. (blogs.windows.com)
• Fragmented availability: region and hardware gating create fragmented user experiences that complicate testing and support. Organizations and power users should not assume feature parity across fleets. (windowscentral.com)
• Preview volatility: Dev Channel builds are experimental by design; features can change or be removed entirely. The staged rollout and feature flags are a double-edged sword that accelerates innovation but can create support churn for ISVs and admins. (blogs.windows.com)

What to watch in the coming months​

• Microsoft’s enterprise documentation and DLP integrations for Copilot Vision.
• Any announcements about moving visual analysis to on‑device models or private cloud processing options.
• The pace of expansion beyond initial markets and whether the feature becomes a standard, supported element of general Windows releases. (blogs.windows.com)

---

Bottom line​

KB5065786 marks another deliberate step in Microsoft’s strategy to make Copilot an integral, context-aware part of Windows rather than an optional chatbot tucked into an app. The taskbar Share with Copilot affordance and Click to Do translation show the company prioritizing contextual convenience and multimodal assistance. Those gains are real — they promise faster research, clearer troubleshooting, and a reduced need to copy, paste, and switch apps — but they also raise immediate privacy and governance questions that enterprises and cautious users must address before broad adoption. Microsoft’s staged rollout model and the Dev Channel preview status mean the feature will evolve based on feedback, so organizations should test, monitor, and set policies before enabling it widely. (blogs.windows.com) (windowscentral.com)
The update is available to Insiders as a staged flight; devices must be enrolled in the Insider Program and may require specific Copilot app and hardware entitlements to access the newest capabilities. For anyone planning to test it, focus initial trials on non-sensitive content, capture telemetry and network traces, and prepare governance rules that reflect the new reality of a desktop that can be seen — with consent — by an AI assistant.

---

Source: Windows Report KB5065786 update adds taskbar sharing with Copilot in Windows 11