Windows updates can leave a PC feeling sluggish for a few hours — or, in unlucky cases, for much longer — but the causes are usually predictable and fixable if you know where to look and what to do.
Background / Overview
Large Windows updates do far more than copy files: they unpack new components, replace system files, update drivers, adjust internal databases, and trigger a raft of post-install maintenance and cleanup tasks. Those background jobs consume CPU, disk I/O, memory, and sometimes network bandwidth — and the cumulative effect is the reason many machines feel slower immediately after an update. The practical result is a short-term slowdown for most machines, but certain conditions (older hardware, slow mechanical drives, problematic drivers, or buggy updates) can turn that temporary lull into a persistent performance problem. The practical checklist below explains the five most common root causes and gives clear, tested fixes for each. The summary guidance in this article aligns with recent reporting and community troubleshooting, including the XDA Developers piece that laid out the same five reasons and practical fixes.
1) Windows Module Installer Worker (TiWorker.exe) — Windows is finishing its work
What’s happening
The service named
Windows Modules Installer Worker (process name TiWorker.exe) runs after Windows Update installs packages. It finalizes patches, prunes superseded update files, applies component store changes, and optimizes updated binaries. That can spawn heavy CPU and disk activity for minutes or hours, especially after cumulative updates or feature upgrades. This is expected behavior when Windows is catching up, but it can be the single biggest source of post‑update slowness.
Symptoms
- High CPU and disk usage in Task Manager by TiWorker.exe or Service Host processes.
- Disk thrashing, long app load times, and a sluggish UI.
- Activity that appears after a restart and keeps running in the background for many minutes to hours.
How to fix it (practical steps)
- Wait first — in most cases the best action is to let the installer finish. If you just installed major updates, allow at least 1–4 hours on lower‑end systems (shorter on modern machines).
- Check Windows Update to see if other updates are queued: Settings > Windows Update > Check for updates; install any pending packages and restart if prompted. This completes staged operations and often collapses the installer activity.
- If TiWorker appears stuck for many hours:
- Run the Windows Update troubleshooter: Settings > System > Troubleshoot > Other troubleshooters > Windows Update. Follow the tool’s recommendations; it automates many reset steps.
- Restart the Windows Update services: open Services (services.msc), stop the Windows Update service, then stop the Windows Modules Installer, delete the contents of C:\Windows\SoftwareDistribution (stop services first), then start services and check for updates again. This removes corrupted cached update data that can jam the installer.
- If nothing works, use System File Checker and DISM to repair component store corruption:
- Open an elevated command prompt and run:
sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth
These commands can repair files that prevent updates from completing.
Caution
Disabling the Windows Modules Installer or permanently stopping Windows Update is a stopgap and increases security risk. Use it only briefly for troubleshooting; re-enable updates as soon as you can.
2) Old, missing, or incompatible drivers — the silent performance killers
What’s happening
Windows Update may deliver
generic or broadly compatible drivers (especially for graphics and chipsets) rather than the vendor‑optimized package. After an OS update, vendor drivers that previously worked might be replaced, rolled back, or left behind. Graphics, chipset, and storage drivers are the most likely to produce visible slowdowns, stuttering, crashes, or reduced gaming frame rates. Incompatibilities can also show as long boot times or high CPU usage by driver-related tasks. Microsoft documents that Windows Update can supply recommended drivers, but the manufacturer package often contains the performance optimizations users need.
Symptoms
- Lower FPS in games after a system update.
- Slower UI, longer app startup, or unexpected crashes.
- Newly visible artifacts or system instability after updating.
How to fix it (clean driver refresh)
- Use the hardware vendor’s official updater first:
- NVIDIA: GeForce Experience or manual driver download.
- AMD: AMD Software (Adrenalin Edition) or manual download.
- Intel: Intel Driver & Support Assistant or manual download.
Official installers are the preferred route for GPU updates because they include vendor patches and optional components.
- For persistent issues, perform a clean uninstall:
- Download the latest driver package from the vendor site before you remove anything.
- Use Display Driver Uninstaller (DDU) in Safe Mode to remove all traces of the old driver (this prevents leftover bits from causing conflicts). After DDU finishes, install the freshly downloaded vendor driver. DDU is widely used by enthusiasts and is documented by its authors.
- For chipset, storage, and network drivers, check the PC OEM (Dell, HP, Lenovo, etc. first; some laptops require OEM‑specific versions. If you cannot find OEM drivers, return to the vendor’s site for chipset or controller firmware.
- Roll back a driver if the problem started immediately after an update: Device Manager > Display Adapters (or relevant category) > Properties > Driver > Roll Back Driver.
When to be conservative
- If your machine is an OEM laptop, prefer the manufacturer’s driver package unless the manufacturer recommends the vendor release.
- Avoid third‑party driver “updaters”; use official vendor or Microsoft channels.
3) Windows Search indexing — the background indexing rebuild
What’s happening
When Windows or major apps (Outlook, Copilot features, etc. change during an update, the
Search Indexer (SearchIndexer.exe / SearchHost.exe) may
rebuild the index. Indexing scans files and metadata and writes database entries; on slower drives or low‑RAM systems the I/O and CPU cost can be noticeable. Rebuilding a large mailbox or an entire drive can take hours or even days on older hardware. Microsoft documents the indexing modes and advises that initial indexing can take a couple of hours; on large data sets it can extend further.
Symptoms
- SearchIndexer.exe or SearchHost.exe running high in Task Manager.
- Slow file browsing, delayed search results, and elevated disk activity.
- Outlook search results delayed or partial until indexing completes.
How to fix or mitigate
- Let it finish if possible — the indexer is doing necessary work and will complete faster on SSDs.
- Reduce indexing scope:
- Settings > Privacy & security > Searching Windows > Find my files → choose Classic (indexes only Documents, Pictures, Music, and Desktop) instead of Enhanced (entire PC). This change dramatically reduces indexing workload.
- Rebuild manually if the index is corrupted:
- Settings > Privacy & security > Searching Windows > Advanced indexing options > Advanced > Rebuild. Expect a warning that rebuilding may take a long time.
- Exclude heavy folders (video libraries, backup folders, VM images) from indexing so the service doesn’t repeatedly scan constantly changing or huge files.
- If indexing breaks or repeatedly fails, use the Search and Indexing troubleshooter (Settings > System > Troubleshoot > Other troubleshooters > Search and Indexing) or follow Microsoft troubleshooting guidance for indexing performance.
Cautionary note
Disabling search completely is a last resort. You lose instant search functionality and will rely on slower file enumeration. Instead, fine‑tune the index’s scope and rebuild only when necessary.
4) Feature resets, re-enabled services, and bloatware — Windows can “undo” customizations
What’s happening
Major upgrades or version feature updates can behave like a partial system reinstall: core system files are replaced, default configuration files are restored, and certain features that had been disabled or removed by the user may reappear. This can re-enable visual effects, background telemetry, or OEM apps that consume CPU and memory. The result is a system that looks like it regained its defaults — and that default behavior can be more resource‑hungry than the carefully tuned configuration you had prior to the upgrade. Community reporting shows this is common after milestone upgrades and can reintroduce preinstalled apps and startup entries.
Symptoms
- Previously disabled visual effects or services are back.
- New startup entries, “free” apps, or trialware reappear.
- Higher memory and CPU use after a major version upgrade.
How to fix it
- Recheck performance settings:
- Control Panel > System > Advanced system settings > Performance Settings, and reapply “Adjust for best performance” or selectively disable animations you previously turned off.
- Audit Startup and Services:
- Task Manager > Startup: disable unwanted startup items.
- Services (services.msc): set non-essential services to Manual or Disabled (be cautious — don’t disable security or input device services).
- Uninstall reintroduced apps:
- Settings > Apps > Installed apps: remove bloatware and trial applications you don’t want.
- Reapply privacy/performance tweaks (e.g., OneDrive pause, telemetry settings) that you previously used to keep the machine lean. The goal is to restore the set of intentional changes you had before the update.
5) Faulty updates, regressions, and known‑issue rollouts — when the update itself is the problem
What’s happening
Occasionally Microsoft ships an update that has a regression for a particular hardware or software configuration. These can cause memory leaks, driver conflicts, storage/database corruption, or heavy resource usage. Microsoft maintains a
Windows release health dashboard that lists
known issues and any mitigations or workarounds; administrators and power users should check that dashboard before chasing obscure local causes. If an update is confirmed to be the problem, the recommended action is often to apply a Microsoft-provided workaround or uninstall/roll back the problematic update until a fix is available.
Symptoms
- System slowdowns that coincide exactly with a specific KB installation.
- Widespread reports on vendor forums, social channels, or Microsoft support with matching symptoms.
- Fixes from Microsoft documented on the release‑health page.
How to investigate and remediate
- Confirm timing and scope:
- Open Settings > Windows Update > Update history to see which KBs installed and when.
- Search the Windows release health page for the KB number to see if Microsoft has documented a known issue.
- If there’s a confirmed issue and Microsoft suggests a workaround, follow those steps. If Microsoft recommends removal, uninstall the update:
- Settings > Windows Update > Update history > Uninstall updates. Pick the offending KB and uninstall (some updates can’t be removed; follow Microsoft’s instructions).
- Use System Restore or the Recovery environment to remove updates if Windows won’t boot, or roll back feature updates via Settings > System > Recovery > Go back (availability is limited — typically 10 days after a feature upgrade).
- If the issue is driver‑related within the KB (Microsoft often documents which driver families are impacted), roll back the driver or obtain a vendor hotfix.
When to contact support
If the release health dashboard shows no known issue yet the slowdowns are severe and reproducible, gather logs (Event Viewer, Reliability Monitor) and open a support ticket with Microsoft or your OEM — they can escalate to engineering if it is a new regression.
General checklist: quick diagnostics and fixes to try now
- Open Task Manager (Ctrl+Shift+Esc) and sort by CPU, Disk, or Memory to identify top consumers.
- If TiWorker.exe or Windows Update is active, wait several hours if possible. Then check Windows Update and apply any pending optional updates.
- Rebuild the search index only if SearchIndexer is repeatedly failing or returns corrupt results; otherwise reduce indexing scope.
- Update or clean‑install GPU and chipset drivers (vendor installers or DDU + vendor installer for stubborn cases).
- Run SFC and DISM to repair system files.
- Audit Startup items and uninstall reinstalled bloat apps.
- Check the Windows release health dashboard before uninstalling updates; when needed, uninstall via Update history.
When slow = symptomatic of deeper problems (and what to do)
If you’ve waited, updated drivers, rebuilt the index, and checked for release‑health advisories but the PC is still slow, treat the slowdown as a potential symptom of corruption or hardware limits:
- Corruption: Run full checks (sfc /scannow; DISM /RestoreHealth; chkdsk C: /f). If errors persist, consider an in-place repair install or clean install (back up data first).
- Hardware: On machines with HDDs, heavy indexing and update work will always be slower. Upgrading to an SSD and adding RAM are the single most effective remedies for persistent sluggishness.
- Firmware: For storage and chipset issues, check BIOS/UEFI and SSD firmware updates from OEMs — sometimes performance regressions are fixed at firmware level.
What to watch for and a final take
- Short‑lived slowdowns (minutes–a few hours) after updates are normal and usually don’t require intervention.
- Persistent, reproducible slowdowns that start immediately after a given update should be investigated via Update history and the Windows release health dashboard; if confirmed, uninstall or apply Microsoft’s workaround.
- Drivers are often the true source of lingering performance problems — vendor packages and a clean install (or DDU) are the best remedy.
- Indexing and background maintenance are essential services; limit their scope rather than disable them permanently unless you accept the trade‑offs.
In most cases, the five reasons outlined here — Windows Module Installer activity, outdated/incompatible drivers, search indexing, restored defaults/bloatware, or a buggy update — cover the likely causes of post‑update slowdown. Follow the step‑by‑step fixes above in order of least‑to‑most‑invasive: wait → apply pending updates → restart → run troubleshooters → target drivers and indexing → roll back or uninstall only if you can confirm the update is the root cause. For routine maintenance, keep a habit of checking for optional driver updates in Windows Update and maintaining a small index scope on older machines to keep the system responsive without sacrificing search usefulness. Conclusion: most slowdowns after Windows updates are temporary and fixable — but patience plus a methodical checklist (check Task Manager, let system maintenance finish, update drivers, rebuild indexes only when needed, and use Microsoft’s release‑health guidance) will resolve the vast majority of issues.
Source: XDA
5 reasons your PC can feel slow after a Windows update, and how to fix each one