Microsoft’s latest Dev Channel flight lands with a focused patch for Copilot+ PCs, smoother voice dictation, expanded Studio Effects camera support, and a collection of targeted fixes — but it also brings a set of hardware-gated rollouts and a handful of stability warnings that Insiders and IT teams need to weigh carefully. (blogs.windows.com)
Microsoft released Windows 11 Insider Preview Build 26220.5790 (KB5065779) to the Dev Channel as a cumulative flight built on the Windows 11, version 25H2 servicing stream. The release continues Microsoft’s recent practice of using the Dev Channel as a testbed for AI-driven features, while delivering many experiences via controlled feature rollouts (a toggle you can enable under Settings > Windows Update). This approach means not every Insider will see all changes immediately — features are frequently gated by hardware, account type, or regional rules. (blogs.windows.com)
The release is small in build delta but significant in intent: it prioritizes Copilot+ device experiences, accessibility improvements, and incremental File Explorer and camera enhancements — the kind of user-facing refinements that shape the Windows 11 workflow rather than wholesale UI overhauls.
Cautionary note: some public discussion has framed the stagger as a possible exclusivity or prioritization issue. That is speculative and not confirmed by Microsoft; the practical reality is driver and binary differences across silicon vendors necessitate careful, staged deployments. Flagging the speculation is important — it’s a separate conversation from the engineering reasons Microsoft has documented. (windowscentral.com)
For Insiders and IT teams evaluating this flight, the priorities are clear: pilot on representative hardware, validate audio and camera stacks, test Copilot and data governance flows, and maintain rollback options for hibernation or Bluetooth controller regressions. Done carefully, this build offers a sneak peek at the direction of Windows’ on-device AI and a chance to shape the features before they mature for broader release. (blogs.windows.com)
Source: Windows Blog Announcing Windows 11 Insider Preview Build 26220.5790 (Dev Channel)
Background
Microsoft released Windows 11 Insider Preview Build 26220.5790 (KB5065779) to the Dev Channel as a cumulative flight built on the Windows 11, version 25H2 servicing stream. The release continues Microsoft’s recent practice of using the Dev Channel as a testbed for AI-driven features, while delivering many experiences via controlled feature rollouts (a toggle you can enable under Settings > Windows Update). This approach means not every Insider will see all changes immediately — features are frequently gated by hardware, account type, or regional rules. (blogs.windows.com)The release is small in build delta but significant in intent: it prioritizes Copilot+ device experiences, accessibility improvements, and incremental File Explorer and camera enhancements — the kind of user-facing refinements that shape the Windows 11 workflow rather than wholesale UI overhauls.
What’s new (high-level summary)
- Fluid dictation in Voice Access — On Copilot+ PCs, voice access now offers fluid dictation, an on-device SLM-driven dictation mode that auto-corrects grammar, punctuation, and filler words while you speak. Enabled by default and available in English locales, it is disabled in secure fields such as password/PIN inputs.
- Windows Studio Effects on additional cameras — Studio Effects can now be applied to a secondary camera (for example, an external USB webcam) on supported Copilot+ PCs. The requisite driver update is rolling out first to Intel-powered Copilot+ PCs, with AMD and Snapdragon updates following.
- File Explorer Home on‑hover actions — Hovering over entries in File Explorer Home surfaces quick actions like Open file location and Ask Copilot about this file (Microsoft account required for now). This feature is gradually rolled out and currently excluded for Insiders in the EEA.
- Triage of targeted fixes — The build addresses specific lag and taskbar preview alignment regressions, corrects context menu flapping in File Explorer with certain third‑party apps, and resolves an Event Viewer error tied to the Pluton cryptographic provider.
Deep dive: fluid dictation — what it is and why it matters
What Microsoft shipped
Fluid dictation is billed as a smoother, more conversational dictation experience inside Voice Access on Copilot+ PCs. The system uses small language models (SLMs) that run on the device — a design that reduces latency and keeps text-processing local for improved privacy. The feature performs real-time punctuation, grammar correction, and removal of filler words so users spend less time editing the text after dictation. It is enabled by default and controllable via the voice access settings flyout or voice command.Practical benefits
- Faster composition for email, notes, and messaging where punctuation and sentence structure matter.
- Lower friction for people with mobility or fine-motor challenges who rely on voice input.
- Local processing reduces data sent to cloud services and improves responsiveness on modern Copilot+ hardware.
Caveats and limitations
- Currently available only in English locales.
- Disabled in secure entry fields (passwords, PINs) — a sensible safety measure but one that can be surprising for users trying to dictate into enterprise credential fields.
- As an SLM-powered feature, effectiveness depends on the quality of on-device models and the hardware NPU/accelerator available on each Copilot+ PC. Expect incremental accuracy improvements as the model and rollouts mature. (blogs.windows.com)
Windows Studio Effects: extending the camera stage
The change
Microsoft expanded Windows Studio Effects so that, on supported Copilot+ PCs, you can toggle Studio Effects for an additional camera (for example, an external USB webcam or a rear laptop camera). The toggle lives in Settings > Bluetooth & devices > Cameras under advanced camera options. This extends AI-powered background blur, lighting, and framing features beyond the integrated front-facing camera.Driver rollout and hardware gating
The Studio Effects driver update will be delivered in stages: Intel-powered Copilot+ PCs first, followed by AMD and Snapdragon machines. This staggered driver distribution is intended to reduce risk and manage the complexity of integrating the Studio Effects stack across different SoCs and NPUs.Why this matters
- Users who rely on external webcams for hybrid meetings now gain the same AI camera polish previously limited to integrated cameras.
- IT and AV managers can extend consistent video effects across conference setups and personal docking stations.
Risks and operational notes
- The experience is predicated on a device meeting Studio Effects prerequisites (NPU/accelerator support, compatible driver). Not all external webcams will be supported.
- Driver rollouts risk mismatched expectations if admins or users assume a feature will appear simultaneously across device fleets — validation and staged pilot testing are essential.
- Because Studio Effects involves image processing and possibly synthetic image transformations, organizations with strict privacy or image retention rules should validate behavior in their environments before mass enabling.
File Explorer: hover actions and Copilot integration
What changed
File Explorer Home now reveals on-hover actions in the Home view (Recent, Favorites, Shared) including Open file location and an Ask Copilot about this file action. The latter uploads or references the selected file into the Copilot experience for summarization, outlining, or deeper interaction. The initial rollout requires signing into Windows with a Microsoft account (work/school Entra ID support is forthcoming) and is not available in the EEA at present.Why this is useful
- Cuts clicks and time-to-action for common tasks.
- Makes Copilot’s capabilities more discoverable by surfacing them in context where users already look at files.
- Reduces the friction of extracting quick file information, generating summaries, or launching task-specific AI actions.
Implementation considerations
- The Ask Copilot action implies a content flow between local files and Copilot. Administrators should evaluate data handling policies, especially for corporate tenants where document sensitivity is a concern.
- Work/school account support is required for certain Microsoft 365–bound actions; enterprises should validate Entitlement and licensing requirements for Copilot and Microsoft 365 integrations before assuming feature parity for managed devices. (blogs.windows.com)
Fixes and stability work
Build 26220.5790 includes several technical fixes aimed at improving responsiveness and eliminating UI regressions introduced in earlier flights:- Fixed an underlying lag issue that could add ~500 ms to clicks in File Explorer, taskbar interactions, and affect browser video playback responsiveness.
- Resolved misaligned app preview windows in the taskbar that could follow a display resolution change.
- Corrected a File Explorer context-menu oscillation (switching between initial view and “Show more options” on repeated right-clicks) observed with certain third-party apps.
- Fixed Settings > System > Storage > Temporary files scanning hang.
- Addressed an Event Viewer error related to the Microsoft Pluton Cryptographic Provider not initializing for some Insiders.
Known issues — risk checklist for Insiders and IT
This build ships with several active known issues that range from cosmetic to potentially disruptive. Key items to consider before enrolling devices in the Dev Channel:- Hibernation bugcheck (green screen) — Microsoft is investigating cases where some PCs bugcheck during or after hibernation on the previous flight. Affected users should avoid hibernation until a fix lands. This can appear as if the PC has powered off instead of hibernating. High risk for laptops and machines relying on hibernation.
- PIX GPU capture playback — PIX on Windows is currently unable to play back GPU captures on this OS version; Microsoft expects a PIX update to resolve playback (estimated end of September). Developers relying on PIX should use the PIX feedback path or request private builds.
- Audio driver corruption symptom — Some Insiders in Dev and Beta see audio failures with Device Manager showing yellow exclamation marks on devices such as “ACPI Audio Compositor.” Microsoft published a remediation sequence: update driver → Browse my computer → Let me pick from a list → choose the most recent driver on disk. Enterprise admins should be ready with driver rollbacks or staged updates.
- Xbox controller Bluetooth bugcheck — Some Insiders experienced PC bugchecks when connecting Xbox controllers over Bluetooth. Microsoft’s workaround is to uninstall the specific oemXXX.inf (XboxGameControllerDriver.inf) installer entry via Device Manager (View → Devices by Driver → uninstall the oemXXX.inf entry). This is a heavy-handed fix and should only be used as directed.
Security and privacy implications
- On-device SLMs: The fluid dictation feature’s use of local small language models is a net positive for privacy compared with cloud-only transcription flows. Because text processing stays on the device, less data is transmitted to remote endpoints. However, enterprises should confirm that local models and telemetry settings meet organizational data-handling policies before enabling the feature broadly.
- Copilot file interactions: The Ask Copilot action in File Explorer implies a content handoff between local storage and Copilot services. Organizations must review whether that handoff triggers data egress or logging in tenant-level services and update DLP or governance rules accordingly. This is especially important where regulated data or export controls apply. (blogs.windows.com)
- Driver updates and kernel-mode components: The Studio Effects driver and audio driver workarounds touch kernel-level components in some cases. IT security teams should validate signatures, test on non-production hardware, and ensure compatibility with endpoint protection tooling to avoid false positives or driver-blocking scenarios.
How to evaluate and pilot this build (recommended process)
- Identify a small, diversified pilot group including Copilot+ hardware variants (Intel, AMD, Snapdragon where available).
- Verify critical app and driver compatibility (audio stacks, USB webcams, productivity suites, virtualization and GPU tooling such as PIX).
- Enable the Insider toggle only on pilot machines and monitor Feedback Hub reports and telemetry for new regressions.
- Prepare rollback and recovery plans: full system image backups, known-good driver packages, and documented uninstall steps for problematic oemXXX.inf entries.
- Test privacy and DLP flows for Copilot interactions, especially for users who handle regulated data.
The broader context: rollout strategy and hardware gating
Microsoft’s pattern across recent Insider flights is clear: many AI and Copilot-centric features are hardware-gated to Copilot+ PCs and often prioritized for Snapdragon (Qualcomm) variants in early previews, with Intel and AMD following. This creates a staggered user experience that can look like preferential treatment of certain OEM/SoC platforms. Independent reporting has noted the timeline gaps between Snapdragon and Intel/AMD availability, and this release follows that same pattern (Studio Effects driver first to Intel, then AMD and Snapdragon in coming weeks). While the technical reasons for staggered rollouts are real (different NPUs, driver ecosystems, and certification paths), organizations should plan for phased feature availability across device fleets. (windowscentral.com)Cautionary note: some public discussion has framed the stagger as a possible exclusivity or prioritization issue. That is speculative and not confirmed by Microsoft; the practical reality is driver and binary differences across silicon vendors necessitate careful, staged deployments. Flagging the speculation is important — it’s a separate conversation from the engineering reasons Microsoft has documented. (windowscentral.com)
What to watch for next
- A follow-up Studio Effects driver roll-out for AMD and Snapdragon Copilot+ devices.
- Microsoft’s promised PIX update for GPU capture playback (Microsoft estimated a PIX release by end of September in the release notes).
- Fixes for the hibernation bugcheck and Bluetooth Xbox controller bugchecks, both of which are high priority for a stable Dev-channel experience.
- Broader regional and account-type unlocking of File Explorer Copilot actions (EEA and Entra ID work/school account support).
Bottom line
Build 26220.5790 is a typical Dev Channel flight: focused, incremental, and experimental. It delivers meaningful productivity and accessibility improvements — notably fluid on-device dictation and expanded Studio Effects camera support — while deliberately keeping those experiences tied to Copilot+ hardware via a controlled rollout. At the same time, the release exposes the friction that comes with hardware-gated features: staggered rollouts, driver dependency complexity, and a non-trivial set of known issues that make this more suitable for Insiders and cautious pilot programs than broad enterprise deployment.For Insiders and IT teams evaluating this flight, the priorities are clear: pilot on representative hardware, validate audio and camera stacks, test Copilot and data governance flows, and maintain rollback options for hibernation or Bluetooth controller regressions. Done carefully, this build offers a sneak peek at the direction of Windows’ on-device AI and a chance to shape the features before they mature for broader release. (blogs.windows.com)
Source: Windows Blog Announcing Windows 11 Insider Preview Build 26220.5790 (Dev Channel)
