The SW in case is:
VMware Workstation 15 Pro. Version 15.1.0 build-13591040.
The host OS in both cases is 64-bit Windows 10. The guest OS is 64-bit Windows 7.
I want to copy a Virtual Machine from one computer to another. I copy the whole directory containing all the files (at least that is what I thought).
I can open the virtual machine but when I try to power the machine up I get these error messages:
"VMware Workstation cannot find the virtual disk "C:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-0.vmdk". Verify the path is valid and try again.
The system cannot find the file specified
Cannot open the disk 'C:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-0.vmdk' or one of the snapshot disks it depends on.
Module 'Disk' power on failed.
Failed to start the virtual machine."
I have tried to pick both "copied" and "moved" but with the same result.
KALAE1VMWin7-0.vmdk specifies a physical disk - is that physical device still available ?
Do you start WS with elevated rights - use right click "run as admin"
Please attach KALAE1VMWin7-0.vmdk to your next reply.
And ? - does the file "C:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-0.vmdk" exist ?
Yes it does.
KALAE1VMWin7 is the folder I have copied containing (as far as I know) the full virtual machine.
The files in the folder is:
c:\Tools\VM-ware maskiner\KALAE1VMWin7\caches\ <DIR> 22-06-2019 23:46 ----
c:\Tools\VM-ware maskiner\KALAE1VMWin7\vmware-2.log 514.285 22-06-2019 18:09 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\vmware-1.log 382.192 22-06-2019 21:15 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\vmware-0.log 375.880 22-06-2019 21:38 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\vmware.log 67.103 26-06-2019 08:53 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-s034.vmdk 524.288 22-06-2019 12:29 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-s033.vmdk 589.824 09-06-2019 11:42 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-s032.vmdk 589.824 09-06-2019 11:42 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-s031.vmdk 589.824 09-06-2019 11:42 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-s030.vmdk 589.824 09-06-2019 11:42 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-s029.vmdk 589.824 09-06-2019 11:42 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-s028.vmdk 589.824 09-06-2019 11:42 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-s027.vmdk 589.824 09-06-2019 11:42 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-s026.vmdk 589.824 09-06-2019 11:42 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-s025.vmdk 589.824 09-06-2019 11:42 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-s024.vmdk 327.680 22-06-2019 12:29 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-s023.vmdk 524.288 05-06-2019 09:52 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-s022.vmdk 524.288 05-06-2019 09:52 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-s021.vmdk 524.288 05-06-2019 09:52 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-s020.vmdk 524.288 05-06-2019 09:52 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-s019.vmdk 524.288 05-06-2019 09:52 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-s018.vmdk 1.140.523.008 22-06-2019 21:38 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-s017.vmdk 524.288 05-06-2019 09:52 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-s016.vmdk 65.536 22-06-2019 12:29 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-s015.vmdk 524.288 09-05-2019 13:04 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-s014.vmdk 524.288 09-05-2019 13:04 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-s013.vmdk 524.288 22-06-2019 12:29 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-s012.vmdk 524.288 22-06-2019 12:29 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-s011.vmdk 997.785.600 22-06-2019 21:38 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-s010.vmdk 2.089.484.288 22-06-2019 21:38 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-s009.vmdk 3.672.899.584 22-06-2019 21:38 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-s008.vmdk 2.895.380.480 22-06-2019 21:38 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-s007.vmdk 2.311.847.936 22-06-2019 21:38 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-s006.vmdk 3.922.853.888 22-06-2019 21:38 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-s005.vmdk 3.303.931.904 22-06-2019 21:38 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-s004.vmdk 1.655.701.504 22-06-2019 21:38 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-s003.vmdk 2.050.424.832 22-06-2019 21:38 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-s002.vmdk 4.227.399.680 22-06-2019 21:38 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-s001.vmdk 4.180.475.904 22-06-2019 21:38 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-0-pt.vmdk 64.512 18-06-2019 13:13 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7-0.vmdk 1.011 22-06-2019 21:34 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7.vmxf 3.603 15-05-2019 10:54 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7.vmx 3.955 26-06-2019 08:53 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7.vmsd 0 09-05-2019 13:04 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7.vmdk 1.949 22-06-2019 21:34 -a--
c:\Tools\VM-ware maskiner\KALAE1VMWin7\KALAE1VMWin7.nvram 8.684 22-06-2019 18:09 -a--
KALAE1VMWin7-0.vmdk specifies a physical disk - is that physical device still available ?
Do you start WS with elevated rights - use right click "run as admin"
Please attach KALAE1VMWin7-0.vmdk to your next reply.
If you specify a VMDK that is not available - for whatever reasons - the VM will not start.
Thats basically what the message says.
So your next step should be obvious
After I deleted the attempt to map a partition that is no longer available the VM-ware machine can start.
Thank you very much for the help - I am not sure how I can mark this thread as "solved"?
> I am not sure how I can mark this thread as "solved"?
You already marked my answer as correct - that basically means you consider your question to be solved.