Gaming performance: How to fix FPS drops in Windows 11

Stuttering on a high-end PC running Windows 11? Your system is holding itself back. We'll show you the real FPS killers that have nothing to do with outdated bloatware. Learn how to disable VBS (core isolation)—the biggest FPS boost. We explain the Intel P/E-Core scheduler bug and provide a clear rule for HAGS (important for DLSS 3). Get your full performance back.

A high-end gaming PC sits on the desk. An RTX 4080, a brand-new Core i9 processor. And yet: games sometimes feel stuttery, benchmarks disappoint, and latency is higher than expected.

Many users then begin a frustrating search, disable dozens of Windows services, or download dubious "debloating" scripts.

The reality, however, is that Windows 11 represents a compromise "out of the box." Microsoft has placed a heavy focus on security, which comes at the cost of measurable performance in the default configuration.

This article debunks the myths surrounding Windows optimization. The assumption that disabling twenty services would magically boost FPS is simply false on modern systems. Instead, this analysis focuses on the real performance bottlenecks documented by Microsoft and hardware manufacturers.

The investigation of the Windows 11 system architecture reveals three main causes of performance issues:

1. VBS (Virtualization-Based Security): A security feature that is enabled by default and has been shown to impact game performance.
2. The Windows Task Scheduler: A software issue that can lead to catastrophic misallocations on Intel's modern hybrid CPUs (P-cores and E-cores).
3. HAGS (Hardware-Accelerated GPU Scheduling): A setting that is essential for modern graphics cards but can cause problems with older models or VR applications.

The gaming community often addresses the right symptom (poor performance) but with the wrong solution (unnecessary bloat reduction). This analysis clears up the confusion and shifts the focus to the actual causes.

The biggest FPS killer: Virtualization-Based Security (VBS) and memory integrity

By far the biggest performance bottleneck in Windows 11 is not a bug, but a feature. It is a set of security functions known as Core Isolation, Memory Integrity (HVCI), and Virtual Machine Platform (VMP).

Basically, Windows 11 places a virtual container (a "sandbox") around the core of the operating system. This mechanism is extremely effective at preventing attackers and malware from injecting malicious code into system-critical processes.

However, this protection comes at a measurable price.

The proof: Microsoft admits it itself

The key factor in the credibility of this analysis is that Microsoft has officially documented the performance issue. A (now-removed) Microsoft support document titled "Options to optimize gaming performance in Windows 11" confirms the issue.

Microsoft states that "in some scenarios and some configurations of gaming devices there may be a performance impact" due to memory integrity and VMP.

The company explicitly gives players who want to prioritize performance the option and instructions to disable these features. This is the "Game Mode" that Microsoft failed to explain prominently. These features are enabled by default on all new Windows 11 devices.

The real cost of this standard security feature is significant. Independent benchmarks show that the FPS loss in CPU-limited scenarios can range from 5 % to a staggering 25 %. A side effect confirms this: Users report that the CPU temperature drops after disabling the feature, which proves the reduced system load (overhead) caused by virtualization.

Practical guide: How to release the FPS brake

To unlock full performance, two settings must be changed.

1. Disable Memory Integrity (HVCI):
   • Open the Start menu and type 'Core isolation'.
   • Open the "Core isolation" result.
   • In the Windows Security window, set the switch for "Memory integrity" to 'Off'.
2. Disable Virtual Machine Platform (VMP):
   • Open the Start menu and type 'Windows features'.
   • "Select "Turn Windows features on or off".
   • Clear the check mark next to 'Virtual Machine Platform' in the list.

A system restart is strictly required for both changes.

The price of the open door

This deactivation has a clear downside that Microsoft explicitly points out: "if turned off, the device may be vulnerable to threats".

You actively sacrifice a portion of modern system security for higher framerates. For a dedicated gaming PC that is not used for online banking or sensitive emails, this may be an acceptable compromise.

This need to trust providers and platforms when one’s own system defenses (VBS) are deliberately lowered reflects a broader trend. Players who demand technical transparency in FPS benchmarks expect the same transparency when it comes to online services. The growing interest in clearly regulated and verifiable offerings—such as those provided by Plinko casinos for German players—highlights how important transparent mechanics and secure, compliant processes have become for users. If you lower your own PC’s "firewall" (VBS) for the sake of performance, you need to be able to trust that the "firewall" of the website you’re visiting is intact.

Intel's hybrid nightmare: When Windows confuses P-cores and E-cores

The second major performance bottleneck is not a feature, but a genuine software bug. It affects users of Intel's modern hybrid processors (12th, 13th, and 14th generation).

The theory: how it should work

Intel has revolutionized CPU design with its performance hybrid architecture. The concept is brilliant:

• Performance Cores (P-Cores): Fast cores that are reserved exclusively for the main application (the game).
• Efficient Cores (E-Cores): Efficient, slower cores that handle all background tasks (Discord, Windows Update, antivirus, streaming software).

Intel officially promises that this design enables "smoother gameplay" because the E-cores prevent background tasks from interfering with the game running on the P-cores. This is managed by the "Intel Thread Director" in conjunction with the Windows 11 task scheduler.

The practice: The 24H2 scheduler bug

The reality looks dramatically different for some users. Detailed reports in the Microsoft Tech Community from October 2024 document a "significant performance drop" on high-end CPUs like the 14900K.

The reason: The Windows Task Scheduler (in versions 23H2 and 24H2) makes a catastrophic error. It incorrectly assigns games and benchmarks to the slow E-cores, while the high-performance P-cores remain idle.

The measured drop in performance is dramatic. One user reports how their 3DMark TimeSpy score plummeted from a stable 24,000 points to under 20,000 points.

This malfunction turns the purpose of the E-core architecture on its head. The hardware designed to manage background tasks becomes an incalculable risk to the main application. This explains why some power users are frustrated and dismiss the E-cores as a "marketing gimmick." The problem is not the hardware, but the failure of the software (scheduler) to control it correctly.

As a last-resort workaround, affected users completely disabled the E-cores in the BIOS. The result: The FPS with only P-cores was higher than in the faulty hybrid mode using both P- and E-cores.

Solution approaches:

1. Diagnosis: Users should open the Task Manager while gaming (go to the "Performance" tab, change the CPU view to "Logical Processors") and check whether the utilization of the P-cores (the first 8–10 cores) is high and that of the E-cores is low. If it’s the other way around, the bug is present.
2. Solution: This is purely a software bug. The only permanent solution is to keep an eye on Windows Update and wait for a patch from Microsoft.

The HAGS dilemma (Hardware-accelerated GPU Scheduling): On or off?

The third important setting is "Hardware-accelerated GPU scheduling" (HAGS). This feature is designed to give the GPU more direct control over its own video memory (VRAM) and task scheduling, which theoretically relieves the CPU.

Many optimization guides blanket recommend enabling HAGS. However, a detailed benchmark analysis of 26 games (conducted by BabelTechReviews) reveals a complex picture.

• The reality: In most games, there were "no significant performance differences.".
• The Exceptions (Positive): In some titles, such as Metro Exodus, HAGS improved the stability of frame times (frame pacing).
• The Warning (Negative): In other games, such as Quake 2 RTX, HAGS caused "severe frametime stability and frame-pacing issues." HAGS is also known to cause instability in VR applications and trigger conflicts with hardware acceleration in apps such as Discord or web browsers.

The decisive factor: DLSS 3 Frame Generation

For owners of an NVIDIA RTX 40-series (e.g., 4060, 4070, 4080, 4090), the debate about HAGS is irrelevant. The "HAGS on or off" question is already decided for them.

HAGS is required for DLSS 3 Frame Generation to function.

If HAGS is disabled in the Windows graphics settings, the "Frame Generation" option remains grayed out in games such as Cyberpunk 2077 or A Plague Tale: Requiem and cannot be enabled.

Clear expert recommendation

The confusion surrounding HAGS can be resolved with a clear, two-part recommendation:

1. Owners of an NVIDIA RTX 40 Series GPU: HAGS must be enabled. This is non-negotiable if you want to use the GPU's core function (frame generation).
2. Owners of older GPUs (NVIDIA 30 Series / AMD) OR VR players: HAGS should be turned OFF. The potential performance gain is minimal or nonexistent, but the risk of stuttering, crashes, or VR instability isn't worth it.

Debloating 2024: What really helps and what is a waste of time

No Windows tweak guide is complete without the topic of "debloating." This is where the most myths circulate, ranging from "miracle scripts" to long lists of services that supposedly must be disabled.

The cold shower first: On a modern gaming system, the FPS gain from disabling services or removing UWP apps (Universal Windows Platform) is almost unmeasurable. Testimonials from power users confirm this: The difference is "1-2 fps... Nothing worth the struggle".

Nevertheless, "debloating" can be divided into three sensible categories:

1. dangerous & useless (Snake Oil)

Indiscriminately disabling dozens of Windows services using lists or scripts is the most common mistake. It does not bring any measurable gaming performance, but it can damage important system functions. For example, disabling the "Display Policy Service" can cause monitors above 60Hz to no longer be recognized correctly and block G-Sync/Freesync.

2. sensible & simple (system hygiene)

These tweaks might not give you an extra 20 FPS, but they do make the system more responsive:

• Disable startup programs: (Task Manager > Startup). Apps like Spotify, Discord, or OneDrive don't need to start when Windows starts.
• Reduce visual effects: (Start > "Appearance" > "Adjust Windows appearance and performance"). Select the "Adjust for best performance" option.
• Disable background apps (UWP): (Settings > Apps > Installed apps > [App Name] > Advanced options > Set "Background app permissions" to "Never").

3. meaningful & effective (real FPS levers)

Two Windows features have been shown to consume resources while gaming because they act as overlays:

• Turn off Xbox Game Bar: (Settings > Gaming > Xbox Game Bar > Set the toggle to "Off").
• Disable background recording (Captures): (Settings > Play > Recordings > Set "Record in the background while I play" to "Off").

Instructions for professionals: Bloatware Apps safely remove (PowerShell)

The real "bloat" isn't services, but pre-installed apps. Instead of a "black box" script (which could even be malware), individual PowerShell commands offer full control.

Start PowerShell as administrator, then:

• Remove Xbox Game Bar/Overlay:
  Get-AppxPackage *XboxGamingOverlay* | Remove-AppxPackage
• Uninstall Microsoft Solitaire Collection:
  Get-AppxPackage *MicrosoftSolitaireCollection* | Remove-AppxPackage
• Remove Microsoft Sticky Notes:
  Get-AppxPackage *MicrosoftStickyNotes* | Remove-AppxPackage

Table: Secure Windows services to deactivate

For users who have a PC used exclusively for gaming, there is a short list of services that can safely be disabled (Start > services.msc).

If you want to disable even more services, check this out.

Conclusion: The 3-step plan for maximum performance

The analysis shows that the chase for FPS in Windows 11 often goes in the wrong direction. The biggest bottlenecks are not bloatware apps, but systemic decisions and software bugs.

1. The biggest obstacle is a safety feature (VBS/VMP) that is enabled by default.
2. The second-biggest obstacle is a software bug (the scheduler) that undermines Intel's hybrid architecture.
3. Optimization depends on the situation (HAGS: Yes for DLSS 3, No for VR/older GPUs).

This results in a clear action plan for every gamer:

1. Priority 1 (The biggest FPS gain): Check "Core Isolation" (VBS) and "Virtual Machine Platform" (VMP). Disable them for maximum gaming performance, but be aware of the security risk.
2. Priority 2 (The DLSS 3 Check): Check "Hardware-accelerated GPU scheduling" (HAGS). (RTX 40 series = ON, all others = OFF).
3. Priority 3 (The Stuttering Check): For owners of an Intel hybrid CPU (12th Gen+) who are experiencing stuttering: Monitor the P/E-core allocation in Task Manager and hope for a Windows patch for the scheduler.
4. Priority 4 (System Maintenance): Disable the Xbox Game Bar and background recording, and clean up autostart.

Now the facts are on the table. The hunt for useless services can stop – it's time to tackle the real bottlenecks and unlock the full performance of the gaming PC.