Windows 11 Insider Preview Build 26120.5790 landed in the Beta channel on September 5, 2025, packing two practical AI upgrades for Copilot+ PCs and a File Explorer change that has already divided early testers. The update delivers “fluid dictation” for Voice Access, extends Windows Studio Effects to more cameras, and introduces hover-triggered quick actions in File Explorer’s Home panel—but the Intel-first driver rollout for camera effects and a mandatory Microsoft account requirement for Copilot integration add friction that community members are calling out.

Fluid dictation: AI that cleans up after you speak

Fluid dictation is the star of this build. Unlike basic speech-to-text that leaves you to manually fix grammar and punctuation, it automatically corrects both and strips filler words—“um,” “uh,” and the like—in real time. Microsoft runs the feature entirely on-device using small language models (SLMs) that leverage the NPU inside Copilot+ PCs, promising lower latency and a privacy shield: your voice never leaves the machine.

To try it, launch Voice Access (search Start or use an accessibility shortcut), complete the one-time setup if needed, then toggle the feature in the top-right settings flyout or simply say “turn on fluid dictation.” The system works in any editable text field except secure ones like password boxes—a deliberate safeguard. Microsoft says the feature is enabled by default for Copilot+ devices and supports all English locales in this release.

In practice, the impact is tangible. Early users report spending far less time on post-dictation edits, making voice input viable for long-form writing and note-taking. Accessibility advocates have praised the upgrade; for anyone who relies on voice due to motor or vision impairments, the cleaner baseline transcript is a meaningful quality-of-life leap. Administrators, however, should note that while the SLMs run locally, Windows telemetry may still send diagnostic signals depending on your settings—something to verify in managed environments where data residency matters.

Windows Studio Effects break out of the built-in camera box

For months, Windows Studio Effects—background blur, eye contact simulation, auto-framing, and filters—lived exclusively on the front cameras of Copilot+ laptops. Build 26120.5790 changes that by adding a per-camera toggle that routes an additional camera’s feed through the same NPU-powered pipeline. A USB webcam or a laptop’s rear camera can now deliver the polished video stream that apps consume, no per-app configuration required.

To activate it: open Settings > Bluetooth & devices > Cameras, pick the camera, expand Advanced camera options, and flip “Use Windows Studio Effects.” Camera-specific adjustments then live in the Studio Effects Quick Settings tile. The OS-level approach is a win for hybrid workers who own external webcams and want consistent meeting presence across Teams, Zoom, and other apps.

But the rollout has a twist. Microsoft is delivering the required driver update first to Intel-powered Copilot+ PCs; AMD and Snapdragon devices will follow “in subsequent weeks.” This Intel-first cadence breaks from the Snapdragon-led pattern of earlier Copilot+ waves, sparking discussion in forums and on social media. Some insiders suspect contractual arrangements, while others point to driver maturity. Microsoft hasn’t explained the shift, but the practical result is clear: two Copilot+ laptops running the identical build can behave very differently for weeks. Independent testers and publications have documented this fragmentation, and it adds a complicating factor for IT teams managing mixed-hardware fleets.

File Explorer hover actions: Copilot at the cost of clutter

File Explorer’s Home panel now shows contextual actions when you hover over a file—options like “Open file location” and “Ask Copilot about this file.” The latter requires signing in with a Microsoft account; school and work accounts are promised later. The feature aims to surface Copilot’s insights without leaving the file manager, a nod toward deeper AI integration in everyday workflows.

Early community feedback is split roughly in half. Some power users appreciate one-click access to Copilot summaries, especially for documents and spreadsheets. Others call the hover chrome noisy and distracting. Visual clutter is a sore point in Windows 11’s evolving interface, and adding more floating buttons—without an off switch, at least for now—frustrates those who prefer minimalism. The Microsoft account mandate also rankles privacy-focused users who stick with local accounts. As with many Insider features, the rollout is gradual and may not appear in all regions yet.

Privacy, telemetry, and the hardware reality

Microsoft’s messaging emphasizes on-device AI, and fluid dictation’s secure-field exclusion alongside local SLMs are genuine privacy positives. Yet on-device isn’t the same as zero data flow. Diagnostic logs and crash reports may still travel to Microsoft based on your telemetry settings. Administrators should audit Group Policy or MDM configurations to understand what’s transmitted and whether any cloud fallback is triggered for complex dictation—the precise telemetry paths can vary by device configuration and region.

Hardware gating adds another layer. Studio Effects on external cameras require a compatible NPU and vendor-supplied drivers. The Intel-first driver rollout means even Copilot+ PCs with AMD or Snapdragon NPs—the very silicon that launched the Copilot+ brand—will temporarily lack the feature. Microsoft’s support pages warn that camera effects can hit battery life and performance; organizations planning to deploy these features should pilot them on representative devices to gauge battery drain and thermal behavior before a broad rollout.

Community pulse: praise, puzzlement, and requests for control

The Insider community has largely cheered fluid dictation as a genuine productivity enhancer. “Finally, dictation that doesn’t make me look illiterate,” wrote one tester on a popular forum, while another noted, “I’ve been waiting for Studio Effects on my external webcam since day one.” The Intel-first rollout, however, has raised eyebrows. Many in the community recall that features like instant-on and advanced Windows Hello improvements hit Snapdragon devices first, so seeing Intel lead now has prompted speculation—though no official rationale.

The File Explorer hover actions have triggered a more mixed response. Some users appreciate the integration but want a quick toggle to disable it; others call it a solution in search of a problem. As one user put it: “I don’t need Copilot hovering over every PDF I open,” reflecting a broader tension between AI ubiquity and user control.

Recommendations for different audiences

For enthusiasts: If you have a Copilot+ PC, jump into the Beta channel, enable “get the latest updates,” and put fluid dictation through its paces. Try it across different apps and note whether cleanup time truly drops. Hook up an external webcam and check if Windows Studio Effects are available—Intel users are most likely to see the toggle right now. Use the Feedback Hub to report bugs and suggest improvements.

For IT admins: Inventory your Copilot+ fleet by chip vendor. Pilot the build on a small set of machines to measure battery, thermal, and telemetry impact. Review your diagnostic data settings via Group Policy, and prepare help desk documentation that explains the Microsoft account requirement for Copilot-enhanced File Explorer actions. If you have users on local accounts, plan alternative workflows.

For privacy-conscious users: You can turn off fluid dictation and Studio Effects entirely in Settings; the toggles are straightforward. Additionally, visit Settings > Privacy & security > Diagnostics & feedback and choose the minimal data-sharing option. Be aware that some telemetry may still be collected for system maintenance, even with basic diagnostics chosen.

The bigger picture: incremental AI, hardware seams

Build 26120.5790 is not a blockbuster release, and that’s fine. It refines two AI tools that make Windows more accessible and flexible, and it ties Copilot more tightly into a core productivity surface. Fluid dictation, in particular, could change how many users approach writing—moving voice input from a useful accessibility crutch to a first-class input method for anyone. Extending Studio Effects to external cameras solves a real hybrid-work hassle and gives the OS a competitive edge in video quality.

Yet the Intel-first driver rollout and the mandatory account tie-in for File Explorer actions show the rough edges of Microsoft’s AI ambition. The Copilot+ brand promises a uniform modern computing experience, but hardware-dependent feature gates undermine that. And requiring a Microsoft account to use an AI feature that queries cloud models—even if partially—will feel like an unnecessary push toward account lock-in for some.

As Copilot+ matures, these inconsistencies matter more. Microsoft’s challenge is to maintain momentum with regular, useful drops like this one while closing the vendor gap and respecting user choice in interface density. For now, the build is worth installing on compatible hardware, but with eyes wide open about the fragmentation ahead.