Measure the baseline
Reboot three times and time from the power button to a usable desktop, with the same apps. One measurement is noise; three show the real figure.
Find out where the seconds go - firmware, driver init or startup apps - before disabling anything. Windows keeps the numbers in the event log.
Read **Diagnostics-Performance** event 100 in Event Viewer for the boot duration and the apps that slow it down, then fix the top entry. Disabling random services is not a method.
Reboot three times and time from the power button to a usable desktop, with the same apps. One measurement is noise; three show the real figure.
Open **Event Viewer > Applications and Services Logs > Microsoft > Windows > Diagnostics-Performance > Operational** and look for event 100. It lists the boot duration and the slowest startup items with their times.
eventvwr.msc
Diagnostics-Performance > Operational > Event ID 100
Use **Settings > Apps > Startup** and disable what you do not need at login. Better still, uninstall what you do not need at all - the app then stops re-adding itself.
Event 100 often points at one item with a multi-second delay. A single slow antivirus scan or a network drive mapping costs more than ten small tray apps.
A mapped drive on a NAS that is not awake holds the desktop for its timeout. Set **Always wait for the network at startup** off in the group policy, or map the drive after login.
gpedit.msc > Computer Configuration > Administrative Templates > System > Logon
If the boot is slow before Windows even starts - logo for a long time - the firmware is waiting for a device. Unplug USB drives and check the boot order before blaming Windows.
The log is disabled or the machine uses fast startup with resume instead of boot. Power off fully once with shutdown /s /t 0 and check again.
Startup apps are the delay, not the boot. Work through the startup entries in event 100.
Firmware-level: USB devices, a failing drive or memory training. Unplug peripherals and check the POST timing.
A new startup task or a driver. Compare event 100 before and after the update date.
It shortens the time to the login screen but can cause driver oddities. With an NVMe drive the gain is small.
No. The measured delays come from apps and drivers, not from registry entries.
Re-enable the startup entries you disabled in **Settings > Apps > Startup** and restore the logon policy if you changed it. Nothing is deleted permanently.
Free · no account needed · tracks your progress