Share via

Windows Low Latency Profile (security patch KB5094126) and Intel i7 13850HX causes severe lagging

Ed Morris 36 Reputation points
2026-06-16T10:14:24.09+00:00

The recently rolled out Windows Security update of June 2026, KB5094126, incorporated the Low Latency Profile feature which is designed to momentarily boost CPU clock speeds to improve system responses to things like start menu presses and application startups. However, on installing this update my computer immediately started to severely lag, taking minutes to open up task manager or do anything. What was immediately apparent was the 12 efficiency (non-hyperthreading) cores were continually maxed out at 100% usage. Only the removal of the patch and recovery of the windows OS through DSIM returned the system to normal. The patch was then reinstalled and the same issues returned, confirming it was this update patch. The issue does appear to be the thread handling and perhaps a conflict between these handling processes which appears to be introduced with the update. The current thinking is the Low Latency Profile feature. Have there been any other users reporting similar issues?

Windows for business | Windows 365 Enterprise
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Domic Vo 24,370 Reputation points Independent Advisor
    2026-06-16T10:55:20.8233333+00:00

    Hello Ed Morris,

    The severe system lag is tied to the June 2026 cumulative security update, KB5094126. Your analysis regarding the Low Latency Profile is accurate. On systems with hybrid processor architectures, the Windows Thread Director is misallocating the momentary frequency boosts meant for shell interactions entirely to the efficiency cores. This traps those cores at continuous maximum utilization, starving the operating system of resources for background tasks and causing the extreme unresponsiveness.

    Currently, this is a known bug without an official fix from Microsoft. Using the Deployment Image Servicing and Management tool, executed via C:\Windows\System32\dism.exe, to safely remove the package was the exact correct action to restore system stability without damaging core OS files. You should strictly avoid trying to force the update to work through undocumented modifications within the HKEY_LOCAL_MACHINE registry hive or by artificially disabling processor cores, as this compromises long-term system integrity. Your best course of action is to prevent the patch from automatically reinstalling while Microsoft develops a revised update. You can achieve this by opening your system Settings, navigating to the Windows Update section, and using the Pause updates feature to temporarily halt all installations for up to three weeks.

    Domic V

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.