Windows cannot be installed on MBR, please change to GPT

[the_randomizer]

UEFI + legacy enables MBR booting on your board. If you install via MBR, make sure the USB Stick is MBR too. Tools like Rufus can set it up easy. Windows installer forces GPT installation if its booted via GPT Stick. Same for MBR.

However If you want to keep GPT HDD. I always use the free tool mini partition wizard. It can convert MBR to GPT, GPT to MBR.
https://www.partitionwizard.com/free-partition-manager.html

I tried that, Rufus tool and setting the USB stick to MBR first, booted it up in the boot menu, and it absolutely refused to install to any of my MBR hard drives. I come back, I flash Windows 10 again, using GPT with Rufus, same result. Whether it was MBR or GPT, the USB stick refused to work and won't let me install it to the HDD. As far as that partition wizard goes, I tried that just now, and when I started to convert to GPT, it almost started to wipe the drive, despite only clicking "convert MBR to GPT". This is starting to give me a headache.

I must be doing something wrong, when I tried converting the HDD to GPT, it looked like it was trying to wipe the drive instead of converting. But please, do read my computer issues above with the mouse and monitor.

 

[The Real Jdbye]

My board doesn't have the option to just use legacy, just UEFI and UEFI + legacy. But I'm not sure what it's set to, but couldn't I have the main HDD set as MBR, but have a partition set as GPT? Or is that unfeasible. I'll have to use the dual mode if that's what it's currently not set to.

Example:

Disk 3 936 GB

Partition 0 - 800 GB MBR
Partition 1 - 100 GB GPT

I'll check the BIOS setting in the morning, it's getting late.

MBR/GPT is actually the partition table (GPT=GUID Partition Table)
So, for obvious reasons, you can't have a GPT partition on a MBR drive.
You can however have a hybrid GPT+MBR drive, as they are written to different parts of the drive, but the drive still needs to be formatted as GPT+MBR or converted with a tool. That has the highest compatibility as far as booting different combinations of OS, UEFI, BIOS etc. goes, but isn't something you should need, as legacy boot works fine from GPT as long as what you're trying to boot is recent enough to support it.

 

[the_randomizer]

MBR/GPT is actually the partition table (GPT=GUID Partition Table)
So, for obvious reasons, you can't have a GPT partition on a MBR drive.
You can however have a hybrid GPT+MBR drive, as they are written to different parts of the drive, but the drive still needs to be formatted as GPT+MBR or converted with a tool. That has the highest compatibility as far as booting different combinations of OS, UEFI, BIOS etc. goes, but isn't something you should need, as legacy boot works fine from GPT as long as what you're trying to boot is recent enough to support it.

I can't just use plain legacy on this board, it has to be either UEFI or both legacy + UEFI and it just ain't working. But please can someone at least address the issues I'm having with the mouse as I posted back there?

Maybe the flash drive is garbage.

Current issues:

- Monitor refuses to wake up after going to sleep, and yes, keyboard and mouse are set up to wake it up, forcing reboot
- Mouse will flicker between normal icon and hourglass/loading icon intermittently when using Chrome, nothing else is running in background
- Drivers may be corrupted, may have to use wired mouse

 

[TR_mahmutpek]

Unfortunately but you need to delete all parttitions.

 

[the_randomizer]

Unfortunately but you need to delete all parttitions.

Why? That video I posted shows MBR converting to GPT just fine using Partition Wizard, does it not? You don't mean the drive, but the partition only that I'm trying to use? I
wish to keep it separate from the main disk.

 

[The Real Jdbye]

I can't just use plain legacy on this board, it has to be either UEFI or both legacy + UEFI and it just ain't working. But please can someone at least address the issues I'm having with the mouse as I posted back there?

Maybe the flash drive is garbage.

Let me clarify. In the boot menu (assuming legacy+UEFI is on), it should show two entries for the Win10 USB, one for legacy boot and one for UEFI, my guess is that it has to be booted through the legacy option in order to support installing to MBR.
The mouse thing just sounds like a service is doing something in the background that's causing the cursor to change, does it really matter though?

 

[the_randomizer]

Let me clarify. In the boot menu (assuming legacy+UEFI is on), it should show two entries for the Win10 USB, one for legacy boot and one for UEFI, my guess is that it has to be booted through the legacy option in order to support installing to MBR.
The mouse thing just sounds like a service is doing something in the background that's causing the cursor to change, does it really matter though?

But that's just it, it only happens when I use Chrome, and didn't start doing this till yesterday, after I attempted to install Logitech drivers for my mouse and keyboard, which use two different receivers (long story, but it was a mistake on my part). I tried to sync them to one receiver using SetPoint, it "worked" but the mouse kept doing what I described more rapidly, so I rolled back to the default MS drivers and it worked fine, or so I thought. But now it's doing it intermittently and it's distracting. I may end up just getting a wired mouse tomorrow. I suspect the drivers for the mouse and keyboard somehow got corrupted when I forced reinstalled the default drivers. I'll uninstall the device drivers and restart as well.

Edit: I did notice duplicate entries for the keyboard and mouse, but with a generic driver name.

That being said, when I used the boot menu, I may have overlooked the legacy option, but before I do that, I'll see what BIOS mode the mobo is set to, then go from there and hope that it shows both options.

 

[The Real Jdbye]

But that's just it, it only happens when I use Chrome, and didn't start doing this till yesterday, after I attempted to install Logitech drivers for my mouse and keyboard, which use two different receivers (long story, but it was a mistake on my part). I tried to sync them to one receiver using SetPoint, it "worked" but the mouse kept doing what I described more rapidly, so I rolled back to the default MS drivers and it worked fine, or so I thought. But now it's doing it intermittently and it's distracting. I may end up just getting a wired mouse tomorrow. I suspect the drivers for the mouse and keyboard somehow got corrupted when I forced reinstalled the default drivers. I'll uninstall the device drivers and restart as well.

Edit: I did notice duplicate entries for the keyboard and mouse, but with a generic driver name.

That being said, when I used the boot menu, I may have overlooked the legacy option, but before I do that, I'll see what BIOS mode the mobo is set to, then go from there and hope that it shows both options.

I saw in the other thread that you got Win10 installed, how did you end up getting it installed successfully?

 

[the_randomizer]

I saw in the other thread that you got Win10 installed, how did you end up getting it installed successfully?

I used the F11 boot menu after the computer ran the POST, it gave me options, one was UEFI USB and the other was called "Generic USB storage device", which was the legacy. Turns out
the mobo is set to UEFI+ legacy by default. But this leads to another concern (which I made a thread for), is toying with the idea of cloning my Windows 10 OS install (which is on a 90 GB partition)
to an SSD. Trouble with that is it'd throw the entire boot order out of whack, as there'd be "two" Windows 10 installs that are both called C. I know there are ways around it, but it'd save a lot
of hassle. I think though, I'm being paranoid over the fact my newest HDD that 10 is on has a slightly more noticeable sound that my other drives.

 

[The Real Jdbye]

I used the F11 boot menu after the computer ran the POST, it gave me options, one was UEFI USB and the other was called "Generic USB storage device", which was the legacy. Turns out
the mobo is set to UEFI+ legacy by default. But this leads to another concern (which I made a thread for), is toying with the idea of cloning my Windows 10 OS install (which is on a 90 GB partition)
to an SSD. Trouble with that is it'd throw the entire boot order out of whack, as there'd be "two" Windows 10 installs that are both called C. I know there are ways around it, but it'd save a lot
of hassle. I think though, I'm being paranoid over the fact my newest HDD that 10 is on has a slightly more noticeable sound that my other drives.

So I guess I was right in the end then (referring to my previous post)
I have some ideas for the cloning thing but I'll post that in the other thread.

 

[the_randomizer]

So I guess I was right in the end then (referring to my previous post)
I have some ideas for the cloning thing but I'll post that in the other thread.

Yeah, the OS itself runs smooth as butter and okay