Fixing a VM that had AutoAddVTPM set: Difference between revisions
Fixing a VM that had AutoAddVTPM set (view source)
Revision as of 19:02, 22 September 2023
, 22 September 2023→Here's one solution where you have a few manual steps
mNo edit summary |
|||
| Line 9: | Line 9: | ||
The steps to recover your VM are as follows: | The steps to recover your VM are as follows: | ||
This reddit thread here has the steps: https://www.reddit.com/r/vmware/comments/qy9wns/comment/hmokzl7/ where I helped a user getting back their VM. | |||
For this type of VM none of the data is encrypted and only the descriptor files are encrypted. | |||
You can recreate the descriptor files and get back to a functional VM. If you haven't resized the virtual disks over time then it is a matter of creating a new VM with the exact same virtual disk in size. | |||
That would be enough to get the descriptor data to copy over into the currently encrypted descriptor files. That should work. | |||
If OTOH you have increased the size of your virtual disks over time then you have to repeat that increase in the exact same manner. | |||
The steps are basically: | The steps are basically: | ||