Microsoft has released Windows 11 Builds
26100.7296 and
26200.7296 (packaged as KB 5070311) to Insiders in the Release Preview Channel, bringing a mix of Copilot+ PC–specific AI features, wide-ranging polish across File Explorer and Settings, and a non-security stability fix for the Local Security Authority Subsystem Service (LSASS).
Background / Overview
This Release Preview update targets both supported tracks of Windows 11:
version 24H2 (Build 26100) and
version 25H2 (Build 26200). The Windows Insider announcement describes two delivery patterns: a
gradual rollout for features that Microsoft is enabling selectively across devices, and a
normal rollout that delivers quality and stability improvements to the broader Release Preview population.
The build notes emphasize Copilot+ PC exclusives — notably expanded capability for
Windows Studio Effects to work with secondary cameras — alongside system-wide UX and reliability refinements such as a more consistent
dark mode in File Explorer, new Settings layout elements, Taskbar animation tweaks, widget dashboard controls, and an important fix to address an LSASS crash condition. Several changes are explicitly labeled as
gradually rolling out and may not appear immediately or across all markets (the update notes also call out availability restrictions for some features in the European Economic Area).
This article summarizes what’s new, verifies key technical requirements where possible, and provides analysis for enthusiasts and IT pros about adoption, compatibility, and potential risks.
What’s new at a glance
- Copilot+ PC camera improvements: Windows Studio Effects can now be applied to alternate cameras (e.g., USB webcams or rear laptop cameras) on supported Copilot+ devices.
- Click to Do: redesigned context menu and automatic context invocation for large images/tables on Copilot+ PCs.
- Agent-driven Settings: improved search results, inline recommended controls, and clarity dialogs on Copilot+ PCs.
- File Explorer: consistent dark mode across dialogs, refreshed progress and confirmation UI, consolidation of share options (limited preview), and several bug fixes (thumbnails, old white toolbar, generic open icon).
- Drag Tray (Nearby sharing): multi-file sharing, more relevant app suggestions, and toggle control in Settings.
- Settings: migration of some keyboard controls from Control Panel into Settings; a new Device Card on the Settings home page (U.S. only, Microsoft account required); updated About layout.
- Windows Hello ESS: peripheral fingerprint sensor support for Enhanced Sign-in Security.
- Widgets: default dashboard selection and alert-count badges for dashboard icons.
- OneDrive & UI polish: new OneDrive icon in Accounts/Homepages, haptic feedback for compatible pens, display and graphics performance improvements, Quick Machine Recovery behavior adjustments, and Virtual Workspaces control in Advanced Settings.
- Normal rollout: a non-security fix addressing an LSASS instability caused by an access violation.
Copilot+ PC features: Windows Studio Effects on alternate cameras
What changed
Copilot+ PCs gain the ability to run
Windows Studio Effects (AI-powered camera and audio enhancements) on an
additional camera, such as an external USB webcam or a laptop’s rear camera. Previously, Studio Effects were generally restricted to the primary, built‑in front-facing camera on many devices.
How to enable
- Open Settings > Bluetooth & devices > Cameras.
- Select the secondary camera from the connected cameras list.
- Open Advanced camera options and toggle Use Windows Studio Effects.
- Adjust effects from the camera settings or via the Studio Effects quick-setting in the taskbar.
Verified requirements and caveats
- Studio Effects require a device with an appropriate Neural Processing Unit (NPU) and the vendor driver for Studio Effects. Microsoft’s published product documentation specifies device prerequisites and indicates that available effects vary by NPU capability.
- Some advanced effects (for example, creative filters and teleprompter eye-contact) are gated behind stronger NPU performance and OEM opt-in; lower-capability NPUs support a subset of effects like background blur and basic eye contact.
- Microsoft’s release notes and product pages indicate phased rollouts — the driver and feature may appear first on certain OEM platforms (for example, Intel‑powered Copilot+ PCs) with AMD and Snapdragon variants following in subsequent weeks.
Practical impact
This change is meaningful for users who run docks, external monitors, or high-quality USB webcams. It reduces a long-standing scenario where Studio Effects could only influence the built-in camera, forcing users who prefer an external webcam to miss out on on-device AI enhancements. Expect improved video-call presentation for hybrid workers and creators using Copilot+ hardware. However, users should watch for battery and CPU/NPU usage, as some effects consume significant power and on-device compute.
Click to Do and Agents in Settings
Click to Do
- The Click to Do context menu on Copilot+ PCs receives a streamlined design focusing on frequently used actions: Copy, Save, Share, Open.
- The context menu can auto-open whenever a large image or table appears, speeding access to relevant actions and results.
Agents in Settings
- Settings’ agent-driven search now shows more results with a scroll bar and offers inline recommended settings for recently changed options.
- When settings can’t be adjusted further, a dialog explains why and directs users to make required changes.
These features reflect Microsoft’s push to integrate lightweight Copilot/assistant interfaces into OS surfaces. They are currently confined to Copilot+ PC test groups during gradual rollout.
File Explorer: dark mode polish and contextual sharing consolidation
Visual and UX changes
- File Explorer dialogs (copy, move, delete) and progress visuals have been updated to match dark mode across both default and expanded views.
- Confirmation dialogs and several error dialogs have had UI refreshes for visual consistency.
- Microsoft is experimenting with a consolidated share entry in the context menu; initially this will surface to a limited set of devices for evaluation.
Bug fixes
- Thumbnails failing to render for videos with certain EXIF metadata have been addressed.
- An old white toolbar that could appear randomly has been fixed.
- The Open entry’s icon sometimes appearing generic instead of the default app icon has been corrected.
Why this matters
These are usability-focused improvements that reduce visual friction and inconsistency, especially for users who rely on dark mode. Consolidating share options into one menu entry could reduce clutter, but it also risks hiding previously obvious share targets behind an extra click — Microsoft’s limited roll-out suggests they are evaluating trade-offs.
Drag Tray and Nearby sharing updates
Drag Tray — a Nearby sharing surface for moving and sharing files — now supports:
- Multi-file sharing
- Better selection of relevant apps and folders
- A toggle to enable/disable Drag Tray under Settings > System > Nearby sharing
Availability is gradual and varies by device and market. Administrators should note the KB guidance that Drag Tray availability can differ and to refer to the specific KB referenced by Microsoft for deeper configuration options.
Settings, Device Card, and accessibility changes
- Keyboard settings (character repeat delay/rate) and cursor blink rate have been migrated from Control Panel to Settings under Accessibility, consolidating legacy controls into modern Settings.
- A Device Card showing key specifications and usage details will appear on the Settings home page when signed in with a Microsoft account, initially available in the U.S. only.
- About in Settings receives an updated layout to group device details and direct links to storage and other related settings.
This migration continues the long-running effort to retire Control Panel relics and centralize configuration inside Settings — good for discoverability, but enterprise admins should catalog where legacy policies map to the new UI.
Security and stability: LSASS fix and Quick Machine Recovery change
LSASS fix
The normal rollout notes an important stability fix: this update addresses an issue where
LSASS (Local Security Authority Subsystem Service) could become unstable due to an access violation. LSASS instability can manifest as sign-in failures, unexpected restarts, or system instability. Applying this update is recommended for Release Preview devices experiencing related symptoms.
Quick Machine Recovery
On devices with both
Quick Machine Recovery (QMR) and “automatically check for solutions” enabled, QMR now runs a one-time scan by default rather than looping. This change prevents repeated loops that could consume resources and confuse users; if no immediate repair is found, QMR will now quickly point users to appropriate recovery options.
Other notable improvements and fixes
- Windows Hello: Enhanced Sign-in Security now supports peripheral fingerprint readers — useful for devices that use external biometrics for secure, fast login.
- Widgets: You can set a default dashboard and widgets now surface numeric alert badges for dashboards.
- OneDrive: A refreshed OneDrive icon appears in Accounts and Homepages in Settings.
- Input: Pens that support haptics now produce tactile feedback on certain UI interactions (for example, when resizing windows or hovering over close buttons).
- Display & Graphics: Improved monitor mode query performance to reduce stutter on very high-resolution setups; brightness slider and false “unsupported graphics card” game messages have been fixed in certain scenarios.
- Smart cards: Resolved a logon error (STATUS_NOT_SUPPORTED 0xc00000bb) that could affect ECC Smart Card logons.
- Advanced Settings: Virtual Workspaces can now be toggled, giving a single control over virtual environments such as Hyper‑V and Windows Sandbox — this feature is being rolled out gradually and may vary by market.
Rollout behavior, availability, and regulatory notes
- Several features are part of a gradual rollout, meaning they may not be visible immediately to all Release Preview devices. This staged approach allows Microsoft to monitor telemetry and user feedback before broad availability.
- Some Copilot+ PC functionality and OneDrive sharing options depend on being signed into a Microsoft account and may have market-specific availability. The release notes explicitly call out limited availability in the European Economic Area for certain features.
- The Windows Insider blog post names KB 5070311 as the packaging number for these builds. At the time of publication, the Windows Insider announcement is the authoritative note for these builds. If you are planning deployments or testing, check Windows Update and Microsoft’s official update history pages for the KB’s Support entry and file lists, because some KB pages appear after the Insider blog post.
If you do not see KB 5070311 in the Microsoft Support knowledge base immediately, this can be normal for preview-channel updates; Microsoft sometimes posts the blog first and the Support article and file information shortly after.
Verification and technical details (what was checked)
- Device and hardware requirements for Windows Studio Effects (NPU requirement and effect availability per NPU capability) were validated against Microsoft product documentation for Studio Effects and Copilot+ PCs.
- The Settings navigation paths listed in the release notes (for cameras, Windows Studio Effects, Device Card, and migrated keyboard controls) were confirmed by checking the Windows Studio Effects support article and the Windows Insider blog post for the build.
- The LSASS access violation is described in the normal rollout notes as resolved; administrators should monitor for any corroborating KB support articles and start validating the fix in test devices.
Where a Microsoft Support KB page for KB 5070311 was not immediately present in official KB pages at time of writing, the Windows Insider blog and Microsoft product documentation were used to corroborate feature descriptions and requirements. Any claims that reference rollout timing, regional availability, or driver delivery schedule are subject to change as Microsoft iterates.
Risks, trade-offs, and what to watch for
- Privacy and data governance: On-device AI effects (Studio Effects) reduce cloud exposure for video and audio processing, but some related AI features may still rely on cloud models or account-linked services. Validate organizational policies before allowing Copilot+ features on managed endpoints.
- Battery and thermal impact: Studio Effects and other NPU-driven features can increase power draw. Laptops used unplugged may see reduced battery life when effects are enabled. Test realistic workloads to measure impact.
- Compatibility and driver rollout: Studio Effects and some camera driver updates may roll out by OEM and CPU architecture. Expect staged driver delivery (Intel-first, then AMD/Snapdragon in earlier previews), and be prepared to update camera and platform drivers to unlock features.
- Fragmented user experience: Microsoft’s gradual rollout model means a mixed UX across endpoints; some users will have new capabilities while others do not, complicating internal support scripts and documentation.
- Regulatory limitations: Some features are absent from certain markets (notably the EEA for specific sharing options). Enterprises with cross-border deployments should verify availability for each market.
- Regression risk: Any large UI or system update can cause regressions. The release notes include fixes for some known Explorer and taskbar quirks; nonetheless, administrators should stage deployment and watch for regressions in secure sign-in paths (LSASS fixes are important but underscore past instability).
Recommendations for Insiders, enthusiasts, and IT admins
- Validate prerequisites:
- Confirm the device is on the Release Preview Channel and its OS build via winver.
- For Studio Effects: verify the device is a Copilot+ PC with a supported NPU and that the OEM-provided Studio Effects driver is present.
- Test in a controlled group:
- Pilot the update on a representative set of devices: business laptops, Copilot+ devices with and without NPUs, and any machines using external webcams.
- Check settings paths and policies:
- Update internal documentation to reflect the Settings locations for new controls (e.g., Cameras > Advanced camera options, Accessibility > Keyboard for repeat rate).
- Map Group Policy or MDM configuration equivalents for new Settings entries where applicable.
- Watch authentication and security:
- Validate Windows Hello ESS enrollments for peripheral fingerprint devices.
- Monitor for LSASS stability post-update and ensure recovery options are documented.
- Observe performance and battery:
- Measure battery life and thermal behavior with Studio Effects enabled on portable Copilot+ devices.
- Prepare rollback and remediation steps:
- Keep a plan for uninstalling the LCU or using system restore if needed, and document known workarounds (for example, clearing WER/ReportQueue entries if event flooding occurs).
- Monitor Microsoft’s Support article:
- Look for the KB 5070311 knowledge base entry and the update file list for the official installable packages and file information; Microsoft may publish Support documentation after the Insider blog post.
How to check and install (quick practical steps)
- Check your build:
- Press Windows + R, type winver, and confirm the OS build (26100.xxxx or 26200.xxxx).
- Opt into Release Preview Channel:
- Settings > Windows Update > Windows Insider Program > choose Release Preview.
- Install the update:
- Settings > Windows Update > Check for updates. Install the offered KB (it may show as an Insider preview or optional update).
- Enable Studio Effects on an alternate camera:
- Settings > Bluetooth & devices > Cameras > select the camera > Advanced camera options > Use Windows Studio Effects.
- If experiencing issues, revert:
- Use system restore, uninstall the latest cumulative update via Control Panel or DISM/Remove-Package (follow official Microsoft guidance to remove an LCU/SSU combo package).
Final analysis and verdict
This Release Preview roll — builds
26100.7296 and
26200.7296 — extends Microsoft’s broader strategy of pushing AI-first experiences to Copilot+ hardware while continuing steady refinement of Windows 11’s UX and stability surface. The most visible, practical improvement is the expansion of
Windows Studio Effects to alternate cameras; that alone resolves a common pain point for many users who favor higher‑quality external webcams. On-device AI that respects hardware locality is a positive development for user privacy and call-quality, but administrators must evaluate battery and thermal trade-offs.
The steady refinement of File Explorer, Settings, and Widgets reflects attention to everyday polish that benefits large numbers of users, while the LSASS fix addresses a potentially serious stability issue. The staged rollout approach minimizes blast radius but creates a transitional period of fractured feature availability that enterprises must plan for.
For enthusiasts and testers on Copilot+ hardware, this update is worth installing and exploring — particularly because the Studio Effects changes materially improve teleconferencing options. For IT organizations, the prudent path is measured testing: validate device prerequisites, simulate real workloads with AI effects enabled, and ensure rollout plans include monitoring and rollback strategies.
Overall, this release is another step toward integrating contextual AI into the Windows shell while keeping incremental improvements to polish and reliability. Users and administrators should proceed with an informed pilot program to reap the benefits while mitigating the practical trade-offs.
Source: Microsoft - Windows Insiders Blog
Releasing Windows 11 Builds 26100.7296 and 26200.7296 to the Release Preview Channel