

This article from Microsoft explains how to do this. In this case, you would not have to disable the Controlled folder access option. Note: it's also possible to add the Native Access application to the allowed list of friendly apps. The activation should now work as expected. Disable the option under Controlled folder access.Might not help, but if using safari, switch to chrome.if that does not help, try switching the default dns from your isp to google dns or cloudflare. Select Virus & threat protection, and then choose Virus & threat protection settings. Something is blocked the password to login into NA.Choose Windows Security > Open Windows Defender Security Centre.

NATIVE ACCESS SERVER PROBLEM UPDATE

This can be done by right-clicking the "Native Access.exe" and selecting " Run as administrator".Ģ.2 If unable to create the Native Instruments folder Now open Native Access in administrator mode.Important note: Do NOT navigate to "C: > Users > *Your Username* > Documents"!Ģ.1 If missing the Native Instruments folderĬ: > Users > Public > Public Documents > Native Instruments > Native Access > ras3 Now open Native Access to check if the products are now activated.Macintosh HD > Users > Shared > Native Instruments > Native Access > ras3 The folder structure should then look like this: And finally, within the "Native Access" folder, create an additional folder named " ras3".Within that "Native Instruments" folder, create a new folder called " Native Access".In this location please create a new folder and name it " Native Instruments".Please note that if you can't carry out the steps in chapter 2, you might be missing the “Native Instruments” folder at the above location. 2.1 If missing the Native Instruments folder Delete the " Native Instruments" folder.This can be solved by following the steps outlined here: Your activation fails because of corrupted or missing activation tokens Ensure that you are logging in with the same email address you initially used to register your NI products. It may be that you are logged in via Native Access with the incorrect account (Native ID).
