Microsoft is preparing to broaden one of Windows 11’s kernel-level security protections, and the change is likely to revive an old question for PC users: how much performance should be traded for stronger default security?
Beginning in October 2026, the company plans to expand automatic Memory Integrity protection across more eligible Windows devices. The feature is not new, but wider enablement means more users could encounter its benefits, compatibility checks and possible performance effects without changing a setting themselves.
What changes in October
Microsoft says the October rollout will expand Memory Integrity across eligible devices with little or no additional configuration required from users. The company describes the move as a way to strengthen protection against sophisticated attacks at the kernel level while reducing the amount of security setup people have to manage manually.
Memory Integrity is built on Virtualisation-based Security, or VBS. Instead of trusting every part of the operating system equally, VBS uses hardware virtualisation to create an isolated environment that can protect sensitive security processes from code running in the normal Windows kernel. That separation is intended to make tampering harder even when an attacker gains a foothold elsewhere on the machine.
Why the feature matters below the desktop
Most Windows users never interact directly with the kernel, yet it is one of the most valuable targets on a PC because kernel-level code has extensive privileges. Memory Integrity, also known as HVCI, checks whether kernel-mode code meets integrity requirements before it is allowed to run in protected memory.
This matters because modern attacks do not always begin with an obvious malicious application. Vulnerable drivers, compromised software and low-level components can serve as entry points into the system. A stronger default at the kernel layer reduces the number of assumptions Windows has to make about code that already appears to be trusted.
For Microsoft, expanding the feature also fits a broader strategy of making security protections opt-out rather than opt-in on compatible hardware. That can raise the baseline for ordinary users, although it also increases the importance of good compatibility testing before a protection is enabled automatically.
Performance and compatibility are still part of the equation
Tom’s Hardware notes that Memory Integrity can affect performance on some systems, particularly older hardware where virtualisation support is less efficient. Microsoft’s own documentation similarly warns that incompatible applications or device drivers can malfunction when the feature is enabled.
That does not mean every gaming PC will suddenly slow down in October. Eligible systems are assessed for hardware capability and driver compatibility, and machines where users have already disabled Memory Integrity are not simply forced back into the setting. The effect also varies by workload, processor generation, drivers and the way a game uses CPU and system resources.
The practical issue is therefore less dramatic than a simple “security versus speed” argument. Users with recent hardware may notice little difference, while older systems or specialised peripherals can present more edge cases. The important point is to test before assuming either that the protection is cost-free or that it must be disabled for acceptable performance.
Browser gaming has a different resource profile
The performance discussion becomes even more nuanced when gaming moves from native applications into the browser. A large PC title with anti-cheat software, kernel drivers and heavy rendering has a very different system footprint from a lightweight web game that runs inside a browser tab.
That spectrum includes casual interactive products such as an online Plinko gambling game, which relies on a browser-based interface rather than the same low-level components used by many native PC games. The comparison does not make one format safer than another, but it shows why security settings cannot be judged only through the lens of high-end game benchmarks.
For users, browser activity still depends on the security of the operating system, browser and account environment beneath it. Kernel protection remains relevant even when the application itself never installs a driver, because the operating system is still responsible for isolating processes, memory and device access.
What PC users should check before changing anything
The most useful response to the October change is not to disable Memory Integrity pre-emptively. Users who encounter a problem should first check Windows Security, update device drivers and confirm whether a specific application or peripheral is actually incompatible. On modern hardware, the protection is designed to work with minimal intervention.
Gamers who benchmark their systems may also want to compare results before and after the rollout rather than relying on older tests from different hardware generations. A small performance difference in one title does not automatically translate into the same result across every game, browser workload or productivity application.
Microsoft’s wider enablement is ultimately a reminder that PC performance is no longer measured only in frames per second. Security features increasingly consume real hardware resources because they are doing real work. The challenge for Windows is to make those protections strong enough to matter while keeping the performance cost low enough that users have little reason to sw
