Native Access doesn't accept NTK DAEMON version

STARRIDER2276
STARRIDER2276 Member Posts: 1 Newcomer
edited July 2023 in Native Access

In order for me to use the new Native Instruments Access I had to do a few things. First, I had to download the Ntk Daemon installer which I ran and installed. I then had to disable the firewall. Then I ran services.msc this brings up the run command box. It will take you to the services module. Find Ntk Daemon in services and double-click it to run it. It's a bit weird which is a little weird it brings up another sub-module that requires you to start the service and requires opening up menu keys, scroll down to the letter N and look for it. NI has a new update for Native Access I found it today. When running it I got a prompt basically saying that the version I had of NTK Daemon wasn't the version it was looking for. The program was looking for an earlier version which I now have to find. I HAD VERSION 1.13.0.0 and it wouldn't accept that version. WELCOME TO THE JUNGLE.

Tagged:

Best Answer

  • PoorFellow
    PoorFellow Moderator Posts: 1,587 mod
    edited July 2023 Answer ✓

    Most of what you write ought not be required at all and it points to a completely failed and dysfunctional installation either prior or now. I am running Windows 10 , 64 bit myself also and never had the type of problems that you describe. I don't know if you have some very strict security software on your PC or what ever has caused your experience. But to me it sounds as the only real fix would be to uninstall and clean your Windows of any traces of both Native Access and NTKDaemon and then do a clean re-install attempt of newest version !

    Take a look at my post at the bottom of page 3 here : https://community.native-instruments.com/discussion/8803/issues-native-access-2-dependency-installation-process-is-taking-longer-than-normal/P3#86487

    If that doesn't help then you might have to clean your Windows installation even deeper....

    But in short , after cleaning Windows of old installation then there must not be any traces of Native Access or NTKDaemon in registry , on drive or in list of services or list of processes (not after a reboot either !) ! Then re-boot and only then re-install Native Access : https://www.native-instruments.com/en/specials/native-access-2/

Answers

  • PoorFellow
    PoorFellow Moderator Posts: 1,587 mod
    edited July 2023 Answer ✓

    Most of what you write ought not be required at all and it points to a completely failed and dysfunctional installation either prior or now. I am running Windows 10 , 64 bit myself also and never had the type of problems that you describe. I don't know if you have some very strict security software on your PC or what ever has caused your experience. But to me it sounds as the only real fix would be to uninstall and clean your Windows of any traces of both Native Access and NTKDaemon and then do a clean re-install attempt of newest version !

    Take a look at my post at the bottom of page 3 here : https://community.native-instruments.com/discussion/8803/issues-native-access-2-dependency-installation-process-is-taking-longer-than-normal/P3#86487

    If that doesn't help then you might have to clean your Windows installation even deeper....

    But in short , after cleaning Windows of old installation then there must not be any traces of Native Access or NTKDaemon in registry , on drive or in list of services or list of processes (not after a reboot either !) ! Then re-boot and only then re-install Native Access : https://www.native-instruments.com/en/specials/native-access-2/

Back To Top