Windows 11 performance issues: why it's slow and the 15 fixes that actually work

The single biggest mistake in Windows tuning is shotgun tweaking. Before touching a single setting, spend ten minutes finding out what is actually saturating. Open Task Manager (Ctrl+Shift+Esc), sort by CPU, Memory and Disk in turn, and watch it for a few minutes while the slowdown happens. If nothing is obviously pegged, your problem is latency rather than throughput — different disease, different cure.

For stutter and audio cracksles, install LatencyMon (free) and let it run through a gaming session. It reports which driver is blowing its DPC/ISR deadlines — nine times out of ten it's a network driver (Killer/Intel Wi-Fi) or Realtek audio, not 'Windows'. For startup pain, Task Manager's Startup apps tab shows measured startup impact per app.

Whatever you find, write it down. Every fix below notes which symptom it addresses, and you'll want to verify afterwards that the number actually moved — that's the difference between tuning and superstition.

This is the most boring fix on the list and the one most people skip — and it fixes more real-world performance issues than any registry tweak ever will. Chipset drivers control how Windows schedules work across your CPU cores; GPU drivers carry per-game fixes; a stale BIOS can leave an entire performance state (resizable BAR, uplifted boost behavior) disabled.

Do them in order: Windows Update (including optional/advanced driver updates, and restart twice), then your motherboard vendor's chipset package (AMD or Intel — not Device Manager, which picks generic ones), then a clean GPU driver install with the 'clean installation' checkbox (or DDU if things are genuinely weird), and finally BIOS if a release note mentions memory training or boost behavior.

One warning from hard experience: never source drivers from random 'driver updater' utilities — they are the single most common source of adware and broken installs on freshly-debloated machines. Vendor pages and Windows Update only.

A stock Windows 11 install ships with promoted apps (games, streaming services, news widgets), third-grade trials and a steadily re-appearing crop of suggestions. Each one is a process, a scheduled task, and a startup entry you didn't ask for. They mostly cost RAM and attention rather than FPS — but they add up, and the re-install mechanism (the Content Delivery Manager) means deleting them once isn't always enough.

Go through Settings → Apps → Installed apps and uninstall anything you don't recognize or use. Be more careful than the average internet list: keep anything starting with 'Microsoft', 'Windows', or 'Visual C++' unless you know what it is; leave 'Microsoft Edge Webview' and 'Windows App Runtime' strictly alone — apps you actually use depend on them.

The re-install loop is worth breaking: Settings → Personalization → Start turns off 'Show suggestions for how to set up my device', and a small group policy (or the equivalent playbook step) stops CDM from ever re-downloading promoted apps. That is exactly the class of change UltraOS automates — with a manifest of what was removed so a re-run can restore it.

Every autostart entry delays your desktop becoming usable and competes for disk and CPU during the most congested minute of Windows' day. Launchers, updaters, cloud-sync clients and RGB utilities are the usual suspects — each one small, together a traffic jam.

Task Manager → Startup apps shows Microsoft's own measured impact rating. Disable everything that isn't security-critical (antivirus, drivers' companions like audio consoles you actually use). You are not deleting anything — apps simply start when you open them instead of at logon, which is what you want.

If an app keeps re-enabling itself (a genuinely obnoxious habit of some vendor software), the scheduled-task route in the next section is where you take that fight. A single honest pass here typically cuts tens of seconds from boot-to-usable on a two-year-old machine.

Windows 11 lets Store apps run in the background by default, and the Widgets feed (weather/news) is a separate web-hosted process that idles at a surprising amount of RAM while phoning home for content. None of this matters on a 32 GB workstation; on an 8 GB laptop it is the difference between comfortable and swapping.

Settings → Apps → Installed apps → (app) → Advanced options → Background apps permissions → 'Never' for anything that doesn't genuinely need push updates (mail and chat clients are the reasonable exceptions). Widgets can be disabled per-user from the taskbar settings — on Home editions the taskbar settings toggle is the whole story.

The honest note: background apps are a convenience feature, not a conspiracy. Disabling them saves memory and a little idle CPU; it will not add frames per second in games. Treat it as part of the 'make idle actually idle' pass rather than a gaming tweak.

SSDs slow down as they fill: the controller needs free blocks for wear-leveling and SLC caching, and below roughly 10% free space write amplification starts to hurt everything. A nearly-full system drive is one of the most common 'Windows is slow' causes that no software tweak can fix.

Run Storage Sense (Settings → System → Storage) to let Windows clear temp files automatically, then look at the breakdown: 'Temporary files', 'Delivery Optimization' leftovers and hiberfil.sys are the usual recoverable gigabytes. Moving the pagefile off the SSD is old advice from the SATA-days — on NVMe, leave it where it is.

While you're there: fragmentation is a non-issue on SSDs (Windows runs TRIM automatically), so don't defragment — but DO run 'chekdsk' or the disk health check if you suspect the drive itself, because a dying SSD behaves exactly like 'Windows performance issues' on every benchmark.

Virtualization-Based Security (VBS) and Hypervisor-Enforced Code Integrity (HVCI) are genuine security features: they isolate credentials and verify kernel drivers, meaning a large class of kernel-level attacks simply don't work. The cost is a measurable overhead — typically mid single digits on CPU-bound games, more in specific titles — because every context switch goes through the hypervisor.

Microsoft ships them enabled by default on new Windows 11 installs, which is why 'clean install FPS vs upgraded FPS' comparisons look different. Turning them off is a real decision, not a free lunch: you are trading away kernel-level hardening for frames. Anti-cheat systems are fine with VBS off (it's a supported configuration), but a small number of competitive titles prefer security features present — check yours if you play ranked.

If you decide the trade is worth it: Windows Security → Device security → Core isolation → Memory integrity off, plus 'Virtualization-based security' services disabled (HVCI Service / Virtualization Service Providers). Reboot twice. And know how to undo it — the toggle works in both directions, which is exactly how a reversible playbook handles it (Balanced and Performance presets keep VBS on; only Ultra turns it off, with the warning shown in the wizard).

SysMain pre-loads frequently-used app data to make launches feel faster. On an old-school hard disk that is often still useful; on an NVMe SSD the drive is so fast that the 'help' mostly shows up as background disk churn you can see in Task Manager — and occasionally as the infamous 100% disk spike at idle.

The drive-type nuance matters and most guides get it wrong: on HDD machines, leave SysMain enabled (it genuinely helps); on NVMe systems with the disk-churn symptom, disabling it is reasonable. It is a services.msc change — 'SysMain', stop then set Startup type to Disabled — and fully reversible (set back to Automatic).

What you should NOT do is disable half the service graph around it. Old playbooks disabled 'SysMain, Search, Superfetch, DiagTrack' as a bundle because a 2018 forum post said so; on 26H2 several services have interdependencies, and breaking them causes the 'why is my Start menu broken' posts. Change one thing, verify, move on — or use a tool that models the dependency graph.

Windows Search maintains a full-text index of your files, and on 'Enhanced' mode that means every file on every drive, continuously. On a busy machine that is a permanent background workload — the classic cause of the disk-activity-at-idle complaint. The indexer also has a documented history of getting stuck rebuilding after big updates, which shows up as days of churn.

The surgical version: Settings → Privacy & security → Searching Windows → switch Enhanced off (Classic indexes only documents/mail), then click 'Advanced indexing options' and exclude folders you never search — game libraries, video folders, build artifacts and node_modules-style directories are the usual terabyte-scale offenders. Rebuilding the index (Advanced → Rebuild) fixes the stuck state.

Disabling the Windows Search service entirely is the nuclear option and it breaks Start-menu file search, Outlook search and Settings search — genuinely not worth it on a daily machine. Classic mode + exclusions gets you 95% of the benefit with nothing broken, which is why UltraOS implements it as a warned opt-in ('Search indexing' on the Tuning extras page) rather than a default.

Since Windows 10, the memory manager compresses least-recently-used pages in RAM before writing them to disk — 'System and compressed memory' in Task Manager. It looks scary ('Windows is eating my RAM!') but it is a genuine win: decompressing a few MB of RAM is orders of magnitude faster than a disk read. Disabling it (the old Disable-MMAgent -mc advice) forces swapping to disk instead and makes memory-pressure stutter worse on anything but very old CPUs.

The counter-intuitive modern advice: leave compression ON, and leave the pagefile system-managed. The 'disable pagefile for speed' folklore dates from Windows XP on 5400rpm drives; on Windows 11, removing the pagefile can cause allocation failures and crash-to-desktop in memory-hungry games, and does not make anything measurably faster.

If you have 32 GB or more and want to experiment, the safe experiment is sizing the pagefile to a fixed 4–8 GB rather than eliminating it — enough for crash dumps and rare overflow without the system growing it at a bad moment. That is the kind of knobs the 'memory compression' opt-in in UltraOS exposes, with revert values recorded.

The 'Balanced' power plan parks cores, drops clocks aggressively and suspends USB devices to save milliwatts — fine for a battery, actively hostile to latency on a desktop. The two big levers: set the plan to 'High performance' (or the vendor's 'Ultimate Performance' variant), and disable 'USB selective suspend' and PCI Express link-state power management inside the advanced settings.

On laptops, keep Balanced on battery (battery life is a feature too) and switch only on AC power — or use the 'Best performance' power-mode slider in Settings → System → Power, which on modern standby machines is the actual control surface rather than the legacy plans.

What does NOT help anymore: 'processor idle disable' and the ancient '0% minimum processor state' tweaks from 2010-era guides. Modern Intel/AMD boost behavior is controlled by the platform firmware and the chipset driver, and forcing old knobs fights the scheduler for no measurable gain. Setting the sane plan and letting 26H2's scheduler do its job is the modern answer.

The acrylic/blur material on the taskbar, Start menu and context menus is rendered live by the compositor, and on weak iGPUs or older dGPUs it costs real GPU time on every frame the effect is visible. The rest of the visual-effects list (shadows, animations) is nearly free on any hardware from the last decade — despite the internet's love of 'Adjust for best performance'.

The surgical setting: Settings → Personalization → Colors → Transparency effects → Off. That single toggle removes the expensive part. In the classic 'Performance Options' dialog (sysdm.cpl → Advanced → Performance → Settings), leaving 'Smooth edges of screen fonts' and 'Show window contents while dragging' ON matters — disabling font smoothing makes text look 2003-era and doesn't buy a measurable frame.

The honest expectation: this fixes UI micro-stutter on genuinely weak graphics. It will not change your game FPS at all — games draw their own frames; the compositor isn't in your way during exclusive fullscreen. Anyone claiming 10% gaming gains from transparency settings is measuring noise.

Windows 11's diagnostic data collection runs as scheduled tasks and services: CompatTelRunner (compatibility scans), DiagTrack (the diagnostic telemetry service), and various 'Windows Error Reporting' and Feedback tasks that wake the disk at odd hours. Microsoft documents the enterprise Group Policy route; on Home/Pro, the Settings-level 'Diagnostic data → Basic' is the supported knob, with services-level changes being the deeper cut.

The measured performance impact is honest-to-goodness small — single-digit background CPU percentages and occasional disk wakes. People don't block telemetry for FPS; they do it for privacy, principle and disk-noise-at-2am reasons, and that's a completely valid motivation — just don't expect a speed miracle and don't break the service graph doing it.

The risky-but-popular route is disabling the services outright; the safer route is setting diagnostic data to the minimum in Settings and disabling the known scheduled tasks individually. UltraOS does the deep version as an audited, manifest-tracked module with per-module rollback — the difference between 'I ran a script from a forum' and 'here is the exact list of what changed and how to put it back'.

Hardware-Accelerated GPU Scheduling (HAGS) lets the GPU manage its own video-memory scheduling, reducing a small amount of CPU overhead in the render pipeline. On modern NVIDIA/AMD drivers it is enabled by default on capable hardware and generally worth leaving on — the historical stutter issues were driver bugs from 2020–2021, long fixed. If you run an older driver or a hybrid-graphics laptop, toggling it off is a legitimate test; on desktop 40/50-series or RX 7000+, leave it on.

Windows 'Game Mode' (Settings → Gaming) is the opposite of what forum lore claims — it is genuinely useful: it tells the scheduler to keep background work (Windows Update installs, Indexing) from interrupting your game session. Keep it ON. Game Bar capture features are separate and fine to disable if you never use them.

In your GPU control panel, the two settings that matter for consistency: set the 'Power management mode' to 'Prefer maximum performance' for your main games (kills clock-dips between frames), and make sure G-Sync/FreeSync is actually enabled for fullscreen AND windowed mode. These driver-side settings do more for perceived smoothness than every registry tweak in this guide combined.

Windows applies pointer acceleration by default — 'Enhance pointer precision' — which scales cursor movement by speed. For desktop work it's fine; for aiming it is a consistency disaster, because the same physical hand motion produces different on-screen distances depending on how fast you moved. Every FPS player disables it: Settings → Bluetooth & devices → Mouse → Additional mouse settings → Pointer Options → uncheck 'Enhance pointer precision'.

The two supporting tweaks that actually matter: raise the mouse polling rate to 1000 Hz in the vendor software (reduces the interval between position reports to 1 ms), and drop the legacy menu-show delay so context menus feel instant. The latter is the registry's MenuShowDelay — default 400 ms, tuned to 0–50 ms. It's the classic 'windows finally feels snappy' change that costs nothing.

What to skip: 'MarkC mouse fix' registry files (obsolete — the built-in checkbox is the supported path now), 'USB polling 8000 Hz' experiments (measurable on paper, invisible in aim, and some motherboards object), and anything that touches interrupt affinity by hand. Input feel is a chain: polling rate, acceleration off, refresh rate, then practice. The first two are settings; the last two aren't.