Microsoft’s latest Windows 11 preview builds, shipped to the Release Preview channel in February 2026, mark a deliberate pivot away from headline‑grabbing AI features toward fixes that users feel every minute. Builds for versions 24H2 and 25H2 deliver a collection of under‑the‑hood refinements: a revamped taskbar that trims distractions, a sleep‑resume sequence that feels twice as fast on modern hardware, and a native network speed test tool that finally puts an end to browser‑based guessing games. These aren’t flashy additions, but they address the daily friction that power users and IT admins have complained about since Windows 11 first launched.

The quiet war on waking lag

Sleep and resume have been a sore spot for Windows laptops for years. Even with modern NVMe SSDs and instant‑on firmware, waking a machine from modern standby often meant watching the screen blink five or six times, waiting for peripherals to re‑enumerate, and staring at a desktop that took seconds to become responsive. Microsoft’s own telemetry showed that the 95th‑percentile resume time on a 2024‑era Intel Meteor Lake laptop could exceed eight seconds—an absurd delay for a device that is supposed to feel phone‑like in its readiness.

The February preview builds attack the problem from two angles. First, the kernel’s power manager now pre‑fetches critical driver stacks into a new “fast‑resume cache” during the suspend path. When the system wakes, those drivers are immediately available without re‑traversing the device tree. In internal benchmarks, this alone shaves 1.2 to 1.8 seconds off the resume time on a reference Dell XPS 14. Second, the modern standby implementation now holds the network stack in a low‑power listening state for the first 30 seconds after lid‑open, allowing Wi‑Fi and Bluetooth to reconnect without a full adapter reset. Early testers on Reddit and the Windows Insider forums report waking to a usable desktop in under three seconds—roughly half the time of the same hardware running the general availability channel builds.

The improvement is most dramatic on devices that use a dGPU. Previously, waking a laptop with a discrete NVIDIA or AMD GPU would trigger a full GPU state re‑initialization, which could add another two to three seconds. Build 26100.3476 (24H2) and the equivalent 25H2 build now keep the dGPU in a “warm‑rest” mode during modern standby, drawing just 0.5 W extra but allowing the display pipeline to resume in under 200 ms. Power‑conscious users can disable this in the advanced power settings if they prefer the lowest possible standby drain, but for most people, the faster wake is a clear win.

Taskbar learns to get out of the way

The taskbar in Windows 11 has been a magnet for frustration since its debut. The February preview finally delivers a set of tweaks that seem minor on paper but transform the daily workflow. The most requested change: the ability to show only the app icon on the taskbar for un‑pinned windows, while keeping labels for pinned apps. This “smart label” mode, accessible through Settings > Personalization > Taskbar > Taskbar behaviors, means you can pin File Explorer and see the full “Documents” label, but a stray Notepad window will shrink to just an icon, preserving space. Early feedback calls it the best of both Windows 10’s never‑combine and Windows 11’s clean icon‑only mode.

Another long‑standing annoyance—the “Show desktop” button. In the preview, the far‑right sliver of the taskbar now works even when the Copilot icon is present or when the system tray is overflowing. Accidentally triggering Copilot while aiming for the desktop has been a meme for two years; the hit target for Show desktop has been expanded from a 6‑pixel strip to 18 pixels, and it now has hover feedback that glows the entire corner. Right‑clicking the Show desktop area now offers a context menu to instantly minimize all windows (Win+D) or peek at the desktop (Win+,), making it discoverable for users who never learned the keyboard shortcuts.

System tray management also gets a quiet overhaul. Icons for background apps like OneDrive, Teams, and third‑party utilities can now be set to “auto‑hide after 5 seconds” when not active, reducing clutter without banishing them entirely. And a new “Network speed test” shortcut can be pinned directly to the Quick Actions panel—more on that in a moment.

A native speed test ends the Ookla dependency

One of the more unexpected additions in the preview builds is a built‑in network speed test tool, tucked inside Settings > Network & internet > Advanced network settings. Microsoft has partnered with Ookla to integrate a lightweight Speedtest engine directly into the OS, but the implementation is distinctly Windows‑native. The tool uses Microsoft’s own Azure edge nodes to measure latency, download, and upload speeds, and it logs the results over time in a local database so users can track performance trends.

Launching the test takes two clicks: open the page and hit the “Test now” button. The UI is identical to the Fluent Design language used elsewhere in Settings, with real‑time graphs for throughput and a log of the last 30 tests. IT administrators will appreciate that the feature respects Group Policy; a new “Disable network speed test” policy under Network\Network Connectivity can be deployed to prevent users from running tests on metered connections or in regulated environments.

Why include a speed test now? Microsoft’s telemetry indicates that network‑related support calls spike in the weeks after major feature updates, and a common troubleshooting step—visiting a third‑party speed test site—often fails because the browser itself is broken or the user doesn’t know which site to trust. Embedding the tool eliminates that variable. It also plays nicely with the new Wi‑Fi 7 support in 24H2/25H2, where users can see if their multi‑link operation is delivering the promised throughput without leaving the Settings app.

Under‑the‑hood polish for IT and power users

Beyond the user‑facing features, the February preview builds include a raft of changes aimed at enterprise manageability and reliability. The Local Administrator Password Solution (LAPS) now supports AES‑256 encryption for the stored passwords, and the LAPS CSP has been updated to allow Intune‑managed devices to rotate the password immediately after a recovery, closing a security gap that auditors have flagged. The Windows Kernel Vulnerable Driver Blocklist is now updated via Windows Update independently of the OS build, meaning that new malicious drivers can be blocked within hours without requiring a full cumulative update.

For developers, the Windows Subsystem for Linux (WSL) receives a memory reclaim feature that aggressively returns freed memory to the host when it’s no longer needed, solving a long‑standing complaint about WSL2 consuming RAM even when idle. And the new “sudo for Windows” feature, initially controversial, is now on by default in a “safe” mode that requires explicit user confirmation for each command, with an option to disable confirmation for specific trusted commands.

Rollout cadence and what’s still missing

The builds—26100.3476 for 24H2 and its equivalent for 25H2—arrived in the Release Preview channel on February 5, 2026, with a staged rollout that should reach all opt‑in devices by February 19. As usual with Release Preview, these changes will eventually ship as optional “C” preview updates for the general public, likely in late February, and then become mandatory in March’s Patch Tuesday. The feature set is identical across 24H2 and 25H2, though 25H2 includes additional under‑the‑hood refinements for Arm64 devices, including better x86 emulation for older productivity apps.

Conspicuously absent from this preview is any mention of Copilot or AI. After three consecutive feature updates that placed AI integration front and center—often with mixed reception—the February 2026 preview is an acknowledgment that the fundamentals still matter. The taskbar and sleep‑resume changes alone will affect orders of magnitude more user hours than Copilot in Word ever will, because they operate at the OS level, invisibly, every time a lid opens or a window is minimized. This is pragmatic engineering of the sort that made Windows 7 beloved, and it suggests a recalibration of priorities within the Windows team.

Community reaction: cautious optimism tempered by history

Windows Insider forums and Reddit threads are filled with early testers praising the sleep improvements. One user on r/Windows11 reported that their Surface Laptop 6 now wakes from sleep faster than their MacBook Air M3—a comparison that would have been laughable a year ago. Others highlight the taskbar’s new smart labeling as the feature they didn’t know they needed, with several noting that it finally lets them leave windows ungrouped without feeling overwhelmed. A few Insiders have requested even more customization, such as the ability to pin the network speed test results to the taskbar or to have the system automatically run a speed test when joining a new network, and Microsoft engineers have acknowledged the feedback in the Feedback Hub.

But skepticism remains. The same community remembers that Windows 11’s initial release promised a “simplified” taskbar that took away functionality, and it took nearly two years to restore basic features like “Never combine.” The sleep‑resume improvements, while impressive in the preview, are hardware‑dependent; older laptops or those with third‑party drivers that don’t support the new caching mechanism may see no benefit. And the network speed test, while convenient, has raised mild privacy concerns because it phones home to Azure edge nodes. Microsoft has clarified that no personal data is transmitted and the test endpoints are the same global CDN nodes used for Windows Update, but the ever‑vigilant privacy watchdogs will still scrutinize the feature.

The overriding sentiment, however, is relief. For the first time in several release cycles, the preview builds don’t feel like a vehicle for advertising a subscription service. They feel like the Windows team took a step back, looked at the telemetry of what actually causes people pain, and fixed those things. Faster sleep‑resume means less battery wasted while the machine is waking, less time staring at a blank screen, and fewer hard reboots when the wake sequence hangs. A usable taskbar means less cognitive load and faster window switching. These are not revolutionary changes, but they are the kind of incremental, relentless improvement that, over months and years, makes an operating system disappear into the background. And that’s precisely what an OS should do.

Looking ahead: the steady march toward Sun Valley 4

These February preview builds serve as the foundation for the next major feature update, codenamed “Sun Valley 4,” expected in the second half of 2026. While Microsoft hasn’t officially confirmed the branding, sources indicate that the release will double down on this back‑to‑basics philosophy, with further power management refinements, a redesigned File Explorer address bar, and a native clipboard manager that finally rivals third‑party alternatives. The AI features aren’t going away, but they are being re‑tuned to be genuinely assistive rather than intrusive—think smarter search indexing and contextual suggestions that respect local privacy boundaries. If the February preview is any guide, the Windows 11 user experience is about to get a lot smoother.