VMware Player cant find .vmdk Files anymore

[Noah0302]

So I just upgraded my Win 10 machine from my Ryzen 2700 to a 3950x.

Testes everything, temps, Cinebench, if XMP is stable... no problems at all.

 

But when I wanted to start my Truenas VM, this error popped up:

 

I tested most solutions I found on Google, but those did not work. (Removing the .lck files, importing it as a new VM...)

 

Does anyone have an Idea what might be the solutions here?

[BloodKnight7]

have you tried creating a new vm and just attatching the old vmdk drives?

[Noah0302]

16 minutes ago, BloodKnight7 said:

have you tried creating a new vm and just attatching the old vmdk drives?

Yes, same error.
Cant find the path, no idea how this works

[aBattleBorn]

15 hours ago, Noah0302 said:

So I just upgraded my Win 10 machine from my Ryzen 2700 to a 3950x.

Testes everything, temps, Cinebench, if XMP is stable... no problems at all.

 

But when I wanted to start my Truenas VM, this error popped up:

 

I tested most solutions I found on Google, but those did not work. (Removing the .lck files, importing it as a new VM...)

 

Does anyone have an Idea what might be the solutions here?

do you have snpashoots? if you can delete them you should try it,this will reemerge the vdisk

[NelizMastr]

2 hours ago, aBattleBorn said:

do you have snpashoots? if you can delete them you should try it,this will reemerge the vdisk

This.

 

If this doesn't work, your VMDKs are corrupted. This cannot be caused by a CPU swap, so it might be something else. Also check if virtualization (SVM) is still enabled in the UEFI.

[Noah0302]

19 hours ago, aBattleBorn said:

do you have snpashoots? if you can delete them you should try it,this will reemerge the vdisk

Thanks, I will try

[Noah0302]

16 hours ago, NelizMastr said:

This.

 

If this doesn't work, your VMDKs are corrupted. This cannot be caused by a CPU swap, so it might be something else. Also check if virtualization (SVM) is still enabled in the UEFI.

I know, this does not make any kind of sense that it is caused by the swap. But the MSI Afterburner Profiles were also corrupted, so something must have happened to my Documents

 

Virtualization is on. I also had the same thought, but I created a new VM and it booted up and installed Win 10 nicely