Native Access 3.1.0 and dependency / dependencies installation

Jeremy_NI · 2022-12-15T12:47:12+00:00

There was an error rendering this rich post.

Jeremy_NI

Hey all,

The new version of Native Access (3.1.0) should address some of the following issues:

Please grant permission to NTKDaemon to install Dependencies (Mac and Win)
Dependency Installation is taking longer than normal (Mac and Win)

Since auto updating is not possible in these situations, please download the latest version of Native Access from here:

Native Access 3.1.0 for Windows

Native Access 3.1.0 for Intel Macs

Native Access 3.1.0 for M1 Macs

Also make sure to give Full Disk Access to Native Access and NTKDaemon.

If these items don't appear in the list, click the plus (+) symbol and add them from:

Macintosh HD > Applications > Native Access

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

Let us know if this fixes the issue for you or not.

Find more posts tagged with

Native Access 2

ntkdaemon

Accepted answers

PoorFellow

https://community.native-instruments.com/discussion/comment/83186#Comment_83186

Actually they have come a long way in solving a lot of problems. But even if they have not solved your problem then you ought not go back and try to revive a thread that is no longer about a present version of Native Access. Version is now 2/3.4.0 .

Don't get me wrong ! : I did exactly what you did back when it was Native Access 2.X . It was clearly riddled with problems and I for months reverted to version 1 and used that and only very recently upgraded to version 2/3.4.0 (download page says 2 , version say 3.4.0).

At present it appear to me that N.I. have manged to iron most their problems making the Native Access run and work but it also appears to me that they have not been able to make an installer process that can manage to clean up after previous problems made by previous versions and install attempts , not to mention that their N.I. registry tool is simply not up to the task either - ought really be a N.I. cleaner that would both clean registry and hard drive from any traces of previous installations in as much as that it mostly appears that that is most peoples problem that they have to spend a lot of time doing that to get things to run. And which you yourself has noticed that it is simply not reasonable if the average user have to be a Windows or Mac software trouble-shooting 'expert' !

For what it is worth then as already implied then most people here appear to get their things to run by deep cleaning their system from previous Native Access and NTKDaemon installations. If you can not get the Native Access 3.4.0 to run yourself then you should get support to help you by contacting support ! , however please notice that they are swamped with requests due to the recent sale and the many new customers and the many upgrades made !

Otherwise here is an adapted copy of my 'standard advice' by now :

IMPORTANT : prior to any computer tinkering then please at least make a Restore Point , and prior to tinkering with registry take a back up of that. Also generally it'd always advisable to backup the whole system drive once in a while or at least if you got something that you do not want to loose if you mess up anything !

You can not be sure that Native Access 1 will work (it's more or less considered as obsolete by N.I.) so you need to upgrade to Native Access 2 /(3.4.0) . As for the N.I. reg-tool then it does not actually do it's job properly as far as I am concerned. Also after an un-install there may be files left on your hard drive. Also , please check in Task Manager to see if you have the NTKDaemon process running despite you having uninstalled the app or may have failed to install new..

What I did myself were to uninstall Native Access , then kill process NTKDaemon and run the N.I. reg-tool : ref. NI Uninstall RegTool_64bit : https://support.native-instruments.com/hc/en-us/articles/115003509269-Fixing-Software-Update-Installation-Issues-Windows-

to remove Native Access and NTKDaemon from registry , then delete all directories named Native Access from drive and all instances of NTKDaemon - including destinations such as (can not remember which exactly but also depends on version I think - 1 or 2) (Mentioned destinations are Windows 10 , not having Win 11 I can not confirm it for Win 11) :

C:\Users\<user name>\AppData\Local\ and C:\Users\<user name>\AppData\Local\Native Instruments

C:\Users\<user name>\AppData\Roaming\ and C:\Users\<user name>\AppData\Roaming\Native Instruments

C:\ProgramData\ and C:\ProgramData\Native Instruments

C:\Program Files\ and C:\Program Files\Native Instruments

C:\Program Files\Common Files\ and C:\Program Files\Common Files\Native Instruments

Then I cleaned the registry using the free CCleaner (use with caution and remember to backup the registry first - CCleaner only backup alterations) (CCleaner is free but accused by some to be 'bloatware' and generally the use of registry cleaning tools are highly discouraged by N.I)(hence the backup suggestions also) Ref. :https://support.native-instruments.com/hc/en-us/articles/209544929-Notes-on-Using-Registry-or-Property-List-Cleaning-Utilities

Then I used Windows registry editor to then remove any left traces of 'Native Access' and 'NTKDaemon'

And then confident that all traces of Native Access and NTKDaemon were removed from from both drive and registry and that the NTKDaemon process were no longer running after startup then I installed Native Access 2 / 3.4.0 (run install as Admin !) : https://www.native-instruments.com/en/specials/native-access-2/ OR https://www.native-instruments.com/en/support/downloads/

Again :

If you can not get the Native Access 3.4.0 to run yourself then you should get support to help you by contacting support !

All comments

PoorFellow

https://community.native-instruments.com/discussion/comment/83308#Comment_83308

Problem is that N.I. have not expressed recognition of the need to make a better clean tool. But you are right : it is a lot of effort including taking appropriate backups just ion case..

Also , if you are satisfied with or like advice received then please consider using the 'like' option , ref : https://community.native-instruments.com/discussion/11800/ranks-and-rewards/p1

matty2023

oh I was trying every solution over time and gave up, BUT I found System Mechanic was installed, was giving dll error on the old version 1 solution, when I removed the system mechanic EVERYTHING worked !!

Hope that helps someone else

Cause

This issue appears if the programs System Mechanics and/or F-Prot are installed on your Windows system. They will block the installation of Native Instruments products.

Uwe303

https://community.native-instruments.com/discussion/comment/83308#Comment_83308

they still work, you just have to use midi cc2 (breath controller) in order to get a sound out of it, just set a value greater than 0, better way above. you can also edit the instrument so that the mod wheel controls it, you find one modulator for volume set to cc2 and default value 0, set the cc# as you need it.

Quick links

Unanswered questions