PC Slow After a Windows Update: Causes and Fixes
Patience for Two Days, Then Intervention
Short answer: slowness after a major Windows update is usually temporary and clears on its own within 24-48 hours. The cause is three background jobs waiting to finish: the search index being rebuilt, the component store being cleaned (`TiWorker.exe`), and update files being shared out to other computers. Once those complete, the machine returns to its old speed. Two situations, however, do not fix themselves and need action: the update replacing your graphics or chipset driver with Microsoft's generic one, and the `Windows.old` folder filling the disk and slowing the SSD. If it is still slow a week later, the cause is not the update settling but one of those two.
This guide covers what is normal first, then what the process you see in Task Manager actually means, and finally what to do when a week has passed and nothing has improved.
Key Takeaways
- Most post-update slowness clears within 24-48 hours; the search index and component cleanup are finishing in the background.
- If you see `TiWorker.exe` or `MoUsoCoreWorker.exe` in Task Manager, the update has not finished its work — that is normal.
- Updates sometimes replace graphics and chipset drivers with Microsoft's generic versions; that does not fix itself and the vendor driver must be reinstalled.
- The `Windows.old` folder holds 10-30 GB and slows SSD writes by filling the disk; it can be removed within 10 days once the system is stable.
- Delivery Optimization uploads update files to other computers; turning it off reduces network and disk load.
- If it is still slow after a week, the update settling is not the cause; look at drivers, startup programs and disk fullness.
After an update: what to wait out and what to act on
| Symptom | How long | Normal? | What to do |
|---|---|---|---|
| `TiWorker.exe` keeping the disk busy | 2-24 hours | Yes | Wait, leave the machine on |
| `SearchIndexer.exe` running constantly | 4-48 hours | Yes | Wait; rebuild the index if it lasts weeks |
| Stutter in games and video | Permanent | No | Reinstall the graphics driver from the vendor |
| Disk over 90% full | Permanent | No | Remove the `Windows.old` folder |
| Boot slower than before | Permanent | No | Review startup programs |
| High upload with nothing downloading | Variable | Partly | Turn off Delivery Optimization |
Is Post-Update Slowness Normal, and How Long Does It Last?
A major Windows update does not just replace files; once setup finishes it starts a set of background jobs that run for days. The three biggest are rebuilding the search index from scratch, cleaning superseded versions out of the component store, and distributing the new update files to other computers on the network.
These jobs deliberately run at low priority and only progress while the machine is idle. On a typical computer they finish within 24-48 hours. But on a laptop used a few hours a day and then shut down, the same work can stretch across a week — which is why "my computer was slow for a week after the update" is such a common experience.
Leaving the machine on and idle is the fastest fix during this period. Repeatedly shutting down, or immediately starting heavy work, postpones these jobs and extends the slowness. So the right answer for the first two days is not a setting but patience.
What Does the Process in Task Manager Mean?
Open Task Manager > Details and sort by the Disk column. The names at the top tell you directly what is happening. `TiWorker.exe` (Windows Modules Installer Worker) performs component servicing; high disk usage for hours after an update is normal and it stops on its own when done.
`MoUsoCoreWorker.exe` is the process managing the update session; if it is still running, the update chain has not completed. `SearchIndexer.exe` is rebuilding the search index. All three are names that call for waiting, not intervention.
By contrast, if the `System` process or a security product sits permanently at the top, the situation is different: a full scan may have been triggered after the update. Checking your antivirus scan history confirms it. Load drops when the scan finishes; if it does not, the scan is not the problem.
Drivers: What the Update Quietly Rolled Back
This is the most common problem that does not fix itself. Major updates sometimes replace the vendor-installed graphics, chipset or audio driver with Microsoft's generic version. The system still works but performance drops: frame rates fall in games, video playback stutters, and even interface animations lose their smoothness.
Checking is easy. Open Device Manager and look under Display adapters. If it says "Microsoft Basic Display Adapter", the real driver is gone. Downloading and installing the current driver from your graphics card vendor resolves it completely.
Do the same check for the chipset. The chipset driver package from your motherboard vendor restores the power management and storage controller settings the update disturbed. On laptops in particular, if battery life shortened after an update, this is usually why.
If It Is Still Slow After a Week
Once a week has passed with no improvement, "the update is settling" no longer explains it, and there are three places to look. The first is disk fullness. The update leaves a `Windows.old` folder holding 10-30 GB; if the disk was already tight, total usage passes 90% and SSD write speed drops noticeably. Once the system is stable, remove that folder via Settings > System > Storage.
The second is startup programs. Some updates re-enable startup items you had previously disabled. Open Task Manager > Startup apps and review the list; switch off anything you did not expect to see.
The third is a corrupted search index. If `SearchIndexer.exe` has been running for weeks and search still returns nothing, the index is inconsistent and needs a manual rebuild. If slowness persists after checking all three, it is not update-related; look into drive health, insufficient memory, or other software running in the background.
Frequently Asked Questions
Does rolling the update back fix the slowness?
Rarely. The rollback window is usually 10 days, and rolling back restarts the same background jobs, making things slower in the short term. If a driver is the cause, installing the correct driver — not rolling back — is the fix.
Is it safe to delete the Windows.old folder?
Yes, if the system has run without problems for a few days. That folder exists so you can return to the previous Windows version, and Windows deletes it automatically after 10 days anyway. Note that once removed, you can no longer roll back.
Should I clean the component store with DISM?
Once the system is stable, `DISM /Online /Cleanup-Image /StartComponentCleanup` frees space. Adding `/ResetBase` frees more but means you can no longer uninstall installed updates; use it only when you are confident everything works.
Will this happen with every update?
Monthly security updates usually do not produce this effect. Prolonged slowness is specific to major feature updates, which arrive once or twice a year.
Verdict
Most post-update slowness is not a fault but background work waiting to finish; leaving the machine on and idle for 24-48 hours is enough in most cases. Two things do not fix themselves: swapped drivers, and a disk filled by `Windows.old`.
While addressing the second, it makes sense to see what else has piled up. Disk Mop's Disk Analysis module sorts the drive by size including system folders, the Startup Manager shows the startup items the update re-enabled, and the Disk Health module tells you whether the drive itself is genuinely worn.
See what piled up on your disk after the update
One-time payment for lifetime access to all features. No subscription, no hidden fees.
Download Disk Mop Now