Windows 11 Memory Integrity FPS Impact: What Changes

Microsoft will begin switching on Memory Integrity, along with Virtualization-based Security where it isn't already running, on eligible Windows 11 machines through next month's Patch Tuesday update. That's according to Peter Waxman, a group program manager at Microsoft, whose comments on the rollout were reported by The Verge yesterday, with the October timing confirmed by OC3D yesterday.

The feature has existed, but stayed optional, since Windows 10. Gamers have spent years switching it off in pursuit of extra frames per second, a habit well documented by OC3D yesterday.

Coverage of the announcement has centered on the Windows 11 Memory Integrity FPS impact, and the reporting behind those headlines raises two distinct questions: whether older hardware takes a real frame-rate hit, and whether the feature breaks legacy drivers. Here's what's changing, who it touches, and how to check or override it.

What Memory Integrity does, and why Microsoft is turning it on now

Memory Integrity, also called Hypervisor-Protected Code Integrity or HVCI, runs inside Virtualization-based Security. It uses a CPU's own virtualization hardware to verify kernel-mode drivers in an isolated environment before they're allowed to execute, an environment Windows itself can't reach into directly (OC3D, yesterday; PCMag, yesterday). Kernel-mode drivers are subject to that check; ordinary applications are not.

The point of all this is closing off a specific attack path: malware exploiting an old, poorly secured driver to reach the kernel, where it can then run largely unchecked (PCMag, yesterday).

Waxman frames the October rollout as part of Microsoft's "secure by design and secure by default" push, noting the updates will also enable VBS where it isn't already active, "helping make additional security capabilities available" (The Verge, yesterday). Waxman's statement refers separately to enabling Memory Integrity and VBS, while the wider coverage uses the names inconsistently. OC3D, for instance, describes Memory Integrity, VBS, and HVCI as effectively several names for the same feature (OC3D, yesterday). Readers troubleshooting a specific toggle should know both descriptions circulate, and check Microsoft's own documentation rather than assume the terms map onto each other exactly.

Does Memory Integrity reduce FPS on Windows 11?

Yes, conditionally. Microsoft has previously acknowledged the kernel-level check can affect performance on some hardware, and that caveat carries into the October announcement itself (The Verge, yesterday).

The drop, where it happens, shows up mainly in CPU-limited games rather than titles where the graphics card is doing most of the heavy lifting, according to OC3D's reporting (OC3D, yesterday).

Chip generation is the dividing line. PCMag reports that Intel processors from the 7th generation onward, and AMD Ryzen chips from the Zen+ (2000-series) generation onward, include hardware acceleration that leaves "almost no" measurable difference with Memory Integrity switched on. Older processors, lacking that acceleration, are the ones most likely to see a real dip (PCMag, yesterday).

Which PCs are eligible for automatic Memory Integrity enablement?

OC3D reports the automatic-enablement criteria as:

• Intel 8th-generation processor or newer
• AMD Zen 2 or newer
• Qualcomm Snapdragon 8180 or newer
• At least 8GB of RAM
• At least 64GB of SSD storage
• Virtualization enabled in firmware
• Drivers already confirmed compatible with Memory Integrity

(OC3D, yesterday)

PCMag describes that spec sheet as covering "pretty much any PC purchased in the past five or six years, and even some that are older than that" (PCMag, yesterday).

For Intel and AMD systems, the reported auto-enable thresholds land newer than the processor generations PCMag associates with minimal performance impact: Intel's 8th-generation requirement comes after the 7th-generation cutoff PCMag cites, and AMD's Zen 2 requirement comes after the Zen+ generation PCMag says produces "almost no" measurable difference. The supplied reporting doesn't establish the same comparison for Qualcomm hardware, and neither Microsoft nor the outlets covering this say whether that overlap on Intel and AMD chips was deliberate.

None of the reporting reviewed here includes game-by-game benchmark results for this rollout. The performance claims from Microsoft and the outlets covering it are directional, tied to hardware generation rather than measured FPS deltas, since the update hasn't shipped yet.

The compatibility risk behind the FPS headlines

Beyond frame rates, PCMag flags a separate risk: older drivers that interact with memory in insecure ways may be blocked from loading once Memory Integrity is active, potentially disabling hardware or the software tied to it (PCMag, yesterday).

The eligibility rules are supposed to help here too. OC3D reports that automatic enablement requires drivers already confirmed compatible with Memory Integrity (OC3D, yesterday). That requirement should cut down on conflicts, though the reporting doesn't confirm how well it works once the update actually lands.

A separate incident from last month is worth knowing about, even without a confirmed link to Memory Integrity. In a security update issued last month, Microsoft said its ongoing investigation linked reports of ARC Raiders, MARVEL Tōkon: Fighting Souls, and THE FINALS becoming unresponsive or crashing to certain RGB-capable peripherals or internal components, some of which installed files resembling inpoutx64 (Microsoft Support, last month). The documented fix blocked that driver from loading on affected devices.

That incident predates the Memory Integrity rollout, and Microsoft's own writeup attributes it to RGB-related components, not to Memory Integrity or HVCI. It shows the kind of driver conflict a Windows update can trigger, though nothing in Microsoft's report ties this specific case to the feature at the center of October's changes.

Staying in control: checking, disabling, and the anti-cheat wrinkle

Devices that already have Memory Integrity turned off through Group Policy or a registry edit won't have it switched back on in October. Both The Verge and PCMag confirm Microsoft is honoring those explicit opt-outs (The Verge, yesterday; PCMag, yesterday).

Checking status takes under a minute. Search "Core Isolation" from the Start menu, or go to Windows Security, then Device security, then Core isolation details, where a toggle labeled "Memory integrity" shows whether it's currently on or off (The Verge, yesterday; PCMag, yesterday).

Turning it off remains possible after the update installs, but competitive gaming adds a wrinkle. OC3D points to Riot Games' published guide for enabling Memory Integrity as an example of a publisher recommending the feature for its anti-cheat protections (OC3D, yesterday). OC3D suggests Memory Integrity may become harder to avoid for competitive players if more games adopt similar requirements, though that remains a possibility raised by one outlet, not an established industry-wide trend.

For players who want extra frames without giving up the protection outright, Microsoft's own suggestion is a compromise: turn Memory Integrity off before a gaming session, then switch it back on afterward (The Verge, yesterday).

What to check before October's update lands

No source reviewed here provides an FPS percentage or a game-specific benchmark for this rollout, so any performance concern stays directional until real-world testing arrives after the update ships.

The more concrete move is a quick audit rather than a wait-and-see approach. Open Core isolation details and note whether Memory Integrity is already on. Anyone running older RGB peripherals, capture cards, or other niche hardware with vendor-specific drivers should flag that setup now, given how last month's driver conflict played out. If a specific game shows a frame-rate drop after the update installs, toggling Memory Integrity off and back on is currently the only way to isolate the cause, since no benchmark data exists yet to compare against.