Windows 11 Finally Feels Fast Again

I did not move my main desktop back to Windows because Windows got good. I moved it back because the Fedora box on my desk kept hanging on resume, and a daily driver that needs a reboot ritual after lunch is not a daily driver. WSL carries the Linux side now — kubectl, Terraform, the VPN dance — and the host underneath it is Windows again. I wrote the long version of that desktop friction in my Fedora/NVIDIA field report; this post is about what I found waiting on the other side.

What I found, somewhere around the June updates, was a desktop that stopped hesitating. Not faster in a benchmark I could screenshot. Faster in the specific, felt way where Start opens the instant I hit the key, Search returns a result before I’ve finished doubting it, and an app window is on screen before I’ve decided whether the click even registered.

That gap — between “the computer is working” and “the computer responded” — is the whole game on a desktop. Microsoft shipped something that closes it, and it is worth being precise about what it is and what it very much is not.

What Microsoft actually shipped

Two updates, one feature.

The preview was KB5089573, on May 26, 2026, for Windows 11 versions 25H2 and 24H2 (builds 26200.8524 and 26100.8524). Under General Performance, Microsoft’s own wording is deliberately flat: the update “accelerates app launch and core shell experiences such as Start menu, Search, and Action Center.” No codename, no fanfare, one sentence.

Then KB5094126, the June 9, 2026 security update (builds 26200.8655 and 26100.8655), folded those non-security changes into the mandatory channel. It downloads and installs automatically from Windows Update, which means most people on a current Windows 11 get this whether or not they ever read a release note. It also cleaned up after the preview: KB5089573 had triggered virtualization-related stop errors — HYPERVISOR_ERROR (0x20001) and KMODE_EXCEPTION_NOT_HANDLED (0x1E) — on restarts, VM operations, and some games, and KB5094126 fixes them. Worth knowing if you run Hyper-V or WSL all day. Not worth dwelling on, because it’s resolved.

The one operational caveat that matters is delivery: this is a gradual rollout. Microsoft pushes it in phases, “so features reach devices over time instead of all at once, meaning availability varies by device.” Two machines on the same build number can behave differently for weeks. Keep that in your pocket for the part where people argue about whether they “have it.”

What Low Latency Profile seems to do

The flat release-note wording has a name the press attached to it: Low Latency Profile, part of Microsoft’s internal “Windows K2” responsiveness work.

The mechanism, as reported, is unglamorous and sensible. When the system detects a high-priority interactive action — you launch an app, open Start, hit Search, pull down Action Center, switch windows — it briefly pushes the CPU toward maximum frequency, on the order of one to three seconds, and boosts only the core handling that foreground thread. Then it drops back. It is a frequency burst aimed at the exact moment you are waiting on the machine, not a sustained overclock.

Read that carefully, because it tells you what the feature is not. It does not raise CPU utilization; it raises CPU frequency, briefly. It does not make your compile finish sooner or your render run faster — those are sustained workloads, and a one-second burst does nothing for them. It changes perceived latency on the interactive path and nothing else.

Windows has done targeted scheduling tricks for time-sensitive work for a long time; MMCSS has prioritized audio and multimedia threads for years. Low Latency Profile is not MMCSS, but it sits in the same lineage — the OS deciding that some work is latency-sensitive and treating it differently. That isn’t a hack. That’s an operating system doing its job.

The figures floating around are up to 40% faster app launch and up to 70% faster interaction with shell features. I’m repeating those as reported numbers, not as anything I measured — I have not put a stopwatch on my own machine, and you shouldn’t trust a number just because a blog printed it. What I can say is that the direction matches what I feel.

Why this matters more than another benchmark

Here’s the thing benchmark culture keeps getting wrong about desktops: responsiveness is not throughput.

A workstation can have a 16-core CPU, 64 GB of RAM, and an NVMe drive that reads faster than you can think, and still feel bad if Start stutters for 400 milliseconds, if Search spins before it shows you the app you typed three letters of, if the right-click menu lands a beat late. None of that shows up in a Cinebench score. All of it shows up in your mood by 3 PM.

My day is a thousand tiny interactions. Alt-tab to the browser, drop into a WSL pane, hit Search for the editor, open Action Center for a notification, pull up the VPN, switch back. Each one is sub-second work. Each one, when it hesitates, breaks flow — and flow is the actual product of a good desktop. Low Latency Profile targets precisely that path: the short, foreground, “I am waiting on you right now” moments. It is the least glamorous possible improvement and the one I notice most.

The backlash is not wrong, but it is incomplete

When this shipped, a chunk of the community read it as an insult — Microsoft burning CPU frequency to paper over a bloated shell instead of fixing the bloat. That criticism is not stupid. The shell is heavier than it should be, and a frequency boost that makes a slow thing finish faster is not the same as making the thing fast.

But the other half is also true, and Microsoft’s Scott Hanselman said it plainly when he stepped into the argument: every modern OS already does this. macOS aggressively boosts clocks the instant you interact. Linux does it through the kernel scheduler, frequency governors, and schedutil waking faster cores on input. Short interactive boosting is not cheating; it is the standard way modern systems make interaction feel instant. Calling it a band-aid only works if you also call the same behavior on macOS and Linux a band-aid, and nobody does.

The honest caveat sits under both takes: this is only efficient if the system can get back to idle quickly. “Race to sleep” — finish the burst, return to low power — is the whole bargain. On hardware that settles cleanly it’s close to free, and the battery and thermal cost stays small because the boost is measured in seconds. On a machine that never goes quiet, you’d just be adding heat. For most modern laptops and desktops, the bargain holds.

What it does not fix

Credit given. Now the limits, plainly, because preview enthusiasm erases them.

• It is not debloat. The ads in Start, the nags, the “finish setting up your PC” interruptions — none of it is touched. A faster path to an ad is still an ad.
• It is not a shell rewrite. The web-wrapped, framework-heavy pieces of the modern Windows UI are still web-wrapped and framework-heavy. A frequency burst makes them launch faster; it doesn’t make them lighter. The real fix is native code, and that’s slow, boring work no single update delivers.
• It is not a gaming FPS feature. Don’t go looking for it in your frame counter. Sustained game load is exactly the sustained workload this doesn’t address.
• It is not proof your machine has it. Gradual rollout means two identical-looking PCs can be in different states. “I’m on the build and don’t feel it” and “I feel it” can both be true at once.
• It gives you no control. No Settings toggle, no notification, no indicator. It works in the background or it doesn’t, and you are not consulted. For a feature I like, I’d still take a switch and a status line over faith.

How I’d check it instead of arguing about it online

If you actually want to know whether it’s doing anything on your machine, the forum-argument approach is useless. Here’s the grounded version.

Start with the build. Confirm you’re on a version that carries it — 24H2 or 25H2, builds at or past the KB5094126 numbers above — and then remember that being on the build is necessary, not sufficient. Gradual rollout, again.

Then watch the right metric. The mistake everyone makes is opening Task Manager and staring at CPU utilization, which barely moves, because the feature doesn’t push utilization — it pushes frequency. A tool that surfaces per-core clock speed, like HWiNFO, shows the sharp, brief frequency jump on shell interactions that Task Manager flattens into nothing. Frequency, not utilization. That single distinction settles most of the “is it even working” threads.

The clearest demonstration, by the reports and matching what I’d expect, is on lower-powered hardware and VMs, where the burst is dramatic and obvious. On an already-fast primary PC the effect shows up as smoothness rather than a stopwatch number — which is exactly why a benchmark won’t catch it and your own hands will.

And the honest test is the unscientific one: do Start, Search, Action Center, and app launch feel different before and after? That’s a perception, not a measurement, and on a feature whose entire purpose is perceived latency, perception is the correct instrument. I’d skip the registry hacks and the ViVeTool enablement spelunking — if the rollout hasn’t reached you, wait for it rather than poking the OS into a state Microsoft didn’t ship you.

Where this nets out

Microsoft earns real credit here, and I don’t hand that out reflexively. Low Latency Profile made my Windows desktop feel fast again — not in a graph, in the hundred small moments a day where a desktop either keeps up with me or doesn’t. That’s the felt-latency path, and they fixed it.

The pressure stays on, though. Feeling fast is not the same as being clean. The shell still needs the ads gone, the web-wrapped weight rewritten in native code, the Settings sprawl reined in, and admins still deserve visibility and a switch instead of a silent background profile. None of that is solved by making a heavy thing launch quicker.

But I’ll take it. This is exactly the kind of boring, unglamorous, deeply-felt OS work that users actually notice — the opposite of a flashy feature nobody asked for. More of this, please, and keep going until the thing that launches fast is also the thing worth launching.