Windows 11 Gaming 2026: 12 Steps to Stop Frame Drops

For most of its history, "optimizing Windows for gaming" was folklore. A bag of registry edits, a debloat script from a forum with a skull for an avatar, and the unshakeable belief that ending svchost would unlock a hidden 30 percent. Some of it worked. Most of it was cargo cult inherited from the days of trimming autoexec.bat and freeing conventional memory so a DOS game would deign to launch. All of it was mostly harmless, because Windows itself was a static target that only moved between service packs.

That is no longer the situation, and pretending otherwise is how you end up slower than when you started. This guide is a practical, reversible, twelve-step pass you can run in about ninety minutes, plus the deeper context you need to understand why each step exists and when it does nothing. Everything here can be undone. Nothing here requires you to trust a stranger's .bat file. And crucially, it treats the modern reality head-on: in 2026, optimizing Windows is less a one-time ritual and more an exercise in version control.

The 2026 State of Play

The reason this guide reads differently from a 2019 one is that the ground shifted twice in the space of two months at the end of 2025: once when Microsoft made a promise, and once when it broke a build.

Microsoft's five gaming buckets

In late 2025 Microsoft announced it wanted Windows 11 to be "the best place to play," and for once the statement arrived with an engineering agenda instead of a slogan. As reported by Windows Central on December 9, 2025 and echoed by Yahoo Tech the next day, the company named five concrete areas it intends to work through in 2026: background workload management, power, scheduling, the graphics stack, and drivers. That list is not marketing filler. It is, almost verbatim, the table of contents for this tutorial, which tells you the amateurs and the platform owner have finally converged on the same short list of things that actually move the needle.

Part of the same push is the extension of the Xbox Full Screen Experience to Windows PCs in 2026, including handhelds and 2-in-1 devices. It matters here for a boring, correct reason: a console-like shell that suspends the desktop reduces background overhead during a play session, which is the single most reliable way to claw back frametime consistency. Microsoft continues to headline the platform capabilities it has leaned on for years, too. DirectStorage, Auto HDR, and DirectX 12 Ultimate are all still framed as core Windows 11 gaming features, and the company's consumer-facing Windows 11 gaming page was refreshed as recently as March 29, 2026. That last detail is the tell: Microsoft is maintaining its gaming guidance as a living document, not a launch-day artifact.

The KB5066835 wake-up call

Now the part where the promise met reality. Two months before Microsoft pledged to make Windows the best place to play, it shipped a cumulative update that made games measurably worse. The October 2025 update, KB5066835, was flagged by NVIDIA as capable of reducing performance in some titles, a story Yahoo Tech ran on December 1, 2025. WindowsLatest reported on November 20, 2025 that the affected systems were running Windows 11 24H2 build 26100.6899 and 25H2 build 26200.6899 or newer, and a follow-up on December 1 noted that gamers were seeing frame drops from a Windows update Microsoft had not yet acknowledged, even as NVIDIA had already pushed a hotfix driver to paper over it. Gigazine's December 4, 2025 coverage independently named KB5066835 as the culprit behind significant performance loss in certain games.

Read that sequence again, because it is the entire thesis of modern PC tuning. Microsoft shipped the regression. Microsoft had not acknowledged it. The fix arrived from a GPU vendor's hotfix, keyed to specific build numbers. If you did not know your build number, you could not know whether you were exposed, and no amount of toggling Game Mode would have told you.

What "optimization" means now

So here is the reframe. Optimizing Windows 11 for gaming in 2026 is no longer only about the on-off switches in the Gaming settings pane. It is about knowing your exact build and revision, matching your driver to it, watching cumulative updates the way a sysadmin watches a change log, and only then applying the durable, boring settings that have always helped: correct power plan, correct GPU scheduling, no background capture stealing frametime, and the right GPU doing the work. Twelve steps do the durable part. The reading around them keeps you out of the KB5066835 trap. Let's begin with what you need on the bench.

Prerequisites: Builds, Drivers, Hardware

Every good tutorial front-loads the requirements so you do not get four steps in and discover your NVMe is actually a SATA drive in a trench coat. Read this section before you touch anything.

Hardware baseline

Windows 11 already imposes a floor: a 64-bit CPU with two or more cores, TPM 2.0, UEFI with Secure Boot capability, 4 GB RAM minimum (treat 16 GB as the real floor for gaming, 32 GB if you stream or keep a browser hostage in the background). For the gaming-specific features this guide leans on, you want more than the OS minimum:

• GPU: a DirectX 12 Ultimate-class card with Shader Model 6.0 support. Any recent GeForce RTX, Radeon RX, or Intel Arc qualifies. This is the prerequisite for DirectStorage GPU decompression and for hardware-accelerated GPU scheduling behaving well.
• Storage: an NVMe SSD for your games library if you want DirectStorage to mean anything. DirectStorage will run on slower storage, but the entire point is the high-throughput NVMe path.
• Display: a variable-refresh-rate panel (G-Sync, G-Sync Compatible, or FreeSync). VRR is doing more for your perceived smoothness than most registry edits ever will. If you are still deciding on resolution and refresh, our breakdown of why 1440p usually wins over 4K is worth ten minutes before you commit.
• Power: on a desktop, none of this matters. On a laptop or handheld, plug it in. Every scheduling and power step below assumes AC power; on battery, Windows will overrule you and it is right to.

Software versions you need

Pin these down before starting. Guessing here is how the KB5066835 crowd got burned.

• Windows 11 24H2 (build 26100.x) or 25H2 (build 26200.x). Know your exact revision (UBR). The known-bad regression window was 24H2 26100.6899 and 25H2 26200.6899 or newer, paired with a stale driver.
• The current GPU driver, matched to your build. For NVIDIA that means the latest Game Ready or Studio driver, or the specific hotfix if you are inside a known regression window, all available from NVIDIA's driver page. AMD users want the current Adrenalin; Intel users the current Arc driver.
• Display Driver Uninstaller (DDU), latest release, for clean driver swaps. This is the one third-party tool this guide trusts, and only because it does exactly one thing and does it correctly.
• An elevated terminal. Windows PowerShell 5.1 ships in the box; PowerShell 7.x is fine too. Every command below assumes you launched it as Administrator.

Snapshot before you start

Before a single value changes, take a rollback point and record your build. This is not optional. It is the difference between "I undid it" and "I reinstalled Windows."

# Elevated PowerShell. Create a rollback point before anything else.
Enable-ComputerRestore -Drive "C:\"
Checkpoint-Computer -Description "Pre-gaming-tune" -RestorePointType MODIFY_SETTINGS

# Read the exact build and revision (UBR) you are running.
Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion" |
  Select-Object ProductName, DisplayVersion, CurrentBuild, UBR

If Checkpoint-Computer complains, System Protection is off for the drive; the Enable-ComputerRestore line above turns it on. Write down the four numbers that command returns. You will compare them against the KB5066835 range in the next section, and against every future update for the rest of this machine's life.

The 12-Step Optimization Pass

Here is the pass itself: twelve steps, each with the reason it exists, grouped so you can do them in sittings. Do them in order. Reboot when a step says to. Do not skip ahead to step 11 and disable your security because a stranger on the internet said it was worth five percent, because a different stranger on the internet is about to explain the trade-off properly.

Steps 1 to 4: Foundation

The foundation is about being on a known-good software stack and a power profile that does not park your cores mid-firefight.

1. Verify your build, then pause updates. Run the build check from the prerequisites. If your revision sits in or near the KB5066835 window (24H2 26100.6899, 25H2 26200.6899 or newer), you must confirm your GPU driver is the hotfix or later before trusting any benchmark. Once you are on a stable pairing, pause Windows Update from Settings so a surprise cumulative does not silently reintroduce a regression the night before a session. Rationale: a specific build broke games in 2025; treating updates as automatic and invisible is precisely how that hurt people.
2. Do a clean GPU driver install with DDU. Download the target driver first. Then boot into Safe Mode, run Display Driver Uninstaller, choose "Clean and do not restart," and install the fresh driver on the clean boot. Rationale: layered driver installs accumulate stale scheduling and control-panel state, and the NVIDIA hotfix response of late 2025 is the textbook case for why the driver, not just the OS, is where a fix often lives.
3. Enable the Ultimate Performance power plan. This unhides and activates a plan that disables core parking and holds clocks up, trading a little idle power for latency consistency.

   # Import and activate the hidden Ultimate Performance plan.
   powercfg -duplicatescheme e9a42b02-d5df-448d-aa00-03f14749eb61
   powercfg -setactive e9a42b02-d5df-448d-aa00-03f14749eb61
   
   # Confirm it took.
   powercfg -getactivescheme

   Rationale: parked cores and aggressive downclocking add micro-stutter under bursty game loads; on a desktop the power cost is irrelevant.
4. Turn on Game Mode and set your display baseline. In Settings, enable Game Mode, then set your monitor to its native resolution and highest refresh rate, and confirm VRR is available. Rationale: Game Mode nudges the scheduler to deprioritize background work during play; it is one bucket of five, not the whole job, which is exactly why people who "just use Game Mode" plateau.

Steps 5 to 8: The graphics stack

This block is the graphics stack and background workload buckets from Microsoft's own list, done by hand.

5. Enable Hardware-Accelerated GPU Scheduling (HAGS). This moves frame queue management onto the GPU's own scheduler, which can reduce latency and CPU overhead on modern hardware.

   # Hardware-Accelerated GPU Scheduling: 2 = on (reboot required).
   Set-ItemProperty "HKLM:\SYSTEM\CurrentControlSet\Control\GraphicsDrivers" -Name HwSchMode -Value 2 -Type DWord
   
   # Stop background game recording (a silent frametime tax).
   Set-ItemProperty "HKCU:\System\GameConfigStore" -Name GameDVR_Enabled -Value 0 -Type DWord
   New-Item "HKLM:\SOFTWARE\Policies\Microsoft\Windows\GameDVR" -Force | Out-Null
   Set-ItemProperty "HKLM:\SOFTWARE\Policies\Microsoft\Windows\GameDVR" -Name AllowGameDVR -Value 0 -Type DWord

   Rationale: HAGS is a scheduling and graphics-stack change in one; it helps on current GPUs with current drivers and is trivially reversible if a title misbehaves.
6. Kill Game DVR and background capture. The registry values above do it non-interactively; the equivalent lives in Settings under Gaming, Captures. Rationale: continuous background recording is a real, measurable frametime cost that most people never asked for and never notice draining their 1% lows.
7. Assign the correct GPU per game. In Settings, System, Display, Graphics, add each game executable and set it to "High performance." On laptops this forces the discrete GPU; on desktops it makes the preference explicit. Decide fullscreen-optimizations per title rather than globally, because on Windows 11 it is what enables Auto HDR and faster alt-tab. Rationale: the most common "my expensive GPU is slow" ticket is a laptop quietly rendering on the integrated chip.
8. Configure the GPU control panel for latency. Set the power management mode to prefer maximum performance, enable the low-latency or Reflex path where the game supports it, and pair VRR with V-Sync forced on in the driver plus an in-game frame cap a few frames below your refresh ceiling. Rationale: this is the single best latency configuration for a VRR panel, and it matters more than any headline framerate number. If you are chasing input latency all the way to the peripheral, our gaming keyboard shootout covers the other end of the chain.

Steps 9 to 12: Background and latency

The last block trims contention and makes you measure instead of believe.

9. Prune startup and background apps. Open Task Manager's Startup tab and disable everything that does not need to launch with Windows: launchers, updaters, RGB suites, chat apps you open manually anyway. Rationale: every autostart process competes for CPU, disk, and interrupts at exactly the moment you are trying to load a game.
10. Set visual effects to performance. Run SystemPropertiesPerformance.exe, choose "Adjust for best performance," then re-enable font smoothing so your desktop is still legible. Turn off transparency. Rationale: the compositor overhead is small on modern hardware, but it is free to reclaim and it removes animation stalls on alt-tab.
11. Decide on VBS and Memory Integrity deliberately. Check whether virtualization-based security is running, then make an informed choice (the full trade-off is in the power and scheduling section below).

    # Is virtualization-based security actually running?
    Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard |
      Select-Object VirtualizationBasedSecurityStatus, SecurityServicesRunning

    Rationale: VBS has a real, measurable cost in some CPU-bound games, and a real security value; you should choose, not have the choice made for you by a debloat script.
12. Verify, then benchmark. Confirm the settings actually took, run a repeatable benchmark or a known-heavy scene before and after, and record 1% lows, not just averages. Rationale: optimization you did not measure is superstition. The whole reason the KB5066835 story is credible is that people measured the regression.

The Driver Stack and KB5066835

Steps 1 and 2 told you to verify your build and clean-install your driver. This section is the why and the how, because the driver stack is where 2025's most instructive gaming failure lived and got fixed.

How to read your build number

Windows version numbers look opaque until you learn the two parts that matter. CurrentBuild is the OS generation (26100 for 24H2, 26200 for 25H2). UBR, the Update Build Revision, is the cumulative-patch counter that ticks up every Patch Tuesday. Together they form the real version, and that pairing is what vendor advisories reference. Here is what a healthy read looks like:

ProductName        DisplayVersion CurrentBuild UBR
-----------        -------------- ------------ ---
Windows 11 Pro     24H2           26100        6899

That 26100.6899 is not a random example. It is the exact revision WindowsLatest named as inside the KB5066835 exposure window. If your machine reports that build with an older driver, you were, by definition, a candidate for the slowdown. This is why the build check is step 1 and not an afterthought: the number tells you whether the rest of the pass is being measured on stable ground or on quicksand.

Rolling back or getting the hotfix

You have two clean responses to a build-linked regression: move the driver forward to the vendor's fix, or move the OS back off the bad cumulative. Prefer the driver route, because that is where NVIDIA delivered the actual 2025 fix and because rolling back an LCU reopens whatever security holes it closed. If you do need to remove the update, know that recent cumulative updates frequently refuse the classic wusa path and report "not applicable," which sends people into a spiral. Use DISM or the GUI instead.

:: Classic route (frequently reports "not applicable" for cumulative LCUs)
wusa /uninstall /kb:5066835

:: Reliable route for a Latest Cumulative Update
dism /online /get-packages /format:table
dism /online /remove-package /packagename:Package_for_RollupFix~31bf3856ad364e35~amd64~~26100.XXXX

:: GUI fallback: Settings > Windows Update > Update history > Uninstall updates

The broader lesson, and the one worth internalizing, is that a GPU vendor update can matter as much as a Windows patch. In the KB5066835 episode the fix shipped through NVIDIA's driver channel while Microsoft had not yet publicly acknowledged the problem. Treat your driver version and your build number as a single coupled unit. If you are the kind of reader who tunes past stock, our companion pieces on GPU overclocking in twelve steps and the RTX 5090 review both assume you have already locked down a clean, current driver, because an unstable driver stack will masquerade as an unstable overclock every single time.

Clean installs with DDU

Layered driver installs are the sediment of PC gaming: each one leaves a little residue in the scheduling and control-panel state, and eventually the sediment is the problem. Display Driver Uninstaller strips it out. The correct ritual is deliberate: download your target driver first while you still have internet configured, disconnect from the network so Windows Update cannot slam a generic driver on you mid-process, boot into Safe Mode, run DDU with the "Clean and do not restart" option, then install your prepared driver on the clean boot and reconnect. Do this whenever you change GPU vendors, chase a regression, or inherit a machine whose driver history you do not trust. Do not do it every week; a clean stack does not get cleaner by being reinstalled, it just gets more of your Saturday.

Power, Scheduling, and VBS

Two of Microsoft's five named buckets for 2026 are power and scheduling. Both are settings you can control today, and one of them, virtualization-based security, is where the community gives the worst advice with the most confidence.

Ultimate Performance vs Balanced

The Balanced power plan is a compromise tuned for a laptop that wants battery life, and it expresses that compromise by parking cores and dropping clocks the instant load looks light. Games produce exactly the bursty, uneven load that confuses that heuristic, which shows up as micro-stutter and inconsistent 1% lows rather than a lower average. Ultimate Performance disables core parking and holds clocks up. On a desktop plugged into the wall, there is no downside worth the sentence it would take to describe it. On a laptop or handheld away from power, leave Windows on Balanced; it will overrule you anyway, and it is correct to, because the alternative is a dead battery in twenty minutes. If your interest in clocks and thermals runs deeper, the same discipline underpins our CPU undervolting walkthrough, which chases the opposite goal, lower voltage at the same clocks, and which pairs cleanly with a performance power plan.

Hardware-Accelerated GPU Scheduling

HAGS hands a chunk of frame-queue and memory management from the CPU-side WDDM scheduler to a dedicated processor on the GPU. On current hardware with a current driver it can shave CPU overhead and latency, which is why step 5 turns it on with HwSchMode set to 2. The honest caveat: the benefit is modest and occasionally a specific game or capture tool interacts badly with it. Because it is a single reversible value, the correct approach is to enable it, play your actual games, and set it back to 1 only if you observe a real problem rather than because a benchmark you do not run showed a rounding error. This is scheduling and graphics-stack tuning in one toggle, done by hand instead of waiting for the platform to do it for you.

The VBS and Memory Integrity tax

Now the part where The Machine knows the law. Virtualization-based security, and specifically Memory Integrity (Hypervisor-Enforced Code Integrity), runs your kernel behind a hypervisor boundary that blocks whole classes of driver-level and kernel-level attacks. It also has a measurable performance cost in some CPU-bound titles, historically in the mid-single-digit to low-double-digit percent range depending on the game and CPU. That cost is why every debloat script disables it, usually without a word about what it is for.

# Turn OFF Memory Integrity (HVCI). Read the trade-off first.
Set-ItemProperty "HKLM:\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity" -Name Enabled -Value 0 -Type DWord

# Nuclear option: stop the hypervisor entirely (kills Hyper-V, WSL2, Sandbox).
bcdedit /set hypervisorlaunchtype off

Here is the ruling. On a dedicated gaming desktop that stores no work credentials, touches no corporate network, and runs nothing you would mourn, disabling Memory Integrity is a defensible way to recover a few percent, and the commands above do it. On a machine that logs into a company VPN, holds a password manager, or is subject to any compliance regime, leave it on, full stop, because the second command in that block also disables Hyper-V, WSL2, and Windows Sandbox, and re-enabling security you turned off "for FPS" is a conversation nobody enjoys having with IT. Choose deliberately. That is the whole point of step 11: not to reflexively disable, but to know what you are disabling.

Background Workloads and the Graphics Stack

Background workload management is the first item on Microsoft's 2026 list, and it is the least glamorous and most reliable win available to you. Nothing here is exotic. It is just the discipline of not letting the OS do work you did not ask for while a game needs every cycle.

Killing Game DVR and background capture

Windows keeps a rolling capture buffer running so you can retroactively clip the last thirty seconds. It is a genuinely nice feature and a genuinely real cost, because encoding video in the background competes for the exact GPU and memory bandwidth your game wants. Step 6 disables it via the registry; the same switches live in Settings under Gaming and Captures if you prefer clicking. Turning it off does not disable the Game Bar overlay or Game Mode, so you keep the useful parts and drop the frametime tax. If you genuinely use the clip feature, leave it on and accept the cost knowingly; if you have never once used a retroactive clip, there is no argument for paying for it every frame.

VRR, Auto HDR, and per-game GPU

Variable refresh rate is the highest-leverage display setting you own, and it is doing more for perceived smoothness than the entire back half of this guide. Enable it in Settings under Display and Graphics, confirm it in your GPU control panel, and pair it with V-Sync forced on plus a frame cap a few frames under your refresh ceiling. Auto HDR, one of Microsoft's headline features, can add convincing HDR to SDR games on a capable display, but it depends on fullscreen optimizations being left on for that title, which is why step 7 says to decide fullscreen optimizations per game rather than nuking them globally the way old guides told you to. And per-game GPU assignment remains the fix for the most common performance complaint on laptops, where the discrete GPU sits idle while the integrated chip wheezes through a game at a third of the framerate. Resolution choice interacts with all of this; if you are weighing pixel count against refresh headroom, we made the case for 1440p over 4K in detail, and VRR is what makes that trade-off comfortable.

DirectStorage and the SSD

DirectStorage remains one of the platform capabilities Microsoft keeps highlighting, and unlike most things in this guide it does not touch your framerate at all. What it does is collapse load times and reduce traversal stutter by streaming assets straight from an NVMe SSD to the GPU with GPU-side decompression, bypassing the old CPU bottleneck. There is nothing to toggle: it is a capability games opt into, and your job is to meet its prerequisites. That means an NVMe SSD, a DirectX 12 GPU with Shader Model 6.0, and Windows 11, all of which you confirmed in the prerequisites. The one operational rule is to keep meaningful free space on that NVMe, because a drive filled past roughly 85 percent loses sustained throughput, and DirectStorage is precisely the workload that depends on sustained throughput. Use Storage Sense to keep temp files from silently eating your headroom. The engineering detail is documented on Microsoft Learn's DirectStorage overview if you want the API-level version.

5 Pitfalls That Quietly Cost FPS

The failure modes below are not hypothetical. They are the recurring ways people make their machines slower or less safe while believing they are optimizing. Each comes with the fix.

Pitfalls 1 and 2: cargo cult and debloaters

Pitfall 1: Registry cargo-culting. Applying a pile of undocumented registry "tweaks" from a forum post, none of which you can explain, several of which contradict each other, and at least one of which does nothing on Windows 11 because it targeted Windows 7. The fix is discipline: only apply values you understand and can cite, export the key before you change it so you have a real undo, and prefer the documented settings this guide uses over mystery DWORDs. If you cannot say what a value does and why it helps, you are not optimizing, you are decorating.

Pitfall 2: Debloater scripts that gut the gaming stack. The one-click "debloat" tools frequently rip out the Gaming Services, the Xbox app, and Game Bar components, then people wonder why Game Mode, Auto HDR, and the incoming Full Screen Experience no longer work. Some also disable Windows Update entirely, which in a world where a hotfix ships as an update is actively dangerous. The fix: remove apps by hand, keep the Gaming Services intact, and never let a script make your update decisions for you.

Pitfalls 3 and 4: wrong security, wrong driver

Pitfall 3: Disabling the wrong security on the wrong machine. Turning off VBS, Memory Integrity, or Secure Boot on a laptop that logs into work, chasing a few percent you will never feel in the games you actually play. The fix is the ruling from the power section: only disable VBS on a dedicated, low-value gaming box, and leave it on anything that touches credentials or a corporate network. The FPS is not worth the incident report.

Pitfall 4: Blindly installing the newest driver during a regression. The instinct when games get slow is to grab the absolute latest driver, but during the KB5066835 episode the point was to be on the specific hotfix matched to your build, not merely the newest thing. The fix: read the vendor's advisory, match driver to build number, and treat "newest" and "correct" as different words that occasionally happen to agree.

Pitfall 5: starving your SSD and yanking updates

Pitfall 5: Filling the NVMe and interrupting updates. Two failures that share a root cause, impatience. A drive stuffed past 85 percent quietly loses the sustained throughput DirectStorage depends on, so load times crawl and traversal stutters return; the fix is to keep real headroom and let Storage Sense clean up. And yanking power or force-rebooting during a cumulative update install can leave the servicing stack in a half-applied state that is far harder to fix than the slowdown you were avoiding; the fix is to pause updates properly through Settings and let any in-flight install finish before you start tuning.

Troubleshooting Table

When something regresses, resist the urge to change ten things at once. Find the symptom, apply the single indicated fix, retest. The table maps the failures this guide's readers actually hit.

Symptom-to-fix matrix

Reading the expected output

After the pass, a healthy machine should answer three quick checks cleanly. Run these to confirm the durable settings actually took rather than assuming they did:

PS> powercfg -getactivescheme
Power Scheme GUID: e9a42b02-d5df-448d-aa00-03f14749eb61  (Ultimate Performance)

PS> (Get-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Control\GraphicsDrivers').HwSchMode
2

PS> (Get-ItemProperty 'HKCU:\System\GameConfigStore').GameDVR_Enabled
0

Ultimate Performance active, HAGS at 2, Game DVR at 0. If any line disagrees, that setting did not apply, usually because the shell was not elevated or a reboot is still pending.

When to roll everything back

If the machine is worse in a way you cannot isolate, stop tuning and use the restore point you made in the prerequisites. This is not defeat; it is the reason you made it. Restore, reboot, confirm you are back to your recorded build, and then reapply steps one at a time with a test between each, so the next time something breaks you know exactly which change did it. A methodical rollback beats an afternoon of changing variables in the dark.

Advanced: MSI Mode, Nagle, TDR

These are the tweaks for readers who have done everything above, measured a specific remaining problem, and want to chase it. They are situational by nature. If you cannot name the problem each one solves, you do not have that problem yet, and applying them anyway is just Pitfall 1 with extra steps.

MSI mode and interrupt affinity

Message-Signaled Interrupts let a device signal the CPU via a memory write instead of a dedicated line, which can lower interrupt latency for GPUs and NVMe controllers. Most modern devices already use MSI, so the real value here is confirming it rather than "enabling" something that was already on. If you have measured high interrupt latency tied to a specific device, you can confirm and force MSI per device.

:: MSI mode (message-signaled interrupts). Find the device instance in
:: Device Manager > Details > Device instance path, then set:
HKLM\SYSTEM\CurrentControlSet\Enum\PCI\DEVICE_INSTANCE\Device Parameters\Interrupt Management\MessageSignaledInterruptProperties
    MSISupported = 1   (DWORD)

Change one device at a time, reboot, and retest, because a bad interrupt configuration on a storage or GPU device can cost you a boot. This is a scalpel, not a broom.

Network latency and Nagle's algorithm

Nagle's algorithm batches small outbound TCP packets to reduce overhead, which is exactly wrong for twitch multiplayer, where you want each tiny input packet sent immediately. Disabling it per interface can smooth out spikes in fast-paced online games. It is per network interface GUID, so you set it on the adapter you actually game over.

:: Nagle's algorithm off, per network interface GUID:
HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\INTERFACE_GUID
    TcpAckFrequency = 1   (DWORD)
    TCPNoDelay      = 1   (DWORD)

The honest caveat: this trades bandwidth efficiency for latency, it only helps latency-sensitive traffic, and on a clean wired connection you may see nothing. Wireless jitter and congestion are more often the real culprit, and no registry value fixes a bad link.

TDR delay and stability

Timeout Detection and Recovery is the watchdog that resets your GPU driver if it stops responding for about two seconds, producing the "display driver stopped responding and has recovered" message. Extending TdrDelay under the GraphicsDrivers key can stop spurious resets during very heavy compute or shader work, but understand what it is and is not: it is a stability setting, not a performance one, and setting it too high can turn a recoverable hang into a full freeze. Touch it only if you are actually getting TDR resets, and change nothing else while you test it.

The Complete Working Configuration

Here is the whole durable pass in three artifacts: a single elevated PowerShell script that applies the reversible core, a .reg file for the pure registry portion, and a verification checklist. Run the script, reboot, work the checklist. Everything here is undoable via your restore point and the inverse values.

The all-in-one PowerShell pass

# ============================================================
# staresback.gg :: Windows 11 gaming pass (elevated PowerShell)
# Reversible. Creates a restore point. Reboot when finished.
# ============================================================

# 0. Safety net
Enable-ComputerRestore -Drive "C:\"
Checkpoint-Computer -Description "Pre-gaming-tune" -RestorePointType MODIFY_SETTINGS

# 1. Show the build/UBR (compare to the KB5066835 range: 26100.6899 / 26200.6899)
Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion" |
  Select-Object ProductName, DisplayVersion, CurrentBuild, UBR

# 2. Power: Ultimate Performance
powercfg -duplicatescheme e9a42b02-d5df-448d-aa00-03f14749eb61
powercfg -setactive e9a42b02-d5df-448d-aa00-03f14749eb61

# 3. Graphics stack: GPU scheduling on (reboot required)
Set-ItemProperty "HKLM:\SYSTEM\CurrentControlSet\Control\GraphicsDrivers" -Name HwSchMode -Value 2 -Type DWord

# 4. Background workload: no silent capture
Set-ItemProperty "HKCU:\System\GameConfigStore" -Name GameDVR_Enabled -Value 0 -Type DWord
New-Item "HKLM:\SOFTWARE\Policies\Microsoft\Windows\GameDVR" -Force | Out-Null
Set-ItemProperty "HKLM:\SOFTWARE\Policies\Microsoft\Windows\GameDVR" -Name AllowGameDVR -Value 0 -Type DWord

# 5. Scheduling: Game Mode
Set-ItemProperty "HKCU:\Software\Microsoft\GameBar" -Name AutoGameModeEnabled -Value 1 -Type DWord

Write-Host "Pass complete. Reboot to apply GPU scheduling, then verify in Task Manager."

Note what this script deliberately does not do: it does not disable VBS, uninstall updates, or touch your network stack, because those are decisions, not defaults. Make them by hand after reading the relevant sections, on machines where they are appropriate.

The .reg file

If you prefer a portable registry artifact you can double-click on a fresh install, this is the pure-registry subset of the pass. Export your existing keys first if you want a clean undo.

Windows Registry Editor Version 5.00

; Hardware-Accelerated GPU Scheduling (2 = on)
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers]
"HwSchMode"=dword:00000002

; Disable Game DVR background capture
[HKEY_CURRENT_USER\System\GameConfigStore]
"GameDVR_Enabled"=dword:00000000

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\GameDVR]
"AllowGameDVR"=dword:00000000

; Game Mode auto-enable
[HKEY_CURRENT_USER\Software\Microsoft\GameBar]
"AutoGameModeEnabled"=dword:00000001

The verification checklist

After the reboot, confirm the state you intended actually exists. This is the anti-superstition step, the one that separates optimization from ritual:

• Build and UBR recorded, and your GPU driver matched to it (no KB5066835-style mismatch).
• powercfg -getactivescheme returns the Ultimate Performance GUID.
• HwSchMode reads 2; Task Manager confirms Hardware-Accelerated GPU Scheduling is on.
• GameDVR_Enabled reads 0; no background capture running.
• VRR on, V-Sync forced in the driver, in-game cap a few frames under refresh.
• Each game set to High performance and rendering on the correct GPU.
• Startup list pruned; no launchers or RGB suites autostarting.
• A before/after benchmark recorded, comparing 1% lows, not just averages.
• Restore point intact, in case a future update undoes any of this.

That is the whole job. Not a magic .bat file that promises impossible numbers, but a defensible pass grounded in the five areas Microsoft itself named for 2026, hardened against the exact regression the platform shipped in 2025. The single habit that matters most is the one the KB5066835 saga taught for free: check your build, match your driver, and re-run this checklist after every cumulative update. For the platform owner's own framing of these features, Microsoft keeps its Windows 11 gaming page current, and the powercfg flags used above are documented in full on Microsoft Learn. Optimize the machine once. Then treat it like version control forever.