Installing Windows 10 on GPT disk, partitions not in correct order?

Windows 10 Pro
Biostar TZ77XE4

I have been able to "successfully" boot the CD Drive into UEFI mode to install Windows 10 onto my new 4TB SSHD, but I run into the error were it stats that the partitions are not in the recommended order, when the ONLY partitions on the disk are the primary and the "protective MBR" before it at slot 0.

Now, when I am in windows for the first time everything seems fine, but as soon as I restart after doing basic setup, I run into an issue where I cannot browse any partitions (I try to open "This PC", but it acts like it is indexing indefinitely and I never see the drive listing).

It looks like Windows 10 may not be appropriately setting the order for the partitions. I included a screenshot of the setup below.

Is this incorrect? How would I be able to correct the issue?



At the moment I left my original installation on my 1TB HHD intact, so that I can still have an operating PC, and find out some info on this.

I literally never heard of GPT (or at least remember it) before a couple days ago.

Are you trying to do a clean install of Windows 10 or an upgrade? If a clean install, then boot from the Windows 10 USB or DVD and select the Custom install option. Delete all the partitions on the drive, then select the unallocated space to install to.

Ok, I may have managed to find out the issue.

This may not have done anything, as the disk order did not change when I plugged the second back in, but there were 2 installed, Disk 0 (the original installation) and disk 1, the current new installation location.

I unplugged the old one completely and installed and it went completely smoothly, without issue.

Though I did run into some problems with an old registry item I like to use, "TakeOwnership", which when used to snag the old user folders/files, broke the Windows Apps (like weather, or photos). I was able to find a way around this as well.
@NavyLCDR
That was insanely basic steps on just installing Windows 10 in general, and nothing to do with this specific situation.
@Cerberus
The other drive was likely not relevant.


I am still appreciative that both of you at least attempted to reply with something relevant though.