When you do an initial OS install today, you have to boot the computer in the mode that you intend to use (Legacy BIOS / CSM mode vs. UEFI mode, with or without secure boot). This is the case with Linux too. You can't really just switch modes afterwards.
For Windows, you'll definitely need a reinstall. (Edit: I didn't read your post carefully, apparently there's a tool to fix it? Neat!)
For Linux, there's probably a way to re-bootstrap everything yourself (reorganize your partitions, create the EFI partition, copy your kernel and initrd, etc.), but reinstalling is preferred, and will almost certainly be easier.
Several years ago I screwed up a Windows/Linux dual boot by installing one under BIOS and the other under UEFI. The only way to select the operating system was to go into the firmware settings and flip the CSM/UEFI bit each time. That was an annoying week, but the fix was to turn off CSM and reinstall everything under UEFI.
There is this base assumption that UEFI=GPT and that BIOS=MBR which is only partially true (at least for windows 7/8/8.1/10).
In fact the UEFI is perfectly capable of booting from both GPT and MBR disks, the issue is only that when you install an OS in CSM (or BIOS) on a MBR disk, the OS loader/boot manager installed will be the one needed for BIOS booting, and the UEFI one won't be installed.
Besides there is the requisite of having a FAT32 (this can usually be worked around with a UEFI NTFS driver).
But a "normal" BIOS install on MBR (with a dedicated, without drive letter automatically assigned, FAT32 primary partition dedicated to the boot files) can be booted just fine in UEFI by simply adding to that partition the needed UEFI loaders.
The opposite (booting with BIOS from a GPT disk) is as well possible but needs some non-standard modifications/hacks to the disk MBR, that - although proved in the years to be "safe" remain a sort of hack (not recommended if not really-really needed).
That's one worthwhile technique.
Not many users want to go much further since then you need at least twice as many boot files as the minimum and it's best to test each configuration thoroughly.
If you're dual-booting you are already putting twice as much effort into OS installation & maintenance already, this is not really popular but I did post my latest findings just a couple days ago how I use 4 sets of boot files for W10 & Ubuntu on BIOS & UEFI:
https://news.ycombinator.com/item?id=27629350
It's a little entensive background info, the basic outline is shorter than that.
But even then, I see no reason to trust that a given UEFI implementation won't quietly accept some secret hard-coded key even after all of the defaults have been removed, so now I guess we're stuck with older machines that can be flashed with Coreboot?
Yeesh. The number of people who can get this to work has got to be vanishingly small...
In addition, Secure Boot prevents malware from changing the bootloader (and helps stop boot-time ransomware). It's just a good sense fix to many attack vectors left alone for years.
No manufacturer has shipped an mbr formatted drive in the last 5 years.
This is relatively a non-issue for most orgs, you should have an imaging solution in place, if not there is Windows Hello/Autopilot, not free but easy to deploy and helps you manage and orchestrate, which is what every corporation should do with owned devices.
Machines 5yrs+ support TPM 2.0 unless you bought absolutely bargain basement prices like Dell Inspirion models from Walmart instead of Dell.com and such, but even lately those also include TPM and Secure Boot as Microsoft demanded it from it's vendors.
Building your own PC, is something that, is kinda dead in todays times though.
The number of people having issues finding high end graphics cards over the past 18 months says otherwise.
It doesn't help that the Lenovo BIOS updating software is crap too. I don't know why it asks me if I want to change the serial number every time it runs (and it doesn't default to "No").
So, who still using Windows 10 on MBR/BIOS installation is mostly beginner for DIY PC.
Even a tech savvy user then gets bored of the process to change the configuration.
Most other people will simply give up and either not use the new windows version or replace the perfectly good hardware with something else that someone else has already configured.
Now I'm also bored already just trying to explain what's going on here.
Things like this not being setup optimally on pre-built PCs is also not exactly unusual. Although I assume it'll mostly lead to people sticking with Win10 for longer.
For one thing it'll cut the 30% of the story that involved figuring out the compatibility issue iteratively.
I could also see “Your computer is not compatible. Get Surface Pro for XX% off at the Microsoft store!” Because antitrust and MS are a thing, historically.
> Do we even know if UEFI compatible hardware and SecureBoot is enabled by all OEMs by default?
If they have a Windows 8 sticker on them, or above, yes.
Because they play games and the OEMs mostly sell overpriced crap in that market segment.
Because building a computer is very easy as doesn't require deep knowledge of the inner working of BIOS. I put together IKEA furniture, despite not having a deep understanding of carpentry. I added a dimmer light switch in my house, despite not being an electrician. There are many people that can build a computer and troubleshoot 95% of the basic simple problems that come with that, but are not deeply technical.
I went into the BIOS (sorry, UEFI setup) and enabled TPM, which I had read about as being one of the major issues. That wasn't enough, and I was informed that my PC still isn't compatible. I tried enabling Secure Boot, and got an error message that there was something else I had to do first (generate a security key). I figured out how to do that, and I still couldn't enable Secure Boot because my PC was in CSM mode. CSM mode is my B450 motherboard's default mode.
I tried disabling CSM mode, and then I was able to turn on Secure Boot. However, when I rebooted, my computer couldn't find my SSD, and kicked me back to the BIOS, with no message other than a beep. I turned everything off and gave up for the evening.
Then this morning I Googled some of the messages I got and realized that the problem might be that my SSD doesn't use GPT but MBR for the partition table (it was pulled from my previous PC). After thinking I was going to have to back up and recreate my hard drive, I realized that there is a command-line tool I could use, helpfully named mbr2gpt. I ran that with the appropriate options, ignoring some warnings. It ran successfully, although I got an error about my recovery image, which was spurious so far as I can tell.
Once I did all of this, I was able to switch on Secure Boot, and the compatibility checker informed me that my computer is compatible.
The point is that I'm pretty computer-savvy and have a pretty new PC. It still took me quite a while to figure this out, and a lot of people would have given up around the time they had to go mucking around in the BIOS. Unless you are have a recent store-bought PC that has Secure Boot and TPM enabled out of the box, you probably aren't going to be able to upgrade, even if your hardware is compatible.
I'm guessing that Microsoft walks back on this decision.