Impossible to launch Vmware Pro since Mac OS Sequoia

5. RE: Impossible to launch Vmware Pro since Mac OS Sequoia

Recommend

Didier Grob

Posted May 13, 2025 06:59 AM

Hello!

I've tried:

ls -alR "/Users/cabinet/Virtual Machines.localized/ARM Windows 11 64 bits.vmwarevm/Disque virtuel.vmdk.lck"

But the answer:

No such file or directory.

Always the same error...

Thanks to continue helping me.

Didier

Original Message

Original Message:
Sent: May 11, 2025 12:28 PM
From: Paul Rockwell
Subject: Impossible to launch Vmware Pro since Mac OS Sequoia

Here's what I see looking at the logs:

You are running on a Apple Silicon Mac, but have a virtual machine /Users/cabinet/Virtual Machines.localized/Windows 10. x64.vmwarevm. I examined the .vmx file of this VM and find it's a Windows x86_64 (Intel) VM. That will not run on an Apple Silicon Mac. You may wish to remove it to save disk space unless you're using it to transfer files to the new Windows 11 VM.

The listing of files from virtual machine /Users/cabinet/Virtual Machines.localized/ARM Windows 11 64 bits.vmwarevm has a lock directory Disque virtuel.vmdk.lck with a file dated from April 23 (23-Avril). That could prevent the VM from starting as Fusion thinks the virtual disk is in use.

Can you quit the Fusion GUI, open the Terminal app, and run the following command to verify that the lock folder is still present:

ls -alR "/Users/cabinet/Virtual Machines.localized/ARM Windows 11 64 bits.vmwarevm/Disque virtuel.vmdk.lck"

If that command indicates that the directory Disque Virtuel.vmdk.lck and a file located within it are present, then issue the following command in the Terminal app to remove the lock file:

rm -rf  "/Users/cabinet/Virtual Machines.localized/ARM Windows 11 64 bits.vmwarevm/Disque virtuel.vmdk.lck"

Then start the Fusion GUI and try to power on the VM.

------------------------------
- Paul (technogeezer)
vExpert 2025

Original Message:
Sent: May 09, 2025 11:31 AM
From: Technogeezer
Subject: Impossible to launch Vmware Pro since Mac OS Sequoia

Can you go to the Finder and open the Library folder in your account (you'll need to hold the Option key down while clicking on the Finder's Go menu in order to reveal the Library folder.

Then navigate to the Logs > VMware Fusion and zip up the files with a .log extension and staring with vmware-vmfusion. (alternatively if its easier you can right click on the VMware Fusion folder and select "Compress").

Attach that zip file to a reply to this thread. The logs might give us a clue to what is causing directory not empty error.

------------------------------
- Paul (technogeezer)
vExpert 2025

Original Message:
Sent: May 08, 2025 09:43 AM
From: Technogeezer
Subject: Impossible to launch Vmware Pro since Mac OS Sequoia

Did you power off the VM before upgrading macOS?

Try this.

Shut down the Fusion GUI.
Locate the VMs bundle folder from the Finder, right click on it, and select "Show Package Contents".
In the window that appears, see if there are any files or folders with a.lck extension. If there are, delete them and empty the Trash.
Now try to restart the VM

The message about the failure to resolve the updated server is expected. Broadcom now only provides in-product updates for products with an active subscription. As a result of this change in product updates are no longer available for Fusion or Workstation. At this time you need to look at Broadcom's software portal for any available Fusion updates and manually download and install them.

------------------------------
- Paul (technogeezer)
vExpert 2025

Original Message:
Sent: May 08, 2025 06:17 AM
From: Didier Grob
Subject: Impossible to launch Vmware Pro since Mac OS Sequoia

I've upgraded to Macos Sequoia 15.4.1 on my MacBook Pro M3 Max (before on Sonoma and anything was good).. I'm trying to run VMware Fusion Pro 13.6.3. Since I switched to Sequoia, I get an error message: Directory not empty Unable to open the disk '/Users/cabinet/Virtual Machines.localized/ARM Windows 11 64-bit.vmwarevm/VirtualDisk.vmdk' or any of the snapshot disks it depends on. Failure to activate the 'Disk' module. Failure to start the virtual machine

If I run an update search, I get the message: Unable to resolve the update server. Check your Internet settings or contact your system administrator.

Help! I urgently need to access some files!!

Didier Grob

6. RE: Impossible to launch Vmware Pro since Mac OS Sequoia

Recommend

External Moderator

Technogeezer

Posted May 13, 2025 11:23 AM

Didier,

I'm puzzled. According to the logs and the output you posted in the support bundle collection, this folder should exist.

Please post the output of the following command (copy and paste exactly as noted here):

ls -alR ~/Virtual\ Machines.localized/ARM*.vmwarevm

------------------------------
- Paul (technogeezer)
vExpert 2025
------------------------------

Original Message

Original Message:
Sent: May 13, 2025 06:58 AM
From: Didier Grob
Subject: Impossible to launch Vmware Pro since Mac OS Sequoia

Hello!

I've tried:

ls -alR "/Users/cabinet/Virtual Machines.localized/ARM Windows 11 64 bits.vmwarevm/Disque virtuel.vmdk.lck"

But the answer:

No such file or directory.

Always the same error...

Thanks to continue helping me.

Didier

Original Message:
Sent: May 11, 2025 12:28 PM
From: Paul Rockwell
Subject: Impossible to launch Vmware Pro since Mac OS Sequoia

Here's what I see looking at the logs:

You are running on a Apple Silicon Mac, but have a virtual machine /Users/cabinet/Virtual Machines.localized/Windows 10. x64.vmwarevm. I examined the .vmx file of this VM and find it's a Windows x86_64 (Intel) VM. That will not run on an Apple Silicon Mac. You may wish to remove it to save disk space unless you're using it to transfer files to the new Windows 11 VM.

The listing of files from virtual machine /Users/cabinet/Virtual Machines.localized/ARM Windows 11 64 bits.vmwarevm has a lock directory Disque virtuel.vmdk.lck with a file dated from April 23 (23-Avril). That could prevent the VM from starting as Fusion thinks the virtual disk is in use.

Can you quit the Fusion GUI, open the Terminal app, and run the following command to verify that the lock folder is still present:

ls -alR "/Users/cabinet/Virtual Machines.localized/ARM Windows 11 64 bits.vmwarevm/Disque virtuel.vmdk.lck"

If that command indicates that the directory Disque Virtuel.vmdk.lck and a file located within it are present, then issue the following command in the Terminal app to remove the lock file:

rm -rf  "/Users/cabinet/Virtual Machines.localized/ARM Windows 11 64 bits.vmwarevm/Disque virtuel.vmdk.lck"

Then start the Fusion GUI and try to power on the VM.

------------------------------
- Paul (technogeezer)
vExpert 2025

Original Message:
Sent: May 09, 2025 11:31 AM
From: Technogeezer
Subject: Impossible to launch Vmware Pro since Mac OS Sequoia

Can you go to the Finder and open the Library folder in your account (you'll need to hold the Option key down while clicking on the Finder's Go menu in order to reveal the Library folder.

Then navigate to the Logs > VMware Fusion and zip up the files with a .log extension and staring with vmware-vmfusion. (alternatively if its easier you can right click on the VMware Fusion folder and select "Compress").

Attach that zip file to a reply to this thread. The logs might give us a clue to what is causing directory not empty error.

------------------------------
- Paul (technogeezer)
vExpert 2025

Original Message:
Sent: May 08, 2025 09:43 AM
From: Technogeezer
Subject: Impossible to launch Vmware Pro since Mac OS Sequoia

Did you power off the VM before upgrading macOS?

Try this.

Shut down the Fusion GUI.
Locate the VMs bundle folder from the Finder, right click on it, and select "Show Package Contents".
In the window that appears, see if there are any files or folders with a.lck extension. If there are, delete them and empty the Trash.
Now try to restart the VM

The message about the failure to resolve the updated server is expected. Broadcom now only provides in-product updates for products with an active subscription. As a result of this change in product updates are no longer available for Fusion or Workstation. At this time you need to look at Broadcom's software portal for any available Fusion updates and manually download and install them.

------------------------------
- Paul (technogeezer)
vExpert 2025

Original Message:
Sent: May 08, 2025 06:17 AM
From: Didier Grob
Subject: Impossible to launch Vmware Pro since Mac OS Sequoia

I've upgraded to Macos Sequoia 15.4.1 on my MacBook Pro M3 Max (before on Sonoma and anything was good).. I'm trying to run VMware Fusion Pro 13.6.3. Since I switched to Sequoia, I get an error message: Directory not empty Unable to open the disk '/Users/cabinet/Virtual Machines.localized/ARM Windows 11 64-bit.vmwarevm/VirtualDisk.vmdk' or any of the snapshot disks it depends on. Failure to activate the 'Disk' module. Failure to start the virtual machine

If I run an update search, I get the message: Unable to resolve the update server. Check your Internet settings or contact your system administrator.

Help! I urgently need to access some files!!

Didier Grob

7. RE: Impossible to launch Vmware Pro since Mac OS Sequoia

Recommend

Didier Grob

Posted May 13, 2025 11:26 AM

Here the result:

.com/kb/HT208050.

MacBook-Pro:~ cabinet$ ls -alR ~/Virtual\ Machines.localized/ARM*.vmwarevm

total 120945680

drwxr-xr-x@ 40 cabinet staff 1280 13 mai 12:54 .

drwxr-xr-x@ 8 cabinet staff 256 13 mai 12:54 ..

-rw-r--r-- 1 cabinet staff 19198 13 mai 12:54 ARM Windows 11 64 bits-0.scoreboard

-rw-r--r-- 1 cabinet staff 19198 9 mai 18:25 ARM Windows 11 64 bits-1.scoreboard

-rw-r--r-- 1 cabinet staff 19198 9 mai 12:13 ARM Windows 11 64 bits-2.scoreboard

-rw------- 1 cabinet staff 2408448 9 mai 11:43 ARM Windows 11 64 bits.nvram

-rw-r--r-- 1 cabinet staff 832 9 mai 12:11 ARM Windows 11 64 bits.plist

-rw-r--r-- 1 cabinet staff 19198 13 mai 12:54 ARM Windows 11 64 bits.scoreboard

-rw-r--r-- 1 cabinet staff 20 20 août 2024 ARM Windows 11 64 bits.vmsd

-rwxr-xr-x 1 cabinet staff 5226 13 mai 12:54 ARM Windows 11 64 bits.vmx

drwxrwxrwx 3 cabinet staff 96 13 mai 12:54 ARM Windows 11 64 bits.vmx.lck

-rw-r--r-- 1 cabinet staff 1101 21 août 2024 ARM Windows 11 64 bits.vmxf

-rw------- 1 cabinet staff 4188340224 23 avr. 18:49 Disque virtuel-s001.vmdk

-rw------- 1 cabinet staff 4261937152 23 avr. 18:49 Disque virtuel-s002.vmdk

-rw------- 1 cabinet staff 4261937152 23 avr. 18:49 Disque virtuel-s003.vmdk

-rw------- 1 cabinet staff 4261937152 23 avr. 18:49 Disque virtuel-s004.vmdk

-rw------- 1 cabinet staff 4261937152 23 avr. 18:49 Disque virtuel-s005.vmdk

-rw------- 1 cabinet staff 4261937152 23 avr. 18:49 Disque virtuel-s006.vmdk

-rw------- 1 cabinet staff 4261937152 23 avr. 18:49 Disque virtuel-s007.vmdk

-rw------- 1 cabinet staff 4195614720 23 avr. 18:49 Disque virtuel-s008.vmdk

-rw------- 1 cabinet staff 4261937152 23 avr. 18:49 Disque virtuel-s009.vmdk

-rw------- 1 cabinet staff 4261937152 23 avr. 18:43 Disque virtuel-s010.vmdk

-rw------- 1 cabinet staff 4261937152 10 avr. 10:34 Disque virtuel-s011.vmdk

-rw------- 1 cabinet staff 4261937152 23 avr. 18:48 Disque virtuel-s012.vmdk

-rw------- 1 cabinet staff 4261937152 23 avr. 18:49 Disque virtuel-s013.vmdk

-rw------- 1 cabinet staff 3322281984 23 avr. 18:41 Disque virtuel-s014.vmdk

-rw------- 1 cabinet staff 2324234240 15 janv. 13:56 Disque virtuel-s015.vmdk

-rw------- 1 cabinet staff 499843072 23 avr. 18:42 Disque virtuel-s016.vmdk

-rw------- 1 cabinet staff 509476864 15 janv. 00:40 Disque virtuel-s017.vmdk

-rw------- 1 cabinet staff 1245 23 avr. 18:41 Disque virtuel.vmdk

drwxrwxrwx 3 cabinet staff 96 13 mai 12:54 Disque virtuel.vmdk.lck

-rw-r----- 1 cabinet staff 25131 13 mai 12:54 mksSandbox-0.log

-rw-r----- 1 cabinet staff 25131 9 mai 18:25 mksSandbox-1.log

-rw-r----- 1 cabinet staff 25128 9 mai 12:13 mksSandbox-2.log

-rw-r----- 1 cabinet staff 25131 13 mai 12:54 mksSandbox.log

-rw-r--r-- 1 cabinet staff 848 13 mai 12:53 startMenu.plist

-rw-r--r-- 1 cabinet staff 84638 13 mai 12:54 vmware-0.log

-rw-r--r-- 1 cabinet staff 83908 9 mai 18:25 vmware-1.log

-rw-r--r-- 1 cabinet staff 84017 9 mai 12:13 vmware-2.log

-rw-r--r-- 1 cabinet staff 83706 13 mai 12:54 vmware.log

/Users/cabinet/Virtual Machines.localized/ARM Windows 11 64 bits.vmwarevm/ARM Windows 11 64 bits.vmx.lck:

total 8

drwxrwxrwx 3 cabinet staff 96 13 mai 12:54 .

drwxr-xr-x@ 40 cabinet staff 1280 13 mai 12:54 ..

-rw-r--r-- 1 cabinet staff 512 13 mai 12:54 M10903.lck

/Users/cabinet/Virtual Machines.localized/ARM Windows 11 64 bits.vmwarevm/Disque virtuel.vmdk.lck:

total 8

drwxrwxrwx 3 cabinet staff 96 13 mai 12:54 .

drwxr-xr-x@ 40 cabinet staff 1280 13 mai 12:54 ..

-rw-r--r-- 1 cabinet staff 512 23 avr. 18:41 M56500.lck

Thanks

Didier

Original Message

Original Message:
Sent: May 13, 2025 11:23 AM
From: Paul Rockwell
Subject: Impossible to launch Vmware Pro since Mac OS Sequoia

Didier,

I'm puzzled. According to the logs and the output you posted in the support bundle collection, this folder should exist.

Please post the output of the following command (copy and paste exactly as noted here):

ls -alR ~/Virtual\ Machines.localized/ARM*.vmwarevm

------------------------------
- Paul (technogeezer)
vExpert 2025

Original Message:
Sent: May 13, 2025 06:58 AM
From: Didier Grob
Subject: Impossible to launch Vmware Pro since Mac OS Sequoia

Hello!

I've tried:

ls -alR "/Users/cabinet/Virtual Machines.localized/ARM Windows 11 64 bits.vmwarevm/Disque virtuel.vmdk.lck"

But the answer:

No such file or directory.

Always the same error...

Thanks to continue helping me.

Didier

Original Message:
Sent: May 11, 2025 12:28 PM
From: Paul Rockwell
Subject: Impossible to launch Vmware Pro since Mac OS Sequoia

Here's what I see looking at the logs:

You are running on a Apple Silicon Mac, but have a virtual machine /Users/cabinet/Virtual Machines.localized/Windows 10. x64.vmwarevm. I examined the .vmx file of this VM and find it's a Windows x86_64 (Intel) VM. That will not run on an Apple Silicon Mac. You may wish to remove it to save disk space unless you're using it to transfer files to the new Windows 11 VM.

The listing of files from virtual machine /Users/cabinet/Virtual Machines.localized/ARM Windows 11 64 bits.vmwarevm has a lock directory Disque virtuel.vmdk.lck with a file dated from April 23 (23-Avril). That could prevent the VM from starting as Fusion thinks the virtual disk is in use.

Can you quit the Fusion GUI, open the Terminal app, and run the following command to verify that the lock folder is still present:

ls -alR "/Users/cabinet/Virtual Machines.localized/ARM Windows 11 64 bits.vmwarevm/Disque virtuel.vmdk.lck"

If that command indicates that the directory Disque Virtuel.vmdk.lck and a file located within it are present, then issue the following command in the Terminal app to remove the lock file:

rm -rf  "/Users/cabinet/Virtual Machines.localized/ARM Windows 11 64 bits.vmwarevm/Disque virtuel.vmdk.lck"

Then start the Fusion GUI and try to power on the VM.

------------------------------
- Paul (technogeezer)
vExpert 2025

Original Message:
Sent: May 09, 2025 11:31 AM
From: Technogeezer
Subject: Impossible to launch Vmware Pro since Mac OS Sequoia

Can you go to the Finder and open the Library folder in your account (you'll need to hold the Option key down while clicking on the Finder's Go menu in order to reveal the Library folder.

Then navigate to the Logs > VMware Fusion and zip up the files with a .log extension and staring with vmware-vmfusion. (alternatively if its easier you can right click on the VMware Fusion folder and select "Compress").

Attach that zip file to a reply to this thread. The logs might give us a clue to what is causing directory not empty error.

------------------------------
- Paul (technogeezer)
vExpert 2025

Original Message:
Sent: May 08, 2025 09:43 AM
From: Technogeezer
Subject: Impossible to launch Vmware Pro since Mac OS Sequoia

Did you power off the VM before upgrading macOS?

Try this.

Shut down the Fusion GUI.
Locate the VMs bundle folder from the Finder, right click on it, and select "Show Package Contents".
In the window that appears, see if there are any files or folders with a.lck extension. If there are, delete them and empty the Trash.
Now try to restart the VM

The message about the failure to resolve the updated server is expected. Broadcom now only provides in-product updates for products with an active subscription. As a result of this change in product updates are no longer available for Fusion or Workstation. At this time you need to look at Broadcom's software portal for any available Fusion updates and manually download and install them.

------------------------------
- Paul (technogeezer)
vExpert 2025

Original Message:
Sent: May 08, 2025 06:17 AM
From: Didier Grob
Subject: Impossible to launch Vmware Pro since Mac OS Sequoia

I've upgraded to Macos Sequoia 15.4.1 on my MacBook Pro M3 Max (before on Sonoma and anything was good).. I'm trying to run VMware Fusion Pro 13.6.3. Since I switched to Sequoia, I get an error message: Directory not empty Unable to open the disk '/Users/cabinet/Virtual Machines.localized/ARM Windows 11 64-bit.vmwarevm/VirtualDisk.vmdk' or any of the snapshot disks it depends on. Failure to activate the 'Disk' module. Failure to start the virtual machine

If I run an update search, I get the message: Unable to resolve the update server. Check your Internet settings or contact your system administrator.

Help! I urgently need to access some files!!

Didier Grob

8. RE: Impossible to launch Vmware Pro since Mac OS Sequoia

Recommend

External Moderator

Technogeezer

Posted May 13, 2025 11:44 AM

Thanks.

The lock folder and file dated from 23-avr is still there.

Shut down the Fusion GUI. From the menu bar VMware Fusion > Quit VMware Fusion.

(please post the output of the commands that I'm going to tell you to run)

Issue the following command again to display the files that make up the virtual machine with Fusion totally shut down.

ls -alR ~/Virtual\ Machines.localized/ARM*.vmwarevm

You should see the Disque virtuel.vmdk.lck folder with a file M56500.lck within it.

Now remove the lock folder:

rm -rf ~/Virtual\ Machines.localized/ARM*.vmwarevm/Disque\ virtuel.vmdk.lck

Then re-run the file listing to make sure the lock folder is deleted.

ls -alR ~/Virtual\ Machines.localized/ARM*.vmwarevm

------------------------------
- Paul (technogeezer)
vExpert 2025
------------------------------

Original Message

Original Message:
Sent: May 13, 2025 11:26 AM
From: Didier Grob
Subject: Impossible to launch Vmware Pro since Mac OS Sequoia