Catalina vmware fusion black screen3/26/2023 Go to top menu and choose Utilities and then Terminal.ĩ. Go to Recovery Mode (hold CMD+R when computer starts until you see an Apple logo).Ĩ. Sudo sqlite3 "/Library/Application Support//TCC.db" 'insert into access values ("kTCCServicePostEvent", "", 0, 1, 1, "", "", "", "UNUSED", "", 0,1565595574)'ħ. macOS Ventura and OS X Monterey Hackintosh instructions, tutorials, step-by-step how to guides and installation videos Hackintosh systems, parts and more. After macOS starts normally open /Applications/Utilities/Terminal.app and paste this commands: tccutil reset All Go to top menu and choose Apple Logo and the Restart.Ħ. Turn off SIP with this command: csrutil disableĥ. Go to top menu and choose Utilities and then Terminal.Ĥ. Restart computer and go to Recovery Mode (hold CMD+R when computer starts until you see an Apple logo).ģ. Related: How to Install macOS Catalina on VMware on AMD SystemsĢ.RebootĬheck System Preferences → Security & Privacy → Privacy → Screen Recording and you’ll notice VMWare Fusion has the permission it needs. Sh "/Volumes/Machintosh HD/tmp/fixfusion.sh" You can now run the script you created earlier: (Again, adjust the command if your disk isn’t called “Macintosh HD”.)Įnter your passphrase when it asks for it. If your primary drive is encrypted using FileVault (it should be), unlock it first by running the following command: Right click the VM file and click ‘Show Package Contents'įind svga.guestBackedPrimaryAware = "TRUE"Īnd change to svga.Once in Recovery Mode, open Terminal from the menu bar by going to ‘Utilities’ then ‘Terminal’. In the VMWare library, click your VM and make sure it is shut down. Can’t be sure.) I’m on a 27″ iMac Pro but editing the VMX file worked. However, I did find an old tip that was worth a go… and for me, at least, it only bloody worked. How to fix the black screen problem of VMWare Fusion on OS X Catalina Download the version Fusion 11.1.0(exact) from VMWare. I’ve found nothing yet that specifically relates to VMWare Fusion on macOS Big Sur and a black screen on the VM. However, on this occasion, that was all fine. This was fixed usually either by a filthy hack or the proper way which is by allowing VMware Fusion to Screen Record through the System Prefs. There was a very similar issue when Catalina came out, and this was caused by new Security / Privacy controls around Screen Recording. but even then, starting the VM ends up in a black screen. Main issue is that trying to start a VM results in a bunch of error messages… these seem to get resolved by changing the compatibility level of the VM…. $100 later and I have Fusion 12 and… things are still broken. After a quick Google, it was evident it was a VMware incompatibility issue - Fusion 11 will not run on Big Sur and you must upgrade to VMWare 12. I was previously on v11.something and when trying to launch a VM got greeted with “Host OS does not have enough physical memory to launch this VM” which was a complete load of bollocks. Gah.īut anyway, one real issue I have had was with VMware Fusion. I’m sure there’s a huge amount of “don’t like change” in there but there are many things that are annoying the crap out of me with Big Sur. And so far, Big Sur vs Catalina is just a bit nightmare. I’m not sure why I do this sort of thing quite so freely… I always naively assume everything will be OK.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |