Microsoft’s optional preview for Windows 11 version 26H1 arrived on February 24, 2026, as KB5077239 (OS Build 28000.1643), and it’s a busy patch: a mix of Copilot+ enhancements, cross-device continuity improvements, File Explorer polish (including a stronger dark mode), developer- and musician-friendly MIDI updates, and a handful of reliability and accessibility fixes. The update is delivered as a phased rollout — some features appear gradually by device and market, while other improvements are broadly available — and it’s paired with a servicing stack update, so IT teams should treat it as more than a routine “optional” preview before deploying widely.
Background
Windows 11 26H1 is positioned by Microsoft as a targeted release to enable new device innovations in 2026, and KB5077239 is the non-security, preview cumulative that brings early pieces of that work to users and Copilot+ PCs. The update’s official build number is
OS Build 28000.1643, and it was published as an optional preview release on
February 24, 2026. Because this is a preview/non-security rollup, features are being flighted and gated: two machines on the same build can show different experiences depending on feature flags, OEM integrations, and regional availability.
This preview contains two types of changes you’ll notice at once and others you’ll only see if your device is targeted or you’re using a Copilot+ PC: user-visible UX improvements, platform and reliability fixes, and partner-specific feature extensions (notably for certain Android OEMs).
What’s new at a glance
- Copilot+ and Settings Agent: broader language support and improved Settings search UX.
- Click to Do: a streamlined context menu and auto-popup behavior for large images and tables.
- Camera: Windows Studio Effects can be enabled for additional (external and rear) cameras.
- Cross‑Device Resume: expanded handoff scenarios from Android phones to Windows (Spotify, Microsoft 365 apps, some OEM browsers).
- File Explorer: deeper dark-mode consistency, simplified context menu rollout, and a “Recommended” toggle on Home.
- Windows Hello ESS: peripheral fingerprint reader support.
- Accessibility: more granular Narrator options, simplified Voice Access setup, and extra Voice Typing settings.
- MIDI improvements: expanded and modernized MIDI 1.0 and 2.0 support aimed at musicians and developers.
- Servicing stack: integrated SSU (KB5078262) to ensure reliable update delivery.
Each of these items is small on its own but collectively signals Microsoft’s push toward tighter device integration, AI-led experiences, and quality-of-life polish ahead of broader 26H1 availability.
Deep dive: Cross-Device Resume — practical continuity, with caveats
What changed
Cross‑Device Resume has been expanded to support more “pick up where you left off” scenarios from Android phones to Windows PCs. Examples called out in the release include:
- Resuming Spotify playback on PC after pausing on an Android phone.
- Opening and continuing editing of Microsoft Word, Excel, or PowerPoint files that were opened on an Android device, provided the appropriate Microsoft 365 app is installed on the PC (otherwise the file opens in a browser).
- Continuing browsing sessions from specific OEM browsers on the phone (Vivo Browser is explicitly mentioned; other OEMs such as HONOR, OPPO, Samsung, vivo, and Xiaomi appear in the partner list).
- Some Android brands can resume online files opened in the Copilot app on the phone, which then open on the PC in Microsoft 365 apps (or the browser if the app isn’t installed).
Important limitation:
files that exist only offline on the phone (offline-only files) are not supported by the resume flow.
Why this matters
Cross‑Device Resume is an incremental but meaningful step toward reducing friction between phone and PC workflows. Users who regularly move between devices — especially those who use Microsoft 365 on both phone and PC — will find it smoother to continue a task without manually moving files, copying links, or relying on ad-hoc cloud uploads.
From a strategy angle, these resume flows are a practical example of Microsoft combining OEM partnerships and its cloud/ai investments to provide continuity across form factors. When it works, it removes a click or two and keeps task context intact.
Caveats and risks
- Rollout and partner dependency: The feature depends on phone-side integrations and OEM cooperation, so availability will be staggered and app-dependent. Expect different behaviour across brands, phone models, and markets.
- Privacy and telemetry surface area: Any cross-device handoff that involves app context and file metadata increases the surface area for telemetry and cloud processing. Enterprises and privacy-conscious users should confirm what metadata is transmitted during resume flows and whether tokens or access grants are stored on servers or transiently passed between devices.
- Redundancy with app-level sync: Many apps (Spotify, Office, browsers) already provide sync or cloud-based resume features. The net user benefit will depend on how this Windows-hosted resume complements or duplicates existing capabilities.
- EEA restrictions: Some features may not be available in the European Economic Area; organizations in regulated regions must test and confirm availability and compliance.
File Explorer: the long overdue polish
Dark mode and UI consistency
A common complaint since Windows 11’s debut has been inconsistent dark-mode treatment across File Explorer dialogs and progress UI. KB5077239 addresses this by:
- Updating copy/move/delete dialog backgrounds and contrast so they respect the system dark theme.
- Refreshing progress bars and chart views for legibility in dark mode.
- Unifying confirmation and multiple-error dialogs to present a consistent appearance.
These changes are primarily cosmetic, but they have measurable accessibility benefits: consistent contrast reduces cognitive load for users with visual sensitivity and helps screen readers and high-contrast modes behave predictably.
Simplified context menu and Home recommendation toggle
Microsoft is experimenting with a
simplified context menu that consolidates frequent actions (Share, Copy, Move) into a single organized menu. This is currently rolling out to a small test group while Microsoft evaluates feedback.
Additionally, File Explorer’s Home page gains a
Recommended section toggle so users can choose to surface frequently used or recently downloaded files. This is useful for personal accounts and can be toggled from File Explorer > Options.
Networking, thumbnails, and reliability fixes
The update also includes behind-the-scenes fixes:
- Improved responsiveness when navigating network locations.
- Thumbnail fixes for certain video EXIF metadata scenarios.
- A fix where the “Open” icon could appear generic rather than representing the default app.
While none of these are headline-grabbing, they address daily friction and represent the kind of quality-of-life work enterprises typically appreciate.
Copilot+, Settings Agent, and Click to Do: smarter context and AI agents
Settings Agent gains languages and better search UX
On Copilot+ PCs, the Settings Agent now supports more languages (German, Portuguese, Spanish, Korean, Japanese, Hindi, Italian, and Simplified Chinese). The Settings search box displays more results with a scrollbar,
recommended settings actions are faster, and a clearer dialog explains when Settings cannot change something further.
This improves discoverability and reduces user confusion when Settings hits a limit — a welcome step for global users and non-English speakers.
Click to Do: context-aware micro-actions
“Click to Do” receives a compact context menu with frequently used actions surfaced first: Copy, Save, Share, Open. On compatible devices, the menu can open automatically when Windows detects a large image or table on-screen. Availability is device- and market-dependent.
This is another example of Microsoft experimenting with micro-interactions: if streamlined, Click to Do could become a quick productivity booster for content extraction and sharing workflows.
Camera: Studio Effects on more cameras
Windows Studio Effects (the AI-based camera enhancements) can now be enabled for additional cameras, including
USB webcams and supported laptop rear cameras. Users can pick a camera via Settings > Bluetooth & devices > Cameras and enable Studio Effects in Advanced camera options.
This makes the Studio Effects improvements more accessible to users who don’t rely solely on integrated front-facing sensors and is particularly helpful for creators and hybrid workers using external cameras.
Security, sign-in, and reliability: practical fixes
KB5077239 is not a security-only update, but it includes reliability and activation fixes teams will want to note:
- Windows Hello ESS now supports peripheral fingerprint readers, not just the built-in sensors. This is meaningful for enterprises standardizing on a single fingerprint reader model across a fleet or using aftermarket readers for legacy devices.
- Explorer improvements address cases where Explorer.exe could hang on first sign-in (which could prevent the taskbar from appearing).
- Activation improvements help license migration during upgrades — an important reliability improvement for organizations running imaging and upgrade workflows.
- Lock screen fixes for rare unresponsive behavior.
These fixes reduce the risk of end-user downtime following updates or first-run experiences and prevent operational headaches during provisioning.
Accessibility and input: focused refinements
Microsoft continued refinements for assistive technologies and input:
- Narrator lets users choose what it announces and in what order, improving control for power screen-reader users.
- Voice Access gains a simpler setup flow, reducing onboarding friction for speech-control users.
- Voice Typing adds a “wait time before acting” setting to tune when dictation triggers commands.
- Input updates include clearer keyboard setting labels, haptic pen feedback support for compatible pens, and improved keyboard backlight behavior for supported HID keyboards.
These updates are expressly targeted at making Windows 11 more usable for people who rely on alternate input and feedback modalities. They don’t just polish features; they reduce barriers for users who depend on accessibility tools daily.
MIDI and gaming: niche but notable
For musicians and developers, KB5077239 improves MIDI support with enhanced MIDI 1.0 and MIDI 2.0 functionality, offering:
- Full WinMM and WinRT MIDI 1.0 support with built-in translation.
- Shared MIDI ports across apps, custom port names, and loopback/app-to-app MIDI.
- Tools and SDK packages enable inbox MIDI 2.0 features, though they may require separate downloads for SDK tooling.
Gaming gets a smaller mention: the Full Screen Experience (FSE) is expanded to more handheld Windows PCs, and there are display fixes to reduce stutter when applications query supported monitor modes. These are incremental but important for handheld gamers and developers building apps that programmatically query display modes.
Deployment and installation notes for IT
KB5077239 is an optional preview LCU that’s packaged together with an SSU (KB5078262). IT teams should treat it like a test candidate before broad deployment.
Key deployment points:
- Feature variability: Because many features are rolled out gradually or are dependent on Copilot+ hardware or OEM integrations, not every user will see the same changes even after installing the update.
- Servicing stack: The package includes an SSU; when installing manually via MSU or DISM, ensure that the combined package order is respected. Removing the LCU after installing the combined SSU+LCU package is more complicated; SSUs are persistent.
- Enterprise packaging: The update is importable into WSUS and can be staged for targeted rings. Admins using WSUS or SCCM should test activation and license migration behaviors in pilot groups.
- Manual install options: For edge cases, the update’s MSU files can be applied via DISM /Add-Package or PowerShell Add-WindowsPackage. Use caution and test on representative hardware, including Copilot+ PCs and devices with external fingerprint readers.
- Rollback: Since the SSU portion can’t be removed, full rollback may require recovery measures. Validate images and fallback strategies before deploying broadly.
Recommended sequence for pilots:
- Validate on representative Copilot+ and standard devices.
- Test sign-in and Explorer behaviors, especially for first-run users.
- Confirm Windows Hello and fingerprint peripheral compatibility.
- Evaluate Cross‑Device Resume flows with supported Android phones (test offline/online file boundary cases).
- Monitor telemetry for any unexpected activation or licensing anomalies.
Practical guidance: what to test and how
If you’re running a pilot or planning to update a fleet, include this checklist:
- Sign-in and first-run: Reboot and sign in as a new user to confirm Explorer.exe and taskbar appear reliably.
- Windows Hello ESS: Plug in representative peripheral fingerprint readers and validate enrollment and authentication workflows.
- File Explorer UX: Toggle dark mode and run typical copy/move/delete dialogues. Confirm progress indicators and dialog contrast.
- Cross‑Device Resume: With test Android phones (from different OEMs where possible), attempt to resume Spotify playback, open a Word doc in the phone’s Copilot app, and continue browsing from Vivo and other OEM browsers.
- Camera Studio Effects: Connect external webcams and rear laptop cameras and enable Studio Effects from Settings to confirm effects apply as expected.
- Accessibility features: Validate Narrator, Voice Access, and Voice Typing behaviors with screen-reader users and accessibility testers.
- MIDI workflows: For creative teams, run sample MIDI app chains to validate shared ports, loopback, and device detection.
Document any feature variability and capture logs for edge-case failures (Event Viewer and the Feedback Hub traces are helpful).
Analysis: strengths and potential risks
Strengths
- Attention to polish: KB5077239 reflects Microsoft addressing long-standing UX inconsistencies, especially in File Explorer and dark mode. These small fixes pay dividends in perceived quality.
- Cross-device practical integration: The Cross‑Device Resume expansion is sensible and fits how many users actually work across phone and PC.
- Accessibility gains: Focused improvements to Narrator, Voice Access, and Voice Typing show continued investment in inclusive features.
- Enterprise-minded fixes: Improvements to activation license migration and sign-in reliability are practical wins for IT.
- Broader hardware support: Peripheral fingerprint reader compatibility extends Windows Hello ESS utility for mixed hardware fleets.
Risks and limits
- Feature fragmentation: Because many items are gated by device, market, or Copilot+ hardware, inconsistent experiences could confuse users and complicate troubleshooting for IT.
- Privacy and data handling: Any cross-device feature introduces potential telemetry and cloud processing considerations. Organizations must audit how context and metadata are transmitted and stored.
- OEM dependency: Resume flows that depend on phone OEM/browser integrations mean support can vary widely; some partners may implement richer handoffs than others.
- Preview status: As an optional preview, KB5077239 can change; some features will be refined or rolled back based on telemetry and user feedback.
- Update complexity: The inclusion of an SSU and LCU combined package complicates manual rollback and requires careful deployment planning.
Final verdict: practical, incremental, and worth piloting
KB5077239 is not a dramatic platform overhaul, but it’s a meaningful step in the maturation of Windows 11’s everyday experience. Microsoft is prioritizing polish, continuity, and accessibility while continuing to test tighter integrations between phones, OEM partners, and Copilot+ PC experiences.
For early adopters, tech enthusiasts, and teams eager to evaluate Copilot-driven workflows, this preview is worth installing in a controlled pilot. For broad corporate rollouts, wait until the update exits preview or until Microsoft signals broader availability for key features, especially Cross‑Device Resume and the simplified File Explorer context menu.
If you manage devices, test thoroughly: sign-in reliability, Windows Hello ESS peripheral behavior, license migration on upgrade, and any cross-device flows your users will depend on. Pay special attention to the privacy implications of cross-device handoffs and document expected differences by device and market.
Windows 11 KB5077239 demonstrates how Microsoft is nudging Windows toward tighter continuity and more consistent polish. It’s an update that quietly improves the daily user experience while leaving the heavier platform shifts for future releases.
Source: onmsft.com
Windows 11 26H1 KB5077239 adds Cross-Device Resume, File Explorer tweaks, and more – OnMSFT