How to use UEFI | Every other YouTube video is WRONG!

In this video, I go over UEFI and what it is, how to use it, and if your installation is UEFI enabled.
Attribution:
Linus Tech Tips: • BIOS and UEFI As Fast ...
PowerCert Animation Vids: • BIOS, CMOS, UEFI - Wha...
Chris Titus Tech Bios vs UEFI: • UEFI vs Legacy BIOS Bo...
BTNHD: • Difference Between BIO... .
►► Digital Downloads ➜ www.cttstore.com
►► Reddit ➜ / christitustech
►► Titus Tech Talk ➜ / titustechtalk
►► Twitch ➜ / christitustech

[@MyszkaAgresorka]

4:45 suggested method by M$, in command prompt: reg query HKLM\System\CurrentControlSet\Control /v PEFirmwareType (return code: 0x1 -> BIOS; if 0x2 -> UEFI). Another way is check output of bcdedit (Vista+) command... 9:44 in theory yes, MBR partition entries has relative sector and number of sectors so you can reach size ~4 TiB (512B sectors) but this is very risky and could cause data corruption by software with internal 32-bit calculations.

[@davybloggs1564]

Myszka - under W10Pro, that req query string doesn't work.

[@MyszkaAgresorka]

​@@davybloggs1564 It doesn't matter if it's "Pro", "Home" or another edition because as registry value name suggests: "PEFirmwareType" is PE (Preinstalled Environment) specific thing. Before querying registry you must instruct WinPE to update his registry with this command: wpeutil UpdateBootInfo Under (installed) "W10Pro" you can check "BIOS mode" (UEFI or Legacy) in msinfo32; by checking bcdedit output; looking in Disk Management at partition types on your boot drive; etc.

[@georgesmith3022]

@@MyszkaAgresorka so just to make things clear i can install os on drive larger than 4 tb as long as the partition is less than 2tb with mbr while with gpt i have no suc problem? Is gpt and mbr a feature of os or bios?

[@maximchintalov8387]

@@georgesmith3022 MBR is a feature of BIOS. (And UEFI in CSM mode.) GPT is a feature of UEFI. Both are features of the OS. For example, Windows 7 does not support UEFI, so if you have UEFI you have to use CSM mode.

[@regdarstreetwise1537]

@@georgesmith3022 You can do that but Windows 10 can't update an MBR installation anymore. I got the problem and had to change to GPT to be able to update to version 190x.

[@kriswillems5661]

Idea for a next video: what is secure boot, which OS-es support it? What is the relation to UEFI? What if you linux distribution does not support it?

[@beezanteeum]

Latest Linux distro use a shim bootloader

[@powerpc64]

@@beezanteeum that's compatible with a secure boot enabled computer right

[@beezanteeum]

@@powerpc64 Yes, Except: Arch or any of it's forks like Steam OS, Manjaro, Artix, etc.

[@harvester7578]

@@beezanteeum Secure boot will only work in UEFI. It will not work with legacy uefi. So it will be a requirement for windows 11 I guess.

[@beezanteeum]

@@harvester7578 That's my point, but not all Linux Distro with UEFI support, has a shim loader Just look at Arch and their derivatives, they support UEFI, but you must sign your own EFI bootloader or build your own shim loader

[@vangoda]

The main difference between classic BIOS and UEFI is that regular BIOS can only read MBR partitioned drives. Regular BIOS also only reads the first sector (512bytes) and if it is not a boot sector it will try the next device. Now UEFI can read gpt fat32 formatted drives and can boot from ANY partition or folder on the drive (via UEFI console), although boot files are usually stored in EFI folder on the root of boot drive. UEFI reads a file with EFI extension.

[@LucaOrtolano]

A years old Win10 installation can even be converted from legacy to UEFI with a couple of recovery console commands. Done that

[@amanr11314]

can you provide me those commands i am unable to convert from MBR to GPT It says following when i run mbr2gpt.exe command : MBR2GPT: Attempting to convert disk 0 MBR2GPT: Retrieving layout of disk MBR2GPT: Validating layout, disk sector size is: 512 bytes Disk layout validation failed for disk 0

[@Gornius]

4:53 - Windows Installer will be displayed in native resolution, with additional DPI scaling, where in Legacy Mode it's in low resolution, 4:3 stretched.

[@lperkins2]

efibootmgr can indeed change the boot order. It can also add and remove boot loaders. Fastest startup time (and better security if you deal with signing the image in a password protected bios) is to directly use the linux kernel as your boot loader, skipping Grub or similar. Doing that involves setting up the boot entry via efibootmgr.

[@chromerims]

Thx. Helpful to know more about efibootmgr.

[@esra_erimez]

I'm still confused. This video needs diagrams.

[@ChrisTitusTech]

Probably should of done it like this *BIOS* (Legacy or UEFI) >>> *Bootloader* (Legacy or UEFI) >>> *Installation Media* (Can ONLY install the TYPE of system it is BOOTED from)

[@esra_erimez]

@@ChrisTitusTech With this in mind, I rewatched your video and it is much clearer now. I missed the distinction between the ROM and Bootloader.

[@ChrisTitusTech]

Yup, it is very confusing and a very hard topic to cover. Glad that cleared it up for you.

[@MrDegsy69]

What Chris has not made plain as day here is that Apples implementation of the Extensible Firmware Interface is actually contained on a small 100mb boot partition of the computer hard drive itself and is not contained in resident flashable ROM as is the scenario on a PC. A Mac has no directly addressable BIOS as such and merely a few TPM enabler chips on the mobo itself. Universal Extensible Firmware Interface is a hybrid of both traditional BIOS and EFI hence the 'Universal' moniker. Indeed to make Mac OS boot on generic intel hardware as in the case of an Hackintosh you need to create a bootable EFI partition installation with a piece of sofware called 'Chameleon bootloader' or 'Clover' to enable this pre boot environment that Mac OS requires. In practice it is a bit more complicated than this as older BIOS only mobos often require a special bespoke crafted DSDT file that enables the EFI instruction set to handshake with the legacy BIOS. If you ever intend to go down the hackintosh route check out the Tony Mac OSX86 Hardware Compatibility Lists (HCLs) and choose a more current UEFI model that is fully supported and you will save yourself a lot of grief and heartache this way. It is a truism to say that if your mobo supports UEFI out of the box it is more 'vanilla' and henceforth more hackintoshable by its very nature. Editing and compiling DSDT file translation tables is not for the technologically inept or faint of heart.

[@fennec7906]

Can you explain this to me? I have mouse control in my BIOS (which should indicate UEFI), my C: drive is MBR, but when I load msinfo, my BIOS mode says "Legacy" I'm really confused about this. I don't know what I'm using. Since my PC is under a month old and the hardware is new (not old), shouldn't I be using GPT/UEFI?

[@LawrenceRobinson-xr2ix]

This is actually the very first time commenting on a video or any other web content for that matter. Since I'm currently trying to get a hold of the boot process (specifically the Linux boot process), I wanted to thank you for the great information and the way you laid it out with the accurate terminology for the subject.

[@xnonsuchx]

For any UEFI-capable OS install media, the easiest way to make sure you're installing in UEFI mode is to get into the 'BIOS' boot menu and it will likely have 2 listings for the media...one w/ "UEFI: " or "(UEFI) " or similar at the beginning. Also, there were old legacy BIOSes (at least AMI BIOS) before UEFI was a thing that had mouse support to navigate the settings.

[@toasterthebrot]

this comment has ended my 1 and half day long headache. thank you.

[@emanuelsanchez3762]

​@@toasterthebrotthe headach continues, when you don't get your wifi working in UEFI installation. In Bios installation everything works fine??

[@toasterthebrot]

@@emanuelsanchez3762 idk, but i dont think it matters whether you boot the uefi or the bios version

[@emanuelsanchez3762]

@@toasterthebrot if you need broadcom-wl to have wifi it's a problem. I have wifi when I install via bios, and I don't get it to work when I install via uefi

[@chilleddriving1455]

I've watched the rest of the video, and I do not agree with this. UEFI does not have anything to do with fancy screens, it is a method for starting up (much larger than 512 bytes) boot loaders from a (much larger) partition/slice on the disk.

[@CPPLondonUni]

4:06"...I believe I can actually change...." that does not strike confidence.

[@Eivraiiih]

There is also difference in language used BIOS mainly coded in Assembly and UEFI coded in C++. UEFI is more optimized in code because it's newer and offers more security.

[@JSB2500]

Just the clarity and accuracy I needed to succeed. Thanks! Tip in case useful: The only way I know of booting to Windows 10 on an NVMe M2 drive on a PCIe bus with a MB that doesn't supported booting to such a drive and bus is to: • Put Windows 10 iso on a USB memory key using Rufus (GPT / UEFI (non CSM) / FAT32). • Put the Clover bootloader files on a different USB memory key formatted with a single FAT32 partition. Make an NVMe driver available (there are web pages on how to do this - essentially copy the NVMe driver from the "off" folder to both the "BIOS" and "UEFI" folders, all in the "\EFI\CLOVER\drivers" folder structure). • Make the NVMe drive GPT from within an existing OS. I used "MiniTool Partition Wizard". • Boot to Clover. • Install a UEFI installation of Windows on that drive from Clover. I did this by dropping to the UEFI command line and running "efi\boot\bootx64.efi". I think you can instead copy that file (e.g. from within a booted OS) to \efi\microsoft\boot and rename it as bootmgfw.efi, and also rename cdboot.efi in that folder to cdboot.efi.bak

[@johanmyreen1027]

A good video, but I would like to point out one minor detail. You hint in the video that a big disk using MBR has to be split up in partitions less than 2TB in size each. It's worse than that: you simply can not address sectors beyond 2TB, so you can only use the first 2TB of the disk.

[@zinsy23]

Yes exactly! Another detail worth noting is that the bytes per sector also determines the limit, so if you have a hard drive with 4,096 bytes per sector rather than 512, you can technically have up to 16 TB on MBR, and would be able to go beyond the 2 TB limit in that case! MBR or GPT determines the number of addressable sectors, and that multiplied by the bytes per sector, will determine the actual limitation of addressable storage itself. That's why GPT's limitation is approximately 9.4 billion terabytes, but that's with 512 byte sectors. 4,096 byte sectors could be about eight times that theoretically! There's a lot of little intricacies to this.

[@premrajr9527]

I had issues installing grub when I was starting to learn more about linux. That is when I knew I had to check for UEFI boot. Any drive with windows installation normally shows up as two drives, one with UEFI label. It is the one with UEFI label to select while booting. Even if there is no UEFI shown or you select the non UEFI, windows automatically detects UEFI compatibility and switch to UEFI in a normal scenario. My laptop is new but is stuck with legacy BIOS (I don't know why, it's only released last year, curse you HP!). Well, I had no idea I had to run it on GPT and got errors. That is when I knew legacy supports large drives. Also, Linus was not that wrong, he was referring to MBR. GPT is a new way for legacy BIOS. P.S. You can get errors if you try to partition GPT drive in Windows. First, it will give you a warning if you partition during install. If you don't partition during install and does it later, you will soon get BSoD's and such problems. I don't know why this happens. This is the reason I can't run Linux with Windows in my laptop. Any Good Solutions? please reply.

[@ChrisTitusTech]

I've always had issues when dual booting Windows on UEFI based Grub. The only way I've had success is to use Legacy when doing the Linux installation and the os-prob the windows install into it. Note: I do this with 2 different physical drives. Due to the way Windows now does it's bi-annual upgrades I highly recommend separate drives as it can overwrite the grub bootloader if it is on the same drive. If you want to modify the windows based bootmgr I recommend using EasyBCD (neosmart.net/EasyBCD/) Also, Milage will vary in Windows as it seems like it is constantly changing the way Windows 10 is setup. It is very hit and miss. I believe Windows 1803/1809 switched to favoring UEFI mode and why the setup fails when loading these images in Virtual Machines where 1709 doesn't have an issue. As far as Linus's video, I was disappointed in it, as he didn't mention GPT one time and made it seem like all you need is a UEFI based system, which of course isn't right.

[@premrajr9527]

@@ChrisTitusTech I had no issues with dual boot along Windows 10 on an MBR partition ever but on GPT it really is problematic. I am using two drives for windows and linux separate as you said in my old desktop and I used EasyBCD on a Friend's PC. Also, lately using UEFI was somehow causing problems using the new Radeon VII GPU. Somehow AMD forgot UEFI compatibility. There was some fix for this, I don't remember right now.

[@ChrisTitusTech]

Weird that UEFI would cause issues with your GPU. I can't wait to try out that card, but good to know you tracked it down to that. I've had my Windows do some strange things with my GPT drive and at one point it was booting sometimes and other times not. I found that how Microsoft setup bootmgr relies on a very strict partitioning scheme. When I carved up part of my 6 TB with some Linux partitions it really didn't like it. I fixed this simply by booting from another drive that is setup on an MBR which Microsoft's bootmgr sees just fine.

[@premrajr9527]

@@motoryzen Maybe I was confused with partitions drives, sorry, it's been a long time since I DIY deeper into these things. I may be forgetting things here and there.

[@premrajr9527]

@@ChrisTitusTech Exactly! That partitioning scheme was my problem. Thanks for that workaround. I will set up to boot from an MBR disk instead. Also, I am not sure that GPU problem is so much of a issue, let me check weather it is specific to something or there is something else behind it.

[@zomgoose]

Thank you for the clarification and update. It is appreciated that you researched further to correct yourself because the smaller details matter in tech. :)

[@hash-CCFF00]

z

[@room2738]

Thanks! excellent video :-) that GPT vs legacy HD partition *size* (as in - chop up a 6tb into 2tb partitions) was something i was wondering about (gpt clashes with my current backup strategy)

[@user-ro1cc8tz6d]

I use gpt in legacy bios mode

[@C6438911]

Great video and indeed a confusing subject but very well explained !. Whenever I have a new drive and want to use it then I use a live linux distro on a usb, go to the live session and run partition editor (gparted mostly) to enable GPT on it. MBR has a limit of 4 primary partitions and beyond that you have to configure the extended partition (that is the total size of the drive(s) after the primary partitions) and then devide, if needed, the extended partition(s) into logical volumes (up to 2TB each). GPT has a limitation, i think, of 128 partitions and does not have to be flagged as primary or extended or has a size constraint (well maybe in the very very extreme big sizes).

[@theroundduckman]

UEFI isn't really that confusing when you look deeper, but when you think of UEFI as a BIOS replacement, it screws with your mind, as you feel the MBR way of one bootloader in magical space is the way, and that UEFI is only for pretty graphics and 2+TB drives. This is unfortunately because of the Windows-focused PC world where we don't need to deal with multiboot anyways due to the fact that most of us just have Windows installed, so it's not something to mention since one wouldn't notice that unless they dual boot. To many it's just install Windows, and done. They don't realize that UEFI is a completely different beast from the primitive BIOS, like Coreboot. BIOS is in no way that similar to the UEFI and both are quite radically different from one another, it's just that UEFI does have a compatibility mode to boot like a BIOS and that many imported BIOS GUIs to UEFI instead of taking advantage of UEFI. As a result, you get Linux users going "fuck UEFI," when UEFI, like ACPI, is an awesome thing that had some trouble getting set up at first since Linux distros had to adjust to UEFI and make their installers support it and handle it automatically.

[@lperkins2]

Note that if you have an odd setup (most common probably on installs from 4 years ago or thereabouts), the efivars module might not be loaded automatically at boot (or might not be included in the kernel), even if you are running an EFI system. A more reliable method is right after boot to run `dmesg | grep -i efi` and look at the output. The first line will usually indicate both that it *is* efi and the EFI version and vendor in the case that it's an EFI system (usually will be "EFI v2.xx by American Megatrends" or similar).

[@TheJamieRamone]

Hey Chris, how bout a video bout CoreBoot?

[@ChrisTitusTech]

Thanks first I've seen this project, I'll have to check it out!

[@wikingagresor]

@@ChrisTitusTech CoreBoot and LibreBoot are nice projects attempting to open source bios part of your PC. They are a must have for the "paranoid enough" people who don't want to be spied on by the NSA.

[@ThirtytwoJ]

A lot of it is the technicals having to stop and start and go back to bios etc over and over to figure out why your one old system isnt taking one os but will another.

[@thomasmaurer1097]

love the video .. you explained it well ... butt as a old guy i can tell you the reason alot of how to videos are different and some times wrong is because UEFI standers were never set 10 years ago .. man did some manufacturers make a mess out of it ... my 2007 lenovo k230 has uefi sport .. but it only works for USB / SD "removable" boot drives will not see an UEFI partition on a GPT disk but will see the UEFI partition if it was made on a MBR disk and will add the boot options to the F12 menue , but will not boot to an UEFI boot menu and hase no options to change legacy / Effie .. .. myself even on my kool laptop i have never frond a befit to UEFI ... i have only exasperated hardships with UEFI ... to the extra 5 sec boot time 1. the OS gets locked down, and for programs like GRUB or easyBCD "windows" it will take your ability to boot from a .iso, .img that are on your hard drives. so you cant use a live boot .iso to fix your system.. 2. if for some reason that uefi partition gets deleted , good luck booting or duel booting 'this got better over years' but its a horrible situation, if you encrypt any than 3. sincerity issues , the Ufi gives access to devices to change bios settings , if your concerned about that type of stuff 3. MBR is 100% fixable no madder what you do to it, and backwards sport for older or sensitized OS'es.. neosmart.net/wiki/easybcd/portable-entries/iso-images/ help.ubuntu.com/community/Grub2/ISOBoot

[@ChrisTitusTech]

Very good points Thomas, thanks for the comment!

[@dipi71]

Especially glad to read about the additional 5s, thought I configured something wrong whenever I tried UEFI- and GPT-based installations. Again, the old KISS principle holds: I use compatibility mode, Grub2 and Ext4 on a MBR-formatted SSD to boot into KDE in about three or four seconds now (best time according to systemd-analyze: 1.347s, that’s without BIOS initialisation, but including starting KDM). Ok, not quite KISS. Maybe I'll give UEFI another try someday. [Edited to correct: meant to write legacy mode, wrote compatibility mode]

[@anthonyduncalf-uk]

I make sure Secure Boot is enabled in the BIOS as it can't be in legacy mode if that is enabled.

[@komptek]

Chris, thank you for the informative video. I would like to add that I have just recently installed Linux Mint with ZFS as the file system, and it has accepted a 4 TB HDD and is functioning very well with only legacy bios.

[@lperkins2]

Note that 5 years ago, stock Grub for MBR couldn't read from GPT disks, and Grub for GPT couldn't read from MBR disks. Also, some old UEFI systems would not look for an EFI partition on MBR disks. (Legacy boot on GPT disks still worked, as the legacy boot method actually puts the boot loader at a fixed offset on the drive, ignoring the partition table itself). Anyway, that lead lots of us to assume it *must* be that way, and never check again. Recent UEFI systems and recent Grub handle it fine.

[@StenIsaksson]

If you want to dual boot different operating systems installed on separate drives without messing with the boot loaders you need UEFI. Then UEFI handle the boot selection by pressing F8 when you start your computer.

[@simonblackham4987]

Years ago this was easily possible using grub ... just edited menu.lst ... boot three different linuxes or windows7 from the grub menu... chainloader was your friend. Grub could also find boot sectors on disk partitions if you had messed up the mbr. UEFI and grub2 are great until the sh1t hits the fan. The easiest rescue seems to be to 'update' from the (linux) installation disk (always have one!) and (multi-)boot will be restored automatically. Only leave in the disk(s) you want to multi-boot if you want to use the bios to control the boot disk/partition.

[@chilleddriving1455]

I'm sorry, don't know if anyone else have mentioned this in the comments, but I had computers with BIOS menu mouse control long before UEFI came along.

[@RegErvin]

Aaarrrggghhh!!! I stumbled upon this vid today and wished I had it last week when I did my first UEFI install. I looked all over YT for a vid that would explain it and eventually figured out how to do it. This would have made it much simpler. Good job!

[@lperkins2]

You are correct that the maximum number that can be written in the partition size field is 2TB, but the start address is similarly limited. This means that MBR cannot support drives over 4 TB-1, and support for drives over 2 TB is not guaranteed (some old systems, especially 32 bit ones, don't expand the data structure size when reading the disk in memory, which can lead to undefined behavior if they try to write logical->physical address translations). Carving the disk into smaller partition sizes doesn't actually help with this limitation.

[@WilliamRNicholsonLST-1195]

Thx ! I have never heard any Eggspurt explanation that made any sense to any normal nonenhanced Earthling ! I look forward to many more vids by you & will allocate funds to support your work ! You show me that many of my dollars were indeed wasted going to computer shops with techs that knew less than nothing when compared to either you or amateur me !

[@AlexTidmarsh-vg1lr]

Oh my - things have just gotten so complicated since when we used to boot from paper tape, haven't they? Thank you for this great video!

[@vanpeters9751]

I had problems with uefi using linspire so I used volume groups to boot 4tb filesystem on mbr 6x 600gb 2x 146gb hdds

[@xartintv]

There's only one thing missing from this video. Future Chris's Christmas tree at 8:05 🎄

[@michadybczak4862]

1. I am a subscriber and I never saw that first UEFI video, so it looks like it wasn't properly presented by YT algorithm and that could be one of the reasons for its low visibility. The other question is why it happened. 2. What I hate about Legacy is that the boot data is saved in some vaguely defined, pre-partition, invisible and inaccessible space, while in UEFI we have EFI partition and it's clear where and what data is there - kinda helps to understand and control it. Also, because of EFI partition, we can have many grubs, on legacy, it's always one and the next one overwrites the previous one. Often there are issues with it, like the grub wasn't properly installed, or the previous boot sequence wasn't properly replaced and so on. What I dislike about UEFI is: it makes things little more complicated for newbies, because firmware vendors don't have a unified interface or ways of setting it. Because of that none of the dual-boot articles mentions even a world about it. So for example, when I was fresh, I had an issue making dual-boot, because my laptop showed some error prompt. The solution was to navigate with arrows to point the proper file in a proper directory in EFI partition to point it to the firmware FROM THAT ERROR SCREEN (not in UEFI settings, there was no way to set it there). Once it was done, the location was remembered and the next boots were successful. On another laptop Windows UEFI partition was used by default and that was all. I had to create a new boot in UEFI settings and point to proper boot files in order to work. I'm sure there are many other ways vendors do that. Also, the naming is confusing. Is it BIOS or UEFI? In my case, I am presented with typical BIOS interface and I can only use keyboard yet the laptop is rather new (3 years) and from top line (Alienware) so detecting UEFI vs. BIOS because of BIOS alike vs. advanced UI is not a good example. It's hard to explain for newbies and it's hard for me to understand how in someone else computer it is done. I will manage it fine when I see it, but helping others remotely is often impossible.

[@terryspiers2746]

You claim to use the EFI partition in solving booting issues, how do you do this? The EFI partition is not a normal partition like FAT/FAT32/NTFS/EXT2/EXT3/EXT4, it is formatted with an unknown partition type. What software do you use to inspect the EFI partition contents?

[@theignorantphilosopher4855]

What I like the best about UEFI, is that you don't technically need a boot loader. You'll be hard pressed to find a linux distribution, or any other OS (I think) that doesn't use one, but you can set if up yourself and save a couple of milliseconds booting. ;) Other than that it's pretty horrible. GPT of course is great and if I'm not much mistaken you can actually include a MBR and boot from a GTP partitioned drive, even if your old school BIOS doesn't understand GPT. Gosh, I miss the old days...

[@chromerims]

Thx. Helpful insight on 'no bootloader' UEFI.

[@FelixNielsen]

@@chromerims Lol, that's hilarious. Me providing insight. Anyway, you're quite welcome. ;)

[@aeromancer13]

Chris, I just finished reinstalling using legacy boot and everything was under 2T, but I'm glad I watched your vid because I've never (so far built or partitioned anything over 2T) and I would have prolly been lost trying to command line in the BIOS lol

[@ManthaarJanyaro]

UEFI is also more secure than lagacy, means no one with only physical access to your computer can just insert a bootable USB or CD and boot from that and have a complete access to your data. One can only boot from a removable media if s/he has administrative access to your computer. As one can only access UEFI boot menus such as boot from USB from the administrative account.

[@ManthaarJanyaro]

And I don't know what would one do if (and only if) his/her OS crashes. And s/he will loose access to UEFI boot menu.

[@cee128d]

I have to take issue with one of your statements. Having mouse support does not mean it's EUFI. Back in the 90's and early 2000s there were lot's of BIOS that had mouse support, most notably those from Matsonic, ECS, PC-Chips, etc.

[@ChrisTitusTech]

Hehe great point I forgot about those BIOS features, but. That mouse was an ugly block 😂

[@cee128d]

@@ChrisTitusTech Ugly wasn't the word for it. Plus they tended to be way too laggy with the processors that were on those computers.

[@cee128d]

@@bigpod The term BIOS (Basic Input/Output System) was created by Gary Kildall and first appeared in the CP/M operating system in 1975. IBM did copyright there original IBM PC BIOS, but they don't have a trademark on the term BIOS, only the code contained within their version of BIOS.

[@Daniel_VolumeDown]

Another benefit of uefi is that it supports installing 2 (or more I guess) bootloaders on one drive (If I am not wrong in LEGACY bios you can not do that; and also I am not sure if every uefi can do that but probably yes).

[@tawengski8380]

whenever I try to change to uefi in my bios, I only get a beeping sound and my operating system doesn't load. Im using a gpt disk and my installer is on a partition in my second drive which is also gpt. I figure I need to make my installer boot into uefi but I have no idea how.

[@terryspiers2746]

One of the main reasons for UEFI is Secure Boot, not to make the BIOS pretty, who cares about that? You are correct GPT is nothing to do with UEFI, it existed longed before UEFI. Yes modern secure boot systems usually use both UEFI and GPT. During a new install Windows 10 defaults to using GPT partitions with UEFI BIOS's. If you go into the BIOS, turn Secure Boot off, turn off UEFI to give you Legacy BIOS and then initialize the disk as MBR, you can often install Windows 10 like we use to do with old BIOS's, it then only creates 2 partitions (system and boot), instead of 4 partitions (system, boot, MRP, EFI). Some UEFI BIOS's do not support Legacy BIOS at all. When Windows 10 boot gets totally screwed up, it is much easier to fix yourself when using Legacy BIOS. Most people do not understand the EFI partition! I think only the operating system understands this for the Secure Boot feature. Often Windows 10 Startup Repair fails to fix Windows 10 boot issues, it sometimes even refuses to run at all. But using Legacy BIOS and MBR partitions you can usually fix the booting issues in Windows 10. Some recent UEFI BIOS's have had issues with Windows 10 compatibility, Microsoft blame OEM Manufacturers, Manufacturers blame Microsoft. Recent Dell Latitude laptops for example have ended up with 23 BIOS revisions to work correctly. So in my humble opinion, Secure Boot and UEFI BIOS has become a pain in the arse! I hate the damn thing all together.

[@terryspiers2746]

It has been claimed that UEFI Secure boot with GPT is faster at booting than Legacy BIOS with MBR or even GPT. I have not tested this myself, I have not noticed UEFI BIOS being quicker in general.

[@terryspiers2746]

Strictly speaking when ever I said Legacy BIOS, I should of said Legacy Boot. The UEFI BIOS enables legacy booting, ie. booting using non UEFI boot media, whether hard drive or UEFI DVD ROM operating system media. The UEFI BIOS does not turn into a Legacy BIOS, it just enables Legacy Boot, so it appears to be like a Legacy BIOS, but, really is still UEFI BIOS allowing non UEFI media booting.

[@smashogre4766]

2:03 - worth the price of admission right there!

[@snipernote]

windows (10,8.1,7) installed in UEFI mode the easy way ... boot windows installation USB (Made with Media Creation Tool) with CSM enabled and then when you reach the installer screen go to CMD with Shift+F10 and diskpart select your HDD/SSD clean it and convert to GPT ( Windows cannot be installed with a hybrid settings this means MBR for Legacy and GPT for UEFI only believe me i have tried alot and i know that by heart already ) ... now continue installation if everything goes well then you Will boot windows in UEFI ( you can know this from the first boot by looking at the logo at boot if its the MB bios logo then it is UEFI already and if its windows logo then its legacy mode ... hope this helps :) ... have been watching your videos for the last week and i am using CAD software so i am stuck with windows forever :P ... Have you tried Hackintoshing btw ? its very nice once you get the hang of it

[@priit7777]

Your definition of "old computer" is misleading. 5 years "old" in fact is relatively "NEW" computer. I could NOT install large drive as boot drive to my old intel Core 2 Quad system from year 2008, because it did NOT support uefi at all. Also the "old legacy bios" (which is/was the only option available) did not support booting from GPT disk and only MBR -- and yes, I did try (both, to install fresh and even tried GPT disk with already installed OS from another computer, the system reported that there is no bootable drive installed at all). Yes, I could use GPT drives in the system later as data drives, but BIOS refused to boot up from one. And NO -- you can not use big disks with MBR and cut it to 2TB partitions and use it all -- you can only use up to 2TB disk space from the entire 10TB disk when it uses MBR. Yes, it does say there is 8TB more space, but you can not create any more partitions into that space. Tried that also.

[@stephanc7192]

Also working on a 2008 core 2 due! (Probably called a dinosaur!, but can still get it to run win 10 and ubuntu 18.4 and mint 19.04) And although the Bios says support UEFI, for the life in me, I cannot get it to boot into a UEFI drive. Kind regards

[@MrGFYne1337357]

digging the terminal vids! echo "Sweet!"

[@buriedbits6027]

By the way, I run windows 11, Ubuntu and MacOS. As much as I hate the Apple tax, I have to say, they do a lot of things right. Everyday I ask why doesn’t windows it Linux do this? Thanks for UEFI video. Great stuff.

[@steveterry289]

Pretty good, could be better. Point: GPT uses a larger data format than MBR which allows it to not only manage a larger drive, but to manage the space more efficiently as well. Compare a hardbound book (GPT) with various font sizes to a smaller pamphlet (MBR) that has more limited font sizes. Analogy breaks down easily, but GPT can have many more file records stored compared to MBR, and with more granularity of information concerning the files (therefore more efficient). Still, UEFI seems like a hack. I keep kicking myself for not learning machine language back when it wasn't that hard on a Commodore 64.

[@Kcorey]

Your explanation is very clear and straightforward. Thank you. BTW, The antivirus app has detected a UEFI issue, but the antivirus app can't remove the UEFI detected thing. What to do... Do you have any knowledge or recommended tools ?

[@orthodox8224]

Can I install Windows on one drive and Linux on second without grub, and just boot pressing f11 (on my motherboard) for boot menu? Can I do that with uefi and legacy?

[@ChrisTitusTech]

Yes. You should be able to modify Microsoft's bootmgr using EasyBCD. There is some free version floating around but I just noticed they just started charging for it.

[@michadybczak4862]

You could but it's better to install grub and launch windows or linux from it.

[@TubeSkaterRudy]

The biggest benefit of UEFI is its security over BIOS. UEFI can allow only authentic drivers and services to load at boot time, making sure that no malware can be loaded at computer startup. But I wonder if this is only true for Windows .

[@_VeritasVosLiberabit_]

Sorry, but you're falling in the same kind of error as people with GPT and UEFI (as presented in this video): it is not UEFI what performs security checks in pieces of software as kernels and drivers, it is secure boot who does it. If you disable secure boot you won't get those security checks anymore, even when using UEFI. Finally, that's not only true for Windows, you can have secure boot enabled in Linux distros like Ubuntu, but not in others like Kali (at least at the moment).

[@LampJustin]

Thanks for all the hard work u put in your videos!! I loved when u showed ur videoclip 😂😂! That said, I think there's another reason to go UEFI and that is the bootscreen! Cause with EFIboot u r able to see the bootscreen in the full resolution and not some 4:3 crap. If u want u can also change the Windows logo at bootup by changing it in the (UEFI-)BIOS...

[@kennethflorek8532]

One thing that confused me (and so I ignored it) is that the BIOS on this newest motherboard has two icons for each possible boot device, one plain and one UEFI. (which you can drag and drop to any order, BTW.) So when I was adding another linux OS (I have a bunch) the setup gave me odd choices, only allowing EFI boot (which I have been successfully avoiding for years.) It turned out that the DVD booted different setups according to whether the BIOS was set to boot the EFI-version icon or the plain icon. Not every linux distro setup DVD does this, though.

[@JohnRaschedian]

Thank you! I'll go through your videos one by one. There's a lot of useful information in there. Thank you!

[@GS540]

wait so my thumb drive needs to be GPT and not MBR? i thought this was supposed to be easier. this is insanely confusing.

[@Appalling68]

Thank you for this video but man, I'm still confused. I'm planning a new desktop build in a month or two. I will be using a Ryzen CPU along with an Asus x470 mobo, probably two SATA SSD's, one NVMe 1TB SSD, 1TB HDD, 32GB RAM, etc. I was planning on installing Linux Mint on my NVMe ssd as my primary OS, and then maybe Win10 on a separate ssd to be used only occasionally. I use a boot manager/partition manager from Terabyte Unlimited called BootItBM. Are you saying I cannot or should not install my OS's under Legacy mode BIOS? Do I HAVE to use UEFI?

[@ChrisTitusTech]

Nope you can choose either, on newer PCs it really doesn't matter.

[@RickRomig]

I still find it confusing and getting Linux installed on some of my "newer" machines has been difficult. They work but I'm not entirely sure I got them right.

[@PhilReynoldsLondonGeek]

It still leaves me with questions - though you do say how to make sure you get UEFI at install time, is there any way (perhaps only after migrating all the drives to GPT) to migrate to UEFI from Legacy? (I'm running a Debian system)

[@Odank]

Well this made it more clear for me. At least with Win 10 and newer installs it seems that UEFI is kind of a default. So the main regard after this is formatting the actual drive(s) with MBR or GPT - GPT being the more modern and future-looking database method. What I didn't find anywhere however is if using a 2tb or lesser drive and not planning on more than 4 partitions if there is any benefit or downside in the format selection. Does NTFS / FAT 32/ exfat perform any differently in this scenario? From what I gather, GPT has a data security benefit by default? if anyone can chime in on this - it'll be much appreciated.

[@LinoshTheHaloGamer]

Here's the thing Windows 7/8/8.1/10 REQUIRES that your disk be formatted in GPT partitioning for UEFI Boot Meaning if you have MBR disk you are forced to legacy boot. So to put it simply in Windows UEFI Boot = GPT Disk formatting Legacy Boot = MBR Disk formatting No mix and match is possible Also in the case of Windows 7, your BIOS must be set to UEFI Hybrid or UEFI with CSM Support to boot into UEFI since Windows 7 still uses a 16 bit mode INT10H call during booting even in UEFI Windows 11 has dropped Legacy boot support completely and will not boot from MBR disks or Legacy boot mode (Workarounds have been found, but none fully functional) Linux can have mixed and matched boot modes, such as GPT with Legacy boot and MBR with UEFI Boot

[@asdbef3667]

Full of misinformation

[@LinoshTheHaloGamer]

@@asdbef3667 Okay... Comment articles for right... I'll correct the comment

[@kamelkadri2843]

Exactly I have UEFI installed on MBR drive and it works flawlessly

[@antwanreynolds7121]

Windows 8.X and up will attempt to install a UEFI based boot loader if you booted your install media into UEFI mode. In most firmware it's easier to force this from USB than using DVD. Windows 7 is also UEFI and GPT aware but in 64 Bit Only.

[@Mzansi74]

Thanks for the video! I'm curious, we generally use MSI or ASUS motherboads and the same for Nvidia GPUs. What is common in the USA / UK / Europe / India and other parts of the world?

[@terrysalisbury2183]

Thanks for the detailed information. I learned I can install Windows 10 on a 1 TB SSB in Legacy mode. Easy Enough. Keep It Simple!

[@miettoisdev]

the golden piece of info here is that: if you want to install UEFI you MUST boot from USB as UEFI

[@mrparalyzed6024]

If you use the Calamares installer installing a Linux distro on Legacy on a clean HDD/SSD, you will get a message saying about how to use GPT with a Legacy Bootloader.

[@thexthretics]

finally found the way to boot to usb for my chuwi surbook 12.3. Thank you very much for making things clear.

[@broken1965]

Cloning software doesn't help check for GPT so you clone 1tb nvme GPT to 1tb nvme MBR it says yea ok, then you gotta use GPT2MBR if you wanna change it lots of users are not fluent in these security requirements from Win11 an boot loaders setting up thier drives

[@SianaGearz]

I have a modern PC now (AMD B450 platform; my last PC was 10 years old) and while all of my PCs have supported UEFI boot, i haven't made use of it due to some dicey experiences i had. Like an older laptop i have will insist on also enabling secure boot when UEFI boot is enabled, which means i can't load my own drivers into the Linux kernel, or at least i couldn't figure it out back then. Not nice when i'm trying to patch up a buggy driver for obscure long forgotten hardware or considering i have NVidia GPUs in every PC including that very laptop. And no i don't need a lecture on how i should be buying AMD GPUs, i have my reasons. So i'm using CSM boot and MBR disk. Now i'm finding that a number of options in the BIOS setup disable CSM, such as resizeable BAR (not supported by my GPU anyway, but will be by the next one) and "Above 4G decoding", so it seems like UEFI is the strongly preferred way now and i should probably stop resisting, at least on this main PC. The real question is how to make it all work for me, and this is what i want to know, rather than nitpicking someone else's videos. I'm dual booting Windows and Linux. CSM also apparently receives less attention, like MSI published and then nuked a beta BIOS update just a couple weeks ago which completely broke on GPUs which don't have a UEFI compatible option ROM. You say these things are separate, and yet, at least for Windows, MBR system disk and legacy boot, and UEFI boot with GPT system disk are the only two supported configurations, things are just apparently hardwired that way. One of these, it just makes sense, since legacy boot requires 8086 bootsector code, and 512 bytes of code is a little too puny to parse GPT. GPT is supposed to be parsed by the UEFI code provided by the system firmware, but that's 32-bit/64-bit code. Also it would be nice if when i reset the CMOS on the mainboard, i still get the system to boot, while CSM requires a bunch of configuration changes in the BIOS. Also i am just not confident that i can recover from failures. Legacy boot, i understand the boot and can rebuild the boot by hand if i have to, i could even if i have nothing but a hex editor on hand, UEFI just makes my brain melt. BTW the laptop and a number of old AM3 mainboards i have, all of them have UEFI boot, oldest of these is from 2009, neither of these have a graphical BIOS Setup so... one doesn't have to do with the other?

[@politicaljunkie1967]

This is my issue I am not installing Ubuntu MATE from windows. The system has no system and it does have UEFI. I have tried legacy installation and my hard drive didn't see it.

[@NoorquackerInd]

Many motherboards I've seen want CSM off though, except for one old motherboard which says to not turn it off unless running Windows 8 compatibility checks

[@ianide2480]

Marketing is a wonderful thing, it truly is. A new acronym does not make a new animal. Don't get me wrong here, I am not calling anyone out or disagreeing with much of what you have said. I will say this though, they could have skipped the UEFI name and called BIOS it 2.0.. It wouldn't have made any difference, but someone in marketing decided a new name plus all the "new tech" would gear up the geeks and get them excited about the new features (I consider myself in that category, so this is not derogatory). It wasn't to long ago and there just wasn't enough space on a BIOS chip for the UI and clickable menu, lets not forget that it just wasn't conceptualized. The BIOS was intended to be lightweight, init all the devices, let the OS know the properties of said devices, and get the system up and running (it's true purpose after all). That the BIOS has gotten more and more complicated is a product of time and tech. All of the "UEFI" features could easily go into a more classic looking BIOS with a Enable/Disable option or some other easy to use drop-down menu, but hey clickable stuff is cool isn't it? I've spent no small amount of time writing/modifying BIOS code and I can tell you that UEFI is nothing but an addition to "classic BIOS" code. So I find it funny when I read that UEFI is going to replace BIOS, when it's just extra crap (try to keep up with my technical terms) tossed on top what was already there. Support for larger partitions needed to happen certainly, old tech has to make room. Sure there are some new features for security but, the init of devices has not changed one bit. Besides UEFI doesn't just go away when you turn on legacy boot; this is just a simple option enabled or disabled.. And UEFI is not what enables a GUI, the larger space available on a CMOS chip allows that...

[@cwmoser]

Let me see if I understand this. I have an old Lenovo W510 laptop with a BIOS that is Supervisor locked. Still I installed Ubuntu 19.10 in one partition and 20.04 in yet another partition. It has no entries in the BIOS for UEFI. What I understand from your video, I could have installed Ubuntu and let the installation process build a gpt boot partition to boot from instead of the MBR. Is this correct? AND, would the Ubuntu install process create for me a graphical UEFI where I can make the changes that I would normally do with the legacy BIOS? Also, would this gpt / UEFI give me a "Safe Boot" switch?

[@onism3053]

when using sudo apt-get install efibootmgr i get returned "EFI variables are not supported on this system." on kali 2020.3

[@X_TheWolf_X]

so i have an hp7-1205 and it says im in legacy mode ... i need to switch to uefi for it to read my graphics card ! all the videos are so confusing can you make a simple one . ive tried the automatic way from hp support but says no drivers for my pc when i look it up... how do i do it manually

[@versatilityinaction]

You're a LEGEND Chris ✌✔💯

[@n8lbv]

Video had about the same high level info as a number of other UEFI related videoes. Not even an entry level shallow dive into exactly what UEFI is and how to really make use of it blah blah blah. I'm still trying to get a better understanding of it. It's basically what I'd call an alternate bios that has 32 or a 64bit OS that can do more things at boot time. The most common and only thing I have ever seen it do is NOT require an x86 "real mode" kernel and be able to access modern hardware directly before loading the windows or Linux kernel or kernel drivers. Such as the FAT32 driver and be able to boot the "pre os" stuff from a FAT32 partition and not depend on the boot sector in an MBR partition or drive. This barely touches the surface.. next we hav things like the/a UEFI shell which appears to be very powerful and is frequently either loaded from a FAT32 partition on a drive or from the onboard firmware itself on some devices. Cheers, you are still miles ahead and beyond my skills, I am barely getting started. and way behind so to speak. If you look at my KZbin Channel you can experience tot total lameness yourself! I'm considering working to get better at it.

[@bradscott3165]

Do you know your sound is a bit muffled? It sounds very resonant, like the microphone is in a can.

[@ChrisTitusTech]

Noticed this as well, I need to use a new mic or just get the microphone a lot closer. I was just trying to keep it out of the shot, but I guess that doesn't matter.

[@pcrengnr1]

Thx for sharing. I find this all academic if you don't have a bootable system. No OS found is not something that supports Apt Get nor running any kind of anything. Have you got anything that tells how to troubleshoot a non-bootable system ? Again, thx for sharing.

[@jeffsadowski]

So you can do a legacy boot off a gpt partition? I thought the boot sector for legacy boot would interfere with the gpt partition scheme? I thought you needed a MBR disk to boot legacy?

[@somsuvradhar9322]

Just one question, the EFI partition that gets created, does it need to be formatted while doing a fresh install of the OS, or can be kept the way it is. I know its kind of late for this video, but would be really helpful to get a response.

[@danielmadison4451]

I think Twilight Spakle (a few comments below) may be on to something. I am still so confused. Furthermore, I am smart enough and more than capable of understanding this stuff. I started my life by changing MFM Partition tables in DOS Debug with Hex Codes. But I just upgraded from my old Win 7 rig to a NEW Dell laptop. Now I find out I can't duel boot my Win 7 because of UEFI. Still looking for a solution!

[@j800r]

For the moment, there's no reason you should have to use UEFI boot but there's also zero reason not to if your system supports it. It is generally superior. Some are under the misconception that it's a secure boot thing but I believe it was Microsoft that introduced that and UEFI existed before that. E.G OSX has been using UEFI boot since it's switch to Intel architecture. Secure Boot can be easily disabled btw meaning there's literally no reason not to anymore.

[@Remorsed]

If you go to Apps>System Information Says if you have UEFI or Leg

[@longnamenocansayy]

the pain between my ears is so great. i was so thankful when linux came out with this real neat iso that you could burn on cd then zippity doo dah next thing you were up and running. then the next puter bought i started reading about uefi. i felt like a chimpazee in the middle of bios. i avoid bios still, haven't had any troubles, don't want any, but at least i'm not afraid of the main behind the curtain.

[@rbkhyvc]

Is there a something about how to install Clover bootloader on a legacy only BIOS and use the UEFI emulation of Clover to boot to a GPT disk?

[@jorgenlarsen7666]

well which progam will confirm the status of GPT (W10) user.? I continue to have boot failure without any changes to the drive settings. Is it W10 or bios program related?

[@gerald4674]

Great instructional video. I’ve installed Linux three times UEFI without issue. But on my Z77 I have three SSDs for testing distros. One connected at a time. Twice the UEFI configured ones stopped being recognized as bootable after switching to another SSD. MBR I can swap them without issue. Read somewhere this is by design. Why?

[@sunnysun2030]

Well.. i just recently learnt that to be able to boot with a brand new flashy NVMe PCie (4.0 soon..)... you DO need UEFI (and then GPT partition scheme/install).. legacy bios just don't know/recognize natively boot devices on PCIe (they can recognize NVMe boot drives in sata mode only though).. is that true ? if so, well.. that would be a major reason for me to try and test that new UEFI thingy right now then..on a brand new motherboard (x570 style , for the new NVMe pcies 4.0 later..)..formatting windows uefi/gpt on a classic ssd boot right now..just to prepare and make easier a quick clonage to a 4.0 boot nvme later..all in uefi/gpt for the future nvme (same os cloned).. that would be my main reason right now.. is that right?

[@thomasmaurer1097]

for people that want safy - DON'T USE UEFI ... disable it ... it gives the OS compleat control / able to modify you bios setting ... it's just a matter of time until a virus destroy your hardware.... there ben a few do this in the past ... "melt ware viruses" Legacy boot gives no access to the Bios chip ... (unable to flash it without a dedicated flash environment "32 bit dos -most manufacturers" and will be unable to do this on UEFI bios) ..

[@Ibelieve218]

my HP laptop the radio program is in dos so I need freedos on the usb stick but the hp does not see the usb it only sees UEFI SO I NEED TO FIND A WAY to put freedos and the radio software onto usb stick any help would be great thank you

[@Ottonic6]

I followed your video titled "Minimal Windows 10 Install | ISO Creation, Setup, and Config ", and there was a part in there that states "you will need to disable secure boot"... I have watched some videos (including yours) on how to do this, but in my ASUS BIOS (Crosshair V Formula MB which I use UEFI mode, so I don't think it is too old), or am I missing something because I don't have a "Security" tab, nor in my "boot" tab do I see anything on Secure Boot. Now what I was going to try is, disabling Legacy USB (it has auto also) and Legacy USB 3 and then attempt to boot and install W. 10 from my USB 3 flash drive... And yes, My new SSD that I will be installing W. 10 on is set to GPT... We'll see... Any suggestions? Thanks Chris.

[@eingooglenutzer2734]

the videoqualety is very good now, great video!

[@GS540]

I used microsofts "media creation tool" to create a usb thumb drive to install windows. the USB drive says its partition style is "MBR" does that mean when i install windows it wont be GPT and UEFI?

[@brokenos7710]

At the end of this video I still don't know what UEFI it self is? like why do I need to use it? Will I see a performance boost? Is it usually enabled by default? If I already have a working linux distro installed should I reinstall if I am not using UEFI even if it is working fine as far as I can tell?

[@dave4882]

I expected to see the UEFI screen and you going through each of the items there.

[@uniquex232]

Which one is good..i have a laptop with Intel Pentium A1020 ..4GB ram..500gb hdd.... Which one is for me...uefi or legacy..?

[@hamilton4282]

When using the USB stick for recovery or reformatting the harddrive, I get a message stating: "No PBR driver found found! Run mops1 fail"! Once I click "OK", it will just sit there for days, and not do anything. So I unplug and start all over again. My BIOS settings are as follows: CSM Support -> Disabled Boot Mode -> UEFI Only Quick Boot -> Enabled If I take the USB stick out, and run the PC to try and boot, I simply get stuck at a black screen, for days on end, nothing happens. I have to reboot and try again. Any suggestions?

[@emjaycee]

I only have new computer systems, one about 18 months old and one only about 6 months old. The older one is my daily driver (Mint Cinnamon) with a Ryzen 1600X/NVIDIA 1060 GPU/M.2 and it only has one M.2 drive plus a storage drive. The second one is an Intel i5 8600K but it has 10 bootable drives for me to 'play with'. Both has Asus motherboards. On the Ryzen system I left BIOS set at UEFI or Legacy... but I really didn't know what I was doing. On the Intel system I set it up the same way but had lots of issues. I had no problems installing distros using that set up but when I went to another drive and later came back, sometimes I would get the message there was no bootable drive. Checking in BIOS I would commonly see that one drive had a Windows preloader on it, weird given I have never had Windows anywhere near either of these systems. This was always an issue when I installed MX and Antergos specifically. When I changed everything over to Legacy only, all my issues disappeared. MX and Antergos not only 'installed' but they 'stayed'. I've learned a lot, particularly that I'm only a basic user (don't game, don't video edit, don't do fancy design work), I really don't need anything fancy at all... my first system is really overkill for what I need/do. I will eventually change it over to a Ryzen 2400G and no GPU and just get a decent sized SSD instead of an M.2 as the main drive. The KISS principle is now my motto lol. I will only ever use Legacy unless I absolutely HAVE to use UEFI for some reason. I had just ASSUMED as I had new hardware that I HAD to use UEFI. KISS always :)

[@cagedtigersteve]

How about secure boot? What does that mean?

[@rickbaker475]

How's your debian working out? I love my solydx. Using ukuu hasn't really presented any prolems.