Microsoft’s latest Beta-channel Insider preview pushes three changes that matter for day-to-day Windows users: on-device “fluid dictation” for Voice Access, Windows Studio Effects for alternate cameras on Copilot+ PCs, and a small but potentially divisive Ask Copilot option added to File Explorer’s Home hover menu—each arriving in Windows 11 Insider Preview Build 26120.5790 (KB5065779). (blogs.windows.com)
Windows 11’s Copilot era has been defined by two parallel strategies: move latency-sensitive AI inference onto the client (the Copilot+ device model), and gate the richest experiences behind hardware and driver prerequisites so Microsoft and OEMs can control quality and security. The new Beta build continues that approach by shipping features that run primarily on-device and are hardware-gated to certified Copilot+ PCs with supported NPUs and vendor-supplied drivers. The official Windows Insider announcement identifies the build, its channel, and rollout controls—and makes explicit that several of these new experiences are being gradually enabled for Insiders who opt in to “get the latest updates.” (blogs.windows.com)
This release therefore isn’t a broad Windows update for all 24H2 users; it’s a focused preview aimed at testers, accessibility users, and early adopters on Copilot+ hardware. Independent coverage and community writeups confirm the practical details and the staged nature of the rollout. (computerworld.com, ntcompatible.com)
Historically there have been times when Arm/Qualcomm devices received early previews of AI features; the Intel‑first timing here is a delivery choice tied to driver readiness rather than any permanent platform policy. That historical pattern is noted in coverage of Copilot+ PC launches and device availability. (theverge.com, windowscentral.com)
For enthusiasts and creators willing to test on spare hardware, the changes are meaningful and worth exploring now. For organizations and users who need rock-solid stability and strict data governance, the prudent path is staged testing, governance review, and waiting for subsequent fixes and enterprise-grade rollout signals from Microsoft and OEM partners. (windowsforum.com)
Source: TechRadar I'm jealous of a couple of nifty new AI powers coming to Windows 11 with Copilot+ PCs – but there's also a change I'm not so keen on
Windows 11’s Copilot era has been defined by two parallel strategies: move latency-sensitive AI inference onto the client (the Copilot+ device model), and gate the richest experiences behind hardware and driver prerequisites so Microsoft and OEMs can control quality and security. The new Beta build continues that approach by shipping features that run primarily on-device and are hardware-gated to certified Copilot+ PCs with supported NPUs and vendor-supplied drivers. The official Windows Insider announcement identifies the build, its channel, and rollout controls—and makes explicit that several of these new experiences are being gradually enabled for Insiders who opt in to “get the latest updates.” (blogs.windows.com)This release therefore isn’t a broad Windows update for all 24H2 users; it’s a focused preview aimed at testers, accessibility users, and early adopters on Copilot+ hardware. Independent coverage and community writeups confirm the practical details and the staged nature of the rollout. (computerworld.com, ntcompatible.com)
What’s new in Build 26120.5790 — quick summary
- Fluid dictation (Voice Access): Real-time grammar, punctuation, and filler-word removal using on-device small language models (SLMs), enabled by default on Copilot+ PCs in English locales and disabled in secure fields. (blogs.windows.com)
- Windows Studio Effects on additional cameras: Ability to route an alternate camera (for example, a USB webcam or a rear laptop camera) through the Studio Effects pipeline on supported Copilot+ machines; the Studio Effects driver update will roll out to Intel-powered Copilot+ PCs first, followed by AMD and Snapdragon devices. (blogs.windows.com)
- File Explorer Home hover actions: Hovering over items in File Explorer Home can now surface commands such as Open file location and Ask Copilot about this file, with the latter requiring sign-in to a Microsoft account for the initial rollout. (blogs.windows.com)
Deep dive: Fluid dictation — how it works and why it matters
What Microsoft shipped
Fluid dictation is an enhancement inside Voice Access that uses on-device small language models (SLMs) to process speech as it’s transcribed, applying grammar and punctuation corrections and removing filler words like “um,” “uh,” “you know,” or “like” automatically. The aim is to reduce the post-dictation editing burden and offer a smoother, near real-time dictation experience across most text fields while intentionally disabling the feature in secure entry fields (passwords, PINs). Microsoft documents the feature and notes that it’s enabled by default on Copilot+ PCs in English locales. (blogs.windows.com)Benefits for everyday users
- Faster composition: For email and note-taking, automatic punctuation and grammar cleanup reduces manual fixes and accelerates drafting.
- Accessibility gains: Users who rely on voice input (motor-impairment, repetitive-stress, etc.) gain a less error-prone dictation experience that better preserves the speaker’s intent.
- Privacy and latency advantages: Because the SLMs run locally, transcription and cleanup don’t require a cloud roundtrip—useful when network conditions are poor or where privacy rules discourage sending raw text to remote servers. (blogs.windows.com, computerworld.com)
Technical limits and verification
- Model tradeoffs: SLMs are smaller than cloud-scale models; they’re designed for speed and privacy rather than deep contextual understanding. Expect good punctuation and filler filtering, but occasional miscorrections or missed nuance compared with a cloud LLM. This is explicitly noted in Microsoft’s rollout messaging and corroborated by third-party coverage. (blogs.windows.com, ntcompatible.com)
- Locale coverage: Initially English-only in this flight; broader language support is not yet available. (blogs.windows.com)
- Security gating: The feature is disabled in secure fields to avoid accidental leakage of secrets—Microsoft emphasizes this behavior in official notes. (blogs.windows.com)
Practical testing checklist (for users and IT)
- Confirm the device is a Copilot+ PC and is running the Beta build (26120.5790).
- Enable Voice Access and verify the fluid dictation toggle in the Voice Access flyout.
- Test in several apps (note app, webmail, editor) and in offline mode to validate on-device processing.
- Verify that password fields and PIN entries remain immune to dictation.
- Report any inaccuracies or unexpected behavior through Feedback Hub to help model tuning. (blogs.windows.com)
Deep dive: Windows Studio Effects for alternate cameras
What changed
Windows Studio Effects—Microsoft’s OS-level camera processing pipeline that applies NPU-accelerated camera and microphone effects such as Background Blur, Eye Contact, Auto Framing, and Voice Focus—was previously tied tightly to integrated front-facing cameras on Copilot+ devices. Build 26120.5790 expands that pipeline so, on eligible Copilot+ machines, you can select a second camera (typically a connected USB webcam or a built-in rear sensor) and toggle Use Windows Studio Effects for that camera via Settings > Bluetooth & devices > Cameras > Advanced camera options. (blogs.windows.com)Why this matters in practice
- Creators and remote workers who prefer higher-quality external webcams finally get the same OS-integrated effects that used to be limited to the built-in front camera.
- Because Studio Effects is an OS-level pipeline, any app that consumes the camera stream receives the processed feed—so effects are consistent across Teams, Zoom, OBS, and browser-based apps without per-app plugins or virtual-camera drivers. (windowsforum.com, ntcompatible.com)
Hardware and driver gating — Intel first, then AMD and Snapdragon
Microsoft explicitly states the Studio Effects driver update enabling additional camera routing will roll out first to Intel‑powered Copilot+ PCs, with AMD and Qualcomm (Snapdragon/Arm) systems following in the coming weeks. This staged driver rollout is a deliberate risk‑management move: different SoCs and NPUs require distinct driver/adaptor work and OEM coordination. The Intel-first sequence is documented in the official build notes. (blogs.windows.com)Historically there have been times when Arm/Qualcomm devices received early previews of AI features; the Intel‑first timing here is a delivery choice tied to driver readiness rather than any permanent platform policy. That historical pattern is noted in coverage of Copilot+ PC launches and device availability. (theverge.com, windowscentral.com)
Compatibility and gotchas
- NPU required: The feature depends on an NPU supported by the OEM’s Studio Effects driver. Not every USB webcam will be supported immediately. (blogs.windows.com)
- Driver rollout timing: If you don’t see the toggle, you may need an OEM driver update that will be staged by Microsoft and your laptop manufacturer. Expect a phased arrival across vendors. (blogs.windows.com)
- Performance and thermals: Running continuous NPU inference for camera effects can influence battery and thermals on laptops—real‑world testing is recommended before enabling during long calls. Independent reporting suggests administrators and power users measure impact for their hardware profiles. (ntcompatible.com, windowsforum.com)
The File Explorer change that might annoy people: Ask Copilot on hover
What’s new, exactly
File Explorer Home now surfaces on-hover quick actions for items—Open file location and Ask Copilot about this file among them. The Copilot action lets you surface a file into Copilot for summarization, question-and-answer, or other AI-driven interactions; Microsoft requires a Microsoft account sign-in for the initial rollout, with work/school (Entra ID) support planned later. The feature is not yet enabled for Insiders in the EEA in this flight. (blogs.windows.com)Why some users will object
- Perceived clutter: Adding a Copilot action to every hover menu in File Explorer Home increases the visible command density in a UI area many users already see frequently—some will view this as unnecessary bloat rather than a productivity aid. Early community responses highlight the annoyance factor when commonly used file surfaces change subtly.
- Implicit data flow concerns: While the Copilot action is a convenience, it also introduces another path where document content is handed to Copilot for processing. Even when processing is local or hybrid, enterprises must consider data governance, DLP policies, and user consent. Microsoft’s rollout notes ask testers to sign in with a Microsoft account and make clear that enterprise support and entitlements are still being worked on. (blogs.windows.com)
Practical advice
- Individuals who hate extra UI chrome can disable or hide the Home view and use Classic folder navigation or rely on keyboard commands; organizations may choose to delay opt‑in until admin controls for Copilot file actions are published.
- IT teams should validate Copilot file flows against corporate DLP and compliance policy, and pilot the feature on a small set of machines first before any broad enablement. (windowsforum.com)
Privacy, security, and enterprise governance — what to watch
Microsoft’s messaging emphasizes on-device processing where applicable (fluid dictation uses on‑device SLMs; Studio Effects uses the device NPU). That reduces cloud exposure, but it does not eliminate governance questions:- Local vs cloud processing: On-device SLMs and Studio Effects reduce the need to send raw content to cloud endpoints, but certain Copilot actions (especially those that operate across Microsoft 365 or require summarization tied to cloud services) may still leverage cloud systems or tenant-scoped processing. Admins must confirm processing location and audit trails for each Copilot-enabled action. (blogs.windows.com, windowsforum.com)
- Consent and account requirements: The Ask Copilot action currently requires a personal Microsoft account in the initial build. That requirement shifts how organizations must think about sign-in and entitlement—enterprise-grade behavior and Entra support are on the roadmap but not yet fully present. (blogs.windows.com)
- Driver security and supply chain: Studio Effects depends on vendor-supplied drivers. Enterprises and advanced users should source drivers from OEMs and validate driver signatures and update paths to avoid untrusted or tampered drivers. The staged rollout model helps minimize broad exposure while vendors finalize drivers. (blogs.windows.com)
Known stability issues and why you should test first
Microsoft lists active known issues for this flight that meaningfully affect adoption decisions:- Hibernation bugchecks: Some PCs may experience bugchecks (green screens) when attempting to hibernate after the previous flight. Microsoft advises avoiding hibernation on affected PCs until patched. (blogs.windows.com)
- Audio driver problems: Affected Insiders have reported audio stopping and Device Manager flagging “ACPI Audio Compositor” with a yellow exclamation, requiring manual driver selection to recover. (blogs.windows.com)
- Xbox controller Bluetooth bug: Some Bluetooth Xbox controller usage can cause bugchecks; a manual uninstall of a specific driver entry is provided as a workaround. (blogs.windows.com)
Actionable recommendations — for everyday users, creators, and IT managers
For everyday Copilot+ PC users
- Back up important files and test the Beta build on a spare machine rather than your daily driver.
- Try fluid dictation in typical apps (email, notes) and toggle it off if corrections cause more work than they save.
- If you rely on an external webcam, check Settings > Bluetooth & devices > Cameras > Advanced camera options to see if the Studio Effects toggle has arrived; if not, wait for your OEM’s driver update. (blogs.windows.com)
For creators and streamers
- Validate Studio Effects with your preferred streaming and conferencing apps to ensure the processed stream works with OBS, Teams, Zoom, and browser-based tools.
- Monitor CPU/NPU utilization and battery/thermal effects during long recording or streaming sessions. If performance is unacceptable, disable Studio Effects or revert to app-level filters. (ntcompatible.com)
For IT and security teams
- Pilot on a representative subset of Copilot+ hardware and test camera, dictation, and Copilot file flows against your DLP and compliance rules.
- Confirm driver update channels from OEM partners and an enterprise plan for staged rollout.
- Verify whether Copilot file handling is allowed for sensitive data; block or restrict usage until auditability and data residency assurances are in place.
- Keep recovery/reimage plans ready for preview builds and advise users to avoid hibernation on affected machines until Microsoft resolves the bug. (blogs.windows.com, windowsforum.com)
Strengths, risks, and the strategic view
Notable strengths
- Practical feature set: Fluid dictation and broader Studio Effects address two concrete user pain points—cleaner dictation and parity for external webcams—rather than being purely experimental demos. (blogs.windows.com)
- Local-first AI approach: On-device SLMs and NPU-accelerated Studio Effects demonstrate a clear strategy to deliver low-latency, privacy-optimized AI at the OS level. This reduces dependence on cloud roundtrips for latency-sensitive tasks. (blogs.windows.com)
Key risks and limitations
- Hardware and driver fragmentation: Because features are gated to Copilot+ hardware and depend on vendor drivers, availability will be inconsistent across device fleets for the near term. The staged driver rollout (Intel first, then AMD and Snapdragon) makes adoption planning essential. (blogs.windows.com)
- UI clutter and discoverability tradeoffs: Small UX changes—like adding Ask Copilot to File Explorer hover—can increase cognitive load or annoy power users who prefer a minimalist shell. Early feedback suggests this is a live UX debate.
- Preview stability: The flight contains active regressions that can lead to lost productivity (hibernation bugchecks, audio regressions). For production environments, prudence is strongly advised until follow-up fixes arrive. (blogs.windows.com)
Conclusion
Build 26120.5790 is a focused, practical preview: fluid dictation brings cleaner on-device voice input to Copilot+ PCs, Windows Studio Effects finally moves beyond the built-in camera to support alternate cameras (provided your device meets NPU and driver prerequisites), and File Explorer’s Copilot hover action nudges AI into a very visible place—useful for some, clutter for others. Microsoft’s official release notes confirm the build details and the staged rollout strategy, while independent reporting underscores the hardware and driver caveats that will shape real-world availability. (blogs.windows.com, computerworld.com)For enthusiasts and creators willing to test on spare hardware, the changes are meaningful and worth exploring now. For organizations and users who need rock-solid stability and strict data governance, the prudent path is staged testing, governance review, and waiting for subsequent fixes and enterprise-grade rollout signals from Microsoft and OEM partners. (windowsforum.com)
Source: TechRadar I'm jealous of a couple of nifty new AI powers coming to Windows 11 with Copilot+ PCs – but there's also a change I'm not so keen on