Upgrading Fusion Technical Preview Win64 Arm to retail Fusion

[HelgeBecker]

The current retail version of Fusion is not able to decrypt an VM created with the technical preview. How can I switch from the technical preview to the regular Fusion version without loosing my virtual machine?

[Technogeezer]

My first impression is to do the following on the Tech Preview prior to moving the VM to Fusion 13 retail

• Uninstall VMware Tools from the VM.
• Power off  (not suspend) the VM and remove all snapshots 
• Remove the TPM device from the VM.
• Decrypt the VM. 
• Downgrade the VM to hardware version 20
• Now you should be able to move the VM to Fusion 13.

once you move it, add the TPM device back to the VM config and re-encrypt. 
then reinstall tools in the VM provided with Fusiin 13. 

Down

[HelgeBecker]

Following those steps work till decrypting the machine.
That step is giving an error: 
"Unable to decrypt the virtual machine: Dictionary problem"

Any idea how to solve that?

[Technogeezer]

This sounds similar to a problem that's been reported here:

https://communities.vmware.com/t5/Fusion-2023-Tech-Preview/quot-Unable-to-reencrypt-the-virtual-mach...

[ColoradoMarmot]

Honestly, there are issues upgrading VM's from Fusion 13, so would recommend building a new one from scratch using the instructions in the unofficial guide pinned in that forum.

[HelgeBecker]

I will wait for a newer version of the retail client and try again to move. It did cost a lot time to get Win11 Arm clean installed. Beta->Activation->Recovery to retail Win. Not keen to invest this time again

Any news when the next Fusion version will come out?

[Technogeezer]

---

@HelgeBecker wrote:

Any news when the next Fusion version will come out?

---

Some time this fall, if I read what VMware has said correctly.

I hope that it’s sooner rather than later since macOS Ventura Sonoma is slated for release in about 2 weeks.

[billearl]

Sonoma in 2 weeks, of course.

[Technogeezer]

@billearl - D'oh and thank you.

Too much Ventura on the mind. I fixed that in my reply.