VMware Fusion Pro 13 - Windows 11 nt opening after upgrade to MAC OS 14 (Sonoma)

[rvittori]

I can no longer open my Windows 11 VM after upgrading to Somoma. I have uninstalled Fusion Pro 13 completely and reinstalled and still have the same problem.  I tried posting with some log information but it gets tagged as spam. Can anyone help? Has anyone had the same issue? I am on an 2020 Intel Mac with an i5 processor. 

[rvittori]

Attaching a log file. 

[rvittori]

I just tried the VMWare Tech Fusion Preview and it also does not work.

[Technogeezer]

Please zip up and attach the entire contents of the vmware.log and the mksSandbox.log files found in the VM's bundle folder.

Snippets of the log file don't tell the entire story.

[Technogeezer]

Also,

Shut down Fusion, then try running the script found in https://communities.vmware.com/t5/VMware-Fusion-Documents/Script-to-check-if-all-remnants-of-VMware-... Remove all the files it shows to completely uninstall Fusion from your Mac.

Then re-install Fusion 13. 

[Technogeezer]

Another thought. If you're running the Windows VM with Unity, turn it off.

Unity is an abomination of a feature that causes more problems that it solves. (Are you listening VMware???).

[rvittori]

I never use Unity so that is always off. I'm working on your other suggestions now. Thanks for the assistance. 

[rvittori]

Here is the VMWare Log. Please let me know if this is correct. I am still looking for the mks logs.

[rvittori]

Just deleted VMWare fusion and used the script to ensure all VMWare files have been removed and also rebooted the Mac after wards. 

Will check the script again for left over files just in case. Next step will be to download Fusion Pro 13.0.2 and reinstall in hopes this will work. 

[rvittori]

After the removal, reboots, download and reinstall. Still the same issues. 

[Technogeezer]

Could you also zip up the  log files that are found in the VM bundle. Here's how to get them:

Find the VM in the Finder ( should have a .vmwarevm extension).

Right click on it, and select Show Package Contents. 

You will then see all of the files that make up your VM. 

Zip up the vmware*.log files and the mksSandbox*.log files and attach them to a reply in this thread. 

[rvittori]

Here are the files. Thank you so much for the directions and thank you for trying to help. 

[Technogeezer]

The mks component of Fusion is crashing for some reason. One thing I can see is that you have 3D support enabled. Can you try disabling it in the VM and see if it helps things? (There's a similar issue reported with VMware Workstation, and it seems that disabling 3D acceleration was a workaround).

[rvittori]

I disabled 3D Acceleration. That did not help.  I also switch Retina support off. That did not help either. O attached the VM logs and mks logs from the recent attempts. 

Thanks again.

[wila]

Hi,

I saw "remote shutdown" mentioned in the mks logs, not sure if that's a crash.
One thing I do notice however that you have a lot of devices connected to your mac and that the vmware.log stops right in the middle of enumerating those.
Can you try booting the VM after disconnecting every device from your mac?

--
Wil

[rvittori]

There are only two devices attached to the Mac. A super drive and external drive unless you count the wireless mouse and key board. There is nothing else. I disconnected the two drives rebooted the Mac and had the same results. 

[wila]

Hi,

The last lines in most of your logs are looking like:

2023-10-12T03:48:00.487Z In(05) vmx VUsbUpdateVigorFieldsAndAutoconnect: New set of 3 USB devices
2023-10-12T03:48:00.487Z In(05) vmx USB: Found device [name:Robert's\ Time\ Machine\ Backup\ (LaCie\ Mobile\ Drive) vid:059f pid:10bc path:0/2 speed:super family:storage,storage-bulk serialnum:00000000NL6F575X arbRuntimeKey:3 version:5]
2023-10-12T03:48:00.487Z In(05) vmx USB: Found device [name:Apple\ MacBook\ Air\ SuperDrive vid:05ac pid:1500 path:65/4 speed:high family:storage,storage-bulk serialnum:KZ8DBR44219\ \ \ \ \ \ \ \ \ arbRuntimeKey:2 quirks:needs-boot-camp version:5]
2023-10-12T03:48:00.487Z In(05) vmx USB: Found device [name:Virtual\ Bluetooth\ Adapter vid:0e0f pid:0008 speed:full family:wireless,bluetooth virtPath:usb_xhci:5 deviceType:virtual-bluetooth info:0000001 version:5], connected to usb_xhci port 5.

So yes.  I do count the wireless mouse & keyboard as one of the suspects.

--
Wil

[rvittori]

I can wire the keyboard but I do not have a wired mouse to use. It also renders the Mac and Windows VM useless if I can't use a mouse.  I am not sure where to go here. 

I will try disconnecting the drives and wiring the keyboard and see what happens. I need to leave the mouse connected to be able to start VMware. 

I do appreciate folks trying to help. Thanks. 

[rvittori]

With everything disconnected except the wireless mouse and a wired keyboard. Same results. 

[wila]

Hi,

I thought I saw "macbook air" in the log somewhere. That must have been a relic of something else then.
The hardware itself is a normal mac? Not something else? The CPU itself also appears to suggest that it's fairly recent otherwise my next question would be if the host is running OLPC or something else to get Sonoma running on unsupported hardware.

For the rest I'm running out of ideas with the current information that we have, sorry.
In your case I would probably try a fresh install of Sonoma, but that's me.

--
Wil