This discussion was created from comments split from:
NTKDaemon for Native Access won't install
.
"I have solved the issue" without actually telling us how the issue was solved probably shouldn't be "accepted" as an answer. :(
I am having this problem, pretty much verbatim, in Jan 2026. I have tried all of the things listed in the Original Post with the same
Oops! Anyway, I have tried things like reboot, ensure NTKDaemon is not installed, install using the NTKDaemon standalone installer, reboot, ensure that NTKDaemon is running, run the NA installer, NA installer immediately uninstalls NTKDaemon and then fails to install it.
Warning: old support posts link to older versions of NTKDaemon. I have no idea what the latest version is, but am not trying again with 1.28.0.0, the most recent version I can find.
(Sorry for the multipost — no way to edit.) And that confirms it. NTKDaemon release_1.28.0.0_DaemonFullINstaller_Win.zip fails to install on a clean boot with the same error "failed to start, do you have sufficient privileges", so clearly the problem is in the installer (this or a similar version) bundled with NA.
This is on an up to date Win 10/64 with nothing installed except Bitwig, some NI apps (previously somehow installed by NA, I have no idea why that worked), and a couple of IK plugins. Well, hope this helps somebody to … not bother trying all of the stuff I did and wait for multiple reboots in the hope of a solution. There isn't one.
Please do not thread hijack. Criticizing original thread starter and then turning a thread already marked as solved into something about your own issue is neither on topic nor productive. So I have split your comments into a new question.
In general there is no problems with Native Access on Windows 10 , 64 bit, so I have to say that your claim that NTKDaemon will not install on an up-to-date Win 10 , 64Bit installation can only mean that there is either a problem with your Windows installation (or a Windows component - e.g. PowerShell), or a problem with your user account , a problem with another program blocking or a problem with a dependency.
If you can not get your problem solved by getting the problem solved by using the forum or you do not want to bother to try to solve your problem using the forum then please contact N.I. Support (all) and ask them to help. Possibly you should wait doing so until the 'Preliminary Insolvency' issue has been solved since Support at present is overloaded , but if you can not wait then please contact N.I. Support (all)
QuoteTedd from NI , 2026-01-28 :
be prepared to wait and kindly practice some empathy for the very hardworking, stressed out humans who are now fielding a large amount of requests on top of their normal day-to-day.
Your post is severely lacking in detail.
All you have said is an "up to date version of Win 10". That can mean many things - considering Windows 10 was retired on Oct 14, 2025. So it being "up to date" - is a question mark for me.
Please provide a full readout of what you are using (PC, CPU, version numbers AND "flavour" of the the OS (HOme, Pro etc), Native Access version).
There are no issues on an "up to date" version of Windows 10 Pro 22H2 here - but my version IS actually supported. You need to confirm your ESU registration as well.
VP
@tekhedd If you were not able to fix the issue, please get in touch with our support here: https://support.native-instruments.com/hc/en-us/requests/new
