Native Access Update failed
I cannot open Native Access, it sticks on the "Self-Update" page, and that's it. I realize I'm stuck on Windows 7. But my question: I have 15 as of yet unactivated products from ProjectSAM. Costed thousands of francs. They ALL officially work on Windows 7 (that's why I bought them). But I can't use ANY of them, because I can't get to activate them via apparently the only possible channel, which is Native Access. Software's downloaded, all licence numbers clear. But because Native Access 1.14.1 (specifially for Windows 7) won't open properly, usage is completely blocked. That is ridiculous. I legally bought all the software. NI hasn't responded to my ticket, and ProjectSAM simply points out that there is a version 1.14.1 (see above - won't work). The forums are full of complaints. Does somebody know a workaround? English or German - thanks!
Best Answer
-
Hello Teajay, one of the best advices that I can give here would be upgrading the operating system, if it is possible.
If it is not possible,
We have seen more cases recently that are reporting that NA1 is not able to connect anymore. Considering that the last update Win received was at least 5-6 years ago it is possible that issue also reached Win 7 now.
So, if this is the case, you can try this workaround even if it is not promised to work surely:
The following steps will help procrastinate updating Win to a supported 10/11 version.
https://www.stephenwagner.com/2021/09/30/sophos-dst-root-ca-x3-expiration-problems-fix/
- Download the root certs mentioned in the post
- Run mmc
- install the certificate addin in mmc, choose local machine
- install the 2 root certs in trusted root cert authorities
I hope this helps☺️
0
Answers
-
I'm sorry to say, even I cannot help anyone running Windows 7. I know it's not an answer, but it is the problem. I would have (in my humble advice) focused on a new laptop first.
Did you try: https://support.native-instruments.com/hc/en-us/articles/360000407909-Native-Access-Legacy-Installers-for-Older-Operating-Systems0 -
Yes, I've tried that page. I've tried the version 1.14.1 from there - explicitly for Windows 7 systems - about 8 times, deinstalled, rebooted, reinstalled. I've tried the predecessor to 1.14.1 with the same result. All the forums are complaining that Native Access gets stuck on the self-update upon launch and does not go any further. I've tried all this on two different PCs, both with Windows 7, and both with the exact same result. I've used the tool supplied by NI to purge the registry of the entries supposedly causing the problem. I've disabled my anti-virus software and tried many other approaches. I've been at this now for 18 hours. Nothing works. Native Instruments has not replied to my urgent ticket. ProjectSAM merely points out that there is a version of Native Access for Windows 7 systems. Great support.
My customer is getting impatient as to delivery of the two commissioned compositions I must supply. There is a performance scheduled and rehearsals are planned. I've spent thousands of francs on the legal purchase of the great SAM products, have all the licence numbers and cannot use ANY of them due to an activation problem. That is ridiculous.
I do understand the issue of Windows 7 here, but if ProjectSAM explicitly states in their sysreqs that Windows 7 compatibility is given, then surely it cannot be arrested by a simple activation issue. Or more clearly: their commissioned activation partner NI should be accountable for reliable software according to the product offer.
0 -
You know that you can buy Windows 10 or 11 keys for about $20 if you know where to look. I have purchased a few recently for some older laptops..
If your machine meets the specifications, I would create a bootable USB, wipe the hard drive clean by deleting all partitions when the installer kicks off, and re-install clean with a $20 OEM key.0 -
Funny story, I actually bought an official Windows 10 for $136, as Microsoft advised that a dual boot Windows 7/10 on the same machine was possible. The framework was there, but the PC coughed and vomited from there on in, so I gave it up. But you're probably right, that the solution is to leave Windows 7. I'm not a fan, but have around 100 big and small software programs smoothly running - a proper nightmare to update/upgrade them all. And the principle persists that ProjectSAM still today says Windows 7 remains compatible, but NI does not uphold their end through a simple activation program. Thanks for your thoughts anyway.
0 -
Hello Teajay, one of the best advices that I can give here would be upgrading the operating system, if it is possible.
If it is not possible,
We have seen more cases recently that are reporting that NA1 is not able to connect anymore. Considering that the last update Win received was at least 5-6 years ago it is possible that issue also reached Win 7 now.
So, if this is the case, you can try this workaround even if it is not promised to work surely:
The following steps will help procrastinate updating Win to a supported 10/11 version.
https://www.stephenwagner.com/2021/09/30/sophos-dst-root-ca-x3-expiration-problems-fix/
- Download the root certs mentioned in the post
- Run mmc
- install the certificate addin in mmc, choose local machine
- install the 2 root certs in trusted root cert authorities
I hope this helps☺️
0 -
@Teajay Expect to put the time and effort into backup, wiping clean, and re-installing.
Regardless of expected compatibility, your Windows 7 machine has collected so much junk over the years so it is long overdue and you should have seen issues a long time ago. If your hardware is mostly compatible (you have i5 / i7) listed in your profile, and you think your Windows 7 machine has life left in it, then ensure you have a SSD and go from there.
Like you said, you've put so much into this, so why not future proof the installation?0 -
Thanks to you both for your infos! I tried the root certs with no success, then changed the environment variables according to NI support, and a raft of other things. By inserting a "skip" Self-Update into the system environment variables, I actually reached my login page for the first time again. But correct login generated an error message (on two different Windows 7 PCs) "Network error has occurred" with no further access (see attached). Same for safe mode with networking boot.
Project SAM has taken the easy way out, by discontinuing Windows 7 compatibility as of last week (thank you) and has fairly offered me a refund of software purchased, should I prefer that path. I simply cannot believe I am the only Windows 7 user on the planet tumbling to this problem, which neither NI nor Project SAM (officially) realized that it existed… and that there is no simple workaround for the elementary task of activating legally purchased software. I get that you don't necessarily want to cater for dinosaurs for ever, but I do feel a measure of manipulation and still think code-wise there should be a solution.
Don't know how I will proceed, first need to somehow complete the two still waiting composition jobs. That income would possibly help to go for Windows 11 hardware and PEACE for a couple of years…
In any case thanks to you both for your help - most appreciated.
Teajay
0 -
Try this:
https://vi-control.net/community/threads/native-access-please-come-home-na-login-issue-in-windows-7-solved.154058/page-2#post-55852010 -
Hi PatrickW - thanks a lot for the link, and it's totally astounding what Midiman's son has found out. He's a true genius. Needless to say, no luck my side. I meticulously carried out all the instructions in the outstandingly written 16 page pdf, I also put in the self-update skip into system variables and deactivated Norton Firewall. Absolute same result - network error occurred.
The mitmdump log shows every connect attempt is immediately disconnected. So it looks like I will now resort to antique software to urgently complete the two waiting comp jobs, and when I get around to activating all the as yet unactivated software I have purchased, it will apparently have to be on a new Windows 11 machine. I cannot fathom why NI is incapable (or unwilling) to provide a simple activation mechanism for such cases. Waves has a pretty cumbersome system, but it works, and there is support, even by phone to get you really far back in their Waves Central versions.
Well, NI just lost a present and future customer, as I find the development which was not communicated in any way (they have all the customer contact data) nothing less than a scandal. On the other hand, I have enough experience to know they don't have to care. 1st and 2nd level totally out of their depth.
Many thanks in any case and please keep up your awesome contributions! Most appreciated!
Teajay
1 -
Please just wipe the hard drive clean and installl Windows 10 at the very least. Spend $20. Done.
0 -
Like I wrote earlier in the thread, I purchased a legal product of Windows 10 for $136 some time back. It's not about saving a few bucks. It's about the other 89 software products which I will have to update, install and find out that many are not compatible and hence purchase upgrades (again, not about the money) and the one million settings required to get the system working properly: it's about the time consumption, the search for replacement products for those that no longer work on W10, and endless updates. So not just "done" - it's a long process. I also seriously critisize that NI provided no information whatsoever re the pending shutdown of NA on W7. I get mails from NI every day…
0 -
If you have the correct backup solution initially, this shouldn't be difficult. I cannot advise in 89 software programs that wont install again… but would like to know why wouldn't they? You will have to put the time into this. What is done here is Windows 7. Don't try and use it. Back-up and start again. What other option do you have?
If I could help you move forward I will, but you don't have any other option. You have to upgrade the OS and work it out with a better planned backup solution that lets you continue using the files compatible with the latest hardware and OS, with every iteration of said OS and Hardware/Software update, which is what we all have to do.
You know you will move forward much quicker if you spent the time doing all of the above.0 -
Obviously, you are right, and eventually, that's the only way forward. The "89 software programs" include many regularly used useful applications, meanwhile many of them no longer supported. Older data files will mostly work on updateable programs, sure. But my working life often does not allow to invest the required time capacity in order to continuously keep pace with updates/upgrades/new program versions/new OS versions. I get it, though, that if you do not, that sooner or later, you'll be at the bottom of a mountain, with Windows 11 on the other side..
I still strongly critisize the business behavior of NI, just shrugging off Win 7 customers without any prior warning (and the forums prove I'm not alone). But do realize that they don't give a rat's… for this small segment of dinosaurs.
In short terms, what kind of backup solution would you recommend? Windows system image plan or separate software? But even that won't prevent the work of keeping pace. I back up all data manually on a regular basis. Originally, I used Acronis, but hated its intrusive way, and the cumbersome retrieval of data from a proprietary data cluster.
0 -
"I still strongly criticize the business behavior of NI, just shrugging off Win 7 customers without any prior warning (and the forums prove I'm not alone)."
The entire known world was given notice - by Microsoft - for at least 2-3 years in advance - that Windows 7 would be retired in Jan 2020.
And after that occurred - you expect vendors like NI (or anyone else) to just keep supporting that OS?
You clearly do not understand how the OS Vendor/Software vendor relationship works - and has worked - for decades.
If you did not get the memo on Win 7 - that is not NIs fault.
VP
0 -
You are confusing two things. You imply that the discontinued support for Windows 7 covers all subsequent incompatibilities of all software vendors. That is wrong. A new OS does not relieve the individual software supplier from informing his customers on his specific withdrawal process - the approaches taken here are as numerous as the vendors themselves. To be clear: No, I do not expect the vendor to carry on supporting, but I most definitely do expect that a vendor would inform on that withdrawal process for his own products. It's called good business practice. A thing of the past, apparently difficult to explain…
0
Categories
- All Categories
- 19 Welcome
- 1.5K Hangout
- 62 NI News
- 785 Tech Talks
- 4.1K Native Access
- 16.5K Komplete
- 2K Komplete General
- 4.3K Komplete Kontrol
- 5.7K Kontakt
- 1.6K Reaktor
- 378 Battery 4
- 845 Guitar Rig & FX
- 429 Massive X & Synths
- 1.3K Other Software & Hardware
- 5.8K Maschine
- 7.3K Traktor
- 7.3K Traktor Software & Hardware
- Check out everything you can do
- Create an account
- See member benefits
- Answer questions
- Ask the community
- See product news
- Connect with creators