Updated Native Access- dependencies fail, use Legacy Native Access - Install Fails

MFF · 2024-04-14T12:28:07+00:00

There was an error rendering this rich post.

Hello.

I have been trolling the community for 2 days while trying to figure this out off and on.

I'm not sure when this happened, but I bought a new 3rd party library and opened up native access (most recent version) and couldn't even get it to open.

Install window for NTKDaemon keeps popping up after I run the installer. Full disk access for all the Native programs turned on. Nothing in the community pages fixed that issue, so I went to a legacy version of NA.

Now that I'm in the legacy version, nothing will install.

I've looked all over community for this too, redownloaded NA a bunch of times, restarted my computer a bunch of times following different steps, nothing has worked in that regard. I've been so frustrated that I've been excited to use a new product for two days and it feels like everything is broken out of nowhere, and I haven't heard anything back from support.

Find more posts tagged with

Native Access

Accepted answers

PoorFellow

https://community.native-instruments.com/discussion/comment/146783#Comment_146783

Or if it's better to try and figure out this NTK Daemon/Helper tool install issue.

Sorry , I am not a Mac expert and would have expected one of the above suggestions to work. But I think that N.I. support should be able to assist you solving the problem. And I think that you should choose to get the issue fixed !

Mac are giving so many access problem type problems that it's hard to keep track. I read in this forum the other day how the final fix for a problem for one user then after all other didn't help were to make a new user (account ?) on the Mac.

For some users the problem is that they do not use correct disk format, 10.13 High Sierra and later must use APFS

Another user wrote this : one additional step that solved this: I had to change the permissions for the desktop. For some reason, "everyone" did not have read and write permissions for the desktop, and that somehow prevented the dmg to do its thing.

(a) I gave full disk access for NI Access and NTK

(b) changed the permissions to read/write for the destination folder

and then it worked.

And another other user couldn't install Native Access due to a "mutex issue" , read here !

Yet another user did this to fix a problem :

Start the computer in macOS Recovery

Shut down the computer.
Press and hold the power button on your Mac until you see “Loading startup options.”
Click Options, then click Continue.
If requested, enter your account password.

Set the security policy

In the Menu Bar, choose Utilities > Startup Security Utility
Click on the system drive you want to use to set the security policy.
Click Security Policy, select the Reduced Security option, and enter your password if requested.
Check the “Allow user management of kernel extensions from identified developers” option.
Click OK, then restart your Mac for the changes to take effect

Not having any Mac , and in particular not having your Mac then I can not do anything else other than report !

All comments

PoorFellow

Some people have had issues with the two latest versions of Native Access but unless you are one of those then generally you ought to be using latest version of Native Access for your OS (unless you are using a legacy OS , Mac 10.15 and earlier / Win 7 downloads) , and even if you want to downgrade then unless you are using a legacy OS then you ought not roll back further than NATIVE ACCESS 3.8.0 (can't download ? try logging into Google prior to trying to download to see if that helps !)

Else , as you already know, then when installing and after then grant full disk access to all N.I. including the NTKDaemon. When you have installed a newer version of N.A. then please be sure to check the following also ! :

1) Quote Jeremy_NI : please check these articles:

Native Access Error: "Please grant permission to NTK Daemon to install dependencies"

Native Access Freezes on “Installing Dependencies“ at Startup

2) Quote Jeremy_NI :

can you check the following?

Open your Mac's System Preferences and click Security & Privacy.
Under the Privacy tab, choose Full Disk Access from the side bar.
Click the lock icon in the bottom left of the window and enter your Mac password.
Ensure that Native Access appears in the list.
If it does not appear in this list, click the + icon and add the following apps:
Macintosh HD > Applications > Native Access
Macintosh HD > Library > Application Support > Native Instruments > NTK > NTKDaemon
Once completed, click the lock icon again

3) Quote Jeremy_NI :

Also make sure that the NTKDaemon is in the login items in your system preferences, under Users & Groups: (Ventura has "Login Items" under "General".)

If it's not there, unlock and add it, you can find it here:

Macintosh HD > Library > Application Support > Native Instruments > NTK > NTKDaemon

Otherwise the please contact N.I. Native Access and Installation Support !

MFF

I really appreciate you taking the time to help out.

I've run through these steps, and am still having the same problem.

I've put the newest version of NA back, and the problems with it are that it tries to install NTK helper tool over and over, and NA is just looping at "installing dependencies", after 3-5 minutes NA says "unable to start the NTK Daemon Please restart native access"

I'm not sure if it's best to try and get a legacy version to not have the install issue, or if it's better to try and figure out this NTK Daemon/Helper tool install issue. Any thoughts?

Thanks again!

PoorFellow

https://community.native-instruments.com/discussion/comment/146783#Comment_146783

Or if it's better to try and figure out this NTK Daemon/Helper tool install issue.

For some users the problem is that they do not use correct disk format, 10.13 High Sierra and later must use APFS

(a) I gave full disk access for NI Access and NTK

(b) changed the permissions to read/write for the destination folder

and then it worked.

And another other user couldn't install Native Access due to a "mutex issue" , read here !

Yet another user did this to fix a problem :

Start the computer in macOS Recovery

Shut down the computer.
Press and hold the power button on your Mac until you see “Loading startup options.”
Click Options, then click Continue.
If requested, enter your account password.

Set the security policy

In the Menu Bar, choose Utilities > Startup Security Utility
Click on the system drive you want to use to set the security policy.
Click Security Policy, select the Reduced Security option, and enter your password if requested.
Check the “Allow user management of kernel extensions from identified developers” option.
Click OK, then restart your Mac for the changes to take effect

Not having any Mac , and in particular not having your Mac then I can not do anything else other than report !

Quick links

Unanswered questions