You are the hero. I had a second VM drive that I had installed to be sure Taho had not completely broken Fusion and I was able to copy those three files and it opened the broken VM. Can't figure out how those file deleted but I will make a backup to recover better in the future. Thanks again
Original Message:
Sent: Aug 11, 2025 02:27 PM
From: Technogeezer
Subject: Updated M2 Macbook Air to Tahoo now Fusion can't open VM
First, Tahoe isn't a supported macOS version for Fusion 13.6.4. You run Fusion on Tahoe at your own risk.
The log is saying
2025-08-11T15:11:44.738Z In(05) vmx OBJLIB-FILEBE : FileBEOpen: can't open '/Users/charlesjohnson/Virtual Machines.localized/Windows 11 64-bit Arm.vmwarevm/Virtual Disk-s012.vmdk' : Could not find the file (393218).2025-08-11T15:11:44.738Z In(05) vmx DISKLIB-SPARSE: "/Users/charlesjohnson/Virtual Machines.localized/Windows 11 64-bit Arm.vmwarevm/Virtual Disk-s012.vmdk" : failed to open (25): ObjLib_Open failed2025-08-11T15:11:44.738Z Er(02) vmx DISKLIB-LINK : DiskLinkOpen: Failed to open '/Users/charlesjohnson/Virtual Machines.localized/Windows 11 64-bit Arm.vmwarevm/Virtual Disk.vmdk': : The system cannot find the file specified
Something deleted several pieces of your virtual disk from your hard drive. In particular the files Virtual Disk-s012.vmdk, Virtual Disk-s013.vmdk, and Virtual Disk-s014.vmdk are missing.
If you are running a third-party antivirus software on this Mac, check to see that those files were not put into quarantine. If they were, restore them from quarantine.
I hope you have a backup of this VM. I do not recommend trying to restore individual pieces of a vmdk file from a backup. Instead you should be looking at restoring the entire VM. I would first make sure that all the vmdk pieces are contained in the backup. If the backup looks OK, , copy the existing VM in its current state to a new location and then restore the entire VM from the backup copy. .
If those files aren't available, it may be possible to repair this VM. Beware that trying to repair a broken virtual disk may result in a loss of data from the missing VMDK files. @a_p_ can you weigh in on this?
------------------------------
- Paul (technogeezer)
vExpert 2025
Original Message:
Sent: Aug 11, 2025 02:05 PM
From: Charles Johnson
Subject: Updated M2 Macbook Air to Tahoo now Fusion can't open VM
Attached is the requested information. Thanks for your assistance. I did delete application cache files including VMWare Fusion cache after installing Tahoo. Maybe that is a potential cause.
------------------------------
Charles
Original Message:
Sent: Aug 11, 2025 01:08 PM
From: Technogeezer
Subject: Updated M2 Macbook Air to Tahoo now Fusion can't open VM
Open the Terminal and issue the following command to get a file listing of the file s contained in the VM (not a screen shot):
ls -alR "/Users/charlesjohnson/Virtual Machines.localized/Windows 11 64-bit Arm.vmwarevm/Virtual Disk.vmdk" > vm-file-list.txt
Also please collect the files with a .log extension found in the /Users/charlesjohnson/Virtual Machines.localized/Windows 11 64-bit Arm.vmwarevm folder, and zip them up.
Attach the vm-file-list.txt file and the zip file containing the log files to a reply to this thread. Those files may give us an idea of what might be happening.
------------------------------
- Paul (technogeezer)
vExpert 2025
Original Message:
Sent: Aug 11, 2025 11:15 AM
From: Charles Johnson
Subject: Updated M2 Macbook Air to Tahoo now Fusion can't open VM
When I try to open existing VM I receive -
File not found: /Users/charlesjohnson/Virtual Machines.localized/Windows 11 64-bit Arm.vmwarevm/Virtual Disk.vmdk
I then select .vmdk file see attachments for list of files in VM
Then I receive
VMware Fusion cannot find the virtual disk "/Users/charlesjohnson/Virtual Machines.localized/Windows 11 64-bit Arm.vmwarevm/Virtual Disk.vmdk"
Verify the path is valid and try again.
The system cannot find the file specified
Cannot open the disk '/Users/charlesjohnson/Virtual Machines.localized/Windows 11 64-bit Arm.vmwarevm/Virtual Disk.vmdk' or one of the snapshot disks it depends on.
Module 'Disk' power on failed.
Failed to start the virtual machine
I've tried deleting .lnc folder and no change
Thanks for ideas
------------------------------
Charles
------------------------------