How to solve this situation？
Hello Muyu Cat,
If the issue perissts, can you please create a support ticket or open a chat support using the link below:
https://bit.ly/NI_support_NA
So our team can help you further with this case.
I hope this helps☺️
Hello,
please run Native Access as an Administrator, otherwise, follow the steps from this article:
https://support.native-instruments.com/hc/en-us/articles/13712583860125-Native-Access-Error-Please-grant-permission-to-Native-Access-to-install-dependencies
@Sunborn Thank you.But ,I still can't solve my problem. I got your step.But the result didn't change.
That's strange, it is rather a simple step….
Did you opened Native Access as administrator?
Native Access should be completely closed before you do that.
Also make sure that you close the NTKDaemon service through your Task Manager (right-click —> End task).
Then restart Native Access as administrator.
If still you have no result, then please contact NI Support, here:
https://support.native-instruments.com/hc/en-us/categories/360000053677-Native-Access
@Sunborn I can't find the file that named NTKDaemon!
I delete it and download it again.But it didn't take effect.
I also followed the official instructions, but I still can't open the latest update of Native Access. I have to go back to the previous generation to open it. It is really troublesome and disturbing.
@Mert_NI Thank you for your help.Actually,I tried it.Out of my expectation,I can't open the website of NTK Daemon installer.
@YUKIKA What is the previous generation?
3.16.05 3.16 can be opened normally, but 3.17 cannot be opened after installation. Reinstall 3.16 and it works normally It's very unfortunate that it will be automatically updated to 3.17. It's a disaster.
@YUKIKA Where can I download 3.16.I can only download the latest version.
If you have a problem with the version 3.17 then to see if that fix the problem :
then try uninstalling both Native Access and the NTKDaemon
then also use the N.I. reg tool to remove any remnants of bot Native Access and NTKDaemon
then reboot PC
download the latest version of Native Access for your OS and run and install it as an Admin
Then also both run N.A. itself as an admin and give the Native Access ample time to load, especially first time it may take some extra time to load.
Hello. Thank you for your reply and suggestions.
Although I agree with your idea and have thought about implementing it, there is a question that prevents me from agreeing and taking action.
I just hope that the official will release the next stable version as soon as possible, or let me continue to use the previous stable version and will not let you update without knowing it. Sorry, I'm not targeting anyone, but I want a stable product, not a bomb.
"why should i waste my time updating to 3.17"
First of all, for the obvious reason that you must update anything related to software, in general (unless only if your system does not support it):
To get fixes, improvements and new features!
Specifically in 3.17 you are missing the above:
ADDED
Added "Create a Support File" feature in Help menu to assist Customer Care Added feedback mechanism--Native Access will ask from time to time about your experience
FIXED
Fixed crashes at shutdown Fixed crash under specific conditions during downloads Fixed incorrect error message after failed update installation Fixed issue where product dependencies alert wasn't always being displayed Fixed progress bar not showing correctly after failed Kontakt install Fixed Add Serial dialog sometimes not correctly pre-filling serials Fixed issue where content directory detection did not work when a path was malformed Fixed issue where content version became desynchronized on disk Fixed accessibility issues Updated log locations Updated NTKDaemon application icon (old icon may temporarily be cached)
REMOVED Removed the ability to customize VST2 locations on Windows
__________________________________________________________________________
Secondly, because 3.17 is working perfect for the 99% of users. In my case, in an older system than yours, Windows 10.
This post is the only post in the entire forum who reported a problem with that version.
But… the point is that your problem (and every similar problem) is not really related to Native Access. It is related to a bad habit from the past:
Users are actually "guests" instead of admins, in their own system! 3 years here, i wrote it over a dozen times. To not have admin rights in your own system is a really bad, bad practice! And the one to be blamed for this stupidity, is of course Microsoft and its phobic policies and false warnings who only terrorize the average user.
It's been over 6 years that everything is running smooth in my computer and never encountered the slightest problem with NI or any other software. For one simple reason. I have permanent admin rights on my own machine, as anyone should! The worst thing that might happen ever, is to restore Windows: Which is just 2-3 clicks and less than an hour of automated by the system, work. You just go for a short walk, and your system is back as it was before your mistake.
So, there is literally nothing to be afraid of, instead, you are loosing a lot by not doing this. The very least to gain, is to avoid some really simple and silly problems such as this one ("Please grant permission" etc. etc. etc.). 🙏
