Windows Update can slow a PC while it installs, but if the slowdown continues after a restart and a short idle period, treat it as a possible problem. Ignoring that distinction can make you miss a stuck update, a bad recent update, or another process using too many resources. This guide shows how to tell temporary slowdown from a lasting issue and the next step for each case.

Is Windows Update the cause?

Is Windows Update the cause?
A Windows Update error dialog appears over a pink beach background

First check whether Windows Update is still doing work. If Task Manager shows heavy CPU, disk, RAM, or network use from update-related activity, the safest move is usually to let it finish. If the PC stays slow after the update completes, look for background apps, a recently installed update, or another process instead.

Windows Update decision table

Symptom Likely cause How long it should last How to confirm in Task Manager or Settings Safest next action
High disk use during download, install, or reboot Windows Update is actively installing While the update is running Task Manager shows Disk or CPU activity tied to update work; Settings shows an update in progress Leave the PC on and let the update continue
PC feels slow right after sign-in or restart Windows is finishing post-update tasks in the background Usually short, then performance should settle Task Manager shows system activity dropping over time after sign-in Leave it idle for about 30 minutes, then restart once more to trigger any final optimizations
Update keeps failing, hanging, or repeating the same download Windows Update components may be stuck It should not keep looping Settings shows repeated failures or a stalled status instead of progress Run the Microsoft troubleshooter
Slowdown remains after the update finishes A recent update, a driver change, or another process may be using resources It should improve after the update and background tasks finish Task Manager shows another app, not Windows Update, using CPU, memory, or disk Identify the top process in Task Manager and address that process first

Say your laptop restarts after Patch Tuesday, then sits at a spinning desktop for 10 minutes while Task Manager shows disk activity from update-related work. That points to normal post-install work, not a lasting fault. Suppose the same laptop is still sluggish the next afternoon, with no update activity in Task Manager. That points away from normal update work and toward another cause.

Why is your PC slow during an update?

Windows Update can temporarily use CPU, disk, RAM, and network bandwidth while it downloads, installs, and reboots. That load is normal while the update is active. Disk often takes the first hit, then CPU, then memory, while network use shows up during download.

  1. Open Task Manager and look at Processes for CPU, Memory, Disk, and Network activity.
  2. Open Settings > Windows Update and check whether an update is downloading, installing, or waiting for a restart.
  3. If it is a laptop, plug it into AC power before letting the update continue.
  4. If Task Manager shows update activity, leave the PC alone until the download or install phase finishes.

Why is your PC still slow after restart?

If the slowdown begins right after sign-in or reboot, Windows may still be finishing post-update tasks. Those tasks can include search reindexing, file optimization, component updates, and security changes. They can briefly push CPU, RAM, or disk use high enough to make the whole system feel slow.

The safest move is to give the system a clean stretch of idle time after restart. If the machine is still sluggish after that and Task Manager no longer shows Windows Update activity, the slowdown is more likely tied to another background process or a recent update.

What to check right after restart

  1. Open Task Manager and sort by CPU, Memory, and Disk.
  2. If the top process is still tied to Windows Update or another system process, let it keep running.
  3. If the top process is a regular app, close that app and check whether the system recovers.
  4. Restart once more if the slowdown is strongest immediately after sign-in and then settles.

Background apps and startup load

Background apps can keep using memory and CPU after their windows close. That can make a freshly updated PC feel slower than expected, especially if several apps start with Windows.

Use Task Manager to identify the process eating CPU, RAM, or disk. If the slowdown is strongest right after sign-in, review startup apps in Task Manager and disable the ones you do not need at boot. That is a better first move than blaming the update itself when another app is clearly the heavier load.

  1. Open Task Manager > Startup apps.
  2. Sort by Startup impact and disable nonessential apps.
  3. Return to Processes and confirm whether CPU, Memory, or Disk use drops.
  4. If a single app stays near the top, close it and relaunch only if needed.

Stalled update checks and cache problems

Stalled update checks and cache problems
Windows Update settings screen showing an update preparing to install

If updates fail, repeat, or appear stuck, start with the Windows Update troubleshooter before any manual reset. On Windows 11, open the Get Help app for update diagnostics. If you are using Windows 10, open Settings and use the Microsoft Windows Update troubleshooter from the available troubleshooting area.

  1. Open Settings and run the Windows Update troubleshooter.
  2. On Windows 11, also open the Get Help app for update diagnostics.
  3. Check free space in Settings > System > Storage.
  4. Run Storage Sense to remove temporary files and recycle bin data if the drive is crowded.
  5. Return to Windows Update and try the update again after the check finishes.

If the drive is crowded, clear out large downloads, videos, or unused apps before trying again. Low free space can make update installs drag, and Windows Update cache cleanup is the fastest built-in cleanup step to try before moving to deeper repair work.

What if Windows Update still hangs?

What if Windows Update still hangs?
Windows Update settings screen shows update status and options

If the PC still hangs after the standard checks, move from software trouble to blockers that can prevent installation. External hardware can interfere with update troubleshooting, and some updates need administrator access. Managed work or school devices can also block changes until policy allows them.

  1. Disconnect unnecessary external hardware such as docks, drives, and accessories.
  2. Check whether the device is signed in with the right account and has permission to install updates.
  3. If it is a work or school PC, verify whether policy is blocking the update.
  4. Try the update again from Settings > Windows Update.

Another common issue is a buggy update. If the slowdown began only after a specific patch and Task Manager no longer shows update work, uninstalling that update is the cleanest test. Go to Settings > Windows Update > Update History > Uninstall Updates > Uninstall. If a recent driver changed at the same time, open Device Manager, right-click the device, open Properties, and use Roll Back Driver on the Driver tab.

If that did not work, try rollback

Use rollback only when the slowdown started after a specific update and the simpler checks did not help. That is the point where the update itself becomes a stronger suspect than temporary background work.

  1. Open Settings > Windows Update > Update History > Uninstall Updates > Uninstall.
  2. Remove the most recent update that lines up with the slowdown.
  3. If a driver changed at the same time, open Device Manager, choose the device, then select Roll Back Driver on the Driver tab.
  4. Restart and check whether the lag disappears.

Keep a note of the exact update that came before the slowdown so you can remove the right one instead of guessing. If the problem clears, leave Windows Update on and watch for the replacement patch rather than disabling updates entirely.

Keep reading

Frequently asked questions

Does windows update slow down computer?

Yes, but usually only while it downloads, installs, and reboots. That slowdown should line up with visible update activity in Settings or high system load in Task Manager. If the PC is still slow after the update finishes, look for another process, a failed update, or a recent patch that needs rollback.

Does windows update affect performance?

It can affect performance in two ways: temporary background load during installation and longer-term problems if an update triggers a bug or driver issue. Check Task Manager first. If Windows Update is no longer active, the performance hit is more likely coming from a different process or a recent change that needs rollback.

How long should a windows update slow my computer?

Temporary slowdown should last only while the update is actively running and for a short period after restart while background tasks finish. If it keeps going after that, treat it as a problem rather than normal update work. Check the update status in Settings and the active processes in Task Manager.

Is it normal for windows update to use a lot of disk?

Yes. Disk use is often the first resource to spike during update download, unpacking, and install work. That is normal if Task Manager shows update-related activity and Windows Update is still in progress. If disk stays high after the update finishes, a background app or a stuck process is a better suspect.

How do I tell if windows update is the cause of lag?

Open Task Manager and compare the top process with what Settings shows under Windows Update. If the lag matches an active download, install, or reboot, Windows Update is probably the cause for now. If the top process is a regular app or the slowdown stays after the update finishes, look elsewhere.

What should I do if my laptop is slow after windows update?

Plug it in, open Task Manager, and check whether Windows Update is still doing work. If it is, let it finish. If it is not, review startup apps, run the Windows Update troubleshooter, and use Storage Sense if the drive is crowded. If a specific update caused the slowdown, uninstall that update from Update History.