Windows 10 Takes 4 hours to boot on a SSD

Hi, to confirm on a rather simple basis that there is no hardware issue, do you have a spare disk you can use as a system disk- extract the one you have, put the spare disk in, reinstall Windows, check the boot time?

If that works, that just leaves your original system disk in terms of hardware, of course.

reinstalling Windows would mean that I’d have to reinstall and reauthenticate hundreds of audio plugins.

Your best protection offering rapid recovery from disaster is the routine use of disk imaging, as is so, so often recommended here. Thus you can restore an image of Windows (or any partitions) even to a new PC or replacement disk. E.g. Macrium Reflect (free) - also paid.

When your system has booted, does it function normally?

Analysing boot times is possible using the Windows Performance Recorder (free from MS) which gives detailed graphical reports. However most are deterred by its apparent complexity and level of detail. (Tutorial available- examples of screenshots if you search for it here).

You could try verbose boot logging:
Use Verbose Boot Messages to Troubleshoot Windows Startup Problems
Enable verbose logon messages in Windows 10 - Spiceworks

and there's this:

Enable or Disable Boot Log in Windows

The forum prompted you to specify your build number when you wrote your post, so we don't have to keep asking for it.

History: (most people omit this)
When did this start?
Was this related to any specific event?
- hardware change
- power outage
- cat walking over the keyboard
- installation/uninstallation/update..

Hey dalchina, thanks for the response.

This build had Ryzen 5 2600, upgraded to Ryzen 5 3600, that's when the problem started.

I've come across solutions where the issue may lie on other failing hard drives, but the bootloader and other Windows dependencies are on my primary SSD. So I used Macrium Reflect to clone to a different SSD; it does not appear to solve the problem.

Now, I can confirm that by performing a fresh install on a spare disk, the system boots up normally, I'd conclude this to be a software issue, or perhaps specific drivers.

Since I've made a secondary backup on Macrium, I uninstalled all programs on the SSD, and it did not solve this problem, I'd say that software drivers relating to the CPU could be the reason the computer takes up such times to boot.


I'll include the event viewer information in case it provides any valuable information. Event.evtx - Google Drive


But in the meantime, I will try the Windows Performance Recorder, that is one of the best suggestions I've gotten so far, thanks.

That's a very rational approach- interesting outcome.

If you were to use Autoruns (free from MS) and compare, say the driver sections shown for each of the new install and the problem install, you might note something.

As you can also use Autoruns to disable items using checkboxes, you could attempt to reduce those loaded in the problem case to those used by the new install, and see if you can find the problem item by a process of elimination.

Verbose booot logging may help to point the way, especially as the boot time is so desperately long.