#Native access update update

pull your bloody socks up guys, you are wasting many hours for people just trying to start up because of your stupid and very poor Native Access set up.

It begs the question why the hell are we still having this problem? Don't they field test their native access software? It seems 100s of people if not more are having this problem and the NI support is useless. You need to download notepad++ as well (easy to do) and it finally worked!! but then the log in button won't work (facepalm moment again) but this following process worked for me on this post The last couple of updates I have seen from them have been to their installer.

#Native access update update

Then reopen native access (I did also see a post about downloading a latest 圆4 microsoft visual C++ file from microsoft support, which I did, but have lost link now, from doing the reboot needed, but not sure if this solved anything or is needed, but if this fix I listed doesn't work for you then search it up, it's on this forum somewhere)Ģ) This then got me past the locking update page to the login screen this time. hit ok and then close native access with end task. chack box in compatibility mode and selected windows 7. Native Access locked on opening with 'looking for update page'ġ) run Native access - locks - open task manager - right click on native access - click properties - click compatibility tab.

Here was my solution so as to maybe help others (as NI can't be bothered to help properly): The solutions on their help page are rubbish and it has been down to wonderful and bright people on forums to solve it and pass on solutions to others, which is truly disgraceful from NI not doing it themselves. Given this has clearly been happening for a long while, at least 2 years it seems, it appears the NI tech dept are bloody useless/lazy/don't care or whatever, which is a real shame as it's really off-putting for what seems to be a brilliant home studio product (although not able to run it yet to find out!!). Solution here to help for others stuck on this like I was - I had the same issue.