Microphone Not Working (Mac OSX Mojave)

Some Macs have exhibited microphone issues after upgrading to Mac OS X 10.14, Mojave.

We believe this is caused by faulty permissions associated with a new Mac security feature governing microphones specifically. If an app is detected to require access to use the microphone, your OS will ask for permission to allow the application to access the microphone. This will happen for each application that needs access to the microphone after the upgrade to 10.14, even if that application had already been used on your computer, prior to the upgrade.

This error is characterized by an inability to speak and may also include a grayed-out microphone icon in the lower-left corner of the VirBELA UI, even when a known-good microphone is plugged in.

If you're experiencing an issue with the microphone in VirBELA that you did not experience before the update to Mac OSX Mojave, it could be due to this permissions error.
Note: Before proceeding further, please read through our other guide sections on troubleshooting microphone issues.

The solution to this problem is to go to Settings, then click on the Security & Privacy icon.Mojave1.png

In the next window, click the "Privacy" button at the top "Microphone" in the left-hand pane. If you have already attempted to run VirBELA in Mojave, then it should be an option in the window, as shown below.


Check the box to the left of "virbela" to grant VirBELA permission to access the microphone.

Note: You may need to click the lock icon in the lower-left portion of the window, in order to make changes to these permissions.


If VirBELA is open when you click the checkbox, changes to the microphone permissions will not be applied until you close it. A notification window will pop up, giving you the option to close it immediately. Once you have made the changes here, click the lock icon to prevent further changes. If this has not fixed your problem, navigate back to this window, uncheck, and re-check the box, then restart your computer.

Have more questions? Submit a request


Article is closed for comments.
Powered by Zendesk