i doubt you would even care at this point about your problem, but if you still want to know,
The Unified Extensible Firmware Interface UEFis a specification that defines a software interface between an operating system and platform firmware. UEFI replaces the Basic Input/Output System (BIOS) firmware interface originally present in all IBM PC-compatible personal computers, with most UEFI firmware implementations providing legacy support for BIOS services. UEFI can support remote diagnostics and repair of computers, even with no operating system installed.
UEFI (or EFI) comes preinstalled on windows Operating systems Windows 7 and up. anything before that used BIOS (basic Input Output System) they essentially are the same thing but UEFI handles the boot process differently. Unlike BIOS, UEFI can allow you to boot into recovery options, such as the command prompt, BIOS (Not the boot type. however BIOS is pretty much a generic term for the boot options and everything) settings, UEFI can also support disks over 2 TB in size (With GPT [GUID Partition Table]). (Oh and UEFI is a lot prettier)
as far as i know, UEFI checks the boot loaders keys and signitures to verify that it is a non malicious program. This is where secure boot comes in. Secure boot is basically the "anti virus" of the boot manager. It verifies that he boot loader is safe and what not.
The Downside to this is that UEFI ONLY supports booting with UEFI Windows OS's, which are windows 7 and up, and blocks other UEFI or EFI systems from using the windows boot loader.
However, BIOS doesnt do that. Your computer is not broken so dont worry about reinstalling it or anything. your situation was normal. The reason you cant boot your windows OS in legacy/CSM/BIOS mode is because BIOS mode cant boot the modern windows boot loader, and UEFI cant boot the old windows boot loader. The reason you had to switch boot modes to get into linux was because your particular linux distribution was setup to boot in bios mode.
However there is a way around the dual booting block that microsoft did with UEFI. and that is to make sure that your linux is booted into UEFI mode (before installing it, also research how to do this because it would make this way longer than it should be), and then when you install linux, make sure that you mount the boot loader to /boot/efi, or choose the main partition (/dev/sda) (research like i said to make sure) because once this has been done, the GRUB (Grand Unified Bootloader) will overwrite the Windows Bootloader as the one that would boot windows. So instead of the Windows Bootloader running your computer, the Linux GRUB loader would be However there is ANOTHER problem with this...
If GRUB is your main boot loader for windows AND linux, it can render your computer inoperable for a limited amount of time (by that i mean until you rebuild the boot loader and what not, ill provide a link for this)
If something happens to the Linux OS, for example, you wipe all the linux partitions, includeing the boot, swap, and main partition, and you leave only your windows ones, GRUB cant find anything to boot to (windows boot manager was chainloaded to GRUB) so when you turn your computer on, you be stuck in grub recovery mode, because you wiped the boot loader partition FOR grub. The Windows OS is still untouched, however theres no way to access it.
I know this is a mouthful but i hope it answered some of your questions. haha and if this doesnt make a lot of sense, just research it.
Heres how you can rebuild your Windows Bootloader just incase you cant access it because of GRUB being wiped, or for any other reason it wouldnt work:
http://www.fixedbyvonnie.com/2013/12/how-to-repair-the-efi-bootloader-in-windows-8/#.V09tfiuqOM8
This only rebuilds it, it doesnt touch any other part of Windows. your files will be safe.
IF you need further explaination, i can help haha