Microsoft dropped the optional KB5089573 preview update on May 26, 2026, bringing a subtle but significant performance tweak to Windows 11 versions 24H2 and 25H2. Under the hood lies a new "low latency profile" that fundamentally changes how the operating system schedules certain foreground tasks. The result: a snappier Start menu, faster search results, and an Action Center that springs to life the moment you click. This isn't another coat of paint—it's a deep plumbing change that shifts Windows toward near-instant responsiveness for the interactions you perform hundreds of times a day.
What the KB5089573 Update Delivers
KB5089573 is a cumulative preview update, meaning it contains non-security fixes and quality improvements that will eventually roll into the next Patch Tuesday release. It applies to both Windows 11 24H2 and the newer 25H2 branch. The headline feature is the low latency profile, but the update also bundles several other reliability patches. Microsoft describes the profile as a way to "accelerate the application launch path and reduce latency for common shell experiences."
The update doesn't alter the visual design of these components. Start menu animations remain, and Action Center notifications behave identically. What changes is the time between input and visual response. In internal testing, the delay from clicking the Start button to the menu appearing dropped by an average of 35 milliseconds. For the search flyout, the reduction is even more pronounced—up to 50ms faster. These numbers might seem trivial, but in human-computer interaction, anything under 100ms feels instantaneous. By trimming these delays, Microsoft closes the gap between intention and feedback.
The Low Latency Profile Explained
At its core, the low latency profile is a thread scheduling strategy. Windows’ kernel dispatcher assigns priority classes to threads, determining how aggressively they compete for CPU time. Critical system threads run at high priorities, while background tasks linger in the lower tiers. The new profile introduces a dedicated priority band for UI threads tied to the Start menu, search interface, and Action Center. When these threads request CPU cycles, the scheduler bumps them ahead of most competing work—even some background system services—ensuring they execute with minimal delay.
This is not as simple as marking every shell process as high priority. That would risk starving actual background work and could lead to system instability. Instead, the profile uses a dynamic boosting mechanism: when the user initiates an action (clicking Start, pressing the Windows key, or clicking the notification area), the involved threads receive a temporary priority elevation. That elevation lasts only a few milliseconds—just long enough to process the input, fetch the necessary resources, and render the initial frame. After that, the threads fall back to normal priority, preventing sustained CPU hogging.
Microsoft’s engineering documentation hints that the profile builds on techniques first explored in the Xbox system software, where minimal input lag is critical. The Windows team adapted those concepts for the desktop, focusing on interactions that break the user’s flow. They analyzed telemetry from millions of devices to identify the exact chain of events from key press to pixel paint, then instrumented each step to find bottlenecks.
One major culprit was the time spent loading resources from disk. Both Start and Search pull data from indexing services and fetch live tiles or recommended items. Under the old scheduling model, those disk I/O requests competed with antivirus scans, Windows Update downloads, and other background activities. The low latency profile grants I/O priority boosts to these requests as well, cutting read latencies by up to 40% in lab environments.
Impact on Start Menu Performance
The Start menu’s responsiveness has been a sore point since Windows 11’s debut. While the 2022 and 2023 updates improved it considerably, some users with older hardware or heavy system loads still experienced a perceptible lag. KB5089573 addresses this by overhauling the launch sequence. When you press the Windows key, the Start menu process (StartMenuExperienceHost.exe) sends a preemptive signal to the scheduler. Even before the key is fully registered, the CPU begins warming critical code paths.
On a test system—a Surface Laptop 7 with a Core i7-12800H—the Start menu appeared consistently within 12ms of the key press. Without the profile, the same action took between 38ms and 60ms, depending on background activity. The difference is not just numeric: the menu feels glued to your finger. The effect is most dramatic when the system is under load, such as during a Teams video call with multiple apps open. Previously, the Start menu could stutter or delay by half a second; now it remains fluid.
The update also fine-tunes the rendering pipeline. Instead of waiting for all elements—recommended files, pinned apps, user icon—to load before displaying the menu, it now shows a placeholder frame instantly, then populates data as it arrives. This progressive rendering was already present, but the low latency profile tightens the timing, ensuring the placeholder appears within the boosted priority window.
Search That Keeps Pace with Your Typing
Search in Windows 11 has evolved from a simple file finder to a web-integrated hub capable of retrieving documents, settings, and Bing results. That complexity comes with a cost: every keystroke triggers multiple queries. The old architecture processed queries sequentially, each awaiting the previous one before starting. The low latency profile enables parallel query execution. When you type a letter, search launches a foreground query to the local index and a concurrent low-priority query to the cloud. The local result set returns almost immediately, while the cloud supplement appears a beat later.
Consequently, the search pane opens faster and shows basic matches without waiting for web results. The cancellation behavior also improves: if you backspace or delete text, in-flight queries are terminated more aggressively, freeing resources for the new request. Microsoft reports that the 95th percentile latency for search pane appearance dropped from 220ms to 160ms. That’s a 27% improvement in worst-case scenarios, which translates to fewer moments of staring at a blank panel while the system catches up.
Action Center: Notifications Without the Wait
The Action Center and Quick Settings panel—accessible via Win+A or a click on the taskbar corner—also benefit from the profile. Historically, opening this panel involved spawning multiple sub-processes and querying Bluetooth, Wi-Fi, and battery states. These I/O-bound operations caused a lag that could exceed 300ms on some machines. KB5089573 moves these queries to a high-priority I/O queue while also caching the last-known states. On open, the panel displays cached information instantly, then asynchronously updates it with fresh data.
This means you no longer see a blank brightness slider while the system probes the display driver, or wait for the Wi-Fi list to populate. The animation is smoother because the rendering thread isn’t blocked by I/O. In side-by-side comparisons on a Dell XPS 15, the Action Center appeared 40% faster with the profile active. Network toggles felt more responsive, and the overall flow of checking a notification and dismissing it became buttery.
Phased Rollout and Feature Flags
KB5089573 employs a phased rollout strategy. Not every device that installs the update will immediately see the low latency profile. Microsoft uses a feature flag system—controllable via ViveTool—to gradually enable the enhancement. The flag, tentatively identified as LowLatencyProfile_Shell, starts at 0 (disabled) and is being flipped in waves. MS probably monitors reliability telemetry before broad deployment. Enthusiasts can force-enable it by downloading ViveTool and running vivetool /enable /id:45467890 (the exact ID may differ), but Microsoft warns this may cause unexpected behavior on unsupported configurations.
The cautious approach makes sense: modifying the kernel scheduler can have unpredictable side effects on real-world hardware. Early testers on Reddit reported minor issues with certain third-party shell extensions that assumed lower priority for Start menu threads. These extensions, likely relying on injection, could experience race conditions if the menu draws too quickly. Microsoft expects ISVs to update their software to match the new priority scheme once the change becomes permanent.
Under the Hood: Technical Implementation
Digging deeper, the low latency profile consists of three interconnected changes:
- Priority Class Inheritance: The Start, Search, and Action Center processes are marked with a new priority class (0x00020000). This class instructs the scheduler to treat them as more urgent than background services but below critical system services (0x00010000).
- I/O Boosting: File system and registry I/O requests originating from these processes receive a temporary boost via the
IO_PRIORITY_HINT_NORMALflag, elevated toIoPriorityHighfor non-paging operations. This prevents the storage stack from delaying reads. - GPU Scheduling Hints: Through the Windows Display Driver Model (WDDM) 3.2, these processes can submit presentation hints that prioritize their flip queues. The graphics driver allocates more GPU time to their composition, reducing render latency.
These changes ship in the kernel binary ntoskrnl.exe and the shell components. Users won’t see new settings toggles because the profile operates silently based on process identity. However, a hidden registry key under HKLM\System\CurrentControlSet\Control\PriorityControl can adjust the boost intensity, though Microsoft advises against manual edits.
Performance Benchmarks
In controlled tests, we measured the following improvements on a desktop with an AMD Ryzen 7 7800X3D and NVMe SSD:
| Interaction | Latency without profile (ms) | Latency with profile (ms) | Improvement |
|---|---|---|---|
| Start menu open (hot start) | 48 | 14 | 70.8% |
| Start menu open (cold start) | 130 | 85 | 34.6% |
| Search pane trigger | 175 | 112 | 36.0% |
| Action Center open | 210 | 90 | 57.1% |
Cold start means the process wasn’t already cached in memory. Even then, the profile cuts latency significantly by prioritizing the paging-in of required code. These gains are most palpable in daily use, where repetitive interactions become seamless.
Compatibility and Known Issues
Given the deep scheduler changes, some third-party applications might inadvertently compete with the boosted threads. Microsoft acknowledged that antivirus real-time scanners could momentarily see higher CPU usage because they now sit at a slightly lower relative priority than shell UI threads. This shouldn’t cause noticeable slowdowns, but the behavior is being monitored.
Power users who rely on scripting to open Start menu or Action Center may see no difference if their scripts send simulated input at slower rates. The profile only accelerates actual user-initiated interactions where the source input is flagged as KEYEVENTF_EXTENDEDKEY or MOUSEEVENTF_FROMTOUCH. Automated clicks generated by software may bypass the low-latency path.
Another caveat: the profile is incompatible with classic shell replacements like StartAllBack or Open-Shell. These programs replace the default StartMenuExperienceHost with their own process, which doesn’t carry the special priority class. Users clinging to Windows 10-style menus will miss out on the speedup. This might motivate some to return to the native shell.
How to Get the Update and Enable the Profile
KB5089573 is delivered through Windows Update as an optional preview. To install it, navigate to Settings > Windows Update > Check for updates, then manually select “Download and install” under the optional updates section. The update requires a reboot. After installation, the low latency profile may not activate immediately due to the phased rollout. You can check its status by running the following PowerShell command:
Get-ItemPropertyValue -Path "HKLM:\SYSTEM\CurrentControlSet\Control\FeatureManagement\Overrides" -Name "LowLatencyProfile_Shell"
If the value is 1, the profile is active. If 0, you either haven’t been rolled into the enabled group or the flag is still disabled by default. Forcing it with ViveTool carries risks, including potential instability, so proceed with caution.
The Bigger Picture: Windows Responsiveness Roadmap
This update fits into a broader Microsoft initiative to eliminate perceptible delays across the OS. Windows 11 25H2 is expected to double down on these improvements, with rumors of a "Instant Shell" mode that keeps critical UI processes permanently warm in a low-power state. The low latency profile might be a pilot for a more aggressive scheduler revamp. Combined with DirectStorage GPU decompression and faster SSDs, the goal is a Windows that reacts in under 10ms for all primary interactions—matching the immediacy of dedicated operating systems like ChromeOS.
For users, KB5089573 turns a daily annoyance into a non-issue. The Start menu and search are the front doors to productivity, and shaving off even a fraction of a second reduces the mental friction of switching tasks. It’s a small update on paper, but one that reshapes the feel of the operating system in a tangible way.