PC Slow After Windows Update — Fix

PC slow after a Windows update describes a specific pattern: the computer performs normally before an update, slows down immediately after the update and restart, and either gradually returns to normal speed or remains slow. According to Microsoft’s official Windows Update documentation, the post-update period involves several mandatory background processes that run with high priority and temporarily dominate CPU and disk resources before completing and releasing those resources.

PC slow after Windows update fix path: wait for post-update tasks, restart if pending, check device manager for driver conflicts, run Windows Update troubleshooter, repair with DISM and SFC, roll back update if still slow after 24 hours

What causes a PC to slow down after a Windows update

Post-update background processing — After a Windows update installs and the computer restarts, Windows runs TrustedInstaller (component store cleanup), SearchIndexer (search database rebuild), SysMain (memory map update), and Delivery Optimization (distributing update files to other devices on the network). These tasks have high disk and CPU priority and run for 30–120 minutes, making the system noticeably sluggish during this window.

Driver replacement — Windows updates can replace installed hardware drivers with versions bundled in the update package. If the bundled driver is older than the driver previously installed, or if it has a compatibility issue with specific hardware, performance degradation or device instability can result.

Power management changes — Some Windows updates modify power plan settings or introduce new power management features that change CPU frequency scaling behaviour, potentially causing the CPU to throttle more aggressively than it did before the update.

Corrupted update installation — If the update download or installation was interrupted (power loss, forced restart, network drop during update), the resulting partial installation can leave system components in an inconsistent state, causing ongoing instability rather than the temporary post-update background processing pattern.

How to fix a slow PC after a Windows update

Start with step 1 — most post-update slowdowns are temporary and resolve without intervention. If performance has not improved after 24 hours, proceed through the remaining steps.

How to verify the fix

After applying fixes, open Task Manager > Performance and observe CPU and Disk at idle. If no Windows Update processes (TrustedInstaller, TiWorker, SearchIndexer, WaasMedicSvc) appear in the top 10 CPU or Disk consumers, the post-update background tasks have completed. Test the performance of the tasks that were slow before — application launch times, web browsing, file operations — and compare with the pre-update experience.

Known limitations

Some Windows updates permanently change system behaviour in ways that affect performance on specific hardware configurations. When this happens, rolling back the update or using System Restore is the only way to restore the previous performance level, as the change is not caused by temporary background processing but by a deliberate change to Windows configuration or the hardware driver stack. Microsoft typically releases follow-up updates that address driver compatibility issues reported after major updates — checking Windows Update for available updates after the problematic update sometimes applies a compatibility fix automatically.

Frequently Asked Questions

Why does TrustedInstaller use 100% CPU or disk after a Windows update?

TrustedInstaller (Windows Modules Installer Worker — TiWorker.exe) processes Windows update packages after installation, cleaning up old versions of updated components and optimising the Windows component store. This is normal post-update behaviour that can run for 30–120 minutes on computers with slow storage. It will stop on its own. Do not end the TrustedInstaller process — doing so can corrupt the component store and require a Windows repair. Leave the computer on and idle and the process will complete.

What is WaasMedicSvc and why is it using high CPU after an update?

WaasMedicSvc (Windows Update Medic Service) is a self-healing service that monitors and repairs Windows Update components if they are disrupted. It runs with elevated privileges and cannot be permanently disabled through normal means. High WaasMedicSvc CPU usage after an update indicates Windows Update is checking the integrity of the newly installed update's components — this typically settles within 30–60 minutes. If WaasMedicSvc remains at high CPU for more than 2 hours, run the Windows Update Troubleshooter in Settings > System > Troubleshoot.

Can a Windows update permanently slow down a computer?

Yes, in some cases. Windows updates can introduce driver changes that reduce GPU or storage performance, enable new background features that consume additional resources, or modify power management behaviour that throttles the CPU differently. If performance does not recover after 24 hours and background tasks are no longer running, the update itself changed system behaviour. Rolling back the update restores previous performance. If the 10-day rollback window has passed, use System Restore if a restore point exists from before the update, or contact Microsoft Support for guidance.

Should I pause Windows updates to prevent slowdowns?

Pausing Windows updates delays security patches, which increases vulnerability to malware and exploits. A better approach is to schedule updates to install during hours when the computer is not in use — open Settings > Windows Update > Advanced options and set Active hours to the time period when you use the computer most. Windows will install updates and run post-update tasks outside these hours. Updates can also be set to install when the computer restarts overnight, limiting disruption to working hours.

How long does it take for Windows 11 to return to normal speed after an update?

Most post-update background tasks complete within 1–2 hours on SSDs and 2–4 hours on HDDs. The longest task is typically the search index rebuild, which can take 3–6 hours if the drive has a large number of files. If the computer is not fully responsive after 24 hours and background processes are no longer running at high usage in Task Manager, the update itself (rather than temporary post-update tasks) has changed system performance — in this case, driver investigation or update rollback is warranted.