{"id":28018,"date":"2020-02-03T15:52:31","date_gmt":"2020-02-03T20:52:31","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=28018"},"modified":"2020-07-03T16:48:41","modified_gmt":"2020-07-03T20:48:41","slug":"vmware-fusion-10-on-macos-catalina","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2020\/02\/03\/vmware-fusion-10-on-macos-catalina\/","title":{"rendered":"VMware Fusion 10 on macOS Catalina"},"content":{"rendered":"

Boy van Amstel<\/a>:<\/p>\n

Catalina requires apps to request permission for various tasks. Recording the screen is one of them. Apparently Fusion uses this feature, but neglects to ask for permission. Thus the screen stays black.<\/p>\n

Some people<\/a> found a way to get around this by granting permission manually. Here’s how that works.<\/p><\/blockquote>\n

macOS doesn’t let you add Screen Recording permission in System Preferences if the app hasn’t asked for it. VMware 11 asks; version 10 doesn’t, but it otherwise works fine on Catalina. The solution is to boot into Recovery (to get past System Integrity Protection) and then use SQLite to edit the TCC.db<\/tt> file to grant VMware the access.<\/p>\n\n

There’s a similar problem where sometimes macOS fails to prompt for Automation access (or remember said access). The prompting is supposed to happen automatically—there’s no API that apps need to call. If it doesn’t work, there’s likely something wrong with the TCC.db<\/tt> file and you should probably reset it. Sometimes tccutil reset AppleEvents<\/code> does the job. But sometimes the database is so messed up that you have to boot into Recovery and delete the file manually. There really should be a way to do that with tccutil<\/code>.<\/p>\n\n

0x00400000<\/a>:<\/p>\n

\n

I managed to trigger the permission modal for VMware Fusion 10 on Catalina using library injection.\nAfter restarting VMWare Fusion 10 it seems to have done the trick.<\/p>\n

I created a git repo<\/a> with a script to trigger the modal.<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n