Device not yet allowed?

[mivey4]

Anyone else seen this issue? I upgraded the software to 11.1, went through the typical routine of allowing UAD software via privacy and security settings, rebooted the system and was greeted with this in the UAD Control Panel



If I turn off my UAD hardware I get this, so there isn't any communication issue



For some reason UAD software doesn't acknowledge or know that it already has been granted the required access.
I have uninstalled the software via the uninstaller and reinstalled several times without any resolution. Presently dead in the water with Projects I cannot load properly or use b/c of using UAD plugins and having this problem.

IDK why this seems to be an on-going periodic issue with UAD software but starting to get really old.

Anyone seen or have suggestions on how to fix this? Already opened a support ticket but from experience I know it could take a couple of days before I get assistance and I loose precious work time everytime this type of thing happens.

iMac Pro 2017
64 GB RAM
OSX Ventura 13.6.4
3 GHz 10-Core Intel Xeon W

 

[UniversalAudio]

A full uninstall/delete prefs/reinstall should bring back the Allow button. There is a 30 min window where it needs to be clicked.

You can also try installing an older version to get it back and then update again.

 

[mivey4]

A full uninstall/delete prefs/reinstall should bring back the Allow button. There is a 30 min window where it needs to be clicked.

You can also try installing an older version to get it back and then update again.

Everytime I've uninstalled the software I always get the "Allow" button back so it would appear that the OS acknowledges when the software has been removed and the prompt to "Allow" is always presented again. It's just the UAD software that seems to be oblivious to it; and I always click the Allow within less than a minute b/c I know it's an important step.

I'll try your suggestion to delete the prefs after uninstall and see if it makes any difference.

Thanks

 

[mivey4]

Ok, so uninstalling and deleting all the preference files didn't fix it but the suggestion did lead me in a direction that eventually acquired resolution.
Not certain exactly which of these steps led to resolving the issue but:

1. Uninstalled the software via the Uninstaller (both the UA plugin and the UAConnect software)
2. Manually deleted all UA plugins from the system
3. Performed the following (checking at both ~/Library and /Users/<username>/Library directories)
4. Deleted Universal Audio folder from Application Support
5. Identified and deleted every file and/or folder in Caches referring to Universal Audio
6. Identified and deleted every file and/or folder in Preferences referring to Universal Audio
7. Shutdown the computer and performed a reset of the PRAM
8. Booted back and installed the Software again
9. Prompted to "Allow" from within Privacy and Security settings but I opted not to do this
10. Allowed Installer to complete and allowed Installer to complete by selecting to Restart from within the Installer
11. Booted back up with my UAD Hardware turned off
12. Launched the UA Control Panel and it gave the message to Connect UA Device
13. Turned my UAD Hardware on and received the message "Device not yet allowed"
14. Opened System Preferences and at this point I selected to Allow the UA Software, entered my password and rebooted

After the restart I launched the Control Panel and it was properly detecting my hardware w/o Issue

This was way overkill for something that should have been as simple as installing and rebooting but like I said, it's not the 1st time I've had similar issues when doing an update on the Software; as I've also noted with other folks as well.

One point that I will make is that there needs to be more clarity on the installation process somewhere regarding the sequence of when the Allow button is pressed with respect to the restart. Because clicking "Allow" at the time the UA installer is requesting the action creates a conflicting situation where the OS is asking to restart for the permission to be granted before the installation completes, subsequently followed by the installer wanting to initiate the restart after it completes.

Seems to me only one of these entities need to be the one to initiate the restart; and I'd think the OS should be the only component initiating the restart; not the installer. This has always been somewhat of a convoluted process and is very confusing from a User perspective. I'd venture further to say it "may possibly" also be a contributing factor for these types of problems.

My 2 cents dropped.

 

[UniversalAudio]

Ok, so uninstalling and deleting all the preference files didn't fix it but the suggestion did lead me in a direction that eventually acquired resolution.
Not certain exactly which of these steps led to resolving the issue but:

1. Uninstalled the software via the Uninstaller (both the UA plugin and the UAConnect software)
2. Manually deleted all UA plugins from the system
3. Performed the following (checking at both ~/Library and /Users/<username>/Library directories)
4. Deleted Universal Audio folder from Application Support
5. Identified and deleted every file and/or folder in Caches referring to Universal Audio
6. Identified and deleted every file and/or folder in Preferences referring to Universal Audio
7. Shutdown the computer and performed a reset of the PRAM
8. Booted back and installed the Software again
9. Prompted to "Allow" from within Privacy and Security settings but I opted not to do this
10. Allowed Installer to complete and allowed Installer to complete by selecting to Restart from within the Installer
11. Booted back up with my UAD Hardware turned off
12. Launched the UA Control Panel and it gave the message to Connect UA Device
13. Turned my UAD Hardware on and received the message "Device not yet allowed"
14. Opened System Preferences and at this point I selected to Allow the UA Software, entered my password and rebooted

After the restart I launched the Control Panel and it was properly detecting my hardware w/o Issue

This was way overkill for something that should have been as simple as installing and rebooting but like I said, it's not the 1st time I've had similar issues when doing an update on the Software; as I've also noted with other folks as well.

One point that I will make is that there needs to be more clarity on the installation process somewhere regarding the sequence of when the Allow button is pressed with respect to the restart. Because clicking "Allow" at the time the UA installer is requesting the action creates a conflicting situation where the OS is asking to restart for the permission to be granted before the installation completes, subsequently followed by the installer wanting to initiate the restart after it completes.

Seems to me only one of these entities need to be the one to initiate the restart; and I'd think the OS should be the only component initiating the restart; not the installer. This has always been somewhat of a convoluted process and is very confusing from a User perspective. I'd venture further to say it "may possibly" also be a contributing factor for these types of problems.

My 2 cents dropped.

yeah, you just needed 1-6.

 

[srcndr]

yeah, you just needed 1-6.

Hi, I have the same problem. I tried steps 1 through 6, but it didn't work. It's so frustrating; there should be an easier solution. Do you have a list of UAD-related things to manually delete?

 

[UniversalAudio]

Hi, I have the same problem. I tried steps 1 through 6, but it didn't work. It's so frustrating; there should be an easier solution. Do you have a list of UAD-related things to manually delete?

I do not, sorry. The steps listed here are all that is needed. I'd try again.

This:

https://help.uaudio.com/hc/en-us/articles/360057137692-Apple-Silicon-M1-M2-and-M3-Compatibility-with-Universal-Audio-Devices

and this:

https://help.uaudio.com/hc/en-us/articles/19237390771860-UAD-Software-Compatibility-with-macOS-Sonoma-14

Are all that you need.

 

[JBH]

I updated a couple of days ago and all seemed well and normal. Today I got the "driver not yet allowed" message. Carefully tried several times to uninstall/reinstall according to directions here and on the UA site, but no luck.

An odd issue is that new UAD software doesn't show up in the security and privacy pane after install. Is this because I'm in OSX 12 Monterey?

My owned UAD2 plugs are all red in Luna and inactive in Logic.

I can hear both system sounds and the Logic outputs through both the monitors and Apollo twin headphone outputs, just like normal, but console doesn't recognize any inputs.

If my OS is the problem, is there a way to downgrade to a previous compatible version?

I did create a ticket, and hope for a quick resolution.

Thanks

 

[LesBrown]

Earlier versions are here, but Monterey appears to be compatible with the latest version:

https://help.uaudio.com/hc/en-us/articles/215267203-UAD-Software-Archives

 

[JBH]

Thanks Les. I'll try going back to 10 and hope to find a solution for my 11 issue down the road.

 

[teknosmoker]

I updated a couple of days ago and all seemed well and normal. Today I got the "driver not yet allowed" message. Carefully tried several times to uninstall/reinstall according to directions here and on the UA site, but no luck.

An odd issue is that new UAD software doesn't show up in the security and privacy pane after install. Is this because I'm in OSX 12 Monterey?

My owned UAD2 plugs are all red in Luna and inactive in Logic.

I can hear both system sounds and the Logic outputs through both the monitors and Apollo twin headphone outputs, just like normal, but console doesn't recognize any inputs.

If my OS is the problem, is there a way to downgrade to a previous compatible version?

I did create a ticket, and hope for a quick resolution.

Thanks

I had this same issue running Monterey (12.6.1). Regular computer restarts did not help, but after powering everything down fully, then restarting my computer the issue was resolved.

Hope that your situation resolved itself as well!





- T

 

[JBH]

I had this same issue running Monterey (12.6.1). Regular computer restarts did not help, but after powering everything down fully, then restarting my computer the issue was resolved.

Hope that your situation resolved itself as well!- T

Thanks. I ended up downgrading for the moment and will come back to it when I have the time to better investigate my issue.

 

[Iomegamark]

I've been having this issue all day, since I saw an update in UA connect it has fluxed my entire machine...

I have followed every step in every post here so far and nothing has helped...the newer UAD kext where they are moving over the drivers from the legacy stuff to be more compatible is not working...Console shows all my plugins as "Buy" it is not showing I own anything...

I have done everything in the UAD linked help pages as well.

Do not update.

All I get in the Meter app is "Driver not yet allowed" in spite of working a few days ago on a MBP M2 Sonoma 14.5

I have allowed the software in Preferences/privacy now 4 times, as well as run diagnostics on my mac to make sure there were no issues, I have unplugged every other device and simply run the Apollo Twin alone and yet nothing gets me past this Meter/Control red nag screen.

 

[Iomegamark]

I went back to 11.3

I recommend you do NOT update via UA connect somethign is definately broken, this update has caused my MBP M2/Sonoma 14.5 to reboot and kernal panic and the EtreCheck report shows it is UAaudio that is causing the kernal panics...

11.3 is fine everything works again, not sure what UAD did but they broke it.

 

[sonor72]

I've been having this issue all day, since I saw an update in UA connect it has fluxed my entire machine...

I have followed every step in every post here so far and nothing has helped...the newer UAD kext where they are moving over the drivers from the legacy stuff to be more compatible is not working...Console shows all my plugins as "Buy" it is not showing I own anything...

I have done everything in the UAD linked help pages as well.

Do not update.

All I get in the Meter app is "Driver not yet allowed" in spite of working a few days ago on a MBP M2 Sonoma 14.5

I have allowed the software in Preferences/privacy now 4 times, as well as run diagnostics on my mac to make sure there were no issues, I have unplugged every other device and simply run the Apollo Twin alone and yet nothing gets me past this Meter/Control red nag screen.

SAME, I'm also on Sonoma 14.5 and any changes I make to the console don't effect the actual unit infront of me and I currently have no sound coming out from my computer, and nothing indicates that the sound is making it to the unit or the console. quite concerning

 

[UniversalAudio]

SAME, I'm also on Sonoma 14.5 and any changes I make to the console don't effect the actual unit infront of me and I currently have no sound coming out from my computer, and nothing indicates that the sound is making it to the unit or the console. quite concerning

Have you done the Recovery Mode step?
Have you clicked Allow?
What does the UA Meter app say?

 

[sonor72]

Have you done the Recovery Mode step?
Have you clicked Allow?
What does the UA Meter app say?

I have not done the recovery mode step, haven’t clicked allow. The UA meter app says “driver not yet allowed” i have yet to try uninstalling and reinstalling anything which could possibly solve the issue. Haven’t tried anything yet because i lack the motivation to at the moment but what would you recommend for the first steps towards possibly solving this?

 

[UniversalAudio]

I have not done the recovery mode step, haven’t clicked allow. The UA meter app says “driver not yet allowed” i have yet to try uninstalling and reinstalling anything which could possibly solve the issue. Haven’t tried anything yet because i lack the motivation to at the moment but what would you recommend for the first steps towards possibly solving this?

It's all here:

https://help.uaudio.com/hc/en-us/articles/19237390771860-UAD-Software-Compatibility-with-macOS-Sonoma-14

https://help.uaudio.com/hc/en-us/articles/360057137692-Apple-Silicon-Compatibility-with-Universal-Audio-Devices

 

[UniversalAudio]

and if you need it:

https://help.uaudio.com/hc/en-us/articles/360051069691--Mac-UAD-Uninstall-Reinstall-Procedure-?

 

[Iomegamark]

I can assure you I've followed every line of instruction UAD recommends and removed/re-installed/permitted drivers until I'm blue in the face...

Even after allowing the change in permissions (I went so far as to go back and boot into reduced security mode just to make sure I wasn't missing something...every step was followed and the mixer app still showed "driver not permitted yet" even after several re-tries...

I also has these same issues with Apogees new Control 2 software to run out Symphony MKII...both UAD and Apogee newer non-kext or improved kext or whatever the F the code guys are doing are causing kernel panics in Sonoma 14.5...

In both cases with both vendors I had to roll back to the older drivers just to get the systems to work at all.