Windows 11’s latest Beta-channel preview, Build 26120.5790, brings two pragmatic AI upgrades—fluid dictation and expanded Windows Studio Effects for additional cameras on Copilot+ PCs—alongside a UI tweak in File Explorer’s Home panel that may please some users but annoy others with added visual clutter. (blogs.windows.com)
Microsoft shipped Windows 11 Insider Preview Build 26120.5790 to the Beta channel on September 5, 2025, framing this flight around incremental Copilot+ improvements that lean heavily on on-device AI processing. The release is explicitly targeted at Copilot+ PCs—machines equipped with on-device neural acceleration (NPUs) and the associated drivers that enable local AI inference. (blogs.windows.com)
Copilot+ is not a single product but a class of devices where Windows’ new AI features are intended to run locally, reducing latency and, in Microsoft’s framing, improving privacy. The new build bundles accessibility gains, camera-effect expansions, and tighter Copilot integration inside everyday workflows such as File Explorer. Official notes make clear these features are rolling out gradually and may be gated by region, hardware vendor drivers, or service toggles. (learn.microsoft.com, support.microsoft.com)
However, the experience will be uneven across devices during the staged driver rollout, and the File Explorer Home additions walk a line between convenience and clutter—particularly for users who avoid cloud identities. Organizations and power users should treat this flight as a preview: test, measure battery and performance impacts, and plan deployment with clear privacy and driver-update policies in mind. Community reporting suggests the staggered vendor rollouts are likely to continue as hardware ecosystems and OEM drivers catch up; that reality makes a cautious deployment strategy prudent. (windowscentral.com, windowsforum.com)
Windows 11’s incremental AI deliveries in this build represent steady progress: smarter dictation, more flexible camera effects, and deeper Copilot touches in everyday tools. The technical story is credible—on-device models and per-camera routing are verifiable in Microsoft’s documentation—but the user experience will be defined by vendor drivers, device endurance, and whether users welcome a slightly busier File Explorer. For those running Copilot+ hardware, these updates are worth trying in a controlled manner; for everyone else, the benefits are promising but may not justify an immediate jump until vendor parity and driver availability stabilize. (blogs.windows.com, learn.microsoft.com)
Source: Observer Voice Windows 11 Introduces Two Exciting AI Enhancements for Copilot+ PCs and One Potentially Frustrating Change
Microsoft shipped Windows 11 Insider Preview Build 26120.5790 to the Beta channel on September 5, 2025, framing this flight around incremental Copilot+ improvements that lean heavily on on-device AI processing. The release is explicitly targeted at Copilot+ PCs—machines equipped with on-device neural acceleration (NPUs) and the associated drivers that enable local AI inference. (blogs.windows.com)Copilot+ is not a single product but a class of devices where Windows’ new AI features are intended to run locally, reducing latency and, in Microsoft’s framing, improving privacy. The new build bundles accessibility gains, camera-effect expansions, and tighter Copilot integration inside everyday workflows such as File Explorer. Official notes make clear these features are rolling out gradually and may be gated by region, hardware vendor drivers, or service toggles. (learn.microsoft.com, support.microsoft.com)
What’s new — at a glance
- Fluid dictation (voice access): continuous, intelligent dictation that auto-corrects grammar, punctuation and removes filler words using on-device small language models (SLMs). It is enabled by default on Copilot+ PCs and is deliberately disabled in secure text fields (passwords, PINs). (blogs.windows.com)
- Windows Studio Effects on additional cameras: Windows Studio Effects—Microsoft’s AI camera pipeline that provides background blur, eye contact, auto-framing and related features—can now be routed to an additional camera (for example, a USB webcam or a rear laptop camera) on supported Copilot+ PCs, toggled per-camera from Settings. The driver update enabling this behavior is rolling out first to Intel-powered Copilot+ PCs; AMD and Snapdragon devices will follow in subsequent weeks. (blogs.windows.com, learn.microsoft.com)
- File Explorer Home: hover actions: the Home panel will show contextual actions when hovering over files—shortcuts such as Open file location and Ask Copilot about this file. These options require a Microsoft account sign-in to operate and are currently being rolled out selectively. Community previews note the feature is not yet enabled for some geographies. (windowsforum.com)
Fluid dictation: what it does and why it matters
The feature, explained
Fluid dictation is an iteration of Voice Access that promises more natural, “hands-free” writing. Unlike basic speech-to-text, the feature performs inline editing as you speak: punctuation and grammar fixes are applied automatically, and filler words (“um”, “uh”, etc.) can be suppressed. Microsoft says the experience is powered by on-device small language models (SLMs) to keep processing local to the Copilot+ machine, aiming to reduce latency and limit data leaving the PC. The feature is available in all English locales for Copilot+ devices in this preview. (blogs.windows.com)Practical benefits
- Faster drafting: Fewer manual edits after initial dictation means faster conversion of spoken thoughts into clean text.
- Accessibility boost: Users who rely on voice input for mobility, vision or dexterity reasons get a significantly cleaner base transcript.
- Privacy and latency: Local SLM inferencing reduces round-trips to the cloud, improving responsiveness and reducing potential exposure of speech data. (blogs.windows.com)
How to use it (verified steps)
- Launch Voice Access (search Start for Voice Access or launch via accessibility shortcuts).
- Complete the initial setup if you haven't used Voice Access before.
- Use the top-right settings flyout to toggle Fluid dictation on or off, or say “turn on fluid dictation” / “turn off fluid dictation.” The feature runs in any text field except secure fields like password boxes. (blogs.windows.com)
Caveats and verification notes
- The underlying claim that all processing remains local is consistent with Microsoft’s documentation for SLMs on Copilot+ hardware; however, the precise telemetry and fallback behaviors for complex inputs (when the system may prefer cloud assistance) are often gated by device configuration and enterprise policies and should be confirmed with org-specific privacy documentation. Where Microsoft confirms on-device processing, the finer telemetry flows are law- and policy-relevant and thus merit verification for managed environments. (blogs.windows.com)
Windows Studio Effects: now available for more cameras
What changed
Windows Studio Effects has been available on front-facing cameras of Copilot+ laptops for some time. Build 26120.5790 introduces a per-camera toggle that lets Windows route an additional camera’s feed (for example, a USB webcam or a laptop rear camera) through the Studio Effects pipeline so apps receive the processed feed instead of the raw input. This opens the AI effects—background blur, Eye Contact, Auto Framing, etc.—to a wider range of hardware setups. (blogs.windows.com, learn.microsoft.com)How to enable
- Open Settings > Bluetooth & devices > Cameras.
- Select the camera you want to configure from the connected cameras list.
- Open Advanced camera options and toggle Use Windows Studio Effects.
- Adjust effects via the camera settings page or the Studio Effects Quick Settings tile. (blogs.windows.com, support.microsoft.com)
Why this matters
- Flexibility for hybrid setups: Users who connect external webcams to improve image quality can now benefit from the NPU-driven effects without being forced to use the laptop’s built-in camera.
- Consistent meeting presence: Features like simulated eye contact and background controls become available across broader workflows and conferencing apps.
- Simplifies device management: Instead of toggling effects inside every conferencing app, Studio Effects become an OS-level output that apps can consume. (learn.microsoft.com)
Verified rollout detail and fragmentation risk
Microsoft explicitly states the necessary Studio Effects driver update will roll out first to Intel-powered Copilot+ PCs, with AMD and Snapdragon devices following later. This Intel-first sequence is unusual given earlier waves of Copilot+ features that favored Snapdragon silicon in initial rollouts; independent reporting and community testers have documented device-tiered rollout behavior, which can create fragmented user experiences. Microsoft’s stated driver rollout order is authoritative for this build, but the broader pattern of vendor-prioritization is a pragmatic observation from multiple coverage sources and community feedback rather than an official policy explanation. (blogs.windows.com, windowscentral.com)File Explorer Home: hover actions and Copilot integration
What changed
File Explorer’s Home panel now exposes on-hover actions when you mouse over files. The quick actions include shortcuts like Open file location and Ask Copilot about this file. Functionality that queries the Copilot assistant requires the user to be signed into a Microsoft account; business and school accounts are planned to be supported later. The rollout appears region-limited in some Insider flights. (windowsforum.com)The trade-off: convenience vs. clutter
- Pros: Faster contextual actions, one-click access to Copilot insights about a document, and a small productivity win for users who regularly interrogate files.
- Cons: For users who prefer a minimal UI, additional hover chrome can feel noisy, and the requirement to sign into a Microsoft account may be unwelcome for those who prefer local accounts or stricter privacy postures. Insider testers have flagged the potential for visual clutter when multiple overlays and quick actions accumulate in Home. (windowsforum.com)
Privacy, security, and enterprise considerations
On-device processing and privacy
Microsoft’s documentation for this build emphasizes on-device SLMs for fluid dictation and local NPU inferencing for Studio Effects where supported. This architecture reduces the need to send raw speech or unprocessed video frames to cloud services, which is a material privacy win for many scenarios. However, on-device processing does not eliminate telemetry entirely—diagnostic logs and feature-usage signals may still be collected, depending on diagnostic settings and enterprise policy. Administrators should review telemetry configurations and data retention policies before broad deployment. (blogs.windows.com)Sensitive fields and safe defaults
Microsoft has disabled fluid dictation in fields that accept secure data (passwords, PINs), which is a deliberately conservative design choice. For organizations with stricter data residency or compliance needs, confirm whether any Copilot or Studio Effects components fall under corporate data-flow policies. If enterprises require full cloud-auditable logs or need to disable local AI features on certain fleets, Group Policy and MDM controls should be consulted. (blogs.windows.com)Hardware & driver gating
- NPU requirement: Many Studio Effects require a supported NPU and a vendor-supplied driver or companion software.
- Driver rollout and vendor variance: The Intel-first driver rollout means that not all Copilot+ branded hardware will have parity at the same time; device manufacturers must opt-in and ship updated drivers for full functionality. This introduces a window where identical software builds behave differently across hardware vendors. (learn.microsoft.com, support.microsoft.com)
Strengths: what Microsoft did well
- Meaningful accessibility improvements: Fluid dictation elevates voice input beyond raw transcription by reducing cleanup time for users who rely on voice-first input. This is a tangible win for inclusion and productivity. (blogs.windows.com)
- OS-level camera processing: Extending Studio Effects to external cameras simplifies cross-app consistency and reduces per-app configuration burden. It creates a single control plane for webcam enhancements. (learn.microsoft.com)
- Privacy-forward messaging: Emphasizing on-device SLMs and disabling dictation in secure fields are sensible defaults that align with enterprise privacy expectations—if the implementation matches the claims. (blogs.windows.com)
Risks, limitations, and things to watch
- Fragmented experience across hardware: The staggered driver rollout—Intel first, AMD and Snapdragon later—means inconsistent feature availability across Copilot+ PCs. This can be problematic for teams standardizing on a mixed-hardware fleet. Independent reporting and early tester impressions have already highlighted this unevenness. (windowscentral.com, windowsforum.com)
- Performance and battery impact: While NPUs offload work from CPU and GPU, Studio Effects and continuous dictation still consume power and system resources. On laptops, enabling an NPU-driven camera pipeline and continuous dictation may reduce battery life or raise thermal profiles depending on workload and system tuning. Microsoft’s support docs warn that camera effects can impact performance and battery. Test on representative devices before enabling widely. (support.microsoft.com, learn.microsoft.com)
- Visual clutter and discoverability trade-offs: Adding on-hover quick actions in File Explorer increases discoverability for some users but adds UI chrome that others will find intrusive. The Microsoft account requirement for Copilot actions adds friction for local-account purists and some privacy-minded users. (windowsforum.com)
- Unverified motive behind rollout order: Observers have inferred a pattern where certain vendors (e.g., Qualcomm Snapdragon partners) received early access to some AI features in prior waves. While community reporting supports claims of staggered prioritization, Microsoft has not publicly confirmed contractual reasons or specific prioritization policies—this remains an area where public statements and independent reporting diverge. Treat claims of vendor favoritism as plausible but not definitive without official confirmation. (windowscentral.com)
Recommendations: for enthusiasts, admins, and everyday users
For enthusiasts and early adopters
- Enable the Beta channel and the “get the latest updates as soon as they’re ready” toggle to try Build 26120.5790.
- Test fluid dictation with typical note-taking and email scenarios. Measure cleanup time versus typed drafts.
- If you use an external webcam, try toggling Use Windows Studio Effects in Settings to evaluate visual quality, CPU/NPU utilization and cross-app compatibility.
For IT admins and procurement
- Inventory devices by NPU capability and vendor (Intel, AMD, Qualcomm) to set realistic rollout expectations.
- Pilot Studio Effects and fluid dictation on a small, representative fleet to validate battery, thermal and privacy impacts.
- Confirm telemetry and diagnostic settings through your MDM/GPO settings and update compliance guidance so users understand what data is local versus transmitted.
- Prepare communication for end users explaining Microsoft account requirements for Copilot-file actions, and provide alternatives for users on local accounts.
For privacy-conscious users
- Review diagnostics settings (Privacy & security > Diagnostics & feedback) and test with the features enabled vs disabled to confirm you are comfortable with any telemetry footprint.
- If you prefer not to use on-device AI features at all, both fluid dictation and Studio Effects can be toggled off in the relevant Settings panels. (blogs.windows.com, support.microsoft.com)
Technical verification — what was checked and why it matters
Key technical claims in the original preview announcement were verified against Microsoft’s own Insider Blog and Windows documentation pages. These sources confirm:- The build number and Beta-channel release notes for Build 26120.5790. (blogs.windows.com)
- Fluid dictation’s architecture using on-device SLMs and its default-on state for Copilot+ PCs, with secure-field exclusions. (blogs.windows.com)
- The Settings path and per-camera toggle to enable Windows Studio Effects on additional cameras (Settings > Bluetooth & devices > Cameras > Advanced camera options > Use Windows Studio Effects). (blogs.windows.com, learn.microsoft.com)
- Microsoft Support guidance that Studio Effects availability depends on NPU presence and vendor support; effects may impact battery and performance. (support.microsoft.com)
Final analysis and verdict
Build 26120.5790 is a pragmatic, evolutionary update for Windows 11 that does two useful things well and one thing that will polarize users. Fluid dictation addresses a long-standing pain point for voice-first authors and accessibility users by aggressively reducing the post-edit burden. Extending Windows Studio Effects to external cameras is a sensible systems-level approach that reduces friction for hybrid working setups and elevates the baseline video experience. Both improvements align with Microsoft’s broader Copilot+ strategy to push inference onto local silicon where available. (blogs.windows.com, learn.microsoft.com)However, the experience will be uneven across devices during the staged driver rollout, and the File Explorer Home additions walk a line between convenience and clutter—particularly for users who avoid cloud identities. Organizations and power users should treat this flight as a preview: test, measure battery and performance impacts, and plan deployment with clear privacy and driver-update policies in mind. Community reporting suggests the staggered vendor rollouts are likely to continue as hardware ecosystems and OEM drivers catch up; that reality makes a cautious deployment strategy prudent. (windowscentral.com, windowsforum.com)
Windows 11’s incremental AI deliveries in this build represent steady progress: smarter dictation, more flexible camera effects, and deeper Copilot touches in everyday tools. The technical story is credible—on-device models and per-camera routing are verifiable in Microsoft’s documentation—but the user experience will be defined by vendor drivers, device endurance, and whether users welcome a slightly busier File Explorer. For those running Copilot+ hardware, these updates are worth trying in a controlled manner; for everyone else, the benefits are promising but may not justify an immediate jump until vendor parity and driver availability stabilize. (blogs.windows.com, learn.microsoft.com)
Source: Observer Voice Windows 11 Introduces Two Exciting AI Enhancements for Copilot+ PCs and One Potentially Frustrating Change