Convert Windows 10 from Legacy BIOS to UEFI without Data Loss  

I'm getting this Screenshot by Lightshot

Takeshi18 said:

I'm getting this Screenshot by Lightshot

Too many Capcha wanted on your image website there, I'm not going to waste time trying to get past them all to see your photo. Why don't you just upload it to your forum post here?

This is good information.
I want to get read for Windows 11 so I want to do this process. Is the thread still valid?
My older MSI motherboard has what's called "Windows 8/8.1 Support" in the BIOS, so I enable that. There are some Fast Boot options which I temporarly disable for experimental purposes. When I look at the boot order on the drive manager (in the BIOS) it indeed says UEFI. A straight up enabling of those options simply gives a command prompt instead of a system boot.

So, if I convert the system MBR using the OP's method from within Windows 10, then go to the BIOS and enable UEFI, should that be all I need to be in business?

There are multiple criteria for a supported upgrade.

If not performing an upgrade you can clean install in an unsupported fashion.

For example there are many computers that do not have the required CPU, Drive partition structure, BIOS settings, Secure boot, TPM, etc.

Krawk said:

So, if I convert the system MBR using the OP's method from within Windows 10, then go to the BIOS and enable UEFI, should that be all I need to be in business?

Yes

This is what I get when I try the process:

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


I also get an app crash, bad_module.info

Brink said:

Hello,

Does this below apply to your issue with disk 0?

Although disks configured with MBR-style partition can have up to four primary partitions, for this process to work the disk you want to convert can't have more than three partitions, because one allocation is needed to create the new UEFI system partition.

Thanks for the quick reply.

The drive is a 2TB Samsung 860 PRO SSD with a 1.9 GB primary C partition and the system reserved 500Mb space created by Windows.

Related? Earlier today I was trying to create a recovery drive just in case of failure but the system says it is missing the required system files to do so. Could the two be related? When I tried troubleshooting that process, one of the possible choices for failure was that it was caused by cloning software, going from a smaller drive to a bigger one.
Yesterday, I did create a USB install media from Microsoft. I do have an older system repair CD as well in my backup trove. The 'Recover' file could not be mounted because it has changed format and/or name.

Current Windows 10 build 20H2.

Sure... Here's the image.

I have to still wonder if the program has stopped working "bad_module.info" is the cause or the effect?
I've considered creating a flash drive of Windows PE and trying the CLI there to do the convert. The instructions for creating such a device are not 100% clear.
I did update to 21H1 19043.1288 and that has made no difference.