"Please grant permission to Native Access to install dependencies" NTK - Google is FULL - fix it!

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.

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.

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.

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.