Knowledge Base


Disabled Drivers: StudioLive Classic or AI not showing/connecting on Mac OSX 10.13 or later through Firewire

Updated 11/4/2020


If you are trying to use OSX 10.15 Catalina with a StudioLive 'Classic' console, please review our compatibility statement for the StudioLive Classic consoles using Firewire 400:

Apple macOS X 10.15 Compatibility Statement


If your Firewire StudioLive is not showing as a connected Audio Device:

Your StudioLive will show as the "PreSonus FireStudio" when able to be selected as an Audio Device.

If you do not see the FireStudio as an option for your Audio Device, your Mac 10.13+ operating system may have disabled our Firewire drivers from being installed during installation.

More info can be found here:Installation Issues with Universal Control on High Sierra Mac OSX 10.13

If you've installed Universal Control in the last ~20 minutes, the allow button mentioned in the link above will re-enable the disabled Firewire drivers. Power-cycle your StudioLive to reconnect. Reboot your computer if needed.

If you do not see the [Allow] button, please see the recommendation below.


How do I know if my Firewire drivers are disabled?

If your StudioLive shows in the "Firewire" section of your System Report- in the 'Hardware' category- but not as an Audio Device then it likely that your Firewire drivers are disabled or not installed.

To see if your Mac has disabled our Firewire drivers, you'll need to check the "Disabled Software" section of your System Report or 'SPX' file.

>>>To access your MAC's System Report:

  • Apple Menu --> About this Mac... --> System Report

Once opened, click on "Disabled Software" in the 'Software' category.

If you see "TC Technologies", "Devguru", or "PaeFireStudio" or other PreSonus related drivers in this category, your drivers were disabled.


*Please note, that the SPX file you've opened does not refresh. It is only as current as when you first opened it. You will need to close and reopen a new SPX report after making changes to your system to see if your drivers are no longer disabled.*


If you see "No Information Found" (see below) then you do not have any disabled drivers.



What if I do not see an [Allow] button in Security & Privacy?

In the event that you do not see the [Allow] button in the "General" tab of Security & Privacy in System Preferences and you see our drivers as Disabled in your SPX report, you will need to uninstall and reinstall Universal Control using the Uninstaller found in the Universal Control download PKG from

>Power off and disconnect your StudioLive

>Run the PreSonus Uninstaller

>Restart your computer

>Run the PreSonus Installer from the download.

>Return to the download and run the Firewire Installer.

>Before restarting, check Security & Privacy for the [Allow] button. 

If visible, follow the instructions in the above link to allow our Firewire drivers.

*Please Note- if you have multiple drivers disabled you will be asked which drivers to allow. Otherwise the [Allow] button will disappear. Indicating that the drivers have been re-enabled.

If the [Allow] button is grayed-out, unlock the pad-lock in the bottom-left corner to make changes to your system.


'Disabled Software' says "No Information Found" and I still don't see the StudioLive/FireStudio as an Audio Device.

If you see "No Information found" in the Disabled Software section of your SPX, then the drivers have not been disabled.

Be sure that you have ran the Firewire driver Installer from the download of Universal Control 3.3+ and follow the above recommendations.

If you have ran the Firewire installer, drivers are not disabled, and still are unable to connect your StudioLive though Firewire:

>Be sure that your AI or Classic StudioLive are running their latest firmware.

>Check to ensure the Firewire cable is not at fault by swapping it with another for comparison testing.

>If available, try another computer for comparison testing.




Please contact PreSonus Technical Support by creating a Support Ticket at for further assistance.

>How to create a support ticket<




Was this article helpful?
2 out of 2 found this helpful
Powered by Zendesk