"Please grant permission to Native Access to install dependencies" NTK - Google is FULL - fix it!
Answers
-
Ok, here is the solution! It was posted almost 2 years ago but… none of us bothered to search…
For all Windows users with the "NTKDaemon failed to start" issue:
On some systems, having Administrator privileges are not enough, if some other options are not enabled as well. Please follow the steps from this guide.
0 -
While this is (was?) a solution a couple years ago - it is very involved and might be a tad much for some to navigate - plus there are a few nasty spots in here that could cause more damage than the current problem itself.
Firstly - the version of NTKDaemon listed in that article is super old (v1.11.0) when we are currently running 1.18.0.
Not exactly sure what will happen if someone forces this super old version back into a current install - but I am guessing that Native Access (v3.11.1) will not like it.
Secondly - if a user is running any flavour of Windows 11/10 Home - there is no group policy editor. So none of the settings in part 2 of that article can occur.
VP
0 -
Yes, what you wrote are all true, however i can not see other solutions that might explain why thousands of Windows users run Native Access (and NTKDaemon) without any problem, but for some others it is not working!
It is clearly a missing permission problem, it can not be anything else.
____________________________________________________________________________________Edit:
1- I edited Jeremy's post and replaced the Native Access and NTKDaemon links with the current versions.
2- About gpedit.msc (Group Policy Editor), there is a way to enable it in Windows 10/11 Home Editions!
To install the Local Group Policy Editor in Windows 10/11 Home Edition, open a command prompt as administrator and run two one-line commands in sequence:
FOR %F IN ("%SystemRoot%\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientTools-Package~*.mum") DO (DISM /Online /NoRestart /Add-Package:"%F")
FOR %F IN ("%SystemRoot%\servicing\Packages\Microsoft-Windows-GroupPolicy-ClientExtensions-Package~*.mum") DO (DISM /Online /NoRestart /Add-Package:"%F")For convenience, you can save this code to a text file, name it as gpedit-install.bat and run it as administrator. Wait a while until DISM installs the packages from the Windows 10 component store.
Now try to run the gpedit.msc console. The Local Group Policy Editor interface should open now with no reboot required, should be fully functional even in the Home edition of Windows 10 or Windows 11 and should contains all the necessary policy sections that are available in the Pro editions! 😉
_________________________________________________________________________________________________________WARNING:
Running scripts and manipulate administrative options requires a very good knowledge of Windows!
Do NOT try this if you do not know what you are doing. The script itself is harmless. But changing values inside Group Policy Editor without a clear understanding of what each option does, it might, on some cases, cause you serious troubles.0 -
These basic "add GPEDIT to home" commands - have been shown to be incorrect.
They "appear" to work on the surface but when you start actually changing values in GPEDIT - the values do not actually change. This could get a user into some real trouble if not careful.
Stuff like this should be handled by NI Support.
VP
1 -
Ok, so lets leave the people with their problem, not be able to run their software….
In this particular case, user action is required at least for some steps.
NI Support can not "magically" enters user's computer and change Windows privileges.
It is something that only the user can do.Sure, it is not something easy for the average user, but any power user can do this quickly.
And it does work. It is tested and confirmed by many major tech sites, long ago. I have it on my 3rd computer, a laptop with Win 10 Home for almost 5 years. It is not something that i "randomly" found on "some web site".However, if for some people the method doesn't work, there is a simple extra step that has to be done.
Go to C:\Windows\SysWOW64 and copy the following folders and files to C:\Windows\System32:
GroupPolicy, GroupPolicyUsers, and gpedit.msc.Try it and you will see by yourself.
________________________________________WARNING:
Running scripts and manipulate administrative options requires a very good knowledge of Windows!
Do NOT try this if you do not know what you are doing. The script itself is harmless. But changing values inside Group Policy Editor without a clear understanding of what each option does, it might, on some cases, cause you serious troubles.0 -
I am not saying we should be letting people "not run their software".
What I am saying is this place (and the awesome mods in here like you :) posting hard core deep technical scenarios and code to run - a lesser-equipped user might see this thread and believe that this is all OK to just run, then they run it wrong or cause more mysterious issues to occur - leading to a self inducing spiral of trouble - which could make issues with Native Access look like a minor scratch.
I have seen users over the years try something that looked totally innocent one minute and the next they need to reinstall Windows after messing around too much.
A gentle suggestion to not assume that everyone is a power user.
VP
1 -
I fully agree with you, i am fully aware of what you described and i do not assume that everyone is a power user.
However, i strongly believe that knowledge has to be open and freely available to everyone, side by side of course with the necessary warnings.
Then, each one has to be self-responsible on how to use this knowledge. No matter what we do or what we want, there will always be both, the people who will use it correctly and the fools that will make bad use of it. But our primary purpose, our "duty" if you like, is to spread the knowledge, not to hide it out of fear that "might something wrong happen to someone". And after all, we all learn from our mistakes, there is no better teacher than our own mistakes… :-)…i left some serious warning however, on some previous comments.
0 -
It shouldn't be necessary to do any of these things. I run similar programs that never get stuck here. Then NI update their launcher, and it's once again broken. I'm on the newest software and made the changes and it worked. I just went to launch it again.. and BAM… Please.. BLAH BLAH. It is on NI to fix this. There software needs to be written better.
0 -
Hello guys, sorry for the late answer. The discussion seems to be a long one, however the best way to handle this issue would be contacting to support team directly.
So, if the issue persists, please create a support ticket or open a chat support using this page below:
So our team can help you to solve the issue as soon as possible.
I hope this helps☺️
0
Categories
- All Categories
- 19 Welcome
- 1.4K Hangout
- 60 NI News
- 731 Tech Talks
- 3.8K Native Access
- 15.8K Komplete
- 1.9K Komplete General
- 4.1K Komplete Kontrol
- 5.5K Kontakt
- 1.5K Reaktor
- 364 Battery 4
- 813 Guitar Rig & FX
- 416 Massive X & Synths
- 1.2K Other Software & Hardware
- 5.5K Maschine
- 6.9K Traktor
- 6.9K Traktor Software & Hardware
- Check out everything you can do
- Create an account
- See member benefits
- Answer questions
- Ask the community
- See product news
- Connect with creators