Windows 11 Low Latency Profile Hides a Short CPU Sprint

Windows 11’s August 11 security update finally applied a one to three second CPU burst to ordinary app launches, a step Microsoft’s May notes had already advertised. The May 26 optional package, KB5089573, never called Low Latency Profile by name, and installing it still does not mean Microsoft has flipped the switch on your PC.

Microsoft Left the Feature Out of Its Own Notes

Open the May 26 preview update notes and the speed work sits under a bland heading. Microsoft does not say Low Latency Profile. It does not say clock speeds. It does not print a percentage.

This update accelerates app launch and core shell experiences such as Start menu, Search, and Action Center.

Microsoft, KB5089573, May 26, 2026

That sentence is the public record. Briefings around the same work put flyouts at up to 70 percent faster and app launches at up to 40 percent faster, figures that never landed in the support article, which is why later recaps keep swapping them. KB5089573 is a preview for Windows 11 24H2 and 25H2. It moves 24H2 to build 26100.8524 and 25H2 to build 26200.8524.

The mechanics of that clock spike, the CPU sprint behind Low Latency Profile, are simple. When you open Start, Search, Action Center, or a flyout, Windows raises the processor to its top clock for one to three seconds, finishes the draw, then lets the chip fall back. Microsoft files the change under Windows K2, the internal push to make Windows 11 feel faster without waiting for every shell surface to be rewritten in WinUI.

The same preview also makes Search return files after two characters, adds NPU columns in Task Manager, and ships Shared Audio over Bluetooth LE so two headphones can listen to one PC. Those items have names in the notes. The CPU sprint does not.

Installing the Patch Does Not Turn It On

Microsoft splits this class of change into a gradual rollout and a normal rollout. Gradual means the bits can sit on the disk while a server-side flag stays off. Low Latency Profile has no toggle in Settings. Once the company enables it on a device, it runs in the background with nothing for you to click.

So the May optional update was a package, not a promise. Testers who installed KB5089573 and then watched clock speed while opening Start often saw nothing. The code was present. The profile was not.

WHEN THE BURST ACTUALLY SHOWED UP

1. May 26, 2026: KB5089573 ships as an optional preview for 24H2 and 25H2, builds 26100.8524 and 26200.8524, with the unnamed performance line and a Controlled Feature Rollout around the burst.
2. June 9, 2026: The June 9 cumulative security update, KB5094126, folds that preview into the monthly rollup and moves PCs to builds 26100.8655 and 26200.8655. The flag is still staged.
3. June 23, 2026: Preview KB5095093, builds 26100.8737 and 26200.8737, widens the pipe again. Shell flyouts are the part that is live for more machines. App launches are not.
4. August 11, 2026: Security update KB5121003, builds 26100.9168 and 26200.9168, is when testers first see the same burst on ordinary apps, still under the same silent flag.

How-to clips posted on September 9 still treat Low Latency Profile as a hidden switch. That matches the product Microsoft actually shipped: a performance change you cannot see in Settings and cannot confirm from the KB number alone.

App Launches Did Not Get the Burst Until August

The May notes already talked about app launch. Early tests after KB5089573 found that claim was ahead of the code that was actually on. Shell flyouts, Start, Search, and Action Center, were the first surface. Apps waited.

THE THREE UPDATES THAT CARRIED THE BURST

After KB5121003, testers on an Intel Core i5-13420H watched performance cores jump toward 4.6GHz the moment an app opened, with efficiency cores climbing past 2GHz. Notepad, Calculator, Chrome, the Epic Games Store, PowerPoint, VLC, and the Weather app all opened faster on the same PC than they had before the August patch. The Weather app is a WebView2 package, so the sprint is not limited to native WinUI windows.

The scheduler idea has a plain name in chip design: finish the work at a high clock, then drop into a deep idle sooner than a medium clock would allow. Microsoft did not invent that. It also did not ship the app half in May, even though the sentence in the notes already covered it.

Why Microsoft Calls a CPU Sprint Normal

The first public tests in May ran on a constrained virtual machine with two cores and 4GB of RAM. Edge and Outlook opened faster. CPU use jumped to about 96 percent on Edge and 94 percent on Outlook for a few seconds, then fell off. On a fast desktop the same trick is easy to miss, because those chips already hit boost clocks without a special profile. On a cheap laptop the pause before Start paints is the whole complaint Windows 11 has carried since launch.

Critics called the burst a bandage: if the shell needs a full-clock sprint to feel instant, the shell is still heavy. Scott Hanselman, a Microsoft VP, answered that charge on X in May, after people branded the tactic cheating.

All modern operating systems do this, including macOS and Linux. It’s not ‘cheating’; this is how modern systems make apps feel fast: they temporarily boost the CPU speed and prioritize interactive tasks to reduce latency.

Scott Hanselman, Microsoft VP, on X

He added that phones already do the same loop on every tap, and that “Apple does this and y’all love it.” The engineering point is fair. The packaging still looks like an admission. Windows 11 spent years with a Start menu that felt a beat late, and the first K2 performance update does not make that menu lighter. It buys the missing beat with a clock spike, then hides the spike behind a flag so Microsoft can pull it if a device class misbehaves.

Testers who measured the short shell bursts on battery and on charger reported no meaningful extra drain, which fits a one to three second raise in clock rather than a rise in how busy the chip stays. Thin laptops can still spin a fan for a moment. That is a different complaint from killing a charge cycle.

Budget PCs Feel the Spike First

Low Latency Profile needs no extra silicon. There is no NPU gate and no Copilot+ checklist. The machines that show it are the ones that used to sit in a mid clock while Start, Search, or a context menu caught up. High-end towers that already boost on a click will record a prettier graph in HWiNFO and almost no change in the hand.

That split is why the feature became a budget-PC story before it became an everyone story. A two-core virtual machine with 4GB of RAM is a cruel stand-in for a family laptop, and that is exactly where the May tests looked obvious. The August app-launch pass on the i5-13420H is the more typical case: a midrange chip that can sprint, and a stack of apps that were not getting the sprint until KB5121003.

Microsoft is also moving pieces of the shell off web-style UI onto WinUI, which is the slower, more honest fix. Low Latency Profile does not wait for that rewrite. It treats the click as an emergency and spends clock on it. Both tracks can run at once. Only one of them shows up in a changelog as a single sentence about Start, Search, and Action Center.

How to Check If Low Latency Profile Is Running

Build number is the easy half. If Settings, System, About does not show 26100.8524 or 26200.8524 or newer, the May code is not there. June’s KB5094126 and August’s KB5121003 are the later floors. None of those numbers prove the flag is on.

Task Manager is usually too slow to catch a one to three second clock jump if you watch the utilization percentage. Clock speed on the Performance tab is the useful column. A tool that polls sensors faster, such as HWiNFO, is the check testers actually trust.

SIGNS THE PROFILE IS LIVE

• Shell test: Open Start, Search, or Action Center and watch for a sharp jump to the chip’s top clock, then an immediate drop, not a long grind.
• App test: After KB5121003 (builds 26100.9168 or 26200.9168 or newer), the same jump should appear when you launch a normal app, not only a flyout.
• Idle pattern: Between clicks the processor should fall back quickly. A stuck high clock is not this feature; that is a load or a power-plan problem.
• No toggle: If you are hunting in Settings for Low Latency Profile, you will not find it. Microsoft did not ship a switch.

If the clocks do not move, you have the update and not the profile. That is the Controlled Feature Rollout doing what it is designed to do, which is let Microsoft turn a behavior on by machine instead of by KB.

The Only Switch Is Still Unofficial

Community guides use ViVeTool on GitHub, an open-source console app that talks to Windows feature-control APIs. The ID most often used for the core burst is 58989092. Guides that want the app-launch half add 61391826. You run the tool from an administrator Command Prompt, restart, and then repeat the clock-speed check. Microsoft does not support that path.

ViVeTool is a blunt instrument. It flips experiment flags the company uses for staged rollouts, which is why it can turn Low Latency Profile on before your PC is in the enabled cohort, and why it can also turn on neighboring IDs you did not mean to touch. Once Microsoft makes the profile the default on a device, the same disable command may stop working. Waiting for the official flag costs you nothing except patience.

September how-to videos still walk through that unofficial switch, which is the quiet verdict on KB5089573. Microsoft put a performance change into Windows 11, declined to name it, declined to put it in Settings, split the shell half from the app half across three cumulative updates, and left confirmation to a sensor panel. The menus can open faster. The update still does not, by itself, mean that they will.