Process for Converting from Legacy to UEFI (in prep for Win 11)

So, apparently this is possible using the following procedure:

1. Back up your VM file in case you screw up [!!!!]

2. Boot into your Win10 VM as usual.

3. Check your Win10 virtual hard disk using the administrative tools to see:
a. If there are no more than 3 partitions. If there are, see if you can whittle it down.
b. Check the properties to see if it's Master Boot Record (MBR) or GUID. If it's MBR you're legacy. If it's GUID, you're already UEFI and don't have to continue.

4. Do an advanced reboot into a command prompt:
a. While holding down Shift key: Start -> Power -> Restart
b. Select Troubleshoot, then Advanced options
c. Select Command Prompt

5. Log in with your account and Microsoft password (not your pin)

6. Using the command prompt:
a. Type: "mbr2gpt /validate" without quotes and hit return. This will check your hard disk.
b. If there's a problem, type: "mbr2gpt /validate /allowFullOS" without quotes and hit return.
c. If all is well, type "mbr2gpt /convert" without quotes and hit return. It will convert the MBR disk partition scheme to GUID.
d. If might give your some grief about WinRE or some other thing, but generally, if it says 'conversion was a success' you can just type "exit" and hit return to kill the command prompt and return to the advanced menu.

7. Choose "Turn off PC" to kill it. You don't want to restart Windows yet.

8. Find your VM file in the Finder, right click on it, and choose: "Show Package Contents".

9. Find the config.pvs and carefully open it in TextEdit:
a. Search for the section <Bios dyn_lists="">
b. Change <EfiEnabled> from "0" to "1"
c. Change <EfiSecureBoot> from "0" to "1"
d. Save the file back.

10. You should now be able to open the VM Confguration, go to the Hardware tab, click the "+" and add the TPM Chip. If not, restart Parallels first.

11. Run Win10 as you normally would. It might have an issue at first (mine did), but subsequent restarts seem to be ok.

12. You then should be able to run the PC Health Check, obtained from https://aka.ms/GetPCHealthCheckApp. Mine came back with a processor error, since it's an older Quad-core i7 (early 2013 MBP), but it's technically sufficient per Win11 required specs. All the other things checked out:
❌ The processor isn't currently supported for Windows 11 [Intel Core i7-3740QM CPU @ 2.7GHz]
✅ This PC supports Secure Boot
✅ TPM 2.0 enabled on this PC [TPM 2.0]
✅ There is at least 4 GB of system memory (RAM) [8 GB]
✅ The system disk is 64 GB or larger [275 GB]
✅ The processor has 2 or more cores [4]
✅ The processor clock speed is 1 GHz or faster [2.7 GHz]
Not real worried about the first thing because this processor isn't listed as being supported for the current version of Win10 (21H1) on Microsoft's site, either.
 
Thanks to @BradB7, who passes along a way to trick the registry into thinking your system passes all the tests (note that hacking the registry is not for the squeamish. Always backup your VM when doing things like this):
  • Open the Registry Editor and navigate to HKEY_LOCAL_MACHINE\SYSTEM\Setup\MoSetup
  • Search for AllowUpgradesWithUnsupportedTPMOrCPU
  • Change its value to 1.
Once you've done that, restart your PC (or VM in this case) and install Windows 11 using your preferred method.

Thanks for your help. This is interesting. I navigated to the HKEY... but there was no Allow... line anywhere, so I added it. Still didn't work. I tried adding it both as a Key and as a Binary. Other ideas?
 
In my case I actually had to add it to the registry myself. Had no issues upgrading my Win10 using the setup.exe in Win11_English_x64.iso. I did have the TPM and secure boot set, but my processor wasn't on their list.
 
Can anyone who added this value to the registry please post some detailed steps on how your did it? Like JoelH1, I do not have that AllowUpgrades... item in my registry at all.
 
Can anyone who added this value to the registry please post some detailed steps on how your did it? Like JoelH1, I do not have that AllowUpgrades... item in my registry at all.
If it's not there, you have to add it, as I said. that said, if you don't know how to add a value manually to the registry, perhaps you shouldn't.
 
System won't validate my drive when I attempted the conversion. CheckDisk shows everything being okay, but still can't get the validation. Additionally, I don't have the AllowUpgrades... part either.
 
Thanks @Mark Fine, for the instructions. I copied the VM, renamed it and performed the steps to go from MBR to UEFI, and the conversion went ok.
Software Update still said the 'PC does not meet the requirements', but PC Health Check said all was OK for Windows 11.
I went to Microsoft's Windows 11 download page and choose the 'Upgrade' option. All went smoothly.
 
Happy to finally find a way through upgrading from VM with "Legacy bios". For some reason I get stuck in step 5 in the #1 post???
The pwd for my MS account (the very one, I am logged on with - and it IS an administrator account!!) is rejected? I have no idea why?
Since I am stuck there in the procedure, I would be happy if someone can help me to resolve the block??
Thanks in advance....
 
Easy. Change the account to a local login, set an easy password before rebooting into the troubleshooting mode. Finish the upgrade then switch back to your microsoft/live login. Use this on my 4 VM's that I converted.
 
Hey! I got passed step 5 - thanks! I got to the "Grief" in 6.d. and stuck again.
I get the following from the command "mbr2gtp /convert":
"MBR2GPT: Attempting to convert disk 0
MBR2GPT: Retrieving layout of disk
MBR2GPT: Validating layout, disk sector size is: 512 bytes
MBR2GPT: Trying to shrink the OS partition
Cannot find room for the EFI system partition.
MBR2GPT: Conversion failed"
I tried to extend the size of the VM disk w 10GB, but that can't be it. It came back with the error.
SO: I am hoping for someone to give me another clue: How can I come past this one?
Thank y'all!
 
This worked perfectly for me, thanks you very much for posting this response.
I made a copy of my VM after this, got a B SOD first restart but has been working great since.

Now for the Win 11 upgrade on the chipped VM. Pity that Parallels advise this solution but to do a full install of Win 11
 
I attempted to follow these instructions several times, but MBR2GPT consistently failed. A YouTube video informed me how to find the error log, and the error seems to be:
ValidateLayout: First partition too close to the beginning of the disk. Should start at offset 17408 or above, found at 512
This is absolutely the case, but I have no idea what I can do about it. This VM was created under Parallels back in Windows 7 (perhaps even XP) and has simply been upgraded since then. The disk looks like this:

Screen Shot 2022-04-13 at 9.07.04 PM.jpg
and

Screen Shot 2022-04-13 at 9.11.17 PM.jpg

Is there anything I can do (that's not insanely effort-intensive) to end-run this problem?
 
Back
Top