Microsoft shipped Windows 11 Insider Preview Build 26120.5790 (KB5065779) to the Beta Channel on September 5, 2025, packing what could be the most significant accessibility leap in recent Insider history: Fluid dictation that uses on-device small language models (SLMs) to clean up speech in real time. The same build expands NPU-powered Windows Studio Effects to more cameras, adds context-sensitive hover actions in File Explorer, and squashes a handful of nagging regressions — yet it also warns of green-screen hibernation crashes, persistent audio driver failures, and Bluetooth controller bugchecks that should give any tester pause.
For Copilot+ PCs already on version 24H2, this cumulative-style update underscores Microsoft's determination to weave AI deeper into the OS without phoning home to the cloud. But the new capabilities come wrapped in the usual Beta Channel caveats: tiered hardware support, staggered driver rollouts, and a list of known issues long enough to remind IT pros that this is far from production-ready.
The headliner is Fluid dictation inside Voice Access. Previously, dictation on Windows was a blunt instrument: you spoke, the OS transcribed, and you manually tidied up grammar, punctuation, and verbal tics. Fluid dictation now harnesses local SLMs to insert punctuation on the fly, correct grammar, and strip out filler words like "um" and "you know." Microsoft deliberately disables the feature in PIN and password fields — a sensible privacy guardrail. Because the processing stays on the NPU, latency drops and sensitive audio never leaves the device. Insiders can toggle Fluid dictation via the Voice Access flyout or by saying "turn on fluid dictation." For anyone who relies on speech input for long-form writing, coding, or accessibility, that alone is a reason to spin up a test machine.
Equally noteworthy is the expansion of Windows Studio Effects. These AI camera enhancements — background blur, eye contact correction, automatic framing — previously worked only with the primary integrated camera on select Copilot+ devices. Build 26120.5790 opens them up to an additional camera, letting users apply Studio Effects to an external USB webcam or a rear laptop camera through Settings > Bluetooth & devices > Cameras. The catch? It needs an NPU and a driver that explicitly opts the camera into the effects pipeline. Microsoft is staging the driver release: Intel-powered Copilot+ PCs get it first, while AMD and Qualcomm platforms will follow "in the coming weeks." Because Studio Effects operate at the composite camera device level, any app that accesses the camera automatically inherits the effects. That global nature is both a time-saver and a potential headache for users running third-party camera software that could conflict.
File Explorer picks up a small but useful tweak: when you hover over a file on the Home page, contextual commands like "Open file location" and "Ask Copilot about this file" slide into view. The feature requires a Microsoft account sign-in (work and school account support is planned later) and remains unavailable to Insiders in the European Economic Area. It is a clear signal that Copilot is being stitched into everyday file management, one hover at a time.
Other changes include an Agent in Settings experience rolling out to French-language Insiders and a temporary reversion of Advanced Settings back to the legacy "For Developers" layout. The new design will return in a future flight.
On the fix front, this build tackles several regressions that had testers gritting their teeth. Microsoft says it mitigated performance delays of roughly 500 milliseconds that blunted clicks in File Explorer, the taskbar, and browser windows. A jarring context-menu oscillation — where right-clicking would bounce between the modern menu and "Show more options" — has been resolved in certain conditions. Taskbar preview alignment after display resolution changes is no longer broken. The Settings > System > Storage > Temporary files scanning hang is fixed. And a post-boot Event Viewer error 57 tied to "Microsoft Pluton Cryptographic Provider" initialization has been corrected.
Yet the known issues list reads like a roll call of leftover trouble. A newly surfaced hibernation bug can green-screen some PCs or make them appear to shut down completely; Microsoft's advice is blunt — avoid hibernation on affected machines until a patch arrives. Audio problems that started in earlier Dev and Beta builds persist: devices like "ACPI Audio Compositor" show yellow exclamation marks in Device Manager and sound stops working. The workaround is to manually pick a driver from the list already on the machine. Using an Xbox controller over Bluetooth can trigger bugchecks; uninstalling the problematic driver instance (the oemXXX.inf entry for XboxGameControllerDriver in Device Manager) is the interim fix. Developers relying on PIX for Windows cannot play back GPU captures on this OS version, and while Microsoft estimates a PIX update by the end of September, that timeline may slip. Finally, some Insiders may see an empty Shared section in File Explorer Home.
These issues reinforce the Beta Channel's identity as a proving ground. No one should install Build 26120.5790 on a daily-driver PC without a full backup and a recovery plan.
Stepping back, the flight clarifies Microsoft's AI-on-the-edge strategy. Fluid dictation and Studio Effects lean hard on the NPU, keeping data local and latency low. That privacy-by-design approach is a genuine differentiator from cloud-only assistants. But it also exposes the hardware divide. Not every Copilot+ PC packs an NPU that meets the spec; not every vendor has shipped the necessary camera or audio drivers. Expect a staggered feature rollout that mirrors the silicon landscape: Intel first, then the rest. And where NPU support is absent, these features simply won't light up.
Privacy and security implications run deeper than the headlines. On-device SLMs mean that what you say never leaves your chip, yet the global camera-effects paradigm means turning on Studio Effects blankets every app — Teams, Zoom, OBS, your browser — with the same processing. Overlap with third-party effects can produce muddy, unpredictable results. The Pluton Cryptographic Provider fix should reassure enterprise security teams, but they still need to monitor logs to confirm cryptographic subsystems initialize correctly after the update. And the crash triggers — hibernation and Xbox Bluetooth — are real reliability concerns for shops that use those features in production-like test environments.
For Insiders willing to test this build, a methodical approach is the only sensible path. Inventory your hardware: determine which machines are Copilot+ PCs with the required NPU, and if you want to try Studio Effects now, prioritize Intel-based devices. Enable the "get the latest updates" toggle only on sacrificial test units. Before installing, create restore points or full disk images, and document driver versions and OEM software. Then methodically walk through the priority scenarios: long-form dictation across multiple apps, enabling Studio Effects on both internal and external cameras and verifying behavior in collaboration tools, sleep/resume and hibernate transitions (skipping machines that show the hibernation bug), and peripheral workflows involving Xbox controllers and audio gear. When audio falls silent, the quick fix is Device Manager's "Let me pick from a list" option. For Bluetooth controller crashes, nuke the oem driver entry. And if Studio Effects behave unexpectedly, roll back the NPU driver while waiting for an update from your silicon vendor.
Enterprise fleet managers should treat this build as what it is: a preview, not a pilot. Maintain compatibility matrices that track NPU and driver support from OEMs, and coordinate with silicon vendors so you know when their Studio Effects drivers land. Review organizational privacy policies: although dictation stays local, other apps might store audio or text, and the global nature of camera effects needs to be clearly communicated to pilot users. Any Copilot+ features that touch security boundaries — Recall, for example — should be explicitly configured to match compliance requirements.
The bottom line? Build 26120.5790 is the kind of Insider release that rewards curiosity and punishes carelessness. Fluid dictation is a tangible step toward assistive AI that feels fast and private, and broader Studio Effects support finally makes high-quality video tweaks available with better camera options. But the hibernation and audio gremlins, the driver fragmentation, and the developer-tool breakage are serious enough that the build belongs in a tightly controlled sandbox. For Insiders and IT teams who approach it with eyes open, it offers a compelling preview of a Windows that processes speech and video locally — on your terms, and on your silicon.