Microsoft dropped Windows 11 Insider Preview Build 26120.6682 (KB5065782) into the Beta Channel on September 12, 2025, equipping Copilot+ PCs with an on-device prompt box inside the Click to Do experience while wrapping up a raft of reliability fixes that range from a stubborn hibernation bugcheck to audio glitches in OBS Studio. The flight, available for PCs running Windows 11 version 24H2, continues Microsoft’s practice of gating marquee features behind server-side toggles even as it pushes quality-of-life improvements broadly to Insiders who flip the “get the latest updates” switch.

For IT pros and enthusiasts running test labs, this build is a mixed bag: a handful of genuinely useful Copilot refinements, long-awaited accessibility polish for Narrator, and fixes that patch daily annoyances — but also a fresh crop of known issues that demand a careful pre-flight checklist. Here’s everything you need to know.

What’s new: Copilot takes a step deeper into the shell

The headliner in 26120.6682 is a new Copilot prompt box that appears inside Click to Do on Copilot+ PCs. When you capture on-screen content, you can now type a short natural-language instruction that gets sent to Copilot alongside the selected text or image. Suggested prompts appear beneath the box, powered by the on-device Phi Silica model; Microsoft says the feature supports English, Spanish, and French text suggestions but is not rolling out in the European Economic Area or China for now.

Community observers note that this on-device suggestion capability, while modest, reflects Redmond’s broader ambition to blend local AI computation with cloud Copilot services. The prompt box doesn’t replace the existing Copilot pane — it’s an additional interaction model designed to make AI assistance feel more contextually immediate. Insiders who have tried early iterations report that Phi Silica’s suggestions are fast and surprisingly relevant, though the feature is clearly in its infancy.

Complementing this change is an experiment in the Start menu’s Recommended section: some Insiders will see example prompts like “create an image with Copilot” peppered among recently used files and apps. The move is a quiet nudge to make Copilot discoverable for users who might not otherwise launch the assistant. For power users, the experiment may feel like visual clutter, but Microsoft has a history of using such subtle surface-level prompts to drive feature adoption — think of the early days of Cortana or widgets.

Emoji enthusiasts get a boost too. Build 26120.6682 introduces the Emoji 16.0 set to the Windows emoji panel, adding expressive newcomers like Face with Bags Under Eyes, Fingerprint, Root Vegetable, Leafless Tree, Harp, Shovel, and Splatter. The update is cross-cultural and compact, aligning Windows with the latest Unicode standard and keeping the emoji picker feeling fresh.

Xbox controller behavior gets a tweak that might confuse muscle memory for a few days: a short press of the Xbox button still fires up Game Bar, but a long press now opens Task View, while press-and-hold power-off behavior remains unchanged. Microsoft says the change unifies controller interactions with the Windows shell, making it easier to switch between apps without reaching for a keyboard. In testing, the long-press timing feels slightly more deliberate than the old Xbox button action, which could sometimes trigger accidentally.

For users who rely on screen readers, the Narrator improvements in this build are a quiet but significant win. Microsoft has refined footnote navigation, improved continuous reading flow, made list and table navigation commands clearer, and enhanced selection announcements. The result is a more natural reading experience in documents and web pages, which enterprise accessibility leads will welcome.

Bug squashing: hibernation, File Explorer, and Sandbox

Beyond the user-facing feature work, 26120.6682 addresses several reliability headaches that have dogged recent Insider builds. A hibernation bug that could cause a green-screen crash (bugcheck) is finally fixed. Users previously reported that their machines would appear to hang during shutdown or restart after emerging from hibernation; that issue is now resolved.

Taskbar and system tray reliability sees attention, with improvements to auto-hide behavior and a fix for hit-test problems that could prevent clicks from registering above the taskbar. Animations are said to be smoother, though the visual delta is likely only noticeable to those who scrutinize frame rates.

File Explorer gets a suite of polish items: empty Shared sections no longer appear in Home, video thumbnails now generate correctly for files with certain EXIF metadata, context menus are more responsive, and a hang that could occur when launching Open/Save dialogs has been addressed. Content creators and power users who live in File Explorer daily will notice the difference immediately.

Windows Sandbox — a critical tool for developers and QA testers — receives a targeted fix for high CPU usage by the vmmemCmFirstBoot process after login. In previous builds, launching Sandbox could peg a single core at 100% for minutes, making the environment sluggish and impacting host machine performance. The fix returns Sandbox to its lightweight, disposable roots.

Audio and streaming users benefit from a fix for NDI/display-capture audio stuttering in OBS Studio when Display Capture is active. The patch is rolling out broadly in the Beta Channel, suggesting Microsoft considers it high priority. For streamers who rely on OBS for broadcasting Windows content, this is a welcome squashing of a long-standing annoyance.

Known issues: the watch list before you upgrade

No Insider build ships without a proviso, and 26120.6682 is no exception. Microsoft explicitly calls out several new and continuing problems:

  • Click to Do’s right-edge gesture visuals may appear on the wrong display in multi-monitor setups.
  • Lock screen media controls might vanish intermittently.
  • Windows Studio Effects can cause camera preview failures on some external webcams — turn them off in Camera settings to work around this.
  • Audio device driver exclamation marks appear in Device Manager for certain hardware (including the ACPI Audio Compositor); Microsoft’s workaround involves manually updating the driver and selecting from a list of available drivers.
  • PIX on Windows GPU capture playback is currently incompatible with this OS version; a fix is promised by late September.
  • Xbox Bluetooth controllers can trigger bugchecks on certain systems; Microsoft’s recommended workaround is to uninstall the “oemXXX.inf (XboxGameControllerDriver.inf)” entry from Device Manager via the “Devices by driver” view.

Community beta testers advise that anyone deploying this build on test hardware should read the known-issues list twice before committing, especially if the machine hosts critical audio or camera workflows.

The servicing strategy: checkpoint updates and controlled rollouts

Build 26120.6682 is part of the 26120 series servicing stream for Windows 11, version 24H2. Under the hood, Microsoft uses checkpoint cumulative updates to shrink download sizes and improve update sequencing, but it pairs that engineering efficiency with controlled feature rollouts (CFR). In practice, that means the binaries for new features are shipped to all Insiders, but only a subset sees them turned on — the rest wait until server-side flags activate the experience after telemetry analysis.

For IT administrators, this model requires careful planning. Features that arrive via servicing might remain off by default on managed enterprise devices until the next annual feature update or until a policy explicitly enables them. Microsoft’s commercial control documentation details how to manage this gating, but the key takeaway is that Beta builds like this one are previews — not production-ready deployments. Enterprise test rings should treat them as validation fodder, not something to push to critical endpoints.

Actionable advice: install, test, and recover

For Insiders ready to dive in, the installation path is straightforward: Settings → Windows Update → toggle “Get the latest updates as soon as they’re available” (if you want to be in the earliest rollout group) and check for updates. But before hitting install, follow this community-vetted prep list:

  • Snapshot or image your machine. A VM snapshot or a full disk backup is the fastest rollback path if things go south.
  • Document hardware and driver versions for audio, camera, and controller devices. Keep vendor drivers handy in case the update fouls the driver stack.
  • Review the known issues above and decide if any would derail your testing goals.

If trouble strikes, Microsoft provides these immediate recovery steps:

  • Audio exclamation marks: Right-click the device in Device Manager, choose Update driver → Browse my computer → Let me pick from a list → pick the most recent dated driver. Repeat for each flagged device.
  • Xbox controller bugchecks: Open Device Manager, switch to View → Devices by driver, locate the XboxGameControllerDriver.inf entry, and uninstall it.
  • Camera preview fails with Studio Effects: Turn off Windows Studio Effects in Camera settings.
  • System won’t boot: Use your snapshot or image to restore. On physical devices, you can try Advanced Startup (Settings > Recovery) to uninstall the latest update.

Microsoft asks Insiders to file guided feedback via Feedback Hub (WIN+F) for any new issues, attaching repro steps and diagnostic logs.

Looking ahead: Iteration over revolution

Build 26120.6682 is not a major milestone; it’s a targeted maintenance-and-experience flight that refines Copilot’s shell integration, strengthens accessibility, and mops up several irritating bugs. The pattern will continue: more incremental builds in the 26120 line for Beta, parallel flights in Dev/25H2 channels as Microsoft finalizes features toward broader release.

The Click to Do prompt box is a glimpse of how AI will weave deeper into the operating system, but it’s clearly a work in progress. Expect Microsoft to iterate on the suggestion engine, expand language support, and eventually sync these on-device prompts with cloud-side Copilot capabilities. Meanwhile, fixes like the hibernation bugcheck and File Explorer hang are the kind of under-the-hood polish that makes Insider builds feel progressively more solid — even if they don’t generate headlines.

For IT decision-makers, the message is unchanged: validate these builds in ringed deployment groups, document regressions, and keep an eye on the Windows Insider blog for the next flight. Copilot isn’t slowing down, and neither are the cumulative updates.