Hope this also worked for you, and if not let me know if you solved it or what helped for you. Once I changed the setting my vpn connection could connect again. There I changed the adapter settings to Autodetect, instead of Share with my Mac. So from what I read on different forums, a lot of users had this issue after the upgraded to Big Sur and were forced to upgrade towards VMware Fusion 12 as well.Īfter some fiddeling around, I noticed that the VPN connection was able to connect when I changed the settings within the network adapter of my windows vm (in the Virtual Machine Library of VMware). Of course I was not really happy with this. Some of my VPN Connections towards customers, couldn’t connect anymore. I installed it and first everything seemed ok, until the first problem showed up. So I was forced to upgrade the program toward Fusion 12. However, when I opened that program when I upgraded towards Big Sur, the program simply just didn’t respond. This is often an Windows VM that I run on my Macbook with. So for my customer I use different VMs to make VPN connections towards their systems. Anyway, after the update, quite some stuff seems to be intact except when it came towards my VMware Fusion Program. Especially since I’m also using a lot of audio Software because I also have several DAWs for Producing & DJ’ing. This is especially true for OS X updates, cause they almost never go without issues. The reason is simple, every upgrade comes often with new challenges and can interrupt my work flow. However, coming to my own personal life, and I’m actually not that fond of upgrading my software. For my work, I often do upgrades and updates for customers within Windows & VMware.

I came from Catalina and was postponing this upgrade for some time. So almost after a year, I finally updated my macbook pro to Big Sur. so download from the developer) Visual Studio (launches but crashes when trying to open a solution) VMware Fusion 12.

Vmware fusion 12 big sur