Windows 11 Low Latency Profile: What It Actually Changes for Gamers

Benchmark results are in, and they are anticlimactic. Cyberpunk 2077, Call of Duty: Modern Warfare III, and Counter-Strike 2 all show zero measurable FPS difference with Windows 11’s new Low Latency Profile active. The feature, introduced in the June 9 KB5094126 update, does nothing for your frame rates. But the same update quietly fixes a BSOD crash that has been killing games with kernel-level anti-cheat since May, and that fix alone makes it worth installing today.

What the Low Latency Profile Does (and Doesn’t Do)

The Low Latency Profile works by temporarily boosting your foreground process to HIGH_PRIORITY_CLASS and dropping the global timer resolution from 15.6ms to roughly 1ms whenever you interact with the Windows desktop. That burst lasts between 1 and 3 seconds (controlled by a registry key called BurstDurationMs) and then disengages.

In practice, this means the Start menu opens faster. Search results appear snappier. The Action Center feels more responsive. Microsoft’s official KB5094126 release notes describe it as accelerating “app launch and core shell experiences such as Start menu, Search, and Action Center.”

Here is the part that matters for gamers: the profile disengages during full-screen DirectX applications. It does not alter GPU scheduling, shader compilation, render pipeline latencies, or anything related to Game Mode. Independent benchmark testing by WindowsNews confirmed this across three separate titles. With the profile enabled, FPS counters in every tested game stayed identical to baseline runs.

If you saw headlines about a “CPU boost for gaming” and rushed to update expecting higher frame rates, the honest answer is that this feature helps your desktop experience between game sessions, not the sessions themselves.

Why “Low Latency” Misled Gamers

The name is the problem. “Low Latency” sounds like exactly what competitive players chase. Pair it with “CPU boost” in a headline and the hype writes itself.

In audio production, the profile does deliver real results. Round-trip latency in DAW testing dropped from 30ms to under 10ms on compatible hardware, an 18% reduction at a 128-sample buffer size. Music producers running DAWs alongside their game sessions will notice smoother audio pipelines. Discord voice quality may also benefit from the tighter timer resolution during desktop use.

But “latency” in this context means UI response time and audio pipeline delay, not network ping or frame delivery. The profile is not a replacement for NVIDIA Reflex. It will not lower your ping to game servers. It has no relationship to frame pacing or input lag inside a running game. Those are separate systems entirely.

For competitive players who alt-tab between matches, the profile does make Windows feel noticeably snappier outside the game window. After 20 years working in IT operations, I can say this is genuinely useful for anyone who runs monitoring tools, Discord, and a browser alongside their game. The tabbing in and out feels tighter. That is a legitimate quality-of-life improvement, just not the performance headline that social media implied.

The BSOD Fix That Actually Matters for Gamers

The previous cumulative update, KB5089573 (released in May), introduced a race condition in the Windows hypervisor. When games with kernel-level anti-cheat launched, the system would sometimes access Virtual Device (VDEV) descriptors incorrectly during secondary level address translation (SLAT) operations. The result was a blue screen with stop code HYPERVISOR_ERROR (0x20001) or KMODE_EXCEPTION_NOT_HANDLED (0x1E).

Valorant players running Riot Vanguard were hit hardest. Reports on Microsoft’s Q&A forums showed the crash could trigger during game launch, mid-match, or when resuming from sleep with the game still running in the background. Games using EasyAntiCheat (Fortnite, Apex Legends, Rust, Dead by Daylight) triggered the same crash on certain hardware configurations, particularly systems with Intel VT-x/VT-d enabled.

KB5094126 specifically resolves this race condition. Microsoft’s release notes confirm the fix targets VDEV descriptor access patterns during S-power state transitions and SLAT scenarios. In plain terms: the hypervisor no longer gets confused about memory mappings when a kernel-level anti-cheat driver is active alongside virtualization features.

This is a binary fix. Either you were getting these BSODs or you were not. If you have been crashing with HYPERVISOR_ERROR since the May update, KB5094126 is the direct patch.

If the crash fix solved your stability problem but online games still feel sluggish, the bottleneck might be your network route to the game server.

Still Crashing After the Update

Some users report that BSODs persist even after installing KB5094126. In most of these cases, the crash stems from a separate compatibility conflict between the anti-cheat driver, Intel virtualization hardware, and the GPU driver, rather than the specific regression that the update patches.

If you still see HYPERVISOR_ERROR after updating:

1. Update Intel chipset drivers from your motherboard manufacturer’s support page or through Intel Driver & Support Assistant. Outdated chipset drivers are the most common remaining trigger.
2. Clean reinstall your anti-cheat. Uninstall Vanguard or EasyAntiCheat completely, restart your PC, then relaunch the game so it reinstalls a fresh copy of the driver.
3. Run DDU (Display Driver Uninstaller) in Safe Mode and perform a clean GPU driver installation. Leftover driver fragments from previous versions can conflict with the hypervisor fix.
4. Toggle VT-d in your BIOS. Some motherboards have VT-d disabled by default, and cycling it off then on (or the reverse) after the update has resolved the crash for a subset of users running Intel 12th through 14th gen processors.
5. Check your RAM with Windows Memory Diagnostic or MemTest86. A failing DIMM can produce the same HYPERVISOR_ERROR stop code through an entirely different mechanism.

If the crash only happens with one specific game but not others, the issue is almost certainly the anti-cheat driver version rather than the Windows update itself. Reinstalling that game’s anti-cheat is the targeted fix.

GPU Drivers to Pair With KB5094126

The Windows update alone is not enough for a fully stable June 2026 gaming setup. Both NVIDIA and AMD released driver updates in early June that address complementary problems.

NVIDIA GeForce Hotfix 610.52 (released June 8) fixes a G-Sync frame pacing bug on RTX 40 series cards that caused visible micro-stutters at high refresh rates. It also resolves two Smooth Motion issues, an EDID bug that misidentified monitors as “NVIDIA NV-Failsafe,” a monitor wake-from-sleep failure, and a game-specific crash in World of Warcraft. The full hotfix notes from NVIDIA classify it as a beta driver, so install it only if you are experiencing one of these specific issues. Otherwise, wait for the next Game Ready Driver. We covered this in detail in our NVIDIA 610 driver fix guide.

AMD Adrenalin 26.6.1 (released June 4) fixes crashes in Subnautica 2 and Marvel Rivals on RX 9000 series cards, resolves artifact rendering in Enshrouded on RX 6000 cards, and adds support for the new RX 9070 GRE. It also patches a bug where zero RPM fan mode re-enabled itself after a monitor went to sleep. AMD’s release notes list one known remaining issue: intermittent crashes in Battlefield 6 on Ryzen AI 9 HX 370 hardware.

The combination of KB5094126 plus the correct GPU driver for your card covers the widest range of stability issues from this month.

Verifying the Low Latency Profile on Your System

The profile is rolling out gradually and may not be active on your system yet. There is no official toggle in Windows Settings, and no indicator shows whether it is running.

To force-enable it:

1. Download ViveTool from its GitHub releases page and extract it to a folder.
2. Open an elevated Command Prompt (Run as Administrator).
3. Run: vivetool /enable /id:58989092
4. Restart your PC.

To confirm the profile is working, open HWiNFO and watch your CPU core frequencies while clicking the Start menu or opening Search. You should see a brief frequency spike lasting 1 to 3 seconds, then a drop back to normal idle clocks. Task Manager refreshes too slowly to capture these bursts consistently, so a dedicated hardware monitor is necessary.

If the feature was already enabled on your system through the gradual rollout, running the ViveTool command is harmless. It simply ensures the feature flag stays active.

With your OS and GPU drivers current, the remaining lag variable for online play is almost always the network path between you and the server.

Install It for the BSOD Fix, Keep FPS Expectations in Check

KB5094126 is a clear install for every gamer running Windows 11 24H2 or 25H2. The anti-cheat BSOD fix is the headline reason. If you play Valorant, Fortnite, Apex Legends, Rust, Dead by Daylight, The Finals, or any other game with kernel-level anti-cheat, the HYPERVISOR_ERROR regression from May is now patched.

The Low Latency Profile is a bonus for desktop responsiveness. It will not raise your FPS, but it makes alt-tab workflows and UI interactions feel measurably faster between matches.

After installing:

1. Pair the update with your GPU vendor’s latest driver (NVIDIA 610.52 hotfix or AMD Adrenalin 26.6.1).
2. Confirm the update installed: open Settings > Windows Update > Update history and look for KB5094126 in the list.
3. Optionally, force-enable the Low Latency Profile with ViveTool if it has not rolled out to your system yet.

If your multiplayer ping stays high even after sorting out your OS and drivers, the issue is almost always routing between your ISP and the game server. No Windows update can fix that. Our Windows 11 gaming optimization guide covers the remaining OS-level settings worth changing, and our network adapter settings walkthrough handles the hardware side.