I would think that existing apps would be preserved.
The inability to in-place upgrade an Intel Windows VM to Windows 11 ARM is 100% a Microsoft problem. They don't have a mechanism in their installers/upgraders to switch architectures. The only option to migrate from Intel to ARM is the "fork lift" upgrade - install Windows 11 ARM as a new VM, install all the applications you need and then restore your user's files from the old VM. Fortunately you can configure the old VMs virtual boot drive as a additional drive to your new VM and copy the files.
If the Intel CPU in your Mac is earlier than an 8th generation Core processor, PC Health Check will tell you that you can't upgrade to Windows 11 from windows 10 - even if you have met the memory, disk, TPM, and Secure Boot requirements. It will say you're using an unsupported processor. You'll need to research registry settings that will allow the Windows 11 setup to upgrade Windows 10 on an unsupported CPU.
Original Message:
Sent: Sep 02, 2024 05:20 PM
From: hollistonma
Subject: VMWare Fusion W10 to W11
@Oaf,
Thank you for the step by step instructions. Made it easy to get Windows 10 running in Fusion on my MBP ready for Windows 11.
When you used the IOS to install Windows 11, did you have to reinstall apps? I have two apps for which I may not have installation discs so would like to upgrade without having to reinstall apps.
Information on the Internet suggests that I should upgrade within Windows 11 if I want to keep the apps (and data).
------------------------------
Pacoinmass
Original Message:
Sent: Feb 18, 2024 03:39 PM
From: Oaf
Subject: VMWare Fusion W10 to W11
Thanks for your thoughts permaz. I had already turned my VM into Windows 11 but the inability to migrate to ARM has stalled me. The following may appear cryptic, but it's the notes I made in a readme file after getting to Windows 11. Hopefully it's of some use to somebody else:
I started down this road because I had an Intel MacBook Pro with a Windows 10 VM that I used ONLY to run a legacy program for which I no longer had the installation disks. I was about to about to purchase a new Apple Silicon (ARM architecture) MacBook Pro and I heard that ONLY VMs using the ARM version Windows 11 will work. As such, I wanted to move my existing VM from Windows 10 to Windows 11 on my Intel MacBook Pro to make sure the program still worked and then I would worry about migrating my Intel Windows 11 VM to ARM Windows 11. After performing all the steps below to get my VM working in Windows 11 on my Intel Mac I subsequently found out there is no way to migrate that VM to the ARM version of Windows 11 i.e. it was all done for nothing and now I'm definitely rethinking my new MacBook Pro purchase :-(.
There are many steps to make a Windows 10 VM ready for Windows 11 and the order is important.
Allocate 4GB RAM and 2 cores for the VM
You'll also need a minimum of 64G hard disk. This is tricky if you don't already have that much allocated. If you don't then allocate 65GB to the hard disk. That just tacks free space at the end, however the main partition that needs to be 64GB is NOT the last partition i.e. the extra space just added is not added to the main partition, all you did was create an empty partition at the end. Now you need to move the partitions around so that the main partition is beside the new empty partition so they can be merged. This is done within the VM itself using a free utility - there are many, I used NIUBU Partition Editor. It's a little counter-intuitive but it gets the job done. Given that the last partition is the empty space you just created, select the partition beside the last one and then slide it's contents all the way to the right to effectively shift the free space partition to the left. Keep doing that until the free space is to the right of the main partition and you're ready to hit the Apply icon. It will then reboot and after you're done your main partition will be bigger. Confirm all is good by running Disk Management.
Unfortunately, my Windows 10 VM did not use the EFI firmware or the GUID partitioning that is mandatory for Windows 11 so this was a messy affair to fix. The following ended up being the right procedure.
Search for "cmd" and then right-click on the selection and select the option for running as administrator
run the command "mbr2gpt /convert /allowfullos"
If it completes without errors then great. Mine completed with:
Call WinReReapir to repair WinRE
MBR2GPT: Failed to update ReAgent. xm1, please try to manually disable and enable WinRE.
MBR2GPT: Before the new system can boot properly you need to switch the firmware to boot to UEFI mode!
That was worrying, but it turns out you can ignore it.
Shut down the VM and fully quit Fusion
Locate the VM in the Finder, right-click on it and do "Show Package Contents"
Edit the .vmx file and add the line:
firmware = "efi"
Start up Fusion but don't run the VM
In the tools window select the Encryption icon and then select the middle option "Only the files needed to support a TPM". You'll need to provide an encryption/decryption password.
At the top right of the tools window click on Add Device and then select TPM
Start up the VM, and go to the Windows Update control panel
Follow the links to download "PC Health Check" from Microsoft and run that. Hopefully now it'll say your Windows 10 VM is ready to be upgraded to Windows 11. Stupidly, the Windows Update control panel will likely still say your VM is NOT good for a Windows 11 update. Apparently it takes a day or two for the control panel to check with head office to make that determination. No amount of restarting or checking for updates forces it to realize it's Windows 11 ready. Everybody complains about it and Microsoft apparently are never going to fix that. If "PC Health Check" says you're good then that's all that matters.
From within the VM, download the version of Windows 11 you want from Microsoft's website as an ISO. I selected the Home version. Double-click on the ISO and then double-click on Setup.exe. During the install you'll be asked for a product key - just ignore that, Windows 11 will still work (with restrictions) once installed. Note that despite selecting the Home version ISO I ended up with the Pro version of Windows 11 :-/.