Windows 11 Insider Beta Build 26120 6780: Copilot Agent in Settings and Drag Tray Upgrades

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. fileciteturn0file19turn0file18

---

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. fileciteturn0file11turn0file19
• 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. fileciteturn0file11turn0file19
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. fileciteturn0file5turn0file18

---

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. fileciteturn0file11turn0file5

---

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