How to Fix Slow Boot Times After Installing a Recent Windows 11 Update

Quick fix: Open Settings → Apps → Startup, disable everything you don’t need at boot. Then run Disk Cleanup as admin with Windows Update Cleanup ticked. If still slow, the WindowsApps install state is corrupted from the update — repair with sfc /scannow followed by DISM /Online /Cleanup-Image /RestoreHealth.

Before the latest cumulative update, your PC booted in 30 seconds. Now it’s 90 seconds — sometimes longer if you let it sit on the spinning circle. The update added new components, may have re-enabled disabled startup items, and likely left a chunk of post-install operations to complete on next boot. Three culprits to check in order.

What causes this

Updates add three boot-time burdens. Post-install operations: registry merges, driver re-registration, and component updates that finish on next boot. Re-enabled startup items: Windows occasionally re-enables apps you previously disabled at startup (especially after major feature updates). Updated drivers: a new GPU or storage driver might fail signature verification once, requiring a fallback path that’s slow.

Less commonly, the WindowsApps install state itself becomes corrupted, causing the Sign-in screen to delay while Windows tries to repair packages on each boot.

Method 1: Audit and disable startup apps

The first thing to check. Updates often re-enable startup items you turned off.

1. Press Ctrl + Shift + Esc to open Task Manager.
2. Click the Startup apps tab.
3. Sort by Startup impact column. Anything labeled High is a candidate for disabling.
4. For each High-impact app you don’t need at boot: right-click → Disable. Common offenders: Microsoft Teams, Spotify, OneDrive (if you don’t need it auto-synced), gaming launchers (Steam, Epic, Razer Synapse).
5. Also check Settings → Apps → Startup — same list but UI shows toggles. Cross-check.
6. For deeper inspection, open Terminal (Admin) and run:

   Get-CimInstance Win32_StartupCommand | Format-Table Name, Command, Location

   Shows every registered startup entry including registry-level ones not visible in Task Manager.

7. Reboot and time boot to login screen.

Disabling 4–5 High-impact items can cut 20–60 seconds from boot time.

Method 2: Clean up Windows Update leftovers

Updates leave temp files that the system processes during early boot.

1. Open Disk Cleanup: press Win + R, type cleanmgr, press Enter.
2. Pick the C: drive. Click OK.
3. Click Clean up system files button (requires admin elevation).
4. Tick: Windows Update Cleanup, Delivery Optimization Files, Temporary Files, Windows upgrade log files, Previous Windows installation(s) (if present — this can free 10+ GB).
5. Click OK → Delete Files. The cleanup takes 5–20 minutes depending on how much accumulated.
6. Reboot. The first reboot after cleanup may itself be slow as Windows finalizes; subsequent reboots should be faster.
7. Also clear the Software Distribution download cache:

   net stop wuauserv
   rmdir /s /q C:\Windows\SoftwareDistribution\Download
   net start wuauserv

   This removes any partial update downloads sitting on disk.

This route removes the “processing accumulated updates” boot delay.

Method 3: Repair system files

For when Methods 1 and 2 don’t restore boot speed — indicates corrupted system files from the update.

1. Open Terminal (Admin).
2. Run:

   sfc /scannow

   This scans all protected system files and replaces corrupted ones from the Windows component store. Takes 5–15 minutes.

3. If SFC reports corrupted files that it couldn’t repair, follow with:

   DISM /Online /Cleanup-Image /RestoreHealth

   This downloads fresh copies of corrupted components from Windows Update. Takes 10–30 minutes.

4. After DISM completes, run sfc /scannow again to apply the now-healthy component store to system files.
5. Reboot.
6. If you suspect a specific update is the cause: Settings → Windows Update → Update history → Uninstall updates. Remove the most recent update and reboot. If boot speed returns, that update is at fault.

The trade-off: uninstalling an update means losing whatever fix or feature it provided. Use it as a diagnostic confirmation, then wait for Microsoft to ship a follow-up KB that fixes the regression.

How to verify the fix worked

• Time the boot from pressing power button to login screen. Compare to pre-update baseline.
• Open Task Manager → Startup apps → Last BIOS time. Should be a few seconds, not 20+.
• Run Event Viewer → Applications and Services Logs → Microsoft → Windows → Diagnostics-Performance → Operational. Event IDs 100–110 log boot phase timings. Look for entries with duration anomalies.

If none of these work

If boot is still slow after Methods 1–3, the cause is hardware-level slowness coupled with software change. Check storage health: open Terminal (Admin) and run Get-PhysicalDisk | Format-Table FriendlyName, HealthStatus, Wear. If HealthStatus is anything other than Healthy, or Wear is above 80%, your SSD is failing — boot times stretch as the controller does internal recovery on each read. Replace the SSD, restore from backup. For PCs that recently received a BIOS update along with the Windows update: check the BIOS settings for any “Fast Boot” or “Boot Optimization” option that may have reset to default. Enable it. Also check the boot order — some BIOS updates re-introduce network or USB devices ahead of the SSD, causing a timeout while Windows tries to boot from absent media.

Bottom line: Most post-update slow-boot cases are startup app bloat or accumulated update leftovers — Task Manager’s Startup tab plus cleanmgr handles both. SFC/DISM is the path forward when boot delay is from corrupted system files.