Fix Windows 10 Slow Boot or Startup 2017 [Solved]

April Cai, in Technical Tips Tags: Windows 10

 Are you frustrated by the slow boot problem on your Windows 10? Many users have suffered this problem, especially those using Windows 10 upgrade from other Windows version. In this post, we are going to introduce 4 tried-and-true methods for you to fix the problem. Read on to find out the one serves you. 

Method 1: Disable Fast Startup
Method 2. Disable Processes with High Startup Impact 
Method 3. Update your graphics card driver
Method 4. Do a clean install of Windows 10

Method 1: Disable Fast Startup

The first quick and easy fix to solve this problem is to disable Fast Startup of your Windows 10.

Fast Startup is a default enabled feature in Windows 10. It is supposed to reduce startup time by pre-loading some boot information before your PC shuts off.  It works in a similar manner as Hibernation. But in fact, as many users reported, it’s been causing issues.

1) Type power option in the search box from Start, then click Power & Sleep settings.



2) Click Choose what the power button does.



3) Click Change settings that are currently unavailable.



4) Untick Turn on fast startup (recommended). Then Click Save Changes.

5) Reboot your Windows 10 and check to see if it boots quickly.

Method 2. Disable Processes with High Startup Impact 


Some unnecessary processes with high startup impact can cause slow boot in Windows 10. You can those processes to fix your problem. 
Note: Except for the crucial security software.

1) On your keyboard, press Shift Ctrl +Esc keys at the same 
time to open Task Manager.

2) Click Startup and find out the unnecessary processes with high startup impact.



3) Right-click on the Process needs to be disabled. Then click Disable and close the window.


4) Reboot your Windows 10 and check to see if it boots quickly.

Method 3. Update your graphics card driver

If there’re some old or corrupted drivers on your Windows 10, your computer can also boot slowly. You can update your device drivers to solve your problem.

You can choose to download the lastest drivers 
from your graphics card manufacturer’s official website. You’ll need to find out the correct driver and download it all by yourselves.

If you’re not confident playing around with drivers manually, or if you want to save much more time, you can use Driver Easy  to do it automatically. 

1) Download and install Driver Easy.

2) Run Driver Easy and click Scan Now button. Driver Easy will then scan your computer and detect any problem drivers. You  sound driver is no exception.

3)With Free version: Click the Update button next to a flagged display driver to automatically download and install the correct version of this driver.

With Pro version: Click Update All to automatically download and install the correct version of all the drivers that are missing or out of date on your system. (and you get full support and a 30-day money back guarantee)

4) Reboot your Windows 10 and check to see if it boots quickly.

Method 4. Do a clean install of Windows 10


If none the three tips above for you works for you, you can choose to do a clean install of Windows 10.

See How to do a clean install of Windows 10.


Help Us Improve Article
  • Chris Terry

    My Win 10 computer takes about 10 minutes to completely start. Got to love progress? Win 95 started faster.

    • Fyrick24

      Better than 20-40 minutes -.-. I am not sure if it is because I updated my graphics driver since usually that is when problems occur.

  • Timmie Smet

    Hello,

    I had the same problem for a long time. For me, the cause is the graphics driver (I have intel and amd graphics in Switchable Graphics). Here’s what I did:
    – disable fast boot (in power management), and reboot computer
    – go into register (regedit.exe), look for ‘enableULPS’. You will probably see two results next to eachother. Set both keys to zero.
    – Turn fast boot back on and restart computer again.
    – Go back to register and check if those keys still have value zero (if not: change them back to zero and reboot).

    That solved it for me…