{
"title": "Microsoft Ships Insider Builds 26220 and 26120 with On-Device Fluid Dictation and Expanded Camera Effects",
"content": "Microsoft’s latest Insider flight isn’t just a routine update—it’s a deliberate push to embed AI into the fabric of Windows. Builds 26220.5790 (Dev Channel) and 26120.5790 (Beta Channel) deliver fluid dictation that corrects your speech in real time, extend cinematic camera effects to plug-in webcams, and weave Copilot into File Explorer. Yet beneath the gloss lie critical bugs that can crash your machine during hibernation or silence your speakers. Here’s everything you need to know before hitting ‘Update.’

Background: two channels, one set of features

These matching builds follow Microsoft’s pattern of delivering nearly identical cumulative updates to different Insider rings. The Dev Channel stays on the 26200 series (the 25H2 development track), while the Beta Channel remains on 26120 (the 24H2 maintenance track). They aren’t massive feature drops; instead, they represent targeted enhancements that Microsoft wants to validate before wider release. As always, features roll out gradually via feature toggles and telemetry, so not every Insider sees everything on day one.

Fluid Dictation: on-device AI cleans up your voice

The marquee addition is Fluid Dictation inside Voice Access for Copilot+ PCs. It taps an on-device small language model (SLM) to insert punctuation, strip filler words, and apply basic grammar corrections as you speak. The result: you can dictate an email or document without having to manually edit out every “um” or “you know.” Microsoft has enabled fluid dictation by default for all English locales on Copilot+ hardware; you can turn it off via the Voice Access flyout or voice command.

Because the SLM runs locally, voice data never leaves the device. That’s a significant privacy advantage over cloud-based transcription, especially for enterprise or regulated environments. On the flip side, on-device models are smaller and less context-aware than something like GPT-4, so the grammar fixes remain basic. For most dictation users, however, the improvement is dramatic and immediate.

Microsoft has not disclosed the exact SLM architecture, but it’s likely a transformer model distilled for on-device inference. The dictation pipeline first converts speech to text using traditional speech recognition, then the SLM post-processes that text in nearly real time. Because everything runs on the NPU and CPU, there’s no noticeable delay, and CPU usage is minimal. That’s a stark contrast to the latency you’d experience with cloud-based grammar checks.

Early adopter reports on forums indicate that the feature works smoothly on Snapdragon X Elite devices, but users note that the model sometimes over-corrects, inserting commas where none are needed. Microsoft says it will take feedback and tune the SLM over time.

Windows Studio Effects breaks free of built-in cameras

Windows Studio Effects—the AI-powered camera suite that handles background blur, eye contact, automatic framing, and creative filters—is no longer tethered to your laptop’s integrated sensor. Starting with these builds, any connected camera on a supported Copilot+ PC can be routed through the Studio Effects chain. That includes USB webcams, rear-facing cameras on tablets, and even some external capture cards.

To enable it: navigate to Settings > Bluetooth & devices > Cameras, pick your camera, and toggle “Use Windows Studio Effects” under Advanced camera options. Once active, apps see a “composite” camera device that carries the effects. The system chains the Studio Effects driver onto the camera stack, overriding any overlapping OEM driver properties (like KS properties for blur) to ensure consistent behavior. The result is a unified experience across Teams, Zoom, OBS, and any other app that uses standard camera APIs.

Unfortunately, the driver rollout is phased. Intel-based Copilot+ PCs get it first; AMD and Snapdragon machines will follow “in the coming weeks.” That staggered approach could frustrate AMD users who were promised parity. Performance impact is minimal on newer hardware, but on less capable NPUs you may notice a slight thermal or latency increase during video calls. For now, if you rely on an external Logitech Brio or similar pro webcam, this change could finally banish the app-by-app setting dance.

File Explorer: hover actions and Copilot integration

File Explorer’s Home view now shows a pop-up with quick actions when you hover over a file. The two buttons—Open file location and Ask Copilot about this file—aim to speed up common tasks. The Copilot integration ties the AI directly to the file’s context; select a PDF and ask Copilot to summarize it, for instance. That’s a powerful step toward an AI-infused file manager, but it comes with heavy asterisks.

Currently, the Copilot button only appears if you’re signed in with a Microsoft Account. Entra ID (work/school) accounts are not yet supported, and the feature isn’t rolling out in the European Economic Area. Microsoft says both limitations are temporary, but no timeline is given. For everyday users with a personal MSA, it’s a handy addition—assuming you trust Copilot with your file contents. Enterprise admins should treat this as a preview and audit what happens when a user clicks it. Does the file content get sent to Microsoft’s cloud? Official documentation is sparse, so conservative IT shops will want to block or delay this until data governance becomes clear.

The Copilot integration here is similar to the “Ask Copilot” button that appears in Edge and other Office apps, but tied to local file context. When you click it, a side panel opens with Copilot preloaded with the file’s name and possibly metadata. Microsoft hasn’t detailed whether the file content is sent to the cloud; for now, it’s safe to assume it may be, given Copilot’s reliance on Microsoft’s AI services. That makes it unsuitable for sensitive documents until we get clear data flow documentation.

Minor tweaks: Settings roulette and