Microsoft released Windows 11 Insider Preview Build 26220.5790 (KB5065779) to the Dev Channel on September 5, 2025, packing a trio of AI-driven enhancements for Copilot+ PCs alongside targeted fixes and a handful of disruptive known issues. The update introduces fluid dictation in Voice Access, extends Windows Studio Effects to external cameras, and adds on-hover Copilot actions in File Explorer Home—all while keeping a tight hardware gate that limits the new features to devices with dedicated NPUs. For Insiders and IT teams, the build is a tantalizing but risky preview of Windows 11’s on-device AI trajectory.
Fluid dictation turns voice into polished text without the cloud
The star of this release is fluid dictation for Voice Access, a new mode that uses small language models (SLMs) running locally on Copilot+ PCs to transcribe speech with real-time grammar correction, punctuation, and filler-word removal. Unlike cloud-dependent dictation services, fluid dictation keeps all processing on the device, cutting latency and bolstering privacy. It is enabled by default in English locales and can be toggled from the voice access settings flyout or via voice command. Microsoft deliberately disables the feature in secure text fields—passwords, PINs, and other sensitive inputs are off-limits, a prudent design choice that may nonetheless frustrate users who expect seamless voice control in enterprise credential prompts.
Early adopters who have tested the feature report noticeably faster text composition in emails and documents, especially when dealing with complex sentence structures. The SLM’s ability to strip out “um” and “ah” on the fly reduces the need for post-dictation edits, which is a boon for people with mobility or fine-motor challenges. However, because the model runs entirely on the NPU, performance and accuracy will vary across Copilot+ hardware—Qualcomm Snapdragon X Elite devices, Intel Core Ultra 200 series, and AMD Ryzen AI 300 chips each have different AI accelerators, and Microsoft’s models will lean heavily on the NPU’s capabilities. Until the feature matures, users should expect incremental improvements in accuracy as Microsoft tunes the SLM. For now, fluid dictation remains an English-only affair, a limitation that mirrors the broader hesitancy to roll out AI-powered language features without thorough localisation.
Windows Studio Effects gain an external camera stage
Windows Studio Effects—a suite of AI-powered video effects including background blur, automatic framing, and eye contact—has been a staple for integrated front-facing cameras on Copilot+ PCs since their debut. Build 26220.5790 finally breaks that integration-only barrier by allowing users to apply Studio Effects to a secondary camera, such as an external USB webcam. The toggle appears under Settings > Bluetooth & devices > Cameras in the advanced camera options, effectively upgrading any meeting setup with the same polish previously reserved for built-in sensors.
The catch? A staggered driver rollout. Microsoft is pushing the required driver update to Intel-powered Copilot+ PCs first, with AMD and Snapdragon devices to follow in the coming weeks. This phased approach is sensible engineering—different NPUs require different driver stacks, and validating the Studio Effects pipeline across multiple architectures reduces the risk of widespread showstoppers—but it creates a fragmented Insider experience. If you’re on an AMD Ryzen AI platform, you’ll be waiting while Intel users test the feature; if you’re on Qualcomm, you’ll wait even longer. That lag has sparked speculation in forums about silicon favoritism, but Microsoft attributes it solely to technical certification paths. Regardless, IT managers planning hybrid meeting setups must budget for uneven feature availability across device fleets.
Not all external cameras will be supported. Studio Effects demands an NPU-accelerated video pipeline, so a generic USB webcam must be paired with a Copilot+ PC that has the requisite hardware and the new driver. Organizations with strict privacy or image retention policies should also test the effects thoroughly, as synthetic image transformations—even when processed locally—may raise compliance flags in regulated industries.
File Explorer hints at a Copilot-infused future
A subtle but clever change lands in File Explorer Home: hovering over a file in the Recent, Favorites, or Shared views now reveals quick actions like “Open file location” and “Ask Copilot about this file.” The latter action hands off the selected file to Copilot for summarization, outlining, or deeper interaction. For now, this requires a Microsoft account; work/school Entra ID support is promised later. The feature is also not available in the European Economic Area, reflecting Microsoft’s cautious regulatory posture around AI data flows in that region.
This is more than a convenience tweak. It represents a strategic push to embed Copilot directly into the file management workflow, making AI assistance as natural as a right-click. For users, the action eliminates the friction of opening a file, copying content, and pasting it into a Copilot chat. For IT, it triggers immediate data governance considerations: clicking “Ask Copilot” initiates a content handoff from local storage to Copilot services, which may cross egress boundaries or generate logs in tenant-level telemetry. Administrators must evaluate data loss prevention (DLP) policies and ensure that sensitive documents don’t accidentally flow into an ungoverned AI pipeline. As Copilot integrations multiply, this will become a recurring concern.
A bundle of quality-of-life fixes
Beyond the flagship features, Build 26220.5790 addresses several regressions that had been irritating Insiders. Most notably, a ~500 ms lag that crept into File Explorer clicks, taskbar interactions, and even browser video playback has been squashed. This kind of micro-latency can make a modern PC feel sluggish and had been widely reported in feedback channels. Also fixed: misaligned app preview windows in the taskbar after a display resolution change, and a bizarre File Explorer context-menu oscillation—where right-clicking on certain third-party apps would flip between the initial view and “Show more options” repeatedly. Other patches correct a scanning hang in Settings > System > Storage > Temporary files, and an Event Viewer error tied to the Microsoft Pluton Cryptographic Provider failing to initialize on some machines. These fixes collectively improve the day-to-day usability of Insider builds, but they come against a backdrop of unresolved gremlins.
Known issues: hibernation bugchecks, Bluetooth crashes, and more
Microsoft’s release notes for 26220.5790 include a risk checklist that should give any Insider pause. Top of the list: some PCs bugcheck (green screen) during or after hibernation on this and the previous flight. The symptoms mimic a sudden power-off, which can lead to data loss or corrupt workflows. Until a fix arrives, the only safe workaround is to avoid hibernation entirely—a tough pill for laptop users who rely on it to preserve session state.
Developers using PIX on Windows face another blocker: GPU capture playback is broken on this OS version. Microsoft expects a PIX update by the end of September 2025, but in the interim, PIX users must fall back to the feedback path or request private builds. For game developers and graphics programmers, this is a significant inconvenience.
Audio driver corruption continues to plague some Insiders across the Dev and Beta channels, with Device Manager showing yellow exclamation marks on devices like “ACPI Audio Compositor.” Microsoft’s remediation—manually update the driver via Browse my computer → Let me pick from a list → choose the most recent driver on disk—is clunky but effective. Enterprise admins should have driver rollback procedures ready.
Perhaps the most alarming known issue is a bugcheck triggered when connecting Xbox controllers over Bluetooth. Microsoft’s workaround is to uninstall the specific oemXXX.inf (XboxGameControllerDriver.inf) driver entry via Device Manager, a heavy-handed step that eliminates controller functionality entirely. For any test machine used in a pilot program, this means either living without a wireless Xbox controller or risking a crash with every connection attempt.
Security and privacy under the microscope
The shift toward on-device AI in fluid dictation is a net win for privacy. By processing speech locally, the feature avoids transmitting raw audio to Microsoft servers, which reduces the attack surface and aligns with enterprise data sovereignty requirements. However, companies should verify that local model telemetry—if any—complies with internal policies. The Studio Effects driver touches kernel-level components, so security teams must validate digital signatures and test against endpoint protection suites to prevent false positive driver blocks.
The Copilot file interaction creates a more complex data flow. When a user clicks “Ask Copilot,” the file content may be sent to the cloud, even if the device has on-device AI capabilities for other tasks. Organizations handling export-controlled data or regulated documents must map this flow and update DLP rules accordingly, lest an accidental click cause a compliance violation.
Rollout strategy and the hardware gating reality
Microsoft’s approach to this build underscores a broader Dev Channel philosophy: AI features are increasingly tied to Copilot+ hardware, and even then, rollouts are staggered by silicon vendor. The Studio Effects driver sequence—Intel first, AMD next, Snapdragon last—mirrors earlier patterns where Qualcomm devices often received new Copilot features weeks ahead of x86 counterparts. While some community members have speculated about exclusivity deals, the engineering reality is simpler: integrating an AI camera pipeline across three different NPU architectures is a multi-step process, and doing it all at once would risk stability.
This does create a perception problem, though. Insiders on AMD systems may feel like second-class citizens, and IT teams planning a Copilot+ rollout must account for phased feature availability. The lesson from this build is clear: if you’re evaluating Windows 11’s AI capabilities for a fleet, you need a diverse pilot group that includes every Copilot+ SoC you plan to deploy.
How to pilot Build 26220.5790 safely
For Insiders or IT departments brave enough to test, a staged approach minimizes risk. Start with a small, diversified group of Copilot+ machines covering Intel, AMD, and Snapdragon variants. Validate critical applications first—productivity suites, VPN clients, and any software that hooks deeply into the camera or audio stack. Only then enable the controlled feature rollout toggle under Settings > Windows Update. Monitor the Feedback Hub for new reports, and keep full system image backups and known-good driver packages on hand. For labs using Xbox controllers, either switch to wired connections or exclude those machines from the pilot. Test Copilot interactions with non-sensitive documents to observe data flow behavior, and document any anomalies for your compliance team.
What to watch for next
The coming weeks will bring a Studio Effects driver for AMD and Snapdragon Copilot+ PCs, which should level the playing field. Microsoft has also promised a PIX update to fix GPU capture playback by the end of September, though that timeline may slip. The hibernation and Bluetooth bugchecks are high-priority items that will likely get patches in an upcoming cumulative update; until then, they remain a deal-breaker for many. Finally, broader regional and account-type support for File Explorer’s Copilot actions—especially Entra ID work/school accounts—will unlock the feature for enterprise users and the EEA, signaling Microsoft’s confidence in the underlying AI governance.
Build 26220.5790 is a snapshot of Windows 11’s AI evolution: deeply integrated with Copilot+ hardware, aggressively experimental, and still rough around the edges. For those willing to navigate the known issues, it offers an early look at how on-device AI can transform everyday tasks—from hands-free dictation to video-call polish. For everyone else, it’s a reminder that the Dev Channel is a laboratory, not a production line.