The Morning After Patch Tuesday: Why Your PC Drags and What to Do About It

Second Tuesday of the month comes round, Windows pulls down its monthly batch of security fixes, and then your PC turns into a different machine. The fan spins up, the mouse pointer stutters, and the Start menu needs two goes to open. If that sounds familiar, take a breath. This is one of the most common things we hear about at BootUp PC, and it is almost never the catastrophe it feels like at 8am on a Wednesday.

What Windows is actually doing to your PC

People tend to assume an update is 'finished' when the restart completes. In reality, installing the files is only half the job. For a day or two afterwards, Windows gets on with the housekeeping, and most of it is disk-heavy:

• Component cleanup. Windows archives the old update files so you can uninstall them later, then squashes them into the WinSxS folder. Lots of small reads and writes, all of which a mechanical hard drive feels keenly.
• Background code optimisation. Updates to .NET components trigger a recompile of code on your machine. Expect a burst of processor activity for ten or twenty minutes — sometimes longer on an older CPU.
• Windows Defender catching up. Fresh virus definitions usually set off a background scan, and if the scheduled scan was missed while the PC was off, it will want a full one.
• Search index rebuilding. Windows Search recrawls files it thinks have changed. On a PC with thousands of photos, that can run for hours.
• Cloud re-syncing. OneDrive, Dropbox and Google Drive all re-check their folders after a restart, and that means a lot of network and disk traffic.
• Driver shuffling. Windows Update sometimes pushes new drivers along with security patches, and every new device detected is another small flurry of work.
• Automatic Maintenance. Windows likes to run its tidy-up tasks at two or three in the morning when the PC is idle. If yours was switched off, it simply tries again later — occasionally while you are trying to write an email.

All of that competes for the same processor and the same disk as the thing you are trying to do. On a machine with an SSD it is barely noticeable. On one with an older spinning hard drive, it can feel like wading through treacle.

The 48-hour rule: temporary crawl or real problem?

Give it two days before you start worrying. There is a fairly clear line between the post-update hangover and something genuinely wrong.

Likely temporary:

• The slowdown is worst in the first hour after boot and eases off.
• It mostly happens when you are not touching the PC, or straight after a restart.
• Task Manager shows disk or processor busy but falling away over time.
• The fan is loud for a while, then settles.
• Everything still opens, just more slowly than usual.

Worth investigating:

• Blue screens, random restarts, or the PC failing to boot at all.
• The disk pinned at 100% for days rather than minutes.
• A specific thing has stopped working — no sound, no Wi-Fi, the printer has vanished.
• Apps that simply never open, or files that refuse to save.
• Repeated errors in the update history, or the same update trying and failing in a loop.
• Clicking, ticking or grinding noises from inside the case. That is hardware, not software, and it is worth stopping and backing up.

Step one: a proper restart, not a shutdown

This catches people out constantly. Windows uses a feature called Fast Startup, which means clicking Shut down does not really shut anything down — it hibernates the core of the system so the next boot looks quicker. Background maintenance tasks can survive that and keep limping along.

Use Start > Power > Restart instead. Or hold down the Shift key while you click Shut down, which forces a full, honest shutdown. Doing that once or twice after a big update clears a surprising number of minor wobbles.

Step two: give it a quiet night on mains power

Plug the laptop in, leave it switched on but idle, and go to bed. Automatic Maintenance will run in its proper window, the scans will finish, and the index will get built. Next morning, restart once more. That single overnight session fixes more post-update sluggishness than any download ever will.

Step three: make sure the update actually finished

Open Settings > Windows Update and look for a pending restart or a red warning. If an update has failed, Windows usually shows an error code — long strings starting 0x800. Copy it into a search and you will almost always find a specific, well-known cause. There is also a built-in Windows Update troubleshooter under Settings > System > Troubleshooters, which is safe to run and clears a lot of stuck update queues.

Step four: check you are not running on fumes

Windows needs roughly 15 to 20GB of free space to work comfortably, and a big update can eat into that. If your drive is nearly full, everything slows down while Windows hunts for room.

Open Settings > System > Storage and switch on Storage Sense, which clears temporary files automatically. For update leftovers specifically, search for Disk Cleanup, choose Clean up system files, and tick Windows Update Cleanup. It is a Microsoft tool, it is safe, and it can free several gigabytes. Do not go deleting folders inside C:\Windows by hand, no matter what a forum tells you.

Step five: thin out what starts with Windows

Press Ctrl+Shift+Esc for Task Manager and open the Startup apps tab. You will often find five or six things you did not knowingly install, all launching at once and fighting the update's background work. Right-click and disable anything you do not need the moment you log in — cloud drives, game launchers, chat apps. Nothing is uninstalled; it just starts when you open it.

Step six: the two repair commands worth knowing

If things are still odd after a couple of days, Windows has two built-in checks that repair corrupted system files. They are free, they are Microsoft's own, and they are not as scary as they look.

1. Right-click Start, choose Terminal (Admin) or Command Prompt (Admin), and click Yes.
2. Type sfc /scannow and press Enter. Let it run to 100% — usually ten to twenty minutes. Do not close the window.
3. Then type DISM /Online /Cleanup-Image /RestoreHealth and press Enter. This one takes longer and can appear to stall around 20%. Let it be.

A restart afterwards is a good idea. If either tool reports it fixed something, that is your answer.

Step seven: if one specific thing broke

Updates occasionally upset a driver. If your sound vanished or the Wi-Fi stopped the day after Patch Tuesday, open Device Manager (right-click Start), find the device with a yellow warning triangle, right-click it, choose Properties > Driver tab > Roll Back Driver. That returns to the previous version, which was working fine.

If the whole machine is misbehaving and you need it back now, Settings > Windows Update > Update history > Uninstall updates lets you remove a recent patch, and System Restore can roll the PC back to a restore point taken before the update. Both are reversible and neither loses your documents. Do bear in mind that uninstalling a security update leaves you exposed, so treat it as a stopgap and let Windows reinstall the fixed version later.

Things to avoid while you are feeling impatient

Skip the registry cleaners and the 'driver updater' tools that turn up in search results. They cause far more problems than they solve. Ignore any pop-up or phone number claiming to be Microsoft support — Microsoft does not cold-call about updates. And please do not reinstall Windows as a first move; it is the biggest hammer in the toolbox and you rarely need it.

When it really is time to call it

If a week has passed, you have restarted properly, run the repair commands, freed up space and rolled back the offending driver, and the PC is still crawling, then a repair install — reinstalling Windows over the top while keeping your files — is the sensible next step. Back up first, always. But for the vast majority of post-Patch Tuesday complaints, a restart, an overnight idle session and a bit of patience is all it takes. Your PC is not broken. It is just tidying up.