wila
Immortal
Immortal

Hi,

I've written out the steps here: https://www.reddit.com/r/vmware/comments/qy9wns/comment/hmokzl7/
Let me quote myself from one of my replies...

The steps are basically:

  • Create a new VM with a virtual disk of the same size as the encrypted one, make sure it has the same name.
  • use the new descriptor file ('MK Win Desktop.vmdk')

  • use the old vmdk data files ('MK Win Desktop-s001.vmdk' (001 to 016)

  • use the old .vmx file, but remove the lines that start with:

    managedVM.autoAddVTPM

    managedVM.ID

    encryption.encryptedKey

    encryption.keySafe

    encryption.data

If there's no snapshots then you don't need .vmsd (don't copy it in the new vm, delete if there)

Normally also no need for .nvram and .vmxf

That should be all.

As this is one of those type of answers where it is important to get all the details correct, I've just thrown it in a wiki article.
See here: https://wiki.vi-toolkit.com/index.php?title=Fixing_a_VM_that_had_AutoAddVTPM_set

I will update that with whatever detail is still missing.

--
Wil

| Author of Vimalin. The virtual machine Backup app for VMware Fusion, VMware Workstation and Player |
| More info at vimalin.com | Twitter @wilva
Reply
0 Kudos