Fixing a VM that had AutoAddVTPM set: Difference between revisions
Fixing a VM that had AutoAddVTPM set (view source)
Revision as of 19:05, 22 September 2023
, 22 September 2023no edit summary
No edit summary |
|||
| Line 3: | Line 3: | ||
This would encrypt parts of the VM, but not give you a password and as such some people to find out that their VM won't work on some other hosts. | This would encrypt parts of the VM, but not give you a password and as such some people to find out that their VM won't work on some other hosts. | ||
The good part is that your data isn't actually encrypted, the bad part is that it isn't easy perse to get the data out. | The good part is that your data isn't actually encrypted, the bad part is that it isn't easy perse to get the data out. | ||
The following article: https://www.vimalin.com/blog/what-you-should-know-about-vmwares-experimental-vtpm/ has the technical background on what happens if you have used this experimental feature and is good background knowledge if you try to start trying to recover your VM. | |||
=== Here's one solution where you have a few manual steps === | === Here's one solution where you have a few manual steps === | ||
| Line 35: | Line 37: | ||
That ''should'' be all. | That ''should'' be all. | ||
One final note is that it is highly recommended to never touch your original VM and instead work with copies of the data while you try to get your VM back up and running. That way if you make a mistake you can just redo the steps. Otherwise you might introduce more problems and who needs yet another problem? | |||