Windows 11 Gaming Optimization 2026: 14 Steps, 90 Min

Microsoft spent the back half of 2025 insisting that Windows is a premier platform for gaming. That is a real quote, relayed by TechPowerUp on 10 December 2025, and it did not arrive alone. It arrived bolted to a list of things the company said it was still improving: background-task handling, power and scheduling, the graphics stack, and driver updates. Read that sentence twice. When a vendor publishes the areas it is still tuning, it has handed you a confession and a to-do list in the same breath. This tutorial works through that list, in order, with the registry keys and the reasoning attached. Budget ninety minutes, most of it spent waiting on driver installers and two mandatory reboots.

"Premier Platform," They Said

What Microsoft actually said in December 2025

The December statement was not a patch note. It was a direction-of-travel memo, and it named four pillars. Background tasks: the operating system still wakes services in the middle of a frame. Power and scheduling: the default plan throttles clocks to save watts nobody asked it to save on a desktop plugged into the wall. Graphics stack: DirectX, the desktop compositor, and the presentation path a game's frames travel down before they reach your panel. Drivers: the one layer Microsoft does not fully own, which it nonetheless keeps flagging as a problem area. Every tweak below maps to one of those four pillars. That is not a coincidence. It is the shape of the problem, drawn by the people who built it.

Why a stock install leaves performance on the table

A fresh Windows 11 image is tuned for the median machine, and the median machine is a thin-and-light laptop that has to survive a transatlantic flight, not your 320-watt desktop. So it ships with a Balanced power plan, Virtualization-Based Security switched on, Delivery Optimization quietly seeding your neighbours' updates out of your upload bandwidth, and a Startup folder that fills up the instant you install Steam, Discord, and whatever RGB daemon your keyboard demands as tribute. None of that is malicious. All of it is overhead you did not choose and will not miss. The default is a compromise designed to be safe on hardware that is nothing like yours, and safe is rarely fast.

What this guide will and won't do

It will remove overhead and shave input latency. It will not conjure frames from nothing, and anyone promising a fixed percentage uplift is selling you a screenshot. The honest gains here live in frame-time consistency, in input lag, and in the difference between a game that hitches when a background task fires and one that does not. If your GPU is the genuine bottleneck, the real frame-rate lever is upscaling and, failing that, silicon. We cover the tuning end of that story in our companion 12-step frame-drop guide, and in the overclocking and undervolting walkthroughs linked near the end. This piece has one job: make the operating system get out of the way and stay out of it.

Prerequisites

Software you need, and the versions that matter

Windows 11, fully patched. Either 24H2, the build 26100 family, or 23H2, build 22631, is acceptable, and the next section settles that fight, but whichever you run must be patched past the 11 February 2025 cumulative update. That is the update that fixed Auto HDR and several gaming regressions, according to WindowsLatest's reporting at the time, and it is the reason a patch-level check appears more than once below. GPU drivers: the latest package straight from your vendor, not the one Windows Update guessed at during setup. Both NVIDIA and AMD shipped meaningful driver-level gaming optimizations in early 2026, so the word latest is doing real work there. You will need an administrator account, because half of what follows touches HKLM. Optional but recommended: Display Driver Uninstaller, DDU, for clean driver swaps, and your vendor's control panel, the NVIDIA App or AMD Software: Adrenalin Edition.

Before anything else, open an elevated PowerShell, press Win and X, and choose Terminal (Admin). Create a restore point and confirm exactly what you are running:

# Elevated PowerShell: Win+X, then "Terminal (Admin)"
Enable-ComputerRestore -Drive "C:\"
Checkpoint-Computer -Description "Pre-gaming-tweaks" -RestorePointType "MODIFY_SETTINGS"

# Confirm your Windows version and patch level
Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion" |
  Select-Object DisplayVersion, CurrentBuild, UBR

You should see output resembling the following, though your UBR, the patch number after the build, will differ:

DisplayVersion CurrentBuild UBR
-------------- ------------ ----
24H2           26100        4351

Hardware assumptions

Any DirectX 12 GPU will accept these tweaks. Two features carry prerequisites. Variable Refresh Rate needs a display that actually does VRR, which means FreeSync or G-Sync, and if you are shopping, our best gaming monitor 2026 breakdown covers which panels earn the badge. Hardware-accelerated GPU scheduling needs a GPU and driver that expose it: Pascal and newer on NVIDIA, RDNA and newer on AMD, riding a WDDM 2.7 or later driver. If a toggle is missing later in this guide, your hardware is usually the reason, not a bug in Windows.

Make an exit first

The restore-point command above is not optional ceremony. Windows throttles restore-point creation to one per twenty-four hours by default, so if you already made one today, the command will quietly no-op, and you should either override the frequency limit or trust the earlier point. Note your rollback window as well: a feature update like 24H2 can be uninstalled cleanly for ten days, after which the previous installation is purged and you are committed. Write today's date somewhere you will find it. The entire premise of a tutorial that edits the registry is that you can walk every change backwards, and you cannot walk back a point you never set.

The 24H2 Question

The green light, with an asterisk

WindowsLatest reported on 18 January 2025 that Microsoft had given 24H2 the green light for gamers, and in the very same breath noted lingering issues serious enough that rolling back to 23H2 remained the practical fix for some machines. Two weeks later, on 31 January, the outlet reported that the upgrade blocks were coming off and that Auto HDR fixes were expected with the 11 February 2025 updates. By 12 February, the story had become that Microsoft was unlocking 24H2 for more gaming PCs through that exact update cycle. Translate the timeline and it says one thing: 24H2 became genuinely fine for the majority of gaming rigs in February 2025, not at its October 2024 launch. If you are reading this in 2026 on a clean machine, install 24H2 and stop agonising.

When rolling back to 23H2 is the right call

Some configurations still misbehave. A specific mouse driver, an anti-cheat that trips on the new kernel, an audio stack that crackles under load. If you upgraded and immediately began hitting stutter or compatibility gremlins you demonstrably did not have before, 23H2, build 22631, is a legitimate and fully supported destination, not an admission of defeat. Perform the rollback inside the ten-day window and it is a two-click uninstall. Miss that window and it is a clean install with backups. This is the single area in the entire guide where the newest version is not automatically the correct one, and Microsoft's own coverage admitted precisely that. Newer is a default, not a law.

How to check which build you're on

The winver dialog tells you in a friendly box; the registry tells you in a script you can automate. DisplayVersion is the marketing string, 24H2. CurrentBuild is the number that actually matters, 26100. UBR is the patch level, the value that reveals whether you are sitting past February 2025 or three months behind pretending you are optimized. The command from the prerequisites section is the fastest way to see all three at once, and it is worth aliasing if you rebuild machines often.

Steps 1-5: The Foundation

Five steps. None of them are exotic, and that is the point. This is the floor beneath everything else, and skipping it to chase an obscure registry tweak is how people end up posting frame-time graphs that look like a seismograph.

Steps 1-2: Update Windows, then clean-install the GPU driver

Step 1, fully update Windows. Go to Settings, Windows Update, install everything offered, reboot, and check again, repeating until the screen comes back empty. The gaming fixes Microsoft keeps talking about, Auto HDR behaviour, shader-cache handling, scheduler adjustments, ship inside cumulative servicing, not the base install image. A machine that is three months behind on updates is missing the very optimizations the rest of this article assumes are present. Rationale: you cannot tune on top of a broken foundation, and February 2025 taught everyone that the servicing channel is where gaming gets fixed.

Step 2, clean-install the GPU driver. Download the latest package directly from NVIDIA or AMD. For a genuinely clean slate, boot into Safe Mode, run DDU to strip the previous driver to nothing, then install the new one from the desktop. Rationale: both vendors pushed early-2026 optimizations, and stale driver state, orphaned profiles, half-migrated shader caches, a control panel two versions out of sync with its kernel-mode component, is a classic source of stutter that no amount of registry surgery will fix. This is the highest-leverage single action in the whole guide, which is exactly why it sits near the top.

Step 3: Give it a power plan that isn't afraid of watts

Step 3. The default Balanced plan parks CPU cores when idle and ramps clocks lazily to conserve power. On a desktop that is a tax with no upside. Set High Performance, or go one further and add the hidden Ultimate Performance plan, a named Windows profile that reduces the micro-latencies caused by power-state transitions. Rationale: fewer transitions between low and high power states means fewer moments where a core is asleep when a frame needs it. On a laptop, think hard before you do this, because Ultimate Performance means higher temperatures, louder fans, and a shorter battery, and the thermal ceiling can cost you more sustained clock than the plan hands back. The plan is hidden by default, so you conjure it with powercfg:

# List the power schemes already on the machine
powercfg /list

# Add the hidden Ultimate Performance plan
powercfg -duplicatescheme e9a42b02-d5df-448d-aa00-03f14749eb61

# Make it active
powercfg /setactive e9a42b02-d5df-448d-aa00-03f14749eb61

After the duplicate command, powercfg /list should show the new plan alongside the built-ins:

Existing Power Schemes (* Active)
-----------------------------------
Power Scheme GUID: 381b4222-f694-41f0-9685-ff5bb260df2e  (Balanced) *
Power Scheme GUID: 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c  (High performance)
Power Scheme GUID: e9a42b02-d5df-448d-aa00-03f14749eb61  (Ultimate Performance)

Steps 4-5: Game Mode and the startup purge

Step 4, Game Mode. Settings, Gaming, Game Mode. It instructs Windows to deprioritize background work and to hold off on driver installs and restart notifications while you play. Rationale: for competitive gaming, leave it on, because the thing you most want is for nothing to interrupt you mid-round. The 2026 guidance is more nuanced for streamers and content creators, however: some capture setups run better with Game Mode off, because its resource juggling can interfere with an encoder that is sharing the GPU with the game. Test both. It is a per-system toggle, not a creed.

Step 5, prune the Startup apps. Open Task Manager, go to the Startup apps tab, and disable the high-impact offenders. Discord, Spotify, OneDrive, Steam, and RGB control software all love to launch at boot and idle in the background indefinitely. Rationale: disabling startup does not uninstall anything; it means the app runs when you open it, the way software behaved before every program decided it was a resident. The payoff is a lower idle CPU floor and fewer processes elbowing each other for the scheduler the instant a game launches. Sort the tab by Startup impact and start at the top.

Steps 6-10: The Graphics Stack

Five steps inside the part of Windows that Microsoft itself named as still being tuned. Most of them live in one menu, and one of them is the sleeper tweak that the 2026 guides finally started shouting about.

Steps 6-7: HAGS and Variable Refresh Rate

Step 6, Hardware-accelerated GPU scheduling. Go to Settings, System, Display, Graphics, then Change default graphics settings, and toggle HAGS on. Rationale: it hands frame scheduling and some memory management from the CPU to a dedicated processor on the GPU, which can trim CPU overhead and shave latency. Microsoft's own DirectX team documented the feature, so it is not snake oil, but it is also not universally faster; on certain CPU, GPU, and driver combinations it does nothing measurable or, rarely, adds stutter. Treat it as a measured toggle, not an article of faith. A reboot is required before it takes effect. To read or set the state without clicking through menus:

# Read HAGS state: 2 = enabled, 1 = disabled
Get-ItemProperty "HKLM:\SYSTEM\CurrentControlSet\Control\GraphicsDrivers" -Name HwSchMode

# Enable it, then reboot
Set-ItemProperty "HKLM:\SYSTEM\CurrentControlSet\Control\GraphicsDrivers" -Name HwSchMode -Value 2

Step 7, Variable refresh rate. Same menu. Rationale: this is the OS-level VRR switch that extends adaptive sync to DirectX 11 and older titles that would not otherwise receive it from your driver's global setting. If you own a FreeSync or G-Sync display, turn it on. If you do not, it does nothing and costs nothing. Pair it with your monitor's native VRR and cap your frame rate a few frames below the panel's ceiling, which is the tear-free, low-latency sweet spot every serious guide eventually arrives at.

Step 8: Optimizations for windowed games

Step 8. The 2026 guides single this one out, and they are right to. Optimizations for windowed games is a toggle in the same Default graphics settings menu, and it rewrites the presentation path for borderless-windowed titles so that they receive the low latency and the features, VRR and Auto HDR, that once required exclusive fullscreen. Rationale: almost everyone runs borderless now because alt-tab is instant and a second monitor stays alive. This setting means you stop paying a latency penalty for that convenience. It is the closest thing in this guide to a free win, and for years it was buried where nobody looked. Turn it on.

Steps 9-10: Per-app GPU preference and Auto HDR

Step 9, per-app GPU preference. Still inside Default graphics settings, you can pin individual games to High performance. Rationale: on a desktop with a single GPU this is a harmless no-op, but on a laptop with integrated plus discrete graphics it stops a game from accidentally rendering on the iGPU and then blaming the hardware for the frame rate. Set your games explicitly and stop trusting the automatic picker, which guesses wrong often enough to matter.

Step 10, Auto HDR. If you own an HDR display, Auto HDR retrofits SDR games with an HDR presentation. Rationale: this was one of the features broken and then repaired in the February 2025 updates, which is the entire reason the patch-level check in the prerequisites exists. On a good HDR panel it is a genuine visual upgrade for old games at near-zero performance cost. On a mediocre panel it can wash colours out, so judge it with your own eyes on your own hardware rather than trusting a forum.

Steps 11-14: Background Noise

The final four steps attack the background-tasks pillar directly. This is the quietest category and the one where the largest number of tiny, invisible thefts add up.

Steps 11-12: Background apps and Delivery Optimization

Step 11, disable background apps. Go to Settings, Apps, Installed apps, and for the worst offenders set Let this app run in the background to Never, or curb them in bulk through the power settings. Rationale: these are Store apps that keep threads alive for notifications you do not need in the middle of a match, and every one you stop is scheduler contention removed and a little RAM handed back. You are not deleting anything; you are telling apps to sleep when you are not using them.

Step 12, kill Delivery Optimization uploads. Go to Settings, Windows Update, Advanced options, Delivery Optimization, and turn off Allow downloads from other PCs. Rationale: by default Windows can spend your upload bandwidth seeding updates to strangers on the internet and to other machines on your LAN, and during a gaming session that is latency and jitter you are donating for free. Turn it off in the interface, or set the policy directly:

# 0 = HTTP only, no peer-to-peer uploads
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization" /v DODownloadMode /t REG_DWORD /d 0 /f

Step 13: Memory Integrity and VBS, the honest version

Step 13. This is the tweak every guide mentions and few explain properly, so here it is straight. Windows Security, Device security, Core isolation, Memory integrity. Turning it off, and by extension disabling Virtualization-Based Security, removes a hypervisor layer that sits between the kernel and the hardware. Rationale: on CPU-bound workloads it can hand back a few percent of frame time, which is why it appears in every 2026 optimization list. It is also a real security control, the thing standing between a malicious or vulnerable driver and your kernel, and Microsoft ships it on for a reason. Disable it on a dedicated gaming box if you want the headroom. Do not disable it on a machine you also bank and work on, and never disable it on a managed corporate laptop, where policy will fight you, force it back, and flag the attempt. That is the trade, stated plainly rather than buried.

# Turn off Memory Integrity (HVCI)
reg add "HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity" /v Enabled /t REG_DWORD /d 0 /f

# Turn off Virtualization-Based Security
reg add "HKLM\SYSTEM\CurrentControlSet\Control\DeviceGuard" /v EnableVirtualizationBasedSecurity /t REG_DWORD /d 0 /f

# Check status: 0 = off, 2 = running
Get-CimInstance -ClassName Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard |
  Select-Object VirtualizationBasedSecurityStatus

Step 14: Visual effects, then reboot

Step 14. Open the Start menu, search for performance, choose Adjust the appearance and performance of Windows, and either select Adjust for best performance outright or keep the two or three animations you genuinely like and cut the rest. Rationale: the raw frame-rate gain is negligible, but the responsiveness gain in the desktop and in alt-tab is real, and on a weaker integrated GPU it matters more than on a discrete card. Then reboot, and understand that this is not a suggestion. HAGS, the VBS changes, and several of these settings do not take effect until a restart, and a large share of the this-tweak-did-nothing complaints online come from people who edited the registry and never rebooted. Restart, then re-run the audit script at the end to confirm every change actually landed.

The Emulation Angle

A retro-gaming site would be negligent to stop at DirectX. Emulation is where operating-system latency stops being an abstraction and becomes the thing you feel in your thumbs.

Emulators punish latency you can't feel elsewhere

A modern native game's engine can hide a frame of latency with prediction and interpolation. An emulator cannot. It is faithfully reproducing a machine that expected its input on a specific scanline in 1991, and then it is stacking its own layers, the host compositor, the graphics driver, the OS scheduler, on top of that expectation. That is why the same OS jitter you happily ignore in a modern shooter turns into perceptible input lag in a 2D fighter or a precision platformer. Everything in this guide, HAGS, the power plan, killing background wakeups, VBS off on a dedicated box, reduces the variance that emulator latency features then spend their effort trying to claw back. Tune the OS and you widen the window those features have to work in.

The RetroArch settings that interact with your OS tweaks

RetroArch's run-ahead feature runs the emulated core one or more frames into the future and rolls it back, hiding the emulator's internal latency, and its frame-delay feature holds off polling your input until the last safe moment before vsync. Both are documented on the libretro run-ahead guide, and both are acutely sensitive to how much scheduling slack the OS leaves them. A machine on Ultimate Performance with background tasks culled can sustain a higher frame delay, and therefore lower latency, without dropping frames than a stock install can. Auto Frame Delay makes that adaptive rather than a fixed gamble. A conservative starting point, dropped beside retroarch.exe:

# retroarch.cfg  (Windows: sits beside retroarch.exe)
run_ahead_enabled = "true"
run_ahead_frames = "1"
run_ahead_secondary_instance = "true"
video_frame_delay = "0"
video_frame_delay_auto = "true"
vrr_runloop_enable = "false"
video_vsync = "true"
video_max_swapchain_images = "2"

If you run a VRR display, RetroArch's Sync to Exact Content Framerate, the vrr_runloop_enable key, is the cleaner path than forcing sync globally; leave the OS VRR toggle from Step 7 on and let RetroArch drive the timing. The source and issue history live on the RetroArch GitHub, and the run-ahead and frame-delay pages are worth reading in full before you cargo-cult values off a Reddit thread. Run-ahead in particular costs CPU per look-ahead frame, so more is not automatically better.

Or skip Windows entirely

Here is the option nobody selling optimization scripts wants to mention: if a machine exists only to play retro games, Windows is a heavy way to do it. A dedicated Linux distribution such as Batocera boots straight into a front-end with none of this overhead, no Delivery Optimization, no VBS, no Startup daemons quietly waking up, and we walk through flashing it in roughly twenty minutes in our Batocera install guide. The best Windows gaming optimization is sometimes not running Windows. For everyone whose main rig is dual-purpose, and that is most people, keep reading, because the OS is staying.

Common Pitfalls

Six ways this goes wrong, grouped by how they hurt, and how to reverse each one. Every optimization in this guide is a trade, and a trade you do not understand is just damage.

Security and policy own-goals

Pitfall 1, disabling VBS on the wrong machine. On a managed work laptop, Core Isolation is frequently enforced by policy. You will either be unable to turn it off, or you will turn it off, trip a compliance alert, and have it forced back on at the next check-in, having achieved nothing except a conversation with IT. Fix: leave it alone on any machine you do not fully own. On a personal box the trade is yours to make, but make it knowing you removed a genuine mitigation, not a bloat feature.

Pitfall 2, debloat scripts that break more than they fix. The one-click scripts that promise to strip Windows to the studs routinely disable Windows Update, break the Microsoft Store, or nuke the Xbox services that Game Bar and several launchers quietly depend on. Fix: prefer the manual, reversible steps in this guide over a black box. If you already ran one and something broke, sfc /scannow followed by DISM /Online /Cleanup-Image /RestoreHealth is your first recovery tool, and the restore point from the prerequisites is your second.

Cargo-cult tweaks that do nothing, or harm

Pitfall 3, expecting Game Mode to be a booster. Game Mode does not add frames; it prevents interruptions. Turning it off to get more performance is backwards for gaming, and turning it on for a streaming rig can actively hurt. Fix: on for play, tested for capture.

Pitfall 4, HAGS-induced stutter. On a minority of driver and hardware combinations, HAGS makes frame pacing worse rather than better. Fix: if you got new stutter immediately after enabling it and rebooting, set HwSchMode back to 1, reboot, and retest. Change one variable at a time so you can actually attribute the result.

Pitfall 5, Ultimate Performance on a thermally limited laptop. The plan keeps clocks high and cores unparked, which on a laptop means hitting the thermal wall sooner and throttling harder than Balanced ever would. Fix: laptops should use the vendor's performance profile, not the desktop Ultimate Performance plan. If you added it and temperatures spiked, switch back to High Performance or plain Balanced.

The over-pruning trap

Pitfall 6, killing services you actually need. In the enthusiasm of the Startup purge, people disable the vendor GPU service, the audio stack, or the gamepad driver and then spend an evening wondering why their controller or their surround sound stopped working. Fix: disable applications in the Startup tab, not Windows services you cannot identify. If something breaks after a purge, re-enable the last thing you touched. Startup pruning is reversible per item, so treat it that way instead of nuking twenty entries at once and losing the thread.

Troubleshooting

The failure modes above, plus a few more, arranged so you can find the symptom first and the cause second.

Symptom	Likely cause	Fix
New stutter right after enabling HAGS	HAGS incompatible with your driver combo	Set HwSchMode to 1, reboot, retest
Game runs on the integrated GPU	Automatic GPU picker chose the iGPU	Pin the game to High performance in Default graphics settings
Auto HDR looks washed out or broken	Pre-February-2025 patch level, or a weak HDR panel	Update past the 11 Feb 2025 cumulative; if still bad, turn Auto HDR off
Borderless game feels laggier than fullscreen	Optimizations for windowed games is off	Enable it in Default graphics settings, then relaunch the game
Ultimate Performance plan missing from the list	Hidden by default, and absent on some laptops	Run the powercfg -duplicatescheme command; on laptops use High performance instead
Frame rate tanks during downloads	Delivery Optimization uploading, or Update servicing	Disable downloads from other PCs; enable Game Mode to defer updates
Anti-cheat will not launch after the 24H2 upgrade	Kernel or driver incompatibility with the new build	Update the game and its anti-cheat; if unresolved, roll back to 23H2 within 10 days
Tweaks appear to do nothing	No reboot after registry or settings changes	Reboot; HAGS and VBS changes require a restart
VRR toggle greyed out or absent	Display or driver does not expose VRR	Confirm a FreeSync or G-Sync panel and a current WDDM driver
Controller or audio died after the Startup purge	Disabled a needed vendor service, not just an app	Re-enable the last item; only disable identifiable applications

Advanced Tips

For readers who have done everything above, measured the result, and want more, with the standing warning that measurement, not vibes, decides whether any of this helps you specifically.

Stop cargo-culting timer resolution

The old advice was to force a 0.5 ms global timer resolution with a tray tool and never think about it again. That advice aged badly. Since Windows 10 version 2004, timer resolution requests are handled per process, and a game that wants a high resolution timer already asks the OS for one; 24H2 refined the behaviour further still. Forcing it globally on a modern build is at best a no-op and at worst raises DPC latency and idle power draw for no return. Measure with your own frame-time graph before you install another resident daemon that promises magic. Most people should skip this category entirely and feel nothing but relief.

MSI mode and interrupt handling

Message-Signaled Interrupts can lower interrupt latency for the GPU compared with legacy line-based interrupts, and the good news is that most modern GPUs already default to MSI. This is a thing to verify, not to blindly force. The switch lives per device under the PCI enumeration key, and editing the wrong device's Interrupt Management branch is an excellent way to make a component vanish from the system, so back up the registry first and change exactly one device before rebooting.

# MSI mode is per-device under the PCI enumeration key. The path varies:
#   HKLM\SYSTEM\CurrentControlSet\Enum\PCI\VEN_...\Device Parameters\
#   Interrupt Management\MessageSignaledInterruptProperties
# Value MSISupported (DWORD): 1 = MSI enabled. Most GPUs ship this way.
# Verify with GPU-Z or the MSI utility; change one device, then reboot.

The tools that actually move frames

Once the operating system is out of the way and you are still GPU-bound, the honest levers are three, and none of them are OS tweaks. Upscaling, DLSS on NVIDIA or FSR on AMD, buys more real frames than every registry key in this article combined, and it is not close. A careful GPU overclock adds a measured few percent, and our GPU overclocking walkthrough does it in twelve steps rather than by yanking sliders. A CPU undervolt buys thermal headroom that converts into sustained boost clocks under load, which we cover in the undervolting guide. Process Lasso can pin a stubborn game engine off your primary cores if a specific title fights the scheduler, but reach for it last, after the free wins are banked. The pattern is consistent: the hardware levers out-perform the software ones, so exhaust the free OS tuning first and then spend effort where it actually returns frames.

The Complete Configuration

Everything above, condensed into something you can execute in a single pass and, more importantly, reverse when a game or a driver disagrees with a choice.

The checklist

1. Fully update Windows and reboot until Windows Update comes back empty.
2. Clean-install the latest NVIDIA or AMD driver, ideally after DDU in Safe Mode.
3. Set High Performance, or add Ultimate Performance on a desktop only.
4. Turn Game Mode on for play; test it off for streaming and capture.
5. Disable high-impact Startup apps: Discord, Spotify, OneDrive, Steam, RGB software.
6. Enable Hardware-accelerated GPU scheduling, then reboot.
7. Enable Variable refresh rate if you own a FreeSync or G-Sync panel.
8. Enable Optimizations for windowed games.
9. Pin games to the High performance GPU on laptops.
10. Enable Auto HDR on a good HDR display, patched past February 2025.
11. Disable background apps you do not need running idle.
12. Turn off Delivery Optimization downloads from other PCs.
13. Disable Memory Integrity and VBS on a dedicated, self-owned box only.
14. Adjust visual effects for performance, then reboot and audit.

Known-good settings at a glance

Setting	Recommended value	Where
Windows build	24H2 (26100), patched past 11 Feb 2025; 23H2 if unstable	Windows Update
GPU driver	Latest vendor package, clean via DDU	NVIDIA / AMD
Power plan	High or Ultimate Performance (desktop)	powercfg
Game Mode	On for play; test for capture	Settings, Gaming
HAGS (HwSchMode)	2 (on), reboot required	Default graphics settings
Variable refresh rate	On, if the panel supports it	Default graphics settings
Windowed optimizations	On	Default graphics settings
Delivery Optimization uploads	Off	Windows Update, Advanced
Memory Integrity / VBS	Off (own machine only)	Windows Security
Background apps	Off for non-essentials	Settings, Apps
Visual effects	Best performance	Performance Options

If it all goes wrong: the audit and the rollback

Run this audit script after your final reboot to confirm each change landed, and keep the output so you know what a tuned machine looked like before you started experimenting further:

Write-Host "== Windows version =="
(Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion").DisplayVersion

Write-Host "== Active power scheme =="
powercfg /getactivescheme

Write-Host "== HAGS (2 = on) =="
(Get-ItemProperty "HKLM:\SYSTEM\CurrentControlSet\Control\GraphicsDrivers").HwSchMode

Write-Host "== VBS (0 = off) =="
(Get-CimInstance Win32_DeviceGuard -Namespace root\Microsoft\Windows\DeviceGuard).VirtualizationBasedSecurityStatus

Write-Host "== Game Mode (1 = on) =="
(Get-ItemProperty "HKCU:\Software\Microsoft\GameBar").AutoGameModeEnabled

To reverse the guide: restore the Balanced power plan with powercfg /setactive SCHEME_BALANCED, re-enable Memory Integrity in Windows Security, set HwSchMode back to the value it held before Step 6 if HAGS caused trouble, and re-enable any Startup or background apps you miss. If a feature update itself is the culprit, uninstall it within the ten-day window. The restore point you set before touching anything undoes the registry edits wholesale, which is exactly why it was step zero. Microsoft will keep tuning its premier platform on its own schedule, pillar by pillar, background tasks and power and graphics and drivers. Until it finishes, the tuning is yours to do, and the entire value of doing it this way is that every last change of it is reversible.