VMware Communities
WhiteKnight
Hot Shot
Hot Shot

Encryption failed - NEED HELP !!!!

Trying to encrypt one of my virtual machines I got this error message:

Encryption.png

Now my VM is a mess and I don't have a backup !!!

What's that crap?!? Why is this happening? Why isn't VMware Workstation restoring the virtual machine to a consistent, functional state when showing this error message?

What to I need to do to get this VM back running? And what to I need to do to avoid this bloody error?



[VMware]: Workstation 17 Pro; --
[host]: Windows 10x64 host; --
[guests]: Windows 10x64, Windows 8x64.
0 Kudos
13 Replies
Super_Kevin
Contributor
Contributor

Hi WhiteKnight,

I am really sorry about this. Could you post the file list of your VM directory?

You can use the Command Prompt, "cd" to your VM directory and type "dir".

0 Kudos
HiJackson
Contributor
Contributor

Could you please provide workstation log files to us?That will be helpful to investigate the problem ASAP!

0 Kudos
WhiteKnight
Hot Shot
Hot Shot

Hi Kevin, thanks for helping me on this issue.

Attached please find the file list you requested.

Best regards,

Axel



[VMware]: Workstation 17 Pro; --
[host]: Windows 10x64 host; --
[guests]: Windows 10x64, Windows 8x64.
0 Kudos
WhiteKnight
Hot Shot
Hot Shot

Hi Jackson,

thanks for trying to help me on this issue.

Do you mean the VM's log files? Or are there others? Where would they be?

Thanks,

Axel



[VMware]: Workstation 17 Pro; --
[host]: Windows 10x64 host; --
[guests]: Windows 10x64, Windows 8x64.
0 Kudos
HiJackson
Contributor
Contributor

WS_LogFolder.jpg

0 Kudos
WhiteKnight
Hot Shot
Hot Shot

HiJackson

I just sent you a private message with the log's contents.

I used a PM because I fear there's sensitive data included in the logs.



[VMware]: Workstation 17 Pro; --
[host]: Windows 10x64 host; --
[guests]: Windows 10x64, Windows 8x64.
0 Kudos
HiJackson
Contributor
Contributor

Based on the info in the log file:

2018-11-21T13:33:26.717+01:00| vmui| W115: VMCryptoVMDB::Encrypt: Failed to validate the current crypto state of the virtual machine: Dictionary problem

2018-11-21T13:33:26.717+01:00| vmui| I125: DlgUI: This virtual machine is in an inconsistent state.

2018-11-21T13:33:26.717+01:00| vmui| I125+ Its configuration file is unencrypted but at least one of its components is already encrypted. Check to make sure it is not using a disk from an encrypted virtual machine.

So the problem should be the validation before real encryption was failed when trying to loading config file to dictionary.

You may want to check the config file or send us the config file to us.

BR,

Yinghua CHEN

0 Kudos
HiJackson
Contributor
Contributor

Further error found when loading config to Dictionary:

2018-11-21T13:32:20.092+01:00| vmui| I125: DictionaryLoad: Cannot open file "C:\Users\dahmena\AppData\Roaming\VMware\config.ini": Unknown error 2 (0x2).

2018-11-21T13:32:20.092+01:00| vmui| I125: [msg.dictionary.load.openFailed] Cannot open file "C:\Users\dahmena\AppData\Roaming\VMware\config.ini": Unknown error 2 (0x2).

2018-11-21T13:32:20.092+01:00| vmui| I125: PREF Optional preferences file not found at C:\Users\dahmena\AppData\Roaming\VMware\config.ini. Using default values.

SO please check config file: C:\Users\dahmena\AppData\Roaming\VMware\config.ini

BR,

Yinghua CHEN

0 Kudos
continuum
Immortal
Immortal

Hi
if a VM is in such a dubious state the first thing I would check is wether the vmdk files are already encrypted.
If not just, discard the vmx-file and recreate one from scratch using the existing vmdks.


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
HiJackson
Contributor
Contributor

Please also do backp the vmx-file before discard it to avoid more problems!

0 Kudos
WhiteKnight
Hot Shot
Hot Shot

I did a backup right after the error occured.

I won't be at the office until Tuesday. I'll try all the suggestions as soon as I'll be back then.

BTW: The VM seems to run in this state, but I cannot encrypt it or remove encryption, so I cannot apply a TTL.



[VMware]: Workstation 17 Pro; --
[host]: Windows 10x64 host; --
[guests]: Windows 10x64, Windows 8x64.
0 Kudos
WhiteKnight
Hot Shot
Hot Shot

There is no config.ini file in this directory (this is by default):

no Config.ini.png

continuum​: I just sent you a PM with the VMX file's content. I don't find any encrypted part in there. But when I remove the 'dataFileKey = "type=key:cipher=AES-256:key= ...' line, I cannot start the VM. Workstation is telling me then that there's a "dictionary problem" with the configuration file.



[VMware]: Workstation 17 Pro; --
[host]: Windows 10x64 host; --
[guests]: Windows 10x64, Windows 8x64.
0 Kudos
WhiteKnight
Hot Shot
Hot Shot

Any news on this?

VMware, can you please make sure this situation won't ever happen again?



[VMware]: Workstation 17 Pro; --
[host]: Windows 10x64 host; --
[guests]: Windows 10x64, Windows 8x64.
0 Kudos