Your Windows 11 Suddenly became very slow? — Here's What's Actually Happening
Every person who's ever sat down at their PC and felt it was slower than yesterday has done the same thing: started changing settings without figuring out what actually broke first. That approach is why people spend two hours "optimising" a machine and feel nothing change — because they fixed the wrong thing.
Windows 11 slowdowns almost always have a specific cause. Not "Windows got worse." Not "my PC is old." A specific, identifiable thing running on your computer right now that is consuming resources it shouldn't be consuming, or a specific piece of hardware that is failing under load. The difference between a PC that feels slow and a PC that is slow is smaller than most people think — and finding which one you're dealing with takes about five minutes if you know where to look before you start touching anything.
This isn't a list of settings to change. You'll find that in other guides. This is the diagnostic process — how to read what your PC is telling you before you do anything — because fixing the symptom without finding the cause is how you end up in the same situation three weeks from now wondering why nothing worked.
The First Question: When Did It Start?
This sounds almost insultingly simple, but it's the question that eliminates half the possible causes before you open a single tool. Think back carefully. Did the slowness start after a Windows Update installed? Did it appear after you installed something new — a game, an app, a printer, a browser extension? Did it start after a period of heavy use, like a long gaming session or leaving the machine on for several days without a restart? Or did it feel like it crept up gradually over weeks?
Each of those patterns points to a completely different culprit. Post-update slowness is a specific, well-documented pattern with specific known causes, several of which appeared in 2026. A slowdown after installing something new is almost always that specific something, not Windows broadly. Slowness after extended uptime is a memory leak — a process that consumes progressively more RAM the longer it runs. And gradual slowness over weeks is almost always hardware — a drive that's filling up, thermals that have worsened as dust accumulates inside the machine, or a drive that's beginning to fail.
Knowing when it started doesn't fix anything. But it tells you exactly where to look first.
The 2026-Specific Culprits Worth Knowing About
Before getting into the general diagnostic process, here are the specific Windows 11 issues from 2026 that have caused genuine widespread slowdowns — because if your machine started behaving strangely after any of these updates, the cause was already known before you noticed it.
Microsoft's April 2026 preview update addressed a documented Delivery Optimization memory leak — a background service responsible for downloading Windows updates that was consuming unexpectedly large amounts of RAM on many systems. If your machine slowed down noticeably before April and has been fine since, that was likely it. If you haven't installed that update yet and your machine is slow, Delivery Optimization may still be the active cause.
The KB5089549 May 2026 Patch Tuesday update caused a different problem: install failures on certain systems that repeatedly attempted to apply the update and then rolled back, creating a loop of background activity that hammered CPU and disk usage without ever completing. A smaller group of users reported the update also slowed internet performance after successfully installing. If your machine started feeling slow in mid-May 2026, this is worth checking specifically. Go to Settings → Windows Update → Update History and look for KB5089549 — if it shows a failure status with multiple attempts, that background retry loop is actively consuming resources right now.
The June 2026 KB5094126 update brought its own set of performance complaints, with users reporting slow boot times and general sluggishness particularly on systems where Fast Startup was enabled. Fast Startup is a Windows feature that saves part of the system state to disk when you shut down, allowing faster subsequent boots — but it also means the machine doesn't do a genuine full restart, which prevents Windows from clearing accumulated junk from the previous session. If you've been "shutting down" your PC rather than restarting it, the update may have introduced something that's building up between sessions rather than clearing out.
Open Task Manager Before Doing Anything Else
Press Ctrl + Shift + Esc. This is the fastest path to understanding what your PC is actually doing right now, and it's the step that most guides skip because it requires interpreting the result rather than just following instructions. Don't skip it.
In the Processes tab, sort by CPU first by clicking the CPU column header. Watch it for about thirty seconds rather than glancing once — some processes spike momentarily and settle, while a genuine problem process holds high CPU consistently. The column heading will show total CPU usage as a percentage. Anything above 70 to 80% while you're not actively running something demanding is worth noting. If one process specifically is responsible for most of that usage, that process is your starting point.
Then sort by Memory. High memory isn't always a problem — Windows is designed to use available RAM rather than leaving it empty, and seeing 60 or 70% memory usage is normal. What's not normal is consistently seeing 90% or higher while you're doing moderate tasks like browsing and email. If you're in that range, your machine either doesn't have enough RAM for your usage pattern, or a specific process is hoarding memory it should be releasing.
Then look at Disk. This one is frequently the actual culprit when everything else looks fine. A disk column showing 100% active time — meaning the drive is being accessed at full capacity continuously — while data transfer rates are small is the signature of a drive bottleneck. It happens because Windows is asking the disk to do many small operations simultaneously and the disk can't keep up with the queue. On a mechanical HDD, this is normal and indicates you'd benefit significantly from an SSD upgrade. On an SSD, 100% disk usage that persists is a warning sign worth investigating further.
What the Specific High-Usage Processes Actually Mean
Task Manager will show you a high-usage process. It won't tell you whether that's a problem or just Windows doing something legitimate. Here's the distinction that matters.
SearchIndexer.exe consuming high CPU or disk after an update is Windows rebuilding its search index — completely normal, will finish on its own within a few hours, and should not be killed or disabled based on one instance of high usage. If it's been high for days rather than hours, that's a different situation worth investigating.
Windows Modules Installer Worker at high CPU or disk means Windows is installing or configuring an update in the background. Normal. Leave it running. The PC will feel slow until it finishes.
Antimalware Service Executable consuming high disk usage for an extended period after an update is Microsoft Defender running its post-update full scan. Normal and will finish. Not a sign of a virus — an actual virus process would typically not identify itself so clearly.
Delivery Optimization consuming unexplained RAM continuously between updates — particularly before the April 2026 patch — is the documented memory leak. If this process is sitting at several hundred megabytes of RAM while your machine is otherwise idle, updating to the latest Windows version through Settings → Windows Update addresses the root cause.
svchost.exe appearing multiple times in the list is completely normal — Windows runs many background services under that process name. It is not a virus because it shows up multiple times. If a specific svchost instance is consuming unusually high resources, right-click it and select "Go to details," then check which service it's hosting — that's where the actual investigation continues.
When Task Manager Shows Nothing — Go Deeper With Resource Monitor
Sometimes Task Manager will show overall high disk usage but no single obvious culprit process. This is where most people give up, assume it's "just Windows," and start randomly changing settings. Don't. Open Resource Monitor instead.
Press Windows key + R, type resmon, and press Enter. Resource Monitor gives you a more detailed view than Task Manager, and the Disk tab specifically shows you every single file being read from or written to at any moment — including files that are being accessed by System processes that Task Manager groups together without detail. Sort by Total bytes per second to find which files are being accessed most heavily. If one specific file or folder is responsible for sustained heavy disk activity, that tells you which application or service to investigate.
The Network tab in Resource Monitor is worth checking specifically if your machine felt fine until recently and you didn't install anything new. Sustained heavy network activity from a process you don't recognise — particularly at times when you're not actively downloading anything — is worth investigating outside of the performance context.
The Thermal Throttling Problem Nobody Thinks to Check
Here's the cause of PC slowdowns that gets missed most often, particularly on laptops and compact desktop PCs: the processor running too hot and deliberately slowing itself down to avoid damage. Thermal throttling is a built-in CPU protection mechanism — when the chip gets too hot, it reduces its own clock speed to generate less heat. The result feels indistinguishable from having insufficient hardware: everything just runs slower, with no obvious process consuming resources because the CPU itself is operating at reduced capacity.
The symptoms that suggest thermals rather than software: slowness that's worst under sustained workloads and improves when you're doing less demanding tasks. A PC that has performed well for years and suddenly started struggling, particularly if the room temperature has been higher than usual or if the machine hasn't been cleaned in a while. Fan noise that's continuously high even when the PC isn't doing anything particularly demanding.
To check: download HWMonitor or HWiNFO — both are free, reputable tools — and watch your CPU temperature under load. Temperatures consistently above 90 degrees Celsius on a processor while doing moderate tasks indicate a thermal problem. Cleaning dust from the vents and heatsink, or replacing the thermal paste between the CPU and its cooler on older machines, often resolves sustained slowdowns that have no software explanation and return regardless of how many settings you change.
The SSD Health Check That Can Save You From a Catastrophic Discovery
If your PC's slowness is accompanied by specific symptoms — occasional freezing for a few seconds before resuming, File Explorer loading slowly or sometimes failing to load a folder, the PC taking longer than usual to shut down or start up — run a drive health check before doing anything else. Not because it's the most likely cause, but because if it is the cause, every other troubleshooting step you take is time spent on a machine that's about to fail.
Windows 11 has a built-in drive health tool. Go to Settings → System → Storage → Disk & Volumes, select your main drive, and look for the health status. For a more detailed assessment, open Command Prompt as administrator and run wmic diskdrive get status. For SSD-specific health including remaining lifespan percentages, CrystalDiskInfo is a free tool that reads SMART data from both SSDs and HDDs and presents it in plain language rather than requiring you to interpret raw values.
A drive showing "Caution" status in CrystalDiskInfo or specific SMART errors related to reallocated sectors or pending sectors is a drive that's failing. The performance symptoms of a failing drive can be intermittent enough that everything else on the machine looks fine. This check takes five minutes and the information it gives you is irreplaceable before you spend hours trying to fix something that can't be fixed by any software change.
The Restart You've Been Skipping
This is the least glamorous fix and simultaneously one of the most effective — particularly if your machine has been running on Sleep mode for days or weeks without a proper restart. Windows 11's Fast Startup feature means that selecting "Shut Down" from the Start menu doesn't give the machine a full restart — it saves system state to disk to allow faster boot times, but it also means accumulated memory leaks, stuck processes, and update-related background tasks don't get cleared out the way a genuine restart would clear them.
The distinction matters: Restart gives you a genuine fresh session. Shut Down with Fast Startup enabled does not. If you've been shutting down rather than restarting, the slowness may have nothing to do with any setting or installed application — it's just accumulated session state that a proper restart will clear in two minutes.
Go to Start → Power → Restart rather than Shut Down. Wait for the full restart to complete. Use the machine normally for thirty minutes. If the performance improvement is significant, you've found the pattern: the machine accumulates slowness over extended sessions and needs a genuine restart periodically rather than continuous sleep-wake cycles.
After the Diagnosis — Then Change Things
The point of going through all of this before changing any settings is straightforward: a slow PC with a known cause is a problem you can solve. A slow PC where you've changed seven settings without finding the cause is a problem you've obscured — now you don't know whether any of those changes helped, which of them might have made something else worse, or what the original cause actually was.
Task Manager showed sustained high CPU from a specific process? Investigate that process specifically. High disk from a known Windows service that's completing post-update housekeeping? Leave it alone for twenty-four hours. Resource Monitor revealed one specific folder being hammered by a background application? Disable or uninstall that application. Drive health check showed early warning signs? Back everything up before touching anything else and prioritise the hardware replacement over any software fix.
Diagnose first. Fix second. In that order, on every single slow PC, without exception. The guides that skip the diagnosis step produce the people who've "tried everything" and still have a slow computer — because everything wasn't the problem. Something specific was, and they never found it.
Also read: Sony Kept This PlayStation Disc Detail Quiet—But Developers Already Knew
