Thanks in anticipation of some help and guidance.ġ. If someone can give me any guidance I would be grateful meanwhile I am sticking with Catalina and VMware 11 for the moment. I am assuming it is to do with the fact VMWare does not use KEXTs in Big Sur but uses Apples Drive Kit and there are bugs somewhere in the new code for the new APIs, although your blog indicates that, in Catalina, you still use kernel extensions, so that does not explain the Catalina/VMware 12 failure I am observing, but might explain the Big Sur issues where Apple's Drivekit APIs have to be used. There is obviously a fundamental problem here. I reverted to Catalina (with much pain), put back VMWare 11.5.6 and used backups of the VMs and all is well.

At least I did not get the broken pipes message but the VMs were not much use to me. With these 3 VMs the MS Update server could not be reached, my email client in the browser would not load, the Baraccuda VPN adapter did not work etc. I run all my VMs in Bridge Auto mode, so each VMW has its own IP address. The other 3 VMs came up and ran with networking apparently connecting but I discovered that NAT was not working. The VM ran fine, but with no network connection. 1 of them came up with the 'Ethernet0 could not be loaded so networking was disabled' type message so there was no virtual network adapter. I upgraded to Big Sur on one of my Macs and, of course, you need to install VMWare 12 in order to get the VMs to have any chance of running. Has anyone else had these issues and if so what can be done to make it work.Ģ. So it looks as if VMWare 12 would not work for me on Catalina. The VMs were upgraded and then would not start due to 'broken pipes'. Checked everything was working and did the upgrade to VMWare 12 again.

I assumed that an issue I had with OWC's Softraid where I had to unlock the security options prior to doing the upgrade (to allow extensions to be installed), may be the problem, so I put backup copies of VMs back and reinstalled VMWare 11.5.6. I upgraded to VM12 (Player edition) and immediately had issues with 'broken pipes' messages and the VMs refused to start after VMWare 'upgraded' the VMs. I have 4 VMs all working well on VMWare 11.5.6 (standard edition) and OS X 10.15.7. I have been on the trail of several issue and have posted in the general forum but thought I would post here and see what the team has to say.ġ.

Vmware fusion 12 catalina