By Andrew Armstrong 
A PC that’s slow immediately after a Windows update usually isn’t broken. Most of the time it’s doing background work it doesn’t tell you about, and it finishes on its own within a day or two. The trick is knowing which case you’re in before you start changing things.
This separates “leave it alone for 48 hours” from “something genuinely went wrong”, and covers what to do about each.
Quick Facts
- Give it 24-48 hours of normal use before concluding anything. Several background jobs run after an update.
- Search indexing,
.NEToptimisation and driver re-installation all run post-update and are legitimately heavy. - Check Task Manager’s Startup impact tab. Updates sometimes re-enable things you’d disabled.
- If it started exactly at the update, you can uninstall that specific update and pause further ones.
- A feature update leaves behind
Windows.old, which can be several gigabytes and looks like a disk problem.
First: is it actually the update?
Open Reliability Monitor (perfmon /rel) and look at the timeline. If the machine was fine, an update installed, and the slowdown starts on that date, you have your answer. If the decline was gradual, the update is a coincidence and you’re looking at something else.
This takes fifteen seconds and stops you chasing the wrong thing.
The background jobs that legitimately slow things down
| Process | What it’s doing |
SearchIndexer.exe | Rebuilding the search index. Can run for hours |
ngen.exe / .NET Runtime Optimization | Recompiling .NET assemblies for the new build |
TiWorker.exe / TrustedInstaller | Finalising component installation and cleanup |
MoUsoCoreWorker.exe | Update orchestration, checking for further updates |
CompatTelRunner.exe | Compatibility appraisal. Heavy, and safe to leave |
All of these are legitimate, all are temporary, and killing them just means they run again later. Check Task Manager sorted by CPU: if one of these is at the top, the answer is patience rather than intervention.
What’s actually worth doing
Quick Steps
- Restart properly. Not Shut Down, Fast Startup means that isn’t a true restart. Choose Restart specifically.
- Check Startup impact in Task Manager. Updates occasionally re-enable startup items, and vendor updaters reinstall themselves.
- Update your graphics driver from the vendor rather than Windows Update. A generic driver replacing a proper one is a common cause of sluggish visuals after a feature update.
- Check free disk space. Below about 10% free, everything slows down. A feature update can consume a lot.
- Run Disk Cleanup as administrator and remove previous Windows installations if you’re happy you won’t roll back.
On that last point: Windows.old can be 10-20GB. Windows removes it automatically after ten days, but on a machine that was already tight on space that’s ten days of being slow.
If it really is the update
Uninstall the specific update rather than rolling everything back:
# List installed updates with dates
wmic qfe list brief /format:table
# Or in PowerShell
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10Then remove it from Settings, Windows Update, Update history, Uninstall updates, and importantly, pause updates for a week or two afterwards, or Windows will simply reinstall it.
For a feature update specifically, there’s a ten-day window to go back: Settings, System, Recovery, Go back. After ten days that option disappears along with Windows.old.
When it isn’t the update at all
- Failing storage. A drive developing bad sectors is slow, and it’s easy to blame recent software. Check SMART data.
- Thermal throttling. Dust and dried thermal paste cause exactly this pattern, and it worsens gradually rather than suddenly.
- Not enough RAM. If the machine pages constantly, every update that adds background work makes it worse.
- Antivirus doing a full scan. Many products trigger one after a major update.
Glossary
| Term | What it means |
| Fast Startup | A hybrid shutdown that hibernates the kernel. Means Shut Down isn’t a true restart. |
Windows.old | The previous installation, kept for ten days to allow rollback. Often 10-20GB. |
| Quality update | A monthly cumulative patch. Removable individually. |
| Feature update | A major version upgrade, e.g. 24H2. Removable within ten days. |
| Thermal throttling | A CPU or GPU reducing speed to stay within temperature limits. |
Frequently asked questions
How long should I wait before worrying?
Two full days of normal use. Search indexing and .NET optimisation genuinely take that long on some machines, and they only run while the machine is on.
Can I safely stop these background processes?
You can, but they’ll run again. The work still needs doing, so you’re postponing rather than avoiding. The exception is if one is stuck at high CPU for days, which suggests a fault rather than normal work.
Should I uninstall the update?
Only if the slowdown clearly began exactly when it installed, and only after waiting a couple of days. If you do, pause updates afterwards or Windows will reinstall it.
Is it safe to delete Windows.old?
Yes, provided you’re sure you won’t want to roll back. Use Disk Cleanup as administrator rather than deleting the folder manually. It has permissions that resist ordinary deletion.
Why is my PC slow only after a feature update, not monthly ones?
Feature updates replace far more of the system, triggering a full search index rebuild, .NET recompilation and driver re-installation all at once, on top of consuming significant disk space.
Gear We Recommend
If it turns out to be storage or memory rather than the update, here’s what we’d fit.
Browse our General Tech Accessories picks on AmazonAs an Amazon Associate, TechyGeeksHome earns from qualifying purchases
Disclosure: this post may contain affiliate links. If you buy through one of them, we may earn a small commission at no extra cost to you. We only recommend products we’ve tested or genuinely rate.
Discover more from TechyGeeksHome
Subscribe to get the latest posts sent to your email.
