Chicago
Track Your Order
0
Your Windows laptop is probably wasting performance on startup
It's easy to think slow boot means your laptop is old or your SSD is dying. That was my first assumption, too, until I started timing things and realized the hardware was fine. The real problem was everything Windows was doing before and after I saw my desktop, and most of it was invisible to me.
The frustrating part is that the usual advice doesn't help much. You disable a few startup apps in Task Manager, run a cleanup tool, and the boot still drags. That's because the startup apps list in Task Manager only shows a fraction of what actually runs at boot, and a chunk of the delay happens in places Task Manager can't see at all. So instead of guessing, I went looking for where the time was actually going.
If "Last BIOS time" is high, Windows tweaks won't save you
The delay before Windows even starts loading
I spent a while trimming startup apps before I noticed something I had been ignoring. In Task Manager's Startup apps tab, in the top-right corner, there is a value called Last BIOS time. Mine averaged over 25 seconds, and that number has nothing to do with Windows.
Before the Windows logo appears, your motherboard loads its BIOS or UEFI firmware and runs hardware checks on your drives, RAM, GPU, and keyboard before handing control to Windows. Last BIOS time is simply how long the pre-boot phase took the last time you started up.
So if that number is high, no amount of Windows tweaking will fix it. The fixes live in your firmware. Entering BIOS setup and disabling boot devices you never use, like network boot or an optical drive, stops the firmware from probing them every time. Enabling the BIOS-level fast boot option skips some repeated checks, and a BIOS update can bring its own improvements.
That said, if your Last BIOS time is already under 10 seconds, leave it alone. Boards with multiple drives or RGB controllers naturally take longer to initialize, and no tweak will make old firmware behave like new.
Task Manager is lying about your startup apps
Why does the Startup tab show only part of the picture?
Once I ruled out the BIOS, I went back to the startup apps, and this is where I learned the Task Manager list cannot be trusted on its own. Windows has over 200 places a program can hook into startup, called Autostart Extensibility Points, and the Startup apps tab watches only a narrow slice of them.
It mainly covers Run registry keys and items in the Startup folder. It does not show scheduled tasks set to trigger at logon, auto-start services, drivers, or shell extensions that load with File Explorer. So your laptop can carry a heavy startup load while Task Manager still shows a short list.
For the full picture, I use Autoruns, a free Sysinternals tool from Microsoft. It needs no installation, enumerates every known autostart location, and color-codes entries so missing files and unsigned binaries stand out. It is also a useful way to spot malware that hides in startup locations Windows doesn't surface. It is overwhelming at first, so I turn on Hide Windows Entries and Hide Microsoft Entries in the Options menu to see only third-party items, then disable rather than delete anything I am unsure about.
Using PowerShell to find hidden startup apps
A faster way to list what loads at boot
Autoruns is thorough, but sometimes I just want a quick, readable list without scrolling through 19 tabs. For that, I open PowerShell and run a single command.
The command is Get-CimInstance Win32_StartupCommand | Select-Object Name, Command, Location, User | Format-List. It pulls startup entries from places Task Manager skips, including the per-user and all-users Run keys, leftover RunOnce entries, and both Startup folders. The Location and User fields tell me exactly where each entry lives and which account it affects.
If you want something easier to scan, swap Format-List for Out-GridView to get a sortable table, or pipe the output to a text file with >C:\startup_audit.txt to keep as a baseline. Just know this command still misses scheduled tasks and auto-start services, so I treat it as a quick first pass. Removing an entry you don't recognize can break something, so disable and test before deleting anything.
Windows already logged why your PC is slow
The diagnostics log that names the culprit
After all that manual digging, I found out Windows had been quietly recording the answer the whole time. A hidden log called Diagnostics-Performance tracks every slow boot and tells you which process added how many milliseconds.
You'll find it in Event Viewer under Applications and Services Logs > Microsoft > Windows > Diagnostics-Performance > Operational. Event ID 100 logs the total boot duration after each startup. Event ID 101 is the useful one, since it lists the specific executables that delayed boot and how much time each cost.
To cut through the noise, I use Filter Current Log and filter by Event ID 101. For each event, the File Name and Degradation Time fields show what slowed things down and by how much. There is no universal good number, but a delay around 1,000 to 3,000 ms is worth a look, and anything above 3,000 ms is a real drag, especially if the same app keeps showing up across multiple boots. Once you know the offender, disable it from the Task Manager Startup tab, or change a non-critical service from Automatic to Automatic (Delayed Start) in Services so it loads after your desktop is ready.
A quick boot still feels slow if Windows lags after login
When the desktop is up, but nothing responds
Here is something I learned the hard way. You can reach the desktop quickly, and the laptop can still feel slow, because boot time and responsiveness are two different things. On a Lenovo Yoga 7 Slim Ultra I set up, the hardware was excellent, but Windows 11 defaults made it sluggish after login.
The first culprit was OEM bloat. The laptop shipped with nearly a dozen startup apps enabled, including several Lenovo utilities and Microsoft components like OneDrive and Teams. I went to Settings > Apps > Startup and disabled the ones I didn't need, which is one of the simplest ways to stop unnecessary programs from dragging out your boot.
Two more defaults helped. Under Settings > Accessibility > Visual effects, turning off Transparency effects reduced the constant GPU and CPU work Windows does to blend layered windows. And under Settings > Apps > Installed apps, I used each app's Advanced options to set Background app permissions to Never for tools I never use in the background. None of this is dramatic alone, but together it made the machine feel quicker.
Fast Startup costs you more than the seconds it saves
Why the feature meant to speed up boot can hold you back
The last setting I changed is one Microsoft turns on by default and calls a feature. Fast Startup is a hybrid of shutdown and hibernation. Instead of fully closing everything, Windows saves the kernel and loaded drivers to the hibernation file and reloads that snapshot on the next boot.
It made sense in the Windows 8 era, when most PCs used slow mechanical drives. On a modern SSD that already cold-boots in seconds, the time saved is minimal, and the trade-offs are not. Because the kernel session is preserved, memory leaks and misbehaving services can carry over across shutdowns. You can see this in Task Manager, where system uptime keeps climbing for days even though you shut down nightly. It causes other headaches too, like updates that apply incompletely and dual-boot setups that struggle to mount the Windows partition. To turn it off, go to Control Panel > Hardware and Sound > Power Options, click Choose what the power buttons do, then Change settings that are currently unavailable, and uncheck Turn on fast startup (recommended).
Slow startup is rarely one problem
The reason a slow boot is so frustrating to fix is that it is almost never a single cause. On my own laptop, the delay was split between a long BIOS phase, a few hidden startup entries that Task Manager never showed me, and Windows 11 defaults that dragged things down after login. Fixing only one of them barely moved the needle.
So the honest takeaway is to diagnose before you tweak. Check your Last BIOS time first, let the Diagnostics-Performance log point you at the real offenders, and use Autoruns or PowerShell to see what Task Manager hides. You won't shave the boot down to nothing, and old hardware will always set a floor. But you will stop wasting performance on things that were never doing you any good.
