Unable to recover Windows 11 vm (windows credentials)

[Jezbo]

Hi, 

I created a clone of a Windows 11 vm which was created with the "allow the password to be stored in credentials manager".

I moved the clone folder off the original drive so I could removed unwanted files on there and moved the clone folder back to the original drive.

Now I can't access it because it's asking for the password when I created this VM, even though i stored it in the host's credentials manager. Super frustrating. 

Anyway to gain access to this VM again? I can see there is an entry in hash which I'm assuming is the vm's password but unable to view it cause windows credential manger won't allow this. EDIT- This VM was created in the multiple files format.

Please help, thanks,

Jeremy

[wila]

Hi Jeremy,

The default is to partially encrypt the VM, which only encrypts the configuration files, not the actual data on the virtual disk(s).
So if you have kept the default settings then there's a reasonable chance on recovery.

Does the following help?
https://communities.vmware.com/t5/VMware-Workstation-Pro/Updated-Host-BIOS-Now-All-VM-ask-for-passwo...

--
Wil

[Jezbo]

Hi Wila,

Thanks so much for your response, I really appreciate it.

I'm not sure how to export the OVF file. I'll have a look around and see if someone has a step by step guide on this process and I will get back to you.

Thanks again,

Jeremy

[Jezbo]

Hi Wila,

Thanks so much for your response, I really appreciate it.

I'm not sure how to export the OVF file. I'll have a look around and see if someone has a step by step guide on this process and I will get back to you. EDIT - ok I see what it is to do, but the option is greyed out unfortunately

Thanks again,

Jeremy

[wila]

Jeremy,

I  don't have the time to run through these steps myself right now, as I have to run for an appointment. However, I wanted to let you know that there's a command line version of ovftool.
It would not surprise me if you had to do this via the command line anyways.

--
Wil

[Jezbo]

No problem I'm just looking into it now and I'll respond back with my findings.

Thanks,

Jeremy

[Jezbo]

So an update from the list time I responded. 

I wasn't able to gain access again to this VM. I tried multiple times to covert to OVF but unsuccessful, I think because it was a vhd split up over multiple vmdk's, it didn't like it. poduced a very small OVF file to work with. I tested the same procedure using a single vhd VM and the OVF convert tool worked as intended.

Gonna have to call this one and a fail. Fortunately, there wasn't anything super important on the original VM anyways that I can't live with out honestly.

I've attached a screnshot of the folder that the vm is stored in, hopefully makes a bit more sense in what I was up against.

[wila]

Hi,

Ok, the filelist looks fine. I suggested to use ovftool as it seemed like an easy way to get going, there are many ways... as long as the vmdk isn't encrypted.

Having the VMDK split up in multiple files is actually the recommended format and I strongly suggest to keep that for your other VM's.
Can you attach the file "Windows 11 x64-cl1.vmdk" to a reply here?

If that one isn't encrypted then you can also just create a new VM and point it to the old disk. Then choose "copy" (not "take away from existing VM") and you should have the VM back.

--
Wil