Microsoft’s May 26, 2026 optional Windows 11 preview update KB5089573 began rolling out a new performance mechanism, widely identified as Low Latency Profile, for Windows 11 version 24H2 and 25H2 systems on builds 26100.8524 and 26200.8524. The feature is simple in concept and politically revealing in practice: Windows briefly asks the CPU for more urgency when the shell needs to feel immediate. That makes Start, Search, Action Center, and related UI surfaces less likely to stumble at the exact moment users are paying attention. It also says something uncomfortable about Windows 11 in 2026: Microsoft is still trying to earn back the basic sensation of responsiveness.
For years, Windows performance complaints have lived in an awkward space between benchmark reality and user irritation. A modern Windows 11 PC can compile code, render video, run a game, and keep dozens of browser tabs alive, yet still make the Start menu feel like it had to think before appearing. That disconnect is precisely where Low Latency Profile matters.
Microsoft’s own release language for KB5089573 is restrained, describing a general performance improvement that accelerates app launch and core shell experiences such as Start, Search, and Action Center. The broader reporting around the update fills in the mechanism: short bursts of higher CPU frequency when Windows detects latency-sensitive user actions. In plainer English, Windows is trying to get the processor out of its comfortable idle state before the user notices the wait.
That may sound like a hack, and in one sense it is. But it is not necessarily a bad hack. Operating systems have long used scheduling, boosting, prefetching, and power-state nudges to hide latency from humans, because the human eye and hand do not care whether a delay came from a scheduler, a UI framework, a storage queue, or a processor taking too long to ramp up.
The meaningful change is that Microsoft appears to be acknowledging a specific category of Windows 11 pain: not absolute throughput, but interaction latency. A system can be fast and still feel bad. Low Latency Profile is aimed squarely at that gap.
The update applies to Windows 11 version 24H2 and 25H2, moving systems to OS builds 26100.8524 and 26200.8524 respectively. The eTeknix report focuses on build 26200.8524, but the Microsoft support page lists both builds under the same May 26 preview package. In other words, this is not merely a Canary-channel curiosity or a hidden Insider-only experiment; it has crossed into the preview lane for mainstream Windows 11 servicing.
The rollout is still staged. Even after installation, some users may not see the behavior immediately, because Microsoft uses controlled feature rollout machinery to enable new capabilities in waves. That staged model is now familiar to anyone who tracks Windows 11: the bits arrive, the switch may not flip, and users are left comparing notes about whether their supposedly identical builds behave identically.
That ambiguity is bad for communication but useful for risk management. Microsoft can slow or stop an enablement wave if telemetry shows regressions. The downside is that the Windows enthusiast community inevitably fills the silence with ViveTool IDs, screenshots, Task Manager graphs, and a cottage industry of “is it enabled yet?” diagnostics.
Modern processors are designed to sprint. They move between idle, low-power, and high-frequency states constantly, and a short burst can be more efficient than letting a task crawl along at a lower frequency. The industry phrase often used for this is race to sleep: finish the work quickly, then return to an efficient state.
That does not mean every implementation is wise. A CPU boost tied to the wrong signals could waste power, generate heat, or create contention with foreground workloads. But the basic idea of using brief frequency boosts for interaction-sensitive work is not exotic. Smartphones, laptops, macOS, Linux, and game consoles all live by variations of the same principle.
The controversy is less about the technique than the trust deficit. Windows 11 users have spent years watching Microsoft add web-backed surfaces, cloud hooks, AI entry points, and animated shell layers while also promising refinement. When the company then says it will make the OS feel faster by boosting the CPU, some users hear an admission that the software itself remains too heavy.
They are not entirely wrong. But they are not entirely right, either.
What it can do is reduce the penalty of waiting for hardware to ramp up when the shell needs an immediate response. That is valuable because many visible Windows delays are short enough to be infuriating but not long enough to show up in the way users usually discuss “performance.” A 150-millisecond hesitation can make a UI feel broken even if the system is technically under no sustained load.
The better way to understand this update is as one layer in a broader performance campaign. Microsoft has reportedly been pursuing Windows 11 responsiveness improvements under a larger internal push, with attention on shell reliability, app launch behavior, and the cost of modern UI surfaces. Low Latency Profile is the part users can feel quickly because it changes the timing of interaction.
The deeper work still has to happen elsewhere. If Start is too expensive to render, make it cheaper. If a shell flyout depends on too many services or delayed resources, reduce the dependency chain. If inbox apps carry too much overhead, slim them down. Frequency boosting can make Windows feel more eager, but it cannot be the only answer.
Windows 11’s Start menu has carried this burden since launch. Its centered layout, recommendation area, search integration, account surfaces, and cloud-adjacent behavior have all made it feel more like a live service endpoint than a small local launcher. Some of that criticism is aesthetic, but some of it is tactile: the menu has not always felt instant.
Low Latency Profile attacks the tactile problem. If Windows can anticipate that opening Start, Search, Action Center, or a context menu is a latency-sensitive operation, it can temporarily bias the system toward responsiveness. The user does not see the mechanism. The user sees a menu that appears with fewer dropped frames.
That is why early hands-on reports matter even if they are not laboratory-grade benchmarks. A smoother Start menu is not a synthetic score. It is the operating system interrupting the user less often. For Windows 11, which has spent much of its life defending design decisions users did not ask for, that kind of perceived improvement is unusually important.
The key variable is frequency. A short CPU burst when a user opens Start a few times an hour is trivial. A short CPU burst attached to many shell and app-launch events throughout a workday could be more noticeable, especially on thin-and-light machines already tuned aggressively for battery. The difference between “imperceptible” and “users complain by 3 p.m.” can be surprisingly narrow in corporate laptop fleets.
There is also the question of workload interference. If a developer is compiling, a call-center worker is running a softphone, or an analyst is driving a heavy spreadsheet, admins will want confidence that shell responsiveness boosts do not steal priority at the wrong time. Windows scheduling is mature, but every new heuristic is another path for edge cases.
Microsoft’s staged rollout is therefore more than theatrics. It gives the company time to see whether the feature behaves well across the messy diversity of Windows hardware. For IT departments, the practical advice is not to panic, but also not to treat optional preview updates as invisible. Test them on representative devices, especially battery-constrained laptops and systems with aggressive OEM power management.
ViveTool is useful because Microsoft’s controlled rollout model is opaque. It exposes feature IDs that are otherwise hidden behind staged enablement. For testers and forum regulars, that is part of the fun. For ordinary users, it is not a sane product story.
Microsoft has reasons for doing it this way. Feature flags reduce blast radius, allow A/B measurement, and let the company decouple code delivery from activation. Cloud services have operated this way for years. Windows is increasingly serviced like a cloud product even though it still runs on local hardware with local expectations.
The friction comes from the mismatch. A user thinks in terms of “I installed KB5089573.” Microsoft thinks in terms of “this device has the bits, but the flighting service may not have assigned the enablement state yet.” Those are both technically coherent statements, but only one of them makes sense to someone trying to understand why their Start menu still stutters.
The available evidence points mainly to shell and app-launch responsiveness, not a new gaming scheduler mode. Opening Start faster is not the same thing as reducing end-to-end input latency in a game. A CPU boost around shell flyouts does not automatically improve GPU-bound frame times, shader compilation, or driver overhead.
That said, gamers are not wrong to care. Windows shell behavior matters on gaming PCs because launchers, overlays, Game Bar, notification surfaces, anti-cheat services, and background tasks all live alongside games. A more responsive OS can make the desktop experience around gaming feel cleaner, even if it does not increase average FPS.
The risk is expectation inflation. If Microsoft or the press lets Low Latency Profile become a miracle cure narrative, disappointment will follow. The better claim is narrower and more credible: Windows 11 is beginning to prioritize the moments where small delays are most visible, and those moments include launching things and interacting with the shell.
There is no normal Settings toggle for it today. Once it is enabled for a system through rollout, it behaves as part of Windows. Enthusiasts can poke at it while the rollout is in progress, but Microsoft’s intended end state appears to be invisibility.
That is the right product instinct. The best version of this feature is not a checkbox called “Make Windows less annoying.” It is Windows simply responding faster. Users should not need to understand processor boost behavior to get a Start menu that opens smoothly.
Still, the lack of transparency has a cost. Power users want to know what changed, admins want documentation, and laptop owners want confidence that battery life is not being traded away in silence. Microsoft can keep the feature automatic while still explaining the policy, scope, and limits more clearly.
Part of the problem is that user expectations changed. Phones and tablets trained people to expect fluid animation and immediate touch response. High-refresh monitors made desktop stutter more visible. Even budget laptops now ship with SSDs, so the old excuses about spinning disks and low memory carry less weight.
Windows, meanwhile, has become a heavier environment. It is an operating system, a cloud account surface, a search front-end, a notification broker, a gaming platform, an AI host, a security boundary, and a compatibility museum. That breadth is Windows’ strength, but it also makes smoothness harder.
Low Latency Profile is therefore not merely a performance tweak. It is Microsoft conceding that responsiveness is a product feature in its own right. The OS cannot hide behind capability if the interaction layer feels hesitant.
That is a high bar. Windows runs on everything from premium workstations to bargain laptops with thin thermal envelopes and OEM-tuned firmware. A responsiveness heuristic that behaves beautifully on a Core Ultra machine may be less graceful on an older Ryzen laptop or a low-power education device. Microsoft’s telemetry will see more variation in a week than any reviewer can reproduce in a lab.
The other challenge is that smoother shell behavior may raise expectations faster than Microsoft can satisfy them. If Start improves but File Explorer still hangs on network paths, users will complain about Explorer. If Search appears faster but returns poor results, speed will not save it. If app launch bursts arrive but the apps themselves remain bloated, the first impression improves while the second impression still disappoints.
That is not an argument against the update. It is an argument for treating it as the beginning of a performance discipline, not the end of one.
Microsoft’s Low Latency Profile will not settle the long argument over whether Windows 11 is too heavy, too cloud-shaped, or too willing to solve design problems with scheduling tricks. But it does attack a real annoyance at the exact layer where users feel it, and that makes it more consequential than its modest changelog phrasing suggests. If Microsoft follows the same logic deeper into the shell — less waiting, less opacity, fewer excuses — Windows 11 may finally start to feel like an operating system tuned for the machines it already runs on, rather than one still asking for a little patience every time the user clicks Start.
Microsoft Finally Treats Stutter as a First-Class Bug
For years, Windows performance complaints have lived in an awkward space between benchmark reality and user irritation. A modern Windows 11 PC can compile code, render video, run a game, and keep dozens of browser tabs alive, yet still make the Start menu feel like it had to think before appearing. That disconnect is precisely where Low Latency Profile matters.Microsoft’s own release language for KB5089573 is restrained, describing a general performance improvement that accelerates app launch and core shell experiences such as Start, Search, and Action Center. The broader reporting around the update fills in the mechanism: short bursts of higher CPU frequency when Windows detects latency-sensitive user actions. In plainer English, Windows is trying to get the processor out of its comfortable idle state before the user notices the wait.
That may sound like a hack, and in one sense it is. But it is not necessarily a bad hack. Operating systems have long used scheduling, boosting, prefetching, and power-state nudges to hide latency from humans, because the human eye and hand do not care whether a delay came from a scheduler, a UI framework, a storage queue, or a processor taking too long to ramp up.
The meaningful change is that Microsoft appears to be acknowledging a specific category of Windows 11 pain: not absolute throughput, but interaction latency. A system can be fast and still feel bad. Low Latency Profile is aimed squarely at that gap.
The Optional Update Is Also a Public Test
KB5089573 is not a normal Patch Tuesday security update. It is a preview update, which means it is optional, arrives late in the month, and typically serves as a proving ground for fixes and feature work that may become broadly available in the following cumulative update cycle. That matters for admins and cautious users, because optional preview updates are where Microsoft often exposes the future before it becomes the default.The update applies to Windows 11 version 24H2 and 25H2, moving systems to OS builds 26100.8524 and 26200.8524 respectively. The eTeknix report focuses on build 26200.8524, but the Microsoft support page lists both builds under the same May 26 preview package. In other words, this is not merely a Canary-channel curiosity or a hidden Insider-only experiment; it has crossed into the preview lane for mainstream Windows 11 servicing.
The rollout is still staged. Even after installation, some users may not see the behavior immediately, because Microsoft uses controlled feature rollout machinery to enable new capabilities in waves. That staged model is now familiar to anyone who tracks Windows 11: the bits arrive, the switch may not flip, and users are left comparing notes about whether their supposedly identical builds behave identically.
That ambiguity is bad for communication but useful for risk management. Microsoft can slow or stop an enablement wave if telemetry shows regressions. The downside is that the Windows enthusiast community inevitably fills the silence with ViveTool IDs, screenshots, Task Manager graphs, and a cottage industry of “is it enabled yet?” diagnostics.
A CPU Spike Is Not the Scandal Some Think It Is
The most visible behavior reported by testers is a brief CPU utilization spike when opening shell elements such as Start or Action Center. On some systems, that spike can hit 100 percent on performance cores for a second or two before dropping back down. To a casual observer, that looks alarming; to a scheduler engineer, it is closer to a normal bargain.Modern processors are designed to sprint. They move between idle, low-power, and high-frequency states constantly, and a short burst can be more efficient than letting a task crawl along at a lower frequency. The industry phrase often used for this is race to sleep: finish the work quickly, then return to an efficient state.
That does not mean every implementation is wise. A CPU boost tied to the wrong signals could waste power, generate heat, or create contention with foreground workloads. But the basic idea of using brief frequency boosts for interaction-sensitive work is not exotic. Smartphones, laptops, macOS, Linux, and game consoles all live by variations of the same principle.
The controversy is less about the technique than the trust deficit. Windows 11 users have spent years watching Microsoft add web-backed surfaces, cloud hooks, AI entry points, and animated shell layers while also promising refinement. When the company then says it will make the OS feel faster by boosting the CPU, some users hear an admission that the software itself remains too heavy.
They are not entirely wrong. But they are not entirely right, either.
The Real Fix Is Not One Fix
Low Latency Profile should not be mistaken for a deep rewrite of Windows 11’s shell. It does not magically turn slow code into good code. It does not remove every framework boundary, eliminate every background service, or make every third-party application launch instantly.What it can do is reduce the penalty of waiting for hardware to ramp up when the shell needs an immediate response. That is valuable because many visible Windows delays are short enough to be infuriating but not long enough to show up in the way users usually discuss “performance.” A 150-millisecond hesitation can make a UI feel broken even if the system is technically under no sustained load.
The better way to understand this update is as one layer in a broader performance campaign. Microsoft has reportedly been pursuing Windows 11 responsiveness improvements under a larger internal push, with attention on shell reliability, app launch behavior, and the cost of modern UI surfaces. Low Latency Profile is the part users can feel quickly because it changes the timing of interaction.
The deeper work still has to happen elsewhere. If Start is too expensive to render, make it cheaper. If a shell flyout depends on too many services or delayed resources, reduce the dependency chain. If inbox apps carry too much overhead, slim them down. Frequency boosting can make Windows feel more eager, but it cannot be the only answer.
The Start Menu Is the Perfect Test Case Because Everyone Notices It
The Start menu is not the most computationally demanding thing most PCs do in a day. That is precisely why stutter there is so damaging. Users are remarkably tolerant of delay when they asked for something obviously hard; they are far less forgiving when the operating system hesitates while opening its own front door.Windows 11’s Start menu has carried this burden since launch. Its centered layout, recommendation area, search integration, account surfaces, and cloud-adjacent behavior have all made it feel more like a live service endpoint than a small local launcher. Some of that criticism is aesthetic, but some of it is tactile: the menu has not always felt instant.
Low Latency Profile attacks the tactile problem. If Windows can anticipate that opening Start, Search, Action Center, or a context menu is a latency-sensitive operation, it can temporarily bias the system toward responsiveness. The user does not see the mechanism. The user sees a menu that appears with fewer dropped frames.
That is why early hands-on reports matter even if they are not laboratory-grade benchmarks. A smoother Start menu is not a synthetic score. It is the operating system interrupting the user less often. For Windows 11, which has spent much of its life defending design decisions users did not ask for, that kind of perceived improvement is unusually important.
Battery Life Is the Unanswered Enterprise Question
The first wave of enthusiast testing has generally described the CPU boost as brief, visible, and not obviously catastrophic for thermals or battery life. That is encouraging, but it is not the same thing as fleet evidence. Enterprise IT will care less about whether one laptop feels smoother and more about whether thousands of laptops behave predictably across power plans, silicon vendors, docking states, and management policies.The key variable is frequency. A short CPU burst when a user opens Start a few times an hour is trivial. A short CPU burst attached to many shell and app-launch events throughout a workday could be more noticeable, especially on thin-and-light machines already tuned aggressively for battery. The difference between “imperceptible” and “users complain by 3 p.m.” can be surprisingly narrow in corporate laptop fleets.
There is also the question of workload interference. If a developer is compiling, a call-center worker is running a softphone, or an analyst is driving a heavy spreadsheet, admins will want confidence that shell responsiveness boosts do not steal priority at the wrong time. Windows scheduling is mature, but every new heuristic is another path for edge cases.
Microsoft’s staged rollout is therefore more than theatrics. It gives the company time to see whether the feature behaves well across the messy diversity of Windows hardware. For IT departments, the practical advice is not to panic, but also not to treat optional preview updates as invisible. Test them on representative devices, especially battery-constrained laptops and systems with aggressive OEM power management.
ViveTool Remains the Symptom of Microsoft’s Rollout Problem
The eTeknix piece notes that users can force activation with third-party tools such as ViveTool. That is true in the enthusiast sense, but it is also a reminder of how strange Windows feature delivery has become. Users install an update, read that a feature is included, and then may need an unofficial configuration utility to discover whether the feature is actually switched on.ViveTool is useful because Microsoft’s controlled rollout model is opaque. It exposes feature IDs that are otherwise hidden behind staged enablement. For testers and forum regulars, that is part of the fun. For ordinary users, it is not a sane product story.
Microsoft has reasons for doing it this way. Feature flags reduce blast radius, allow A/B measurement, and let the company decouple code delivery from activation. Cloud services have operated this way for years. Windows is increasingly serviced like a cloud product even though it still runs on local hardware with local expectations.
The friction comes from the mismatch. A user thinks in terms of “I installed KB5089573.” Microsoft thinks in terms of “this device has the bits, but the flighting service may not have assigned the enablement state yet.” Those are both technically coherent statements, but only one of them makes sense to someone trying to understand why their Start menu still stutters.
Gamers Should Temper the Victory Lap
The phrase “Low Latency Profile” is almost guaranteed to attract gaming attention. Latency is a sacred word in PC gaming, and any update promising less of it will be read as potentially relevant to frame pacing, input delay, and background interference. For now, that interpretation needs restraint.The available evidence points mainly to shell and app-launch responsiveness, not a new gaming scheduler mode. Opening Start faster is not the same thing as reducing end-to-end input latency in a game. A CPU boost around shell flyouts does not automatically improve GPU-bound frame times, shader compilation, or driver overhead.
That said, gamers are not wrong to care. Windows shell behavior matters on gaming PCs because launchers, overlays, Game Bar, notification surfaces, anti-cheat services, and background tasks all live alongside games. A more responsive OS can make the desktop experience around gaming feel cleaner, even if it does not increase average FPS.
The risk is expectation inflation. If Microsoft or the press lets Low Latency Profile become a miracle cure narrative, disappointment will follow. The better claim is narrower and more credible: Windows 11 is beginning to prioritize the moments where small delays are most visible, and those moments include launching things and interacting with the shell.
The Name Says More Than Microsoft Probably Wanted
Microsoft did not appear to lead the public KB page with the “Low Latency Profile” branding. Instead, the official language sits under general performance improvements. That is probably deliberate. “Low Latency Profile” sounds like a switchable mode, maybe something users could toggle, tune, benchmark, or blame.There is no normal Settings toggle for it today. Once it is enabled for a system through rollout, it behaves as part of Windows. Enthusiasts can poke at it while the rollout is in progress, but Microsoft’s intended end state appears to be invisibility.
That is the right product instinct. The best version of this feature is not a checkbox called “Make Windows less annoying.” It is Windows simply responding faster. Users should not need to understand processor boost behavior to get a Start menu that opens smoothly.
Still, the lack of transparency has a cost. Power users want to know what changed, admins want documentation, and laptop owners want confidence that battery life is not being traded away in silence. Microsoft can keep the feature automatic while still explaining the policy, scope, and limits more clearly.
Windows 11 Needed This Because “Fast Enough” Stopped Being Enough
The PC industry spent years selling users on raw performance: more cores, faster SSDs, better GPUs, more RAM. Windows 11 exposed the limits of that pitch. Many people moved to machines that were objectively powerful and still encountered UI roughness that made the system feel less polished than its specifications promised.Part of the problem is that user expectations changed. Phones and tablets trained people to expect fluid animation and immediate touch response. High-refresh monitors made desktop stutter more visible. Even budget laptops now ship with SSDs, so the old excuses about spinning disks and low memory carry less weight.
Windows, meanwhile, has become a heavier environment. It is an operating system, a cloud account surface, a search front-end, a notification broker, a gaming platform, an AI host, a security boundary, and a compatibility museum. That breadth is Windows’ strength, but it also makes smoothness harder.
Low Latency Profile is therefore not merely a performance tweak. It is Microsoft conceding that responsiveness is a product feature in its own right. The OS cannot hide behind capability if the interaction layer feels hesitant.
The Best Outcome Is That Nobody Talks About It Again
If Low Latency Profile works properly, the long-term result should be boring. Users should stop noticing stutter in common shell actions. Reviewers should stop having to qualify Windows 11 performance with “fast, but.” Admins should not need a new mitigation playbook. The feature should disappear into the baseline expectation of what Windows does.That is a high bar. Windows runs on everything from premium workstations to bargain laptops with thin thermal envelopes and OEM-tuned firmware. A responsiveness heuristic that behaves beautifully on a Core Ultra machine may be less graceful on an older Ryzen laptop or a low-power education device. Microsoft’s telemetry will see more variation in a week than any reviewer can reproduce in a lab.
The other challenge is that smoother shell behavior may raise expectations faster than Microsoft can satisfy them. If Start improves but File Explorer still hangs on network paths, users will complain about Explorer. If Search appears faster but returns poor results, speed will not save it. If app launch bursts arrive but the apps themselves remain bloated, the first impression improves while the second impression still disappoints.
That is not an argument against the update. It is an argument for treating it as the beginning of a performance discipline, not the end of one.
The May Preview Update Turns Smoothness Into a Servicing Issue
The most concrete facts around KB5089573 are straightforward, but their implications are larger than the changelog suggests. Microsoft is using the ordinary Windows servicing pipeline to ship a perceptual performance change, and that means the Windows “feel” is now something the company can tune month by month.- KB5089573 was released as a May 26, 2026 optional preview update for Windows 11 versions 24H2 and 25H2.
- The update moves Windows 11 24H2 systems to build 26100.8524 and Windows 11 25H2 systems to build 26200.8524.
- The Low Latency Profile behavior is designed to improve responsiveness for app launches and core shell surfaces such as Start, Search, and Action Center.
- Early reports describe brief CPU frequency or utilization spikes during latency-sensitive interactions, followed by a quick return to normal activity.
- The rollout is gradual, so installing the update does not guarantee every device will show the new behavior immediately.
- There is currently no ordinary Windows Settings toggle for users to enable or disable the feature.
Microsoft’s Low Latency Profile will not settle the long argument over whether Windows 11 is too heavy, too cloud-shaped, or too willing to solve design problems with scheduling tricks. But it does attack a real annoyance at the exact layer where users feel it, and that makes it more consequential than its modest changelog phrasing suggests. If Microsoft follows the same logic deeper into the shell — less waiting, less opacity, fewer excuses — Windows 11 may finally start to feel like an operating system tuned for the machines it already runs on, rather than one still asking for a little patience every time the user clicks Start.
References
- Primary source: eTeknix
Published: Fri, 29 May 2026 10:49:23 GMT
Microsoft Adds Low Latency Profile to Windows 11 to Remove System Stuttering
Microsoft has started rolling out a new performance improvement for Windows 11 designed to make the interface feel smoother. Called “Low Latency Profile,” the feature was discovered in the optional…www.eteknix.com - Related coverage: windowslatest.com
Windows 11 KB5089573 just made PCs more responsive, direct download links (.msu)
Windows 11 KB5089573 is a major update that bumps the OS to Build 26200.8524 and adds multiple new features.
www.windowslatest.com
- Related coverage: windowscentral.com
Windows 11's latest OS update is packing serious performance gains
Windows 11 update KB5089573 is now generally available as Microsoft's non-security preview update for May, and is packing genuinely notable performance improvements.
www.windowscentral.com
- Official source: support.microsoft.com
May 26, 2026—KB5089573 (OS Builds 26200.8524 and 26100.8524) Preview - Microsoft Support
support.microsoft.com
- Related coverage: notebookcheck.net
Windows 11 update KB5089573: Shared audio & partition fix
Microsoft's KB5089573 preview adds Shared Audio and NPU tracking to Windows 11, while flagging an EFI partition install failure on older OEM hardware.
www.notebookcheck.net
- Related coverage: windowsforum.com
Windows 11 KB5089573 Preview: Low Latency Profile Makes the Shell Feel Faster
Microsoft released the May 26, 2026 preview update KB5089573 for Windows 11 versions 24H2 and 25H2, moving PCs to builds 26100.8524 and 26200.8524 while beginning a staged rollout of performance, audio, camera, Task Manager, setup, search, USB, and reliability changes. The headline feature is...
windowsforum.com
- Related coverage: techspot.com
- Related coverage: tweaktown.com
- Related coverage: tomshardware.com
Microsoft staunchly defends its new 'Low Latency Profile' for Windows 11 after community backlash — says every other OS already boosts CPU speeds for quicker load times
The quest to fix Windows 11 is a bumpy one.www.tomshardware.com
- Related coverage: techradar.com
- Related coverage: pcgamer.com
'Let Windows cook': Microsoft defends new Low Latency mode and asks you 'see it yourself'
The new mode is reportedly snappier.www.pcgamer.com
- Official source: microsoft.com
- Related coverage: techrounder.com
