Windows 11 Insider Preview 26220.6780 CFR Copilot+ UX and Drag Tray Updates

Microsoft has pushed Windows 11 Insider Preview Build 26220.6780 (KB5067103) to the Dev Channel, continuing the 25H2-era enablement-package cadence and delivering a mix of incremental Copilot-era experiments, UI polish, and a pack of reliability fixes — while reminding Insiders that many of the changes are being gradually rolled out and remain gated by hardware, telemetry, or server-side flags.

Background / Overview​

Windows Insiders on the Dev Channel are receiving this flight as part of the 26220.xxxx family, the ongoing development track tied to Windows 11, version 25H2, which Microsoft enables via a tiny enablement package on top of existing servicing binaries. That delivery model means many features are already present in device binaries but are turned on selectively — a pattern Microsoft calls Controlled Feature Rollout (CFR). Turning on the “Get the latest updates as they are available” toggle in Settings increases the odds a device will see staged experiments earlier, but it also increases exposure to intermittent regressions. This particular update continues a recent trend: small, pragmatic, discoverability-focused enhancements (on-screen agents, share UX experiments), deeper Copilot integration on Copilot+ certified machines, and quality fixes across File Explorer, Start, search, and taskbar subsystems. Microsoft’s release notes for the 26220 flight family repeatedly emphasize staged delivery, hardware gating (NPUs / Copilot+), and the experimental nature of many features — some may never ship beyond Insiders.

---

What’s new in Build 26220.6780 — headline items​

The official rollout groups changes into two buckets: items being gradually rolled out to Insiders who have opted into immediate updates, and items enabled for all Dev Channel machines. The most visible items in this flight are:

• Agent in Settings (Copilot+ PCs) — expanded search and recommended-settings affordances, with inline agent actions for recently modified settings and an improved search flyout that surfaces more actionable results.
• Drag Tray — a drag-and-share UX that supports multi-file sharing, prioritizes relevant target apps, and enables moving dragged files into chosen folders. This behavior is an experiment to make desktop sharing feel more mobile-like. Independent coverage and community findings show the Drag Tray can be toggled via Vivetool for testing and is being tracked across Insider builds.
• Click to Do (Preview) refinements — visual cues highlight actionable entities (emails, tables, etc. on Copilot+ PCs; selecting these entities surfaces quick actions such as conversion to Excel tables or Copilot prompts. These enhancements land progressively for Copilot+ hardware.
• Administrator Protection returns — the ability to enable Administrator Protection under Windows Security > Account protection is available again for Insiders.
• OneDrive icon updates — refreshed OneDrive glyphs rolled into Settings’ Accounts and Homepages to match evolving branding.
• Run dialog Dark Mode polish — continued refinements to dark-mode visuals, including the Run dialog experience.

Collectively, these are evolutionary rather than transformational changes: aimed at reducing friction, improving discoverability of Copilot features, and tightening system reliability across common workflows.

---

Deep dive: notable features and UX changes​

Agent in Settings — search that acts, not just suggests​

The agent in Settings expansion aims to reduce friction when users look for or want to tweak system settings. Two practical improvements stand out:

• Recommended Settings now surface inline agent actions for recently modified items, letting users apply common changes quickly without navigating deeper into nested menus. This helps reduce cognitive load when tuning preferences.
• Search flyout improvements show more results and highlight settings that can be acted upon directly from the flyout. Where a setting can’t be changed inline, the flyout will explain why and offer a direct path to make the change.

These iterations reflect a broader design goal: let contextual AI and agent surfaces move useful actions closer to the user’s intent rather than forcing deeper navigation. Expect device- and region-level gating here (Copilot+ entitlement and Controlled Feature Rollout).

Drag Tray — drag-and-drop meets modern sharing​

The Drag Tray experiment surfaces a drop-down share/target tray when you drag files toward the top of the screen. Key characteristics:

• Multi-file support: Tray now supports dragging multiple files at once.
• Smarter target suggestions: It prioritizes relevant apps (e.g., Phone Link, mail clients, cloud providers), surface a “More options” link to the share sheet, and can move files to a chosen folder.
• Experiment, not guaranteed ship: The feature appears in Insider builds as a hidden experiment and has been discovered and tested by the community via Vivetool toggles.

Independent coverage and community testing confirm Drag Tray behavior across several Insider builds and provide practical tips for enabling or disabling it for testing. That widespread attention suggests Microsoft is actively evaluating the UX, but also that the feature is still in an A/B or limited-exposure state.

Click to Do (Preview) — contextual actions get smarter​

Click to Do continues to expand as a front-line Copilot surface. Recent additions in this flight emphasize:

• Entity-aware visuals: On-screen emails, tables, and other recognisable objects are visually highlighted so the user can directly invoke actions.
• Table and email actions: Click-to-Do can convert a detected table to Excel or present contact/persona cards using Microsoft 365 signals (when signed into a work/school account).
• Local suggestion models: On-device models (where available on Copilot+ hardware) generate suggested prompts, improving responsiveness and privacy posture.

This is an incremental but meaningful step toward making on-screen AI actions feel discoverable and frictionless — provided your hardware and licensing entitlements meet the Copilot+ requirements.

---

Reliability fixes and small but important bug patches​

Microsoft’s notes for this flight call out a variety of stability fixes that will interest power users and Insiders:

• Fixes to Click to Do visual launch issues across multi-monitor setups.
• Taskbar & system tray fixes — including corrected cycling through an app’s windows with repeated WIN + [number] key presses.
• File Explorer crash mitigations that addressed an earlier regression causing frequent explorer failures for some Insiders.
• Start menu scroll and touch-context-menu fixes.
• Search fixes for unexpected placeholder text or broken result rendering.
• A broad mitigation for a prior flight’s mass-app crashing issue, including browsers, which Microsoft says should no longer reproduce on affected devices.

These are practical quality-of-life improvements that suggest Microsoft is prioritizing day-to-day polish in this cadence rather than large feature overhauls.

---

Known issues and risk areas​

No Dev flight is shipment-ready; this one is no exception. Known issues listed by Microsoft and corroborated by community trackers include:

• Taskbar preview animations temporarily disabled because they interfered with window sharing from previews. Expect telemetry-driven re-enablement once the conflict is resolved.
• File Explorer copy-dialog oddities in dark mode — copy progress may flash and the scrollbar/footer sometimes renders as a white block when text scaling is applied.
• Xbox controller Bluetooth bugchecks: Some Insiders experienced bugchecks (blue screens) when using Xbox controllers over Bluetooth. Microsoft published a workaround to uninstall a specific OEM driver entry via Device Manager. Community reports and Microsoft’s guidance indicate this was an active known issue in recent flights.
• Hardware and regional gating: Many Copilot features are Copilot+ only (require NPU/partner drivers), and several features are regionally restricted (for example, the EEA and China limitations noted in prior build notes).

These known issues matter: Dev Channel flights are experimental by design. The gating model means two machines on the same build may behave differently — complicating troubleshooting for IT and power users. Verify any critical claim about KB numbers, rollouts, or device eligibility on your own test hardware via Settings > Windows Update or Flight Hub. Flight Hub remains the authoritative dashboard to cross-check build numbers and their channel allocation. Caution: the KB identifier KB5067103 included in the initial announcement text submitted for this article could not be uniformly verified across public indexes at the time of reporting; Insiders are advised to confirm the KB/build reference directly from their device’s Windows Update details or Flight Hub. Where official Windows Insider blog posts exist for adjacent 26220 flights they provide matching feature lists and known issue explanations, but slight KB/build-number mismatches have appeared between community trackers and server-side rollout snapshots — treat those as expected variance in a staged rollout approach.

---

Why Microsoft is taking this incremental approach (strategic context)​

• Controlled Feature Rollout reduces risk by enabling server-side feature flags and stepwise exposure. It gives Microsoft the ability to ramp features based on real-world telemetry, user feedback, and crash statistics rather than a one-time ship event. This is useful for complex, hardware-dependent features like on-device AI.
• Hardware gating (Copilot+ certification) lets Microsoft move compute-heavy inference on-device for latency and privacy benefits, but it creates fragmentation. Insiders and enterprise fleets will see different experiences depending on NPU, OEM drivers, and licensing entitlements.
• The enablement-package model for 25H2 lets Microsoft pre-ship binaries and flip features with a tiny package, reducing upgrade friction for broad rollouts, while still enabling ongoing iterative development in the Dev/Beta channels. This makes the update process less disruptive for pilots and enterprises, but increases the importance of staged validation.

---

Critical analysis — strengths, trade-offs, and enterprise implications​

Strengths​

• Practical polish over spectacle: These flights deliver realistic productivity and accessibility improvements — better search affordances, Click to Do refinements, File Explorer fixes — that ship tangible daily-value enhancements.
• On-device AI emphasis: Local suggestion models and Copilot+ capabilities improve responsiveness and carry privacy advantages by keeping inference off remote servers.
• Faster, lower-impact updates for 25H2: The enablement-package approach allows IT to flip features across a fleet with minimal downtime, aiding staged pilots and rollback scenarios.

Trade-offs and risks​

• Fragmentation and support complexity: Hardware- and region-gating produce inconsistent user experiences across ostensibly identical builds. Support teams will need telemetry and feature-flag awareness to triage issues effectively.
• Driver and peripheral fragility: Regressions like the Xbox controller Bluetooth bugchecks and camera/Studio Effects incompatibilities indicate driver-stack fragility. Enterprises must validate peripherals and AV/agent compatibility before wide deployment.
• Experimental UX friction: Features such as Drag Tray, while promising, have drawn mixed community feedback (some users find it intrusive). Microsoft will need strong UX iteration and the ability to quickly toggle experiments off where they degrade workflows. Community testing has already produced registry/ViveTool workarounds to disable Drag Tray for frustrated users.

Enterprise guidance​

• Treat Dev Channel builds as test-only. Do not deploy on production endpoints.
• Create small pilot rings for Copilot+ feature validation (hardware, drivers, and license verification).
• Validate third-party security agents, virtualization tools, and capture/streaming software (OBS, PIX) in a representative lab; several recent fixes explicitly targeted those toolchains.

---

Practical recommendations for Insiders and IT​

• For Insiders who want to see staged features earlier: enable Settings > Windows Update > Windows Insider Program > “Get the latest updates as they are available.” Be prepared for variability in which features appear.
• For those who prefer stability: stay in Release Preview or keep the feature-toggle off. Dev Channel remains the place for early experiments and may include regressions affecting daily work.
• If you encounter the Xbox controller bugcheck, follow Microsoft’s temporary remediation: open Device Manager → View → Devices by driver → find the OEM driver entry matching “oemXXX.inf (XboxGameControllerDriver.inf)” and uninstall it (then reboot). Microsoft documented this workaround in recent build notes.
• To verify build/Kb numbers and flight availability for your device, use Settings > Windows Update and consult Flight Hub for the official channel mapping rather than a third-party index. Slight KB/build-number variations are common with rolling flights.

---

What to watch next​

• Whether Drag Tray becomes a broadly available feature or remains an experiment — Microsoft is watching user feedback closely; community reaction will matter. Independent outlets and community testers are already documenting behaviors and workarounds, which will likely shape Microsoft’s next decisions.
• Broader Copilot+ expansion across OEM platforms (Intel, AMD, Qualcomm) and whether local models get extended language and feature support beyond initial locales. The extensibility and privacy model of on-device inference will remain a strategic focus.
• Driver and peripheral compatibility improvements — camera Studio Effects, audio capture pipelines, and controller BT stacks have been fragile in some flights; fixes and driver updates will determine how fast Copilot+ features can scale to mainstream hardware.

---

Conclusion​

Build 26220.6780 is a quintessential modern Windows Insider flight: modest, measured, and heavily staged. It delivers helpful UX experiments — agent in Settings, Drag Tray, Click to Do refinements — alongside important reliability patches for File Explorer, Start, and the taskbar. The update reiterates Microsoft’s multi-factor experimentation strategy: deliver small, privacy-minded AI experiences on capable hardware, roll them out incrementally, and iterate from live telemetry.
For Insiders, the value is clear: early access to evolving Copilot surfaces and usability improvements. For IT and enterprises, the message is equally clear: use the Dev Channel for feature validation only, test drivers and peripherals carefully, and treat feature exposure as variable until Microsoft confirms broad availability. As always with staged Insider flights, verify critical details (build/Kb numbers, feature flags) in Settings > Windows Update and on Flight Hub before basing deployment plans on any single flight’s notes.

---

---

Source: Microsoft - Windows Insiders Blog Announcing Windows 11 Insider Preview Build 26220.6780 (Dev Channel)

 

[ChatGPT]

Microsoft is rolling Build 26120.6780 (KB5067103) to the Windows 11 Insider Beta Channel, bringing a focused set of staged Copilot-era improvements — notably refinements to the Agent in Settings experience for Copilot+ PCs and an expanded, more capable Drag Tray — alongside the usual mixture of quality fixes, known issues, and controlled feature rollouts that define Microsoft’s current Insider servicing model.

Background / Overview​

Windows Insider releases in 2025 continue to follow Microsoft’s enablement-pack and controlled feature-rollout pattern: binary code for features is shipped in monthly cumulative updates for the servicing branch (in this case, Windows 11, version 24H2) while feature visibility is managed server-side through flags and “get the latest updates” toggles. That means installing the cumulative package — even one identified as a KB like KB5067103 — does not guarantee every Insider will see every new experience immediately; many items are gated by hardware class, licensing, region, or an on-device toggle.
This particular checkpoint follows the 26120-series enablement flow used across Beta and Dev channels to validate on-device Copilot integrations, accessibility polish, and system reliability fixes. Expect a split between items that are broadly distributed to Beta Channel devices and features that are gradually rolling out to Insiders who have enabled early updates.

---

What’s new in Build 26120.6780 (KB5067103)​

The public announcement highlights two headline upgrades that will attract the most attention from power users and Copilot testers: improvements to Agent in Settings for Copilot+ PCs, and enhancements to the Drag Tray experience. Both are being deployed under the staged rollout model — some Insiders will see them immediately if they’ve opted into the early-rollout toggle, while others will receive them later as Microsoft broadens exposure.

Agent in Settings — faster, more actionable settings discovery​

Microsoft is evolving the agent experience inside Settings to make configuration and remediation quicker for users on Copilot+ machines. The announced changes include:

• Recommend Settings: Inline agent actions will appear for recently modified settings, letting users apply common changes without navigating away. This reduces friction for frequently tweaked options and speeds simple fixes.
• Search flyout improvements: Search results in Settings will surface more actionable results directly in the flyout, and when a setting is not directly adjustable there will be a dialog explaining why plus a route to the correct control. This is intended to shorten the time to resolution for routine configuration tasks.

Why it matters: these changes move Settings from a passive list of pages to a more interactive, assistance-driven surface. For Copilot+ PCs with on-device models, inline actions can remain local (lower latency, fewer network hops) and make common scenarios — privacy toggles, camera/microphone permissions, or energy settings — quicker to manage.
Caveats and verification: the agent enhancements are explicitly staged for Copilot+ certified devices and those Opted-in Insiders; availability will depend on device eligibility and the server-side rollout. Administrators and testers should not assume universal availability immediately after installing the KB.

Drag Tray — multi-file sharing, smarter app suggestions, and folder moves​

The Drag Tray — a long-anticipated reimagining of drag-and-drop for modern workflows — receives several practical upgrades in this flight:

• Multi-file support: Users can now drag multiple files into the tray and move or share them as a single operation.
• Smarter app surfacing: The tray’s suggested apps are prioritized more intelligently, increasing the chance that your target (mail, Teams, Slack, OneDrive share dialog, etc. shows up first.
• Seamless move-to-folder: Dragging files to the Drag Tray then choosing a folder performs a direct move operation rather than an extra copy/confirm dance.

These changes reduce steps when sharing attachments or reorganizing files; for many workflows the Drag Tray can replace a multi-step open-attach-search sequence with a single drag, tap, and drop. Early experimentation and community testing show meaningful productivity wins for frequent sharers and multi-window users.
Practical note: Drag Tray behavior has historically been gated and sometimes hidden by feature flags in Insider builds, and a small subset of Insiders have had to use feature-enablers or registry tweaks to see it early. Expect Microsoft to continue enabling the experience progressively.

---

Quality, fixes, and known issues in this Beta release​

Builds in the 26120 family are as much about stability as they are about small UX improvements. The Beta update stream typically bundles important platform fixes, reliability patches, and targeted mitigations for known regressions.
Notable quality items and fixes that are consistent across recent 26120-series updates include:

• Taskbar and system tray reliability improvements, including fixes for auto-hide peeking and preview focus issues.
• File Explorer stability and context-menu responsiveness patches; improvements to cloud-file launching and thumbnail generation scenarios have been emphasized in this servicing wave.
• Networking and driver corrections, including fixes for incorrect link-speed reporting on certain adapters.
• Hyper‑V and ARM64-specific VM startup fixes where TPM configuration previously blocked boots for some test environments.

Known issues to watch for in Beta flights (typical examples observed in recent related builds):

• Gesture- or display-targeting bugs for Click to Do/Click gestures where visuals appear on the wrong display.
• Occasional audio driver anomalies that manifest as Device Manager warnings for certain ACPI or compositor drivers.
• Xbox controller Bluetooth bugchecks on select configurations — Microsoft has offered a Device Manager uninstall workaround until a patch is broadly deployed.

Because Beta channel releases mix staged features with broad fixes, read the known-issues list carefully in Settings > Windows Update before deciding to install on production hardware.

---

The staged rollout model — toggle, telemetry, and eligibility​

Microsoft’s current Insider servicing approach matters here: a build number and KB alone do not guarantee immediate access to every feature. Key aspects of that model:

• Server-side feature flags control which devices see what: the binaries are present in the update but features are enabled selectively based on telemetry and gating criteria.
• “Get the latest updates as soon as they’re available” toggle (Settings > Windows Update) accelerates exposure for Insiders who want to participate in the earliest waves of controlled rollouts. That also increases the chance of encountering regressions.
• Hardware gating and licensing: many Copilot-era experiences — especially those that rely on on-device inference — are limited to Copilot+ PCs (machines that meet Microsoft’s NPU/hardware profile) and may require a Microsoft 365 or Copilot license for full functionality.

Implication for testers and administrators: treat Beta Channel builds like targeted pilots. Use a non-production test pool, confirm feature exposure via Settings, and collect telemetry and Feedback Hub reports to help Microsoft refine behavior before broader deployment.

---

Enterprise and IT implications​

This build — and the larger 26120/24H2 servicing model — carries several practical consequences for IT and enterprise deployments:

• Feature fragmentation: because features are gated by hardware, licensing, and region, internal documentation and support must prepare for variability across machines. Expect different user experiences even on identically imaged devices.
• Driver and agent compatibility testing: Insider flights occasionally surface regressions in management agents, endpoint protection tools, or drivers (especially third-party storage or biometric drivers). Validate backups, AV, MDM agents, and imaging scripts in a controlled pilot.
• Licensing checks: Copilot-driven features may require Microsoft 365/Copilot entitlements. If an organization intends to pilot Copilot workflows, confirm entitlement assignments and testing accounts before broad trials.
• Security posture and Windows Hello ESS: recent updates in the 26120 series extended support for Enhanced Sign-in Security (ESS) to some peripheral fingerprint readers, which can be a benefit for managed desktops that rely on external readers — but vendor drivers and certification are prerequisites. Validate supported models before mass provisioning.

1. Recommended IT deployment checklist

• Identify a small pilot group of devices that represent your hardware diversity.
• Enable Beta Channel on test devices only and optionally turn on the “get the latest updates” toggle to expose staged features quickly.
• Confirm critical management agents and backups work after installing the build.
• Validate Windows Hello, biometric sensors, and passkey integrations you plan to support.
• Monitor Feedback Hub and Microsoft’s Flight Hub for rollback or mitigation notices.

---

Privacy, performance, and security considerations​

The Copilot-era experiences in these builds emphasize on-device assistance when possible — that can reduce network dependency and improve responsiveness. However, there are trade-offs to be aware of:

• On-device inference improves latency and can be more privacy-friendly compared to cloud-only processing, but it is hardware-dependent and may require NPUs with substantial throughput. Not all devices will benefit equally.
• Telemetry and staged flagging mean Microsoft collects signals to decide rollout progression. Enterprises should understand telemetry flows and their organizational data policies when piloting features that send diagnostics or usage metrics.
• Driver attack surface: enabling peripheral ESS or new camera/Studio Effects hooks increases integration points for third-party drivers; organizations should maintain a strict driver vetting process and sign-off plan.

Flag on unverifiable claims: detailed internally-named model architectures and precise NPU TOPS requirements for Copilot+ certification are not always published in full detail in public Insider posts; those vendor-specific metrics should be verified directly with OEM hardware documentation and Microsoft’s Copilot+ certification guidance before committing to a hardware refresh plan. Treat such numbers as indicative until validated against OEM datasheets.

---

How to get this build and practical testing steps​

For Insiders who want to try Build 26120.6780 (KB5067103) in Beta:

• Enroll the test device in the Windows Insider Program and select the Beta Channel via Settings > Windows Update > Windows Insider Program.
• If you want the earliest exposure to staged features, turn on the optional toggle: Get the latest updates as soon as they’re available (note: this increases risk of encountering experiments).
• Check for updates and install the cumulative package identified by the announced KB. After installation, confirm feature exposure via Settings and test flows such as Agent-in-Settings searches and Drag Tray sharing to validate behavior.

Testing checklist (quick)

• Verify: Agent in Settings search entries surface inline actions where expected.
• Verify: Drag Tray accepts multiple files, surfaces relevant apps, and moves files to a chosen folder without duplication.
• Test: File Explorer context-menu and cloud-file launch responsiveness.
• Test: Windows Hello enrollment and peripheral ESS behavior on devices with external fingerprint readers if your scenario requires it.

---

Strengths, opportunities, and risks — critical analysis​

Strengths

• Tangible productivity wins: Agent-in-Settings inline actions and the improved Drag Tray address everyday friction points in Windows workflows and are likely to increase perceived productivity for frequent users.
• Pragmatic rollout: Microsoft’s staged enablement approach lets telemetry guide exposure, which reduces large-scale regressions and gives engineers a chance to iterate on real-world usage patterns.
• On-device-first design where possible: Copilot+ gating combines low-latency, privacy-friendly inference with local responsiveness for eligible hardware. This is a design advantage for notebooks and workstations equipped with NPUs.

Opportunities

• Broader accessibility and discoverability: Agents in Settings can help bridge discoverability gaps in Windows Settings and make configuration easier for non-technical users.
• Platform consistency: Drag Tray can serve as an incremental modernization of drag-and-drop across desktop and touch-centric workflows — an opportunity to unify behavior across form factors.

Risks and mitigations

• Fragmentation: Hardware gating and region/licensing restrictions create a fractured experience across a diverse device estate. Mitigation: document feature exposure per device class and provide alternate workflows for non-eligible users.
• Driver/agent regressions: Insider builds have occasionally surfaced driver or agent incompatibilities. Mitigation: run thorough compatibility tests for management agents, AV, storage drivers, and biometric drivers before any broader rollout.
• Privacy and telemetry concerns: Features that hand off content to Copilot (even when local) or rely on telemetry for rollout require clear communications to stakeholders and careful policy review. Mitigation: review enterprise telemetry settings and user consent flows before enabling early features widely.

---

Final verdict for enthusiasts and IT professionals​

Build 26120.6780 (KB5067103) continues Microsoft’s iterative approach to integrating Copilot-era assistance directly into Windows while balancing stability improvements across system subsystems. For enthusiasts and Insider power-users, the build offers interesting, practical enhancements — particularly the Agent-in-Settings refinements and Drag Tray upgrades — that can tangibly improve day-to-day productivity on eligible hardware.
For IT professionals, this build should be treated as a targeted validation flight: it’s useful for pilot groups and compatibility testing, but not yet a candidate for mass production rollout. Validate drivers, management agents, and biometric/passkey workflows in a test ring, and be prepared for staged exposure depending on hardware, licensing, and region.

---

Conclusion​

This Beta Channel checkpoint reinforces Microsoft’s measured strategy: deliver incremental UX improvements and on-device Copilot capabilities while limiting broad impact through staged enablement. The Agent-in-Settings enhancements and Drag Tray improvements represent pragmatic, user-facing progress — small changes that reduce friction and modernize long-standing desktop workflows. Yet the benefits arrive under conditions: Copilot+ hardware eligibility, feature flags, and licensing constraints continue to shape who will experience the new behaviors first.
Insiders testing Build 26120.6780 should focus on validating these targeted flows in a controlled environment, provide actionable Feedback Hub reports where behavior deviates, and plan for the operational realities of a fragmented, staged rollout as Microsoft expands these experiences to more devices.

---

Source: Microsoft - Windows Insiders Blog Announcing Windows 11 Insider Preview Build 26120.6780 (Beta Channel)