Slow boot up after fresh install on new m.2 drive

jamespratchett2 · 14 Jan 2021

Hello all first post here I did a brand new installation of windows on my new m.2 drive I used a usb to do that and installed Windows 10 pro on my new sn850 1 TV m.2 drive . Since doing so windows takes upto a minute to load on my old samsung 980 Evo took a matter of seconds . I am also experiencing a small bit of lag in windows by lag I mean try to open settings it sometimes just hangs or will open a box and not let me change anything . Never experienced any of this on the old drive . The new drive is in the same place the old one was and is twice the speed . I have disabled all start up programs etc . Also disabled quick boot in both bios and windows and hasn't made a difference it's like the pc just hangs in the gigabyte screen the a spinning cycle starts then finally boot into windows . I do not understand what is causing the lag I sometimes get and also the slow boot . The only suggestion I have is that something went wrong along the way with the installation and drivers . Should I just do a fresh install again . ?

Build motherboard gigabyte AUROUS MASTER x570

CPU and 5950x

Ram 32gb Corsair dominator PLATINUM RGB 3200

Storage western digital sn850 1tb drive having issues with in top slot same as old drive

Samsung evo970 1tb drive I used for Windows before never had any issues now in bottom m.2 slot

2xCrucial mx500 1tb sad

GPU 3090 ftw ultra

This is driving me crazy

Any help and suggestions would be most welcomed

Paul Black · 15 Jan 2021

Hello @jamespratchett2,
Welcome to TenForums.

[1] Have you checked if there is a BIOS update?
[2] Have you checked the computer manufacturers website for any driver updates?
[3] Where did you get the ISO from?
[4] What did you use to burn the ISO to the USB?
[5] When you performed a Clean Install, did you disconnect ALL other drives?

Disconnect ALL Other Disks

It is highly recommended that you disconnect [ temporarily unplug ] ALL other Disks [ HDD's/SSD's/USB's ] BEFORE installing Windows. The reasons for this are . . .

You CAN'T accidentally OVERWRITE a connected Disk.
The BOOTLOADER [ boot configuration files ] will get installed on the correct Disk [ because Windows has the tendency to install the bootloader rather randomly on ANY connected Disk ], and therefore STOP problems with booting once the installation is complete.

Once the installation is complete . . .

Check that the OS boots correctly.
Check if the boot order in the BIOS/UEFI settings are correct [ if NOT, adjust them accordingly ].
Reconnectthe other Disks.

EXPLANATION:

Windows uses a different partition structure for BIOS/UEFI. During the installation process, Windows asks which Disk / Partition you want to use for the Windows C:\ drive, it does NOT however, necessarily use the same Disk for the other Partitions, and can therefore incorrectly create the hidden recovery partition on ANY attached Disk.

Additionally, for BIOS, if another Disk is left attached, and at a latter stage you remove that Disk, you will find that the OS will NOT boot. If you check the BIOS, you will see that the OS has assigned the AHCI/RAID setting instead of the LEGACY setting and set it up as RAID, therefore breaking the boot process.

I hope this helps.

jamespratchett2 · 15 Jan 2021

Yes iv tried everything you said before making the post I even tried a fresh install of windows direct from Windows website used a different usb stick etc . This time I had an issue of the windows logo appearing on boot for 10 seconds then loaded me into windows tried everything to sort the issue and nothing worked . I am trying to reinstall windows back on the original m.2 drive so I can see if the drive iv bought is faulty . It's driving me mad also seen posts where many other people are having the same issue .

zinou · 15 Jan 2021

Hello and welcome to tenforums.

First we need if the boot delay is occuring during the Bios boot phase or After. Post a screenshot of the taskmanager:

Slow boot up after fresh install on new m.2 drive-image.png

You can also check your new disk health using Hard Disk Sentinel tool

Finally, you can record a boot trace so that we can do an indepth analysis