What BIOS I have, Legacy or UEFI

I am confused now.

I have Asus ROG Maximus VII (I think, or VI) motherboard. Everything working OK, I have no problems with GTX 1080 or 10TB hard drives installed.

So I decided to check, which BIOS I have (it was long time since I got this PC).

I followed https://www.eightforums.com/threads/bios-mode-see-if-windows-boot-in-uefi-or-legacy-mode.29504/
Options 1-3, all of them show that I have Legacy BIOS, how could it be I asked myself, so I opened actual BIOS, see pictures below.

W3CWrFV.jpg


wNyEfg6.jpg


ceBgqDg.jpg


Last 2 pictures are the same TAB, should be side by side, last one on the RIGHT.

SO, my BIOS is UEFI, but Windows show Legacy, WTF?
 
Solution
Maybe some history will help...

Old style BIOS has an understanding of BIOS style partitions. The BIOS does not need an operating system in order to pick a boot entry.

Unfortunately, when we had 32-bit systems starting to see larger disk drives, many computers couldn't use larger than a 2GB disk (this is the limit of a signed 32-bit int...unsigned will actually reach 4GB). It was somewhat trivial to update applications and operating systems to understand 64-bit...this was all software. However, the BIOS is firmware and/or hardware following a standard, so nothing with a BIOS would ever be able to work with larger than the 32-bit limits. Yes, there were hacks, such as doubling the listed number of disk heads and cutting in half the...
Your motherboard is natively UEFI, but supports old style BIOS.

FYI, earlier Windows 7 install disks are not capable of recognizing UEFI style partitions. I have such an install disk. This earlier Windows 7 only understands UEFI after patches...meaning it can't be installed on UEFI. I wouldn't be surprised if you have an older Windows 7.

Most of the time it isn't an issue. If you are dual booting with Ubuntu, then it is probably an issue.
 


It is MBR (check with Aomei). So I have Legacy BOOT with UEFI BIOS?, confusing.

Do I need GPT if everything is working fine, I am not planning partitioning my C drive (Samsung 500GB PRO SSD).

I did not mention it, I have Windows 8.1 Home installed (did not like WIN 10, so I stepped back during free Win10 upgrade times).

And I have 10TB drives and everything is fine.... Why?
 


If you want to be able to boot the OS in EFI mode then GPT is necessary.
 


I know that part. However, I don't see any reason to change.
What am I loosing in Legacy mode? If nothing significant, I will stay then.
 


That is the interesting part, according to the last picture of my BIOS I have Secure Boot enabled. And I disabled Fast Boot, because I could not get to BIOS, system was booting very quickly.

So, we are almost back to square one. If I have Legacy BIOS, how come I have Secure Boot enabled. Digital Storm did something interesting.
I guess I will ask them directly, I hope they will answer.
 
Maybe some history will help...

Old style BIOS has an understanding of BIOS style partitions. The BIOS does not need an operating system in order to pick a boot entry.

Unfortunately, when we had 32-bit systems starting to see larger disk drives, many computers couldn't use larger than a 2GB disk (this is the limit of a signed 32-bit int...unsigned will actually reach 4GB). It was somewhat trivial to update applications and operating systems to understand 64-bit...this was all software. However, the BIOS is firmware and/or hardware following a standard, so nothing with a BIOS would ever be able to work with larger than the 32-bit limits. Yes, there were hacks, such as doubling the listed number of disk heads and cutting in half the number of listed cylinders, but this was just rearranging the logical view of how things are inside the disk (individual components, e.g., cylinder counts, still had limits). Making one lie to the BIOS which was counteracted by another lie to the BIOS aided the use of larger disks (the penalty was that defragmenting no longer really was optimum performance...the internal concept of how the disk was arranged became fantasy).

So someone thought to let the operating system do more. UEFI in part takes some of what was in the BIOS and instead puts it in a UEFI metadata area at the front of the disk. Now if the operating system were one day updated to support something like 128-bit, in theory the same motherboard will still work via software updates (you wouldn't need to replace the entire motherboard). Some of the BIOS capability was transferred to the disk for UEFI and the soldering iron became less important to upgrading disk size (that's only half joking!).

When your disk is UEFI-capable, and also BIOS capable, it means it works with a wider range of disk partition schemes. As long as your operating system installer cannot understand newer UEFI, then installing a UEFI partition scheme will only lead to the operating system failing to load. My older Windows 7 is an example of something forcing me to use BIOS mode because of the installer DVD.

If your Windows install was via BIOS, there is neither need nor reason to worry about UEFI mode. You can buy a newer operating system and key and install from scratch if you want to. You only need to do this if you plan on installing into a C: partition too big for BIOS. In some cases, even if the BIOS can't see an entire partition it will still work if everything needed for boot stays within the 32-bit limits.

What have you been told about UEFI which makes you believe it would be an advantage? It isn't faster, it's just easier to update as hardware changes.

On the other hand I have found Ubuntu's installer to not work correctly when mixing BIOS and UEFI. So if you are dual booting older Win 7 and Ubuntu, then you might have a problem even though the live DVD works (that's Ubuntu's fault).

Btw, having a password in the BIOS is no different for old BIOS versus UEFI. Physical access resetting this will still get around it and the password is not within the bootloader itself (or rather enforcement of a typical BIOS password is not in the boot loader...the operating system itself can have a password in the boot loader, but this isn't what the BIOS/UEFI deals with). You might want to use some form of disk encryption if you are worried about a rebooted system being compromised.
 
Solution