Welcome to the new and improved Native Instruments online community. Join our active forum of 40,000+ members for discussions and much more.

What does NTKDaemon service do?

SF_Green
SF_Green Member Posts: 12 Sine
edited February 23 in Native Access

I have to admit I've always been suspicious of the NTKDaemon service, but there have been statements from NI people here saying it's just for login and access to Sounds.

However, I constantly see the NTKDaemon service using high amounts of CPU time and activity after a fresh boot and other times when my Komplete Kontrol S88 is off and no other NI software has been started since boot that the service is active and using a fair bit of CPU time. I've even reverted to Native Access 1, and the daemon service is still very active on a regular basis.

Is NTKDaemon being used for telemetry and NI is lying to us, or is there some other BELIEVABLE explanation for why this is happening? Sorry but the general state of affairs these days just leaves me highly suspicious of any big software/tech company. Microsoft, Google, Facebook - liars all. Not saying NI is in the same league as them, but still not feeling inclined to be overly trusting these days.

Tagged:

Comments

  • Kaiwan_NI
    Kaiwan_NI Administrator Posts: 1,860 admin

    Hi @SF_Green our Native Access product owner gave an overview of the history of Native Access here:

    Dev Talks: Why We Transformed Native Access

    He explained a bit what NTKDaemon does in the article. Hope it answers your question!

  • James Steele
    James Steele Member Posts: 7 Sine

    Just want to report here on my end that NTKDaemon seems unstable. The process often crashes spontaneously (I saw it spontaneous crash in Activity Monitor when I was typing an email) or it doesn't start up at all upon boot. This seems to explain why I'm always asked for my credentials when running Native Access... because the NTKDaemon process wasn't running. I've actually added the NTKDaemon.app to my dock and launch it manually before running Native Access and I have no problem then with Native Access logging in like it should.

  • Winknotes
    Winknotes Member Posts: 5 Sine

    I had a system crash that I thought Zoom was responsible for but the reliability report showed it was NTKDaemon that crashed even though I didn't have any NI apps running at the time.

  • Vocalpoint
    Vocalpoint Member Posts: 104 Tri

    NTKDaemon is the primary driver of my non-stop "Native Access Reinstalling Itself" process that occurs here every second day.

    NI Support has had me perform all sorts of scans, Visual C++ library replacements and other strange requests - instead of simply reaching out to SF Green and asking why this thing so poorly coded.

    You would think that something as important as this service - would you know - work?

    VP

  • Jaybee101
    Jaybee101 Member Posts: 1 Noise

    Unstable is an understatement. I have a brand new PC on Win 11 and without fail every single day NTKDaemon crashes on boot. Every.Single.Boot. Fresh install of Native Access downloaded from the site etc, latest drivers etc. I'm not even using Native Access at all on a daily basis but it starts up and crashes :)

    The Reliability module reports that the Fault Module Name is ucrtbase.dll

    I think I'll take your workaround and just stop this thing from starting up every day and just enable it if and when I need to use Native Access.

    There doesn't seem to be any way for reporting a bug to NI? Is this forum it? No official channels to the developers? Would be happy to send logs if there was. Can't see that the NTKDaemon crash is actually harming anything by closing but it seems an exercise in futility if it's just going to boot and crash every time the machine starts.

  • Vocalpoint
    Vocalpoint Member Posts: 104 Tri
    edited March 25

    JayBee

    Welcome the jungle! I have been fighting this issue for 6 weeks now and have literally written a technical manual for NI Support on the interactions between NTKDaemon.exe (V1.1.0 to be VERY specific) and ucrtbase.dll - and all NI Support has done with all this knowledge is continue to tell me it's my fault AND make all sorts of ridiculous suggestions like sending me to bizarre links (to Major Geeks etc) for things to try.

    The key observations at this time are these:

    Firstly - ucrtbase.dll is a key Microsoft Windows C++ library that is part of every version of Windows. EVERY Windows user has this file and in four different installs here with 4 different flavours of Windows 10 AND 11 - the file is identical (v10.0.19041.789) This version is on my DAW, on my personal workstation, on my wife's PC and so on. Fair to say this is probably your version too. With the extreme commonality of this file - it is not this file causing any issues.

    Secondly - NI Support is also trying to blame the Visual C++ installers. Native Access 2 (v3.2.0) when installed to a BASE system - in my case - Windows 10 22H2 ENT that had just been installed AND has no software of any kind on it and NO existing Visual C++ Redistributables - installs two Visual C++ redistributable packages dated Oct 10, 2022 – version 14.32.31332

    These versions are a tad older than what's is current from Microsoft but work just fine AND do not alter that ucrtbase.dll file in any way. I swapped out all my Visual C++ libraries on the DAW to be extra sure I was current - but this made no difference. NTKDaemon will crash, Windows Installer will then fire up (seemingly by itself silently in the background) AND then reinstall NTKDaemon from scratch - every time I double click the file icon.

    Finally - NI Support is blaming ANYTHING but the bug ridden NTKDaemon.exe (V1.1.0) itself. And since it appears that no one is listening over there – let me state once again that Version 1.0.0 of NTKDaemon.exe did NOT exhibit any of these issues (delivered up to Native Access 2 v3.1.0) and given the exhaustive study I have given this - it it clear that NTKDaemon v1.0.0 was also using the same ucrtbase.dll that is currently installed

    The bottom line is that NTKDaemon.exe (v1.1.0) is faulty, does not play well with ucrtbase.dll and needs to be examined line by line to see what is going on here. I would also love to know what brainiac at NI thought it was a good idea to have Windows Installer step in to strip the software (silently no less) at the first sign of trouble and then try to cover it's tracks by reinstalling it right back to where it was. This is very definition of insanity.

    It would be better to simply have it crash, die and post a meaningful message on screen so the user can see what is causing the crash and try to troubleshoot it. But instead of exposing its faults - NI simply tries the install again hoping it will work right a second (third, fourth, fifth) time. Sigh.

    For such a critical piece of NI software - the fact that I even need to waste time typing all of this is embarrassing.

    After all this - I should really be offered an interview for a plum role in NI's Q&A department so I get someone to pay attention to what is going on here.

    On a slightly more positive note - I did manage to glean info from NI Support that a new version of Native Access is coming soon but of course no info on whether this new version actually addresses this issue.

    VP

Back To Top