Windows 11 optimization checklist: 6 actionable steps

Step 1 — disable virtualization-based security (VBS / HVCI)

Virtualization-based security and memory integrity (HVCI) are on by default in Windows 11 and carry a constant kernel-level cost, especially on older platforms and machines with little memory. This is one of the most common reasons a machine that is not short on hardware still feels slow.

The Virtualization Fix module checks eight items — Hyper-V, VBS, HVCI and CPU virtualization among them — and can turn them off in one action. A reboot is required; once disabled, Docker, WSL and Hyper-V virtual machines stop working.

This is a security trade-off: memory integrity and other kernel protections are lost after disabling. CPU virtualization is controlled by the BIOS and cannot be changed by the tool — the module shows BIOS setup guidance instead.

Step 2 — clear the preinstalled apps and background services you do not use

Preinstalled apps, Xbox components, telemetry and diagnostic services all stay resident in the background. The goal here is not to disable as much as possible, only what you genuinely do not use.

Basic Optimization offers 13 groups and 174 toggles covering the taskbar and desktop, menus and visual effects, File Explorer, Search and Cortana, privacy and telemetry, Edge, and AI background activity such as Copilot and Recall. Every toggle supports status detection and restore.

Step 3 — GPU driver tuning

Advanced Optimization keeps GPU tuning as its own group: AMD Shader Cache, NVIDIA low-latency mode, DPC latency, power management and P-State locking. These parameters affect frame times rather than average frame rate.

Also clear the shader cache: after a driver update or a GPU swap, stale cache causes stutter or artefacts. The first launch after cleaning recompiles shaders and takes a little longer, which is expected.

Install the correct driver version before tuning. After changing drivers, re-verify the parameters.

Step 4 — input and network latency

The feel-tuning matrix — 9 groups and 47 toggles — is aimed squarely at this: MMCSS multimedia scheduling, keyboard repeat rate and mouse acceleration, the Nagle algorithm and TCP timestamps, DXGI swap-chain frame latency, DPC queues and timer coalescing, and USB input device report rate.

When you need finer control, standalone MSI Interrupt Optimization switches the GPU and network adapter PCIe interrupt mode to MSI, and Input Queue adjusts the keyboard and mouse driver queue depth.

Win32 foreground priority and input queue depth are read by the kernel or driver at load time, so a reboot is required. Original values are backed up automatically on first apply.

Step 5 — power plan

The default Balanced plan downclocks and parks cores on its own. Power Plan unlocks hidden options such as processor performance and core parking, and ships low-latency presets for AMD dual-CCD / single-CCD and Intel P-core-first setups that can be imported in one click.

Importing a preset duplicates the Balanced plan and applies parameters to the copy, leaving the built-in plans untouched; the copy can be deleted at any time.

Step 6 — memory and storage

Memory Clean offers three modes — everyday balanced, pre-game one-click and deep aggressive — with a process whitelist, threshold triggering (80% by default) and scheduled cleaning every 5 to 60 minutes. Pair it with the memory compression and app prelaunch settings in Advanced Optimization.

On the storage side, Clean Junk removes system junk files and Shader Cache reclaims GPU cache usage.

Cleaning cannot be undone. The confirmation dialog lists the categories and total size before anything is deleted.

Order and re-checking

Recommended order: virtualization security → preinstalled apps and background services → GPU driver → input and network latency → power plan → memory and storage. Earlier steps have a wider impact and give more direct gains; later ones are better suited to incremental tweaking.

Reboot and re-measure average frame rate and 1% low after each batch rather than changing everything at once — otherwise you cannot tell which change caused what. Every change can be inspected and restored from its module.

FAQ