The old installer now works. Apple (rather than LMI) have fixed this problem. The issue where you couldn't click to approve the kernel extension was resolved in the release candidate.
Agree it still needs an update so it's no longer reliant on a kernel extension, but it is now usable.
I am receiving msgs in my Mac that hamachi extension will not be compatible with a future version of macOS.
Do we know if there is a new version of hamachi to cover this issue?
Thank you, Domingo
We have quite a few staff members using Macs to connect remotely. I imagine the whole work from home thing will be going on for quite some time. Telling them not to update to macos 11 in the fall doesn't fill me with joy...
Sorry for the delay. I checked with the dev team and we don't have enough info from Apple yet to give specific ETAs. As soon as it becomes available, then the development work will follow.
What does that mean? You don't have enough info from Apple?
Your dev team is no doubt a licensed Apple developer, therefore they should have all the info they need from Apple's developer site and the Xcode app.
Please follow back up with them and get the real story, as whatever line they told you is complete BS.
Will Hamachi run on macOS Big Sur? My Catalina machine tells me that Hamachi needs to be updated to run on a future version of macOS. Has anyone tried in on Big Sur? Will there be an update?
I had catalina running on my macOS 'til yesterday, hamachi worked fine, until I installed big sur. I tried to turn hamachi on and then this pops up:
(a small detail: developer is misspelt here)
When clicking OK, the Security and Privacy window appears without the Allow button:
I know Big Sur is currently unsupported, but is there any way to temporarily fix this?
I'm using a 2014 Mac Mini with the first public beta.
As of macOS 11, Hamachi no longer works in macOS. The above article lists changes in APIs that need to be made (probably not an exhaustive list). Apple seems to be now disallowing direct kernel modules. (This is probably why when I directly upgraded, it would only boot in Safe Boot and kernel panicked otherwise.)