F5F Stay Refreshed Hardware Desktop Double-check your setup—ensure all connections are secure and the device is properly powered.

Double-check your setup—ensure all connections are secure and the device is properly powered.

Double-check your setup—ensure all connections are secure and the device is properly powered.

L
lufos0909
Junior Member
Find
20
10-06-2019, 10:33 AM
#1
I'm trying to boot up a MBR Win10 install in an X570 board to convert it to GPT. 2TB 990 Pro, 5700X3D, 32GB 3600 RAM, 1660 Super. Each time I enable CSM and Legacy Boot it boots back to BIOS and it's disabled again. fTPM is off, ReSize BAR is off, I need to confirm Secure Boot is off once I find it but I don't think that's at play with fTPM off? CSM/MBR boot is limited to 2TB drives, the 990 Pro 2TB should boot, correct? I'm sure I'm missing something terribly simple here but I'm having a hard time recognizing what that is, some feedback would be great. I'm not super accustomed to Gigabyte BIOS layout, been a long time Asus user.
Reply
Reply
L
lufos0909
10-06-2019, 10:33 AM #1

I'm trying to boot up a MBR Win10 install in an X570 board to convert it to GPT. 2TB 990 Pro, 5700X3D, 32GB 3600 RAM, 1660 Super. Each time I enable CSM and Legacy Boot it boots back to BIOS and it's disabled again. fTPM is off, ReSize BAR is off, I need to confirm Secure Boot is off once I find it but I don't think that's at play with fTPM off? CSM/MBR boot is limited to 2TB drives, the 990 Pro 2TB should boot, correct? I'm sure I'm missing something terribly simple here but I'm having a hard time recognizing what that is, some feedback would be great. I'm not super accustomed to Gigabyte BIOS layout, been a long time Asus user.

Reply
Reply
G
Galfaaf
Junior Member
Find
4
10-25-2019, 03:40 AM
#2
Discuss converting a current Windows 10 setup from another version.
Reply
Reply
G
Galfaaf
10-25-2019, 03:40 AM #2

Discuss converting a current Windows 10 setup from another version.

Reply
Reply
M
megsterz
Member
Find
208
11-10-2019, 08:09 AM
#3
It's not recommended to use MBR for Windows on new devices.
Reply
Reply
M
megsterz
11-10-2019, 08:09 AM #3

It's not recommended to use MBR for Windows on new devices.

Reply
Reply
B
badman394
Member
Find
221
11-10-2019, 08:44 AM
#4
I understand the process, I've only tried the online method before. If it doesn't start, I'll attempt the WinPE approach, though it's unfamiliar to me. That's why I need to boot it for conversion.
Reply
Reply
B
badman394
11-10-2019, 08:44 AM #4

I understand the process, I've only tried the online method before. If it doesn't start, I'll attempt the WinPE approach, though it's unfamiliar to me. That's why I need to boot it for conversion.

Reply
Reply
K
kic003
Member
Find
62
11-11-2019, 07:50 PM
#5
You need to ensure the NVME is bootable correctly. Try using the install media command line again, confirming the disk path and options. The validation step is crucial—make sure the original drive matches the expected layout. If it still fails, check for any hidden formatting differences or system restrictions.
Reply
Reply
K
kic003
11-11-2019, 07:50 PM #5

You need to ensure the NVME is bootable correctly. Try using the install media command line again, confirming the disk path and options. The validation step is crucial—make sure the original drive matches the expected layout. If it still fails, check for any hidden formatting differences or system restrictions.

Reply
Reply
B
Boomer1974
Junior Member
Find
25
11-11-2019, 08:13 PM
#6
I located the Secure Boot feature, but it wasn<|pad|>, BIOS didn't display it as expected. The guide I found was for an older BIOS version, so it seems the information was moved. Now it works without issues. I can turn on CSM, boot, convert, reboot, disable CSM, boot via GPT, and remove Windows RE. The current problem lies in having two recovery partitions that Windows resolved, but the EFI and recovery partitions are between the Windows volume and free space, blocking expansion. Should I remove those partitions, leave a gap at the start, use Windows BCD tools to create a new EFI partition, and then re-enable WinRE to restore the recovery partition, or would you prefer using Gparted on a live USB to rearrange everything? Copy the EFI and WinRE, delete them, shift the data partition to create space, then expand it?
Reply
Reply
B
Boomer1974
11-11-2019, 08:13 PM #6

I located the Secure Boot feature, but it wasn<|pad|>, BIOS didn't display it as expected. The guide I found was for an older BIOS version, so it seems the information was moved. Now it works without issues. I can turn on CSM, boot, convert, reboot, disable CSM, boot via GPT, and remove Windows RE. The current problem lies in having two recovery partitions that Windows resolved, but the EFI and recovery partitions are between the Windows volume and free space, blocking expansion. Should I remove those partitions, leave a gap at the start, use Windows BCD tools to create a new EFI partition, and then re-enable WinRE to restore the recovery partition, or would you prefer using Gparted on a live USB to rearrange everything? Copy the EFI and WinRE, delete them, shift the data partition to create space, then expand it?

Reply
Reply