Question Boot drive or partition not recognized after a clean Windows 10 re-install

[eco_bach]

I was forced to do a clean re-install of Windows 10 after a failed update.
I did a simple format of ONLY my C drive partition first before my re-install.

I can boot into my desktop successfully but ONLY after I first boot into BIOS and manually select my startup drive in the Boot list.
I then do a save-exit and can launch my desktop as usual.

The next time I restart (without entering BIOS first) my PC just hangs, fans whirring and a black screen.

Using Diskpart to list partitions on my boot drive I see the following
DISKPART> list partition

Partition ### Type Size Offset
------------- ---------------- ------- -------

Partition 1 Recovery 530 MB 1024 KB

Partition 2 System 100 MB 531 MB

Partition 3 Reserved 16 MB 631 MB

Partition 4 Primary 983 GB 647 MB

Partition 5 Primary 878 GB 984 GB

Its a 2TB M.2 SSD. Partition 4 is the one I did a clean format of to re-install Windows.
Does the above look correct?


Any help or feedback appreciated!!

 

[dwd999]

Yeah, the Windows installer doesn't like it if there is anything on the disk (and only 1 disk) other than the GPT partition table header. I usually prepare my disks using Gparted to ensure that the GPT header is present and the rest of the disk is unallocated.

 

[johnbl]

I have seen cases where if you boot and you are using intel rapid storage technology driver it will reassign drive letters to your drives incorrectly. most of the time it would give drive c: to one of the small partitions by mistake and your windows partition would be on drive d: or e: and your system would not boot.

the old fix for this was to remove the intel rapid storage tech driver and go back to the microsoft generic system.
or you could go into diskpart and assign a drive letter like f: to the small partition and it would respect that drive letter and the system would boot. until something triggers the drive letter updates. I think attempting to boot on a usb drive would trigger the reassigned drives. I fixed someones system several times before just change back to the generic microsoft driver to end the problem.
fixing the problem, involved going into windows control panel device manager, find the sata/ahci driver, right mouse click to bring up properties, attempt to update the driver but you have to pick browse my computer for the driver,
then let me pick the driver from available drivers
then select
standard sata ahci controller

then it should make you reboot.
reboot and go back into control panel to the program uninstall
and find the intel storage driver and uninstall it. (should remove the service so you do not get a bunch of errors logged)

been some time since I have done this, so the wording/locations might not be correct.

I would hope this is now fixed via bios, chipset and intel storage driver update.