Long boot time on Windows 10, need help diagnosing it.

[Athlonite]

after looking at that start up txt there's only two things you need leave on Avast and Realtek everything else you can load when you need it

USB Devices for some reason take a long time to initialize and will slow the boot sequence considerably my WD 2TB Elements USB2.0 HDD slows my machine down to a 45+ second boot time if it's plugged in during boot so now I only reboot or cold boot once a week otherwise it's just power off Sleep mode which takes about 5 secs to come back from sleep to usable

 

[Jetster]

Yes, remove everything from the drive. Do a full format and try it again with noting on it
Or just don't turn it off

 

[aQi]

Have to looked for the bios update ?

May be a driver is taking longer then usual time to load. Perhaps a driver update but which one ?

 

[Vlada011]

Depend a lot from BIOS, if you want to check everything and properly boot,
pass all Q Codes need some time 20 seconds at least, than Windows to boot and you have 30-35 seconds normally.

 

[Jetster]

He figured it out. It's his WD MyBook drive

 

[Voluman]

Can you set the hard drive inizialization time? Older motherboards have that option, i used to set 10 sec, its more than enough, while the def time was around 25-30 sec. Or maybe usb inizialization time?
Btw, win 10 load so long? ( I have 13-15 sec from pushing power on button till i get to desktop and its usable, but win8.1 )

 

[newtekie1]

I amazes me all the people that either didn't read the OP's problem or outright don't understand how Windows boot process works.

Removing programs from startup will not make the section of the Windows boot sequence the OP is having an issue with, the spinning balls, load any faster. Nothing in the startup folder or the startup section of autoruns/msconfig/task manager is loaded during that phase of the Windows boot sequence. Everything in the Startup folder/autoruns/msconfig/task manager is loaded after the login screen.

 

[theFOoL]

As I stated this is more likely a hardware issue. That said, he needs to unplug each USB to find what is causing the problem. To my knowledge it's probably that USB HDD from Western Digital causing the problem

 

[John Naylor]

Win 7 on SSD takes around 30 seconds or so to boot for me. Lots of programs load at startup, too.

Immediately after build, (2 Samsung Pro SSDs, 2 Segate SSHDs and 1 HD each with a bootable Win7 OS selectable from BIOS), Boot times , button push to password screen, was:

15.6 seconds on SSD
16.5 seconds on SSHD
21.2 seconds on HD.

Note that the boot time can be greatly affected by AV programs which scan the boot sector and other areas before allowing boot process to begin

My HTPC is on Win 10 with a 4TB 5400 WD Red and takes a good minute or so. Virtually no programs load at startup - Plex, MSI Afterburner and maybe one other lightweight program.

5400 rpm drives are not known for their speed

At home, I usually power on the computer and then take the dog out or get the mail....I find something to occupy that 30ish seconds I'd otherwise be wasting by sitting at the computer, waiting for it to load into Windows. Once I get back to the computer a couple minutes later, she's ready to go. If you're just sitting and waiting, it can feel like a lot longer than it really is. Try to occupy your time for that 20+ seconds you're waiting for the computer to boot.

Yes ... this is what most people do .... listen to voice mail, check their in box, grab a cupa cawfee, unplug their headphones, wipe snack crumbs off mouse pad, use a screen wipe. Which kinda makes all the fuss about boot and loading speed "much ado about nothing"

 

[trparky]

As I stated this is more likely a hardware issue. That said, he needs to unplug each USB to find what is causing the problem. To my knowledge it's probably that USB HDD from Western Digital causing the problem

That's exactly what it was, the Western Digital drive being the boat anchor during boot.

 

[eidairaman1]

after looking at that start up txt there's only two things you need leave on Avast and Realtek everything else you can load when you need it

USB Devices for some reason take a long time to initialize and will slow the boot sequence considerably my WD 2TB Elements USB2.0 HDD slows my machine down to a 45+ second boot time if it's plugged in during boot so now I only reboot or cold boot once a week otherwise it's just power off Sleep mode which takes about 5 secs to come back from sleep to usable

If the system has Legacy boot, turn those on.

 

[Aquinus]

OK, so I did some experimentation. I have an external Western Digital MyBook that's connected via USB 3.0 and an external BluRay drive that's connected via a sort of janky USB-to-SATA adapter. I disconnected both storage devices from USB and booted the system, that boot time was about 13 seconds (plus or minus a second due to me having to time it on my iPhone). I reconnected the external BluRay drive with the USB-to-SATA adapter and reran the test, again it was 13 or so seconds. I then reconnected the Western Digital drive and that's when the boot time took a shit and reached into the 35 second range. For whatever reason the Western Digital MyBook external hard drive is presenting itself as a major roadblock to booting the system and I have no idea why.

Any theories? Anything that I should maybe look for in my Gigabyte UEFI so as to prevent the MyBook drive from being such a boat anchor during boot?

The problem is that when it goes to detect it, the drive has to spin up and these drives take time to spin up. I have both a 4TB and 8TB WD external drives and they both are a drag on my boot time. If I only had the SATA and NVMe SSDs, it would boot plenty fast but, the rotational media drives are the ones that harm boot time. I've honestly had the same problem and the only real solution would be to move mass storage to another machine and access it via your home network. The sad reality is that as long as the drives are connected to your machine, at some point in the boot process the drive will need to spin up. On my machine it can either happen when UEFI starts up or when the OS does. One way or another, it's going to happen.