Anyone Else Seeing Slow App Launch Times After Recent Windows Update?

samHoney

Member
Joined
Nov 17, 2025
Messages
9
Hey everyone,
After the latest Windows update, a bunch of my desktop apps (like VLC, Notepad++, and even File Explorer at times) are taking noticeably longer to open. I’ve already tried clearing temp files and checking startup programs, but nothing changed.


Is this a known issue with the update, or could it be something on my end? Any fixes or tweaks you’d recommend?
 
Solution
Hey samHoney — that’s a common report lately. A number of users have noticed apps (including File Explorer and third‑party apps) opening much more slowly after recent cumulative updates, and the community has converged on a few reliable diagnostics and workarounds. Before we dive in, a couple quick questions:
  • Which Windows are you on (Windows 11 or Windows 10) and which build/version (Settings → System → About)?
  • Does the slowness only happen right after sign‑in (startup apps), or do apps also open slowly when you launch them later during a session?
  • Did the problem start immediately after a specific Windows update you remember installing?
What’s going on (short)
  • Multiple users have reported slower startup /...
Hey samHoney — that’s a common report lately. A number of users have noticed apps (including File Explorer and third‑party apps) opening much more slowly after recent cumulative updates, and the community has converged on a few reliable diagnostics and workarounds. Before we dive in, a couple quick questions:
  • Which Windows are you on (Windows 11 or Windows 10) and which build/version (Settings → System → About)?
  • Does the slowness only happen right after sign‑in (startup apps), or do apps also open slowly when you launch them later during a session?
  • Did the problem start immediately after a specific Windows update you remember installing?
What’s going on (short)
  • Multiple users have reported slower startup / app‑launch behavior after recent cumulative updates (reports for several KBs like KB5062660 appeared in community threads).
  • A widely used community workaround is to disable Windows’ “startup delay” behavior by adding values under Explorer\Serialize; that fix has helped many people. Guides from HowToGeek, TheWindowsClub and others explain the same registry tweak.
Safe step-by-step I’d try (in this order)
1) Quick checks (no changes)
  • Reboot and try launching the affected apps. Note whether the delay is only immediately after login or at any time.
  • Try launching an app from Task Manager → File → Run new task (type the full exe path) so we can see whether all launch methods are slow.
  • Open Task Manager (Performance / Details) while launching to see CPU / disk spikes that coincide with the slow launch.
2) Clean boot test (isolates third‑party interference)
  • Run msconfig → Services → Hide Microsoft services → Disable all → Startup tab → Open Task Manager and disable non‑Microsoft startup items → Restart.
  • If apps open normally after a clean boot, a 3rd‑party service/startup item (AV, shell extension, updater) is likely the cause.
3) Safe Mode test
  • Boot to Safe Mode and try opening explorer / Notepad++ / VLC. If they’re fast in Safe Mode, suspect a driver, shell extension, or third‑party background process.
4) Community-recommended registry fix (most likely to help for startup-delay issues)
  • Create a System Restore point first (highly recommended).
  • Open Notepad, paste the following and save as disable-startup-delay.reg (then double‑click to import) OR add manually in regedit:
    Windows Registry path:
    HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Serialize
    Values (DWORD 32-bit):
    StartupDelayInMSec = 0
    WaitForIdleState = 0
  • Reboot and test. This removes Windows’ intentional pause before launching user startup apps and has fixed the long‑startup delay for many users. Guides: HowToGeek and TheWindowsClub discuss this tweak. Important cautions: this increases simultaneous CPU / I/O activity during login on low‑end machines. If you see worse behavior after the change, remove the two values (or delete the Serialize key) and reboot to revert.
5) Other useful checks
  • Check Event Viewer (Windows Logs → Application & System) right after a slow launch to see any errors/timeouts tied to explorer or the app.
  • Temporarily disable 3rd‑party shell extensions (use ShellExView) — bad shell extensions commonly slow Explorer.
  • Check SysMain (Superfetch) service status — sometimes stopping it briefly for testing shows if disk filing is related.
  • Make sure AV isn’t scanning every exe on launch; test by briefly disabling real‑time protection (or check AV logs).
6) Last resort: uninstall recent update
  • If you can identify a specific KB that coincides with the change (Settings → Windows Update → Update history → Uninstall updates), you can uninstall it and test. Some people have done that for problematic KBs; be aware this removes that patch’s security fixes. If you uninstall, consider hiding the update until Microsoft issues a fix. Community threads show users doing this for certain KBs.
How I’d proceed now
  • Tell me: Windows version/build and whether the slowdown is only at login or anytime.
  • If it’s mainly startup apps (your mention of many apps that normally start with Windows fits): try the registry Serialize fix after creating a restore point and report back the result. If you want I can paste an exact .reg file you can copy/paste.
Useful reading / references I used
  • Community reports about slower startup apps after recent updates (example thread).
  • HowToGeek guide on disabling startup delay (registry method).
  • TheWindowsClub article describing the same registry tweak and cautions.
  • Background on Explorer features/pauses and paused Explorer features rollout (context for Explorer behavior).
If you want, I can:
  • Give you the exact .reg file text to paste (and the exact reg.exe commands) so you can apply/undo safely.
  • Walk you through a clean boot or how to check Event Viewer entries and interpret them.
Which would you like to try first?
 
Solution