How to "allow" 3rd party apps in Ventura 13.0?

lesliepillay wrote:

1. I'm trying to play Bluestacks games on my iMac, on which I recently installed OS 13.0 Ventura. On starting the game now, I'm asked to accept extensions in System Settings. However in the System Settings > Security section, I see only 2 choices for "Allow applications downloaded from":

App Store

2. App Store and identified developers

In previous OS versions, an extra option to "Allow" or "open anyway" would appear if the app I want to run does not meet these requirement. But with Ventura this extra option doesn't appear.

How do I solve this problem?

see if there is anything here:

Change Extensions preferences on Mac - Apple Support

>System Settings>Extensions

You have to know how to 'turn on' this option via CLI commands. Open up a Terminal window and type the following:

sudo spctl --master-disable

Now if you go to Privacy and Security in the Settings area you will see an option for "Open Anyway".

As a software developer I hope that don't take this away.

IkechukwuNwanze wrote:

This revealed the "Anywhere" radio button. Tried it for Bluestacks and Nox Player but no luck. Will keep digging for a solution. Thanks for the tip though.

@etresoft posted earlier that Bluestacks is not compatible with Ventura or even Monterey in this post earlier in this very thread:

How to "allow" 3rd party apps in Ventura … - Apple Community

Have you checked with the developr of Nox Player to confirm it is actually officially supported with Ventura? Nox Player is not supported on M1/M2 Apple Silicon Macs. I see nothing on their website confirming Ventura compatibility on Intel Macs. Make sure you are not running any anti-virus apps, cleaning/optimizer apps, or third party security software which interferes with the normal operation of macOS. Otherwise you should contact the Nox Player developers for assistance with installing it on Ventura as the issue is most likely with the Nox Player app itself.

Hi, in my own situation, I download an app called Greatdy Computer Audio Device. The app runs fine. However, there is a button on it that says "click to install driver". When I click it is where I get the error message. So it isn't the app that has the issue, it's with the Mac OS not allowing the app too install a driver or plugin.

All I want to do is install something that lets me record system sound, say a video conference or sound effects from a movie, etc.

I find with older versions of macOS it is much easier to Control-click on the app and manually select "Open" for the first time launching a third party app. This will cause macOS to provide a pop-up prompt to confirm you want to grant macOS to run the app. I find this is much easier than going into System Preferences to click "Allow" when many times I was never even presented with the option.

However, if the app includes any extensions, then you will need to follow the suggestion of @leroydouglas.

I agree, this is horrible! I need to install the Greatdy Computer Audio Device Driver and it won't allow me! Come on, Apple, I paid $4000+ for this new Mac Studio and you aren't allowing me to install trusted (by me) software on my own device? I own this computer, and I want to install this software, it's that simple. And you are blocking me? Are we in lawsuit territory yet?

I had seen another post where I believe the person said the option/button to "allow" was just before or after the Filevault options. It was a very tiny entry/button that did not indicate the specific app asking for permission. I'm not certain what this button or link was called, but it will likely appear more generalized and won't mention any specific app asking for permission.

James Dylan wrote:

I agree, this is horrible! I need to install the Greatdy Computer Audio Device Driver and it won't allow me! Come on, Apple, I paid $4000+ for this new Mac Studio and you aren't allowing me to install trusted (by me) software on my own device? I own this computer, and I want to install this software, it's that simple. And you are blocking me? Are we in lawsuit territory yet?

Who are we suing? Apple or Apple's users? The feature described by the OP was always the wrong and most complicated way to do this.

If you want to install something, something that you trust, or something that you shouldn't, you can always override Apple's productions. Just right-click or control-click on the thing you want to run and choose "Open" from the context menu.

etresoft wrote:

If you want to install something, something that you trust, or something that you shouldn't, you can always override Apple's productions. Just right-click or control-click on the thing you want to run and choose "Open" from the context menu.

The one user did mention the software was installing a driver. I don't install many apps utilizing drivers, so I forget how I've handled it in the past. I know a couple of times it was not straight forward even when the "Allow exception" button was available in the Gatekeeper Security settings (the button did not always show up). I believe I may have once approved the driver by right-clicking or Control-clicking the actual installed app, but that was a while ago so I don't recall. I know that at least two times I had to reboot multiple times and approve the driver multiple times before macOS accepted the configuration. I know that sometimes the driver portion of the install must be approved separately. Not sure if this was due to Gatekeeper/macOS or how the developer released/packaged the app & driver.

HWTech wrote:

The one user did mention the software was installing a driver. I don't install many apps utilizing drivers, so I forget how I've handled it in the past.

Hasn't changed any.

I know a couple of times it was not straight forward even when the "Allow exception" button was available in the Gatekeeper Security settings (the button did not always show up). I believe I may have once approved the driver by right-clicking or Control-clicking the actual installed app, but that was a while ago so I don't recall. I know that at least two times I had to reboot multiple times and approve the driver multiple times before macOS accepted the configuration. I know that sometimes the driver portion of the install must be approved separately. Not sure if this was due to Gatekeeper/macOS or how the developer released/packaged the app & driver.

In most (all?) cases, this is due to a poorly written 3rd party driver. You only get 30 minutes to approve the extension. If you wait too long, or if the app doesn't nag you, then it goes away. An app can try to load it again and give you another 30 minutes, but if it was last touched in 2009, as most of them were, it isn't going to do that.

In this case, the explanation is much simpler. BlueStacks simply doesn't support Ventura. It doesn't even support Monterey or M1.

James Dylan wrote:

in my own situation

You should start your own question for your own situation.

I download an app called Greatdy Computer Audio Device. The app runs fine. However, there is a button on it that says "click to install driver". When I click it is where I get the error message. So it isn't the app that has the issue, it's with the Mac OS not allowing the app to install a driver or plugin.

From those screenshots, I can assure you the problem is with the app. That is amateurish, at best. I recommend you find some other app.

James Dylan wrote:

Fine, but your answer still doesn't acknowledge the fact that it appears Apple removed the option from previous versions to click "install all". Only Apple and "verified apps".

That option was removed several years ago and is not something new with Ventura, but I don't recall in which version of macOS it first was removed. Apple keeps increasing the security measures of macOS with each release. It really would not surprise me if Apple stopped allowing unsigned & unverified apps to be installed at some point. I'm actually surprised it hasn't already happened.

HWTech wrote:

It really would not surprise me if Apple stopped allowing unsigned & unverified apps to be installed at some point. I'm actually surprised it hasn't already happened.

Apple actually announced such a policy a few years ago. It they never did it.

I have seen a few situations where unsigned binaries that I build myself don’t work on Apple Silicon. But apparently there are too many ways around that. Malware is not affected.

Ventura 13.0.1 seems to have re-enabled the ability to click right on the app, select "open" and then after the "broken" message have the option to open it anyway. So Apple fixed it (silently since I don't recall this being in the 13.0.1 release notes!).