OMG, this is so frustrating and I can't get any work done because Im running a windows (only) base program on my MB pro... Can you please help me try and resolve this
I have the highest spec 2015 MB Pro, Im running Fusion 12 pro. It worked perfect up until I stupidly installed Big Sur. Now when I click the VM logo to run the program it just simply does the spinning ball and goes no further. If I right click the icon it states "program not responding". The only thing I can do is "force quit" There is nothing I can do to open the program to go to settings in VM Fusion to make those changes stated in another post as I cannot open the program.
Is there something I need to change in my MAC settings to allow it to open so I can progress? Ive even tried reinstalling the software but nothing, still the same, the program will not open.
Is that something that can be done in terminal? and does anyone know the exact commands, as I haven't got a clue what Im doing with that, but can copy and paste stuff.... Thats how desperate I am for the solution to this!!
Can anyone please, please please help me as I really don't know how to resolve this and about to lose work if I don't get it running again.
Thank you
Les
Les
Hi Les,
@les1466 wrote:
Now when I click the VM logo to run the program it just simply does the sinning ball and goes no further. If I right click the icon it states "program not responding".
Les
I don't know what you are clicking, is it an icon in the dock? If so then it might be an old "VM logo" from a removed or relocated copy?
Have you tried starting VMware Fusion from the Applications folder in Finder?
PS: I have removed your other duplicate post. It is better to have its own topic and have the problem debated in one spot instead of spread out over multiple threads. Sorry for the trouble.
--
Wil
hi, thanks fo your reply.
Yes, I have completely removed it, clicked the logo from the applications folder, still nothing.
When trying to reinstall, Ive clicked the install button, put my password in and allowed the setup, it then looks like its loading, does the spinning ball again say, "application not responding".
I then have to force quit. I cannot get past this stage.
When I was installing Big Sur, I may of had VM wear open in the beck ground, although I would assume that this would of been closed by the MB when it was restarting to install. I genuinely have no clue what to do. My time machine will not go back to pre Big Sur and I really dont want to wipe my mac and start again as all my work stuff is on there and I had to do that and spent days getting it back to normal after issues with VM Ware then. Is there something I can send you so you can see what is happening?
Thanks
Les
OMG, it shown that the program wasn't responding and it was just left on in the background.
All of a sudden, and this freaked me out... It just started working again... WTF!!! Obviously I'm elated but, why after me working on the MB doing something totally unrelated , did it decide it wanted to start working.... Now Im frightened if it goes off that I may lose it again, so am backing all my precious files up.
Anyway, try this, if you've had exactly the same experience as me and cannot, no matter what, get VM Fusion to run.... Just leave it turned on and do other stuff on your computer... For some ridiculous reason, for which I am totally clueless ![]()
![]()
![]()
![]()
, It might just start working on its own.
Fingers crossed for you's ![]()
Thank you for your reply
Les
Hi,
Now that it works .. can you attach a support Bundle? (it's under the Help menu)
Perhaps that can shine a light on what happened.
Backups are always a good thing to have (Please do not depend on Time Machine for backing up the VM itself, see also my article here: https://www.vimalin.com/why-is-time-machine-not-a-good-backup-for-virtual-machines/ )
--
Wil
Where is the virtual machine itself, on the internal drive or an external one? What's the guest configuration? It could simply be either an I/O bottleneck, or that the host is starved for resources.
It was on the main mb hard drive.
haven’t a clue why, it’s just working, I’m so happy
![]()
I have been having the same issue how ever I am still not able to get it to work even after leaving it in the state of not responding for a number of hours. I have had this happen multiple times - I have done a clean install and after a few days it will occur again. Any one of any thoughts
I encountered the same issue.
I was using VMware Professional Version 12.1.0 (17195230) and then upgraded to Mac OS Big Sur version 11.2.1. Once I upgraded, VMware appeared as if would not start anymore, the process was highlighted in the Activity Monitor as "Not Responding"
Hardware Overview:
Model Name: MacBook Pro
Model Identifier: MacBookPro11,5
Processor Name: Quad-Core Intel Core i7
Processor Speed: 2.8 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 6 MB
Hyper-Threading Technology: Enabled
Memory: 16 GB
System Firmware Version: 426.0.0.0.0
Solution
It appears that the trick is to do absolutely nothing, but wait. In my case, after about 25 minutes, the VMware became responsive once again. Very strange. Hope this helps.
One other thing that I did was to temporarily remove all of the images that I had from the /Users/${name}/Documents/Virtual Machines/ directory before I tried to restart VMware. Once, VMware was back in action, I moved them back in again. I'm not sure if that will make any difference, that's just one of the steps I took.
I am having the same issue - with the VMware Fusion v 12.1.0 application itself failing to launch - with the spinning beach ball and not responding.
I have let it run for hours on a MacBook Pro 2019 8-core i9.
I have been looking closely at the Log file as it tries to start and notice two things in hopes that they are helpful for someone on this forum to help diagnose and address the issue.
First - there are a few 'Cannot open file' warnings for files in /Library/Preference/VMware Fusion.
I looked at my other iMac which has Fusion working and these files are not on that machine either but it runs fine. So maybe that's not relevant.
And then where it really seems to hang involves the usbarb connection.
Is that at all helpful to those who know a lot more about how Fusion works to help me fix the issue?
Thanks for any help anyone can provide.
2021-02-13T08:45:17.273-05:00| usbArb| I005: Log for VMware USB Arbitration Service pid=2441 version=16.0.0 build=build-16975537 option=Release
2021-02-13T08:45:17.273-05:00| usbArb| I005: The host is 64-bit.
2021-02-13T08:45:17.273-05:00| usbArb| I005: Host codepage=UTF-8 encoding=UTF-8
2021-02-13T08:45:17.273-05:00| usbArb| I005: Host is Mac OS X 10.15.7 (19H524) Darwin 19.6.0
2021-02-13T08:45:17.271-05:00| host-108462| I005: DictionaryLoad: Cannot open file "/Library/Preferences/VMware Fusion/usb-virt-api-switch": No such file or directory.
2021-02-13T08:45:17.271-05:00| host-108462| I005: UsbVirtApiSwitch: product=VMware Fusion state=on
2021-02-13T08:45:17.271-05:00| usbArb| I005: VTHREAD 4533734848 "usbArb" tid 108462
2021-02-13T08:45:17.272-05:00| usbArb| I005: DictionaryLoad: Cannot open file "/Library/Preferences/VMware Fusion/config": No such file or directory.
2021-02-13T08:45:17.272-05:00| usbArb| I005: [msg.dictionary.load.openFailed] Cannot open file "/Library/Preferences/VMware Fusion/config": No such file or directory.
2021-02-13T08:45:17.272-05:00| usbArb| I005: PREF Optional preferences file not found at /Library/Preferences/VMware Fusion/config. Using default values.
2021-02-13T08:45:17.274-05:00| usbArb| I005: DICT --- GLOBAL SETTINGS (null)
2021-02-13T08:45:17.274-05:00| usbArb| I005: DICT --- NON PERSISTENT (null)
2021-02-13T08:45:17.274-05:00| usbArb| I005: DICT --- HOST DEFAULTS /Library/Preferences/VMware Fusion/config
2021-02-13T08:45:17.274-05:00| usbArb| I005: DICT --- SITE DEFAULTS (null)
2021-02-13T08:45:17.274-05:00| usbArb| I005: USBArbRuleStore: Loading device rules from rules file.
2021-02-13T08:45:17.274-05:00| usbArb| I005: VMware USB Arbitration Service Version 19.9.0
2021-02-13T08:45:17.274-05:00| machPoll| I005: VTHREAD 123145361420288 "machPoll" tid 108463
2021-02-13T08:45:17.274-05:00| usbArb| I005: USBArb: Attempting to connect to existing arbitrator on /var/run/vmware/usbarb-socket.
2021-02-13T08:45:17.274-05:00| usbArb| I005: SOCKET creating new socket, connecting to /var/run/vmware/usbarb-socket
2021-02-13T08:45:17.274-05:00| usbArb| I005: SOCKET connect failed, error 2: No such file or directory
2021-02-13T08:45:17.274-05:00| usbArb| I005: USBArb: No other USB arbitrator instance is currently running.
2021-02-13T08:45:17.274-05:00| usbArb| I005: USBArb: listening socket 13 created successfully
2021-02-13T08:45:17.274-05:00| usbArb| I005: USBArb: adding listening socket 13 to poll queue
2021-02-13T08:45:17.282-05:00| usbArb| W003: USBGM: IOCreatePlugInInterfaceForService failed (e00002be)
2021-02-13T08:45:17.282-05:00| usbArb| W003: USBGM: IOCreatePlugInInterfaceForService failed (e00002be)
2021-02-13T08:45:17.282-05:00| usbArb| W003: USBGM: IOCreatePlugInInterfaceForService failed (e00002be)
2021-02-13T08:45:17.282-05:00| usbArb| W003: USBGM: IOCreatePlugInInterfaceForService failed (e00002be)
2021-02-13T08:45:17.282-05:00| usbArb| W003: USBGM: IOCreatePlugInInterfaceForService failed (e00002be)
2021-02-13T08:45:17.283-05:00| usbArb| W003: USBGM: IOCreatePlugInInterfaceForService failed (e00002be)
2021-02-13T08:48:10.984-05:00| usbArb| I005: USBArb: new socket connection estibalished: socket 4
2021-02-13T08:48:10.984-05:00| usbArb| I004: USBArb: new client 7F9339004EC0 created, socket 4 added to poll queue
2021-02-13T08:48:10.984-05:00| usbArb| I005: USBArb: Client 2560 connected (version: ![]()
2021-02-13T08:48:10.984-05:00| usbArb| I005: USBArb: closing listening socket 13
2021-02-13T08:48:10.984-05:00| usbArb| I005: MachPoll: mach_port_extract_member failed for port 10503 (12)
2021-02-13T08:48:10.985-05:00| usbArb| I004: USBArb: removing client 7F9339004EC0: pid=2560, pipe=4
2021-02-13T08:48:10.985-05:00| usbArb| I005: USBArb: Client 2560 disconnected
2021-02-13T08:48:10.985-05:00| usbArb| I004: USBArb: usb-arbitrator exit normally
UPDATE:
After leaving it for several hours in Not Responding, it finally started working. I can't explain what would change for that long and then start working.
