Native Access - No compatible update found

Respectfully - Windows 7 has been unsupported by all vendors for over 4 years now.

And Native Access v1 is - for all intents and purposes - retired and has not been maintained for a long while now. A permanent shutdown is scheduled for Feb 2025.

For ongoing support for your NI products - you will need to upgrade to Windows 10 (at a minimum) and consider Native Access v3.13.0 or higher.

VP

Respectfully, the OP stated windows 8.1, not windows 7 ;-)

Good catch since 8.1 was primarily mentioned and tried first. Should've be an apology for that but I wouldn't hold my breath.

And Native Access v1 is - for all intents and purposes - retired and has not been maintained for a long while now. A permanent shutdown is scheduled for Feb 2025.

Respectfully as well, you are over labouring this point to the point of disturbing. Over and over in this forum you are hardlining your rhetoric like someone waving the big stick, and using words to add more emphasis than needed to make things look worse than they are. Why dont you lay off. The fact is NA1 has been said to stop around that time next year. That means it is still active or should be. May I remind you, it was only a short while ago the fix for NA2 woes was to go back to NA1 and this was over and over and OVER again. Throughout the last couple of years this became a standard fix and yet you persist in coming down like a ton of bricks on anyone who simply wants to run their gear/software which they paid for on a working system.

Im not sure if 8.1 is out of support now. There was mention in the Dev talks of NI looking into activating peoples products offline or get something workable for legacy products. From what I can see OP only needs activation and NI needs to get something organized so people can authorize their paid for products. I can only see people getting more uptight about this and NI needs to step up. Its the right thing to do.

@Jojo123

"From what I can see OP only needs activation and NI needs to get something organized so people can authorize their paid for products. I can only see people getting more uptight about this and NI needs to step up. Its the right thing to do"

Not disagreeing with you whatsoever. But ask yourself - if it is the right thing to do - why is it not done?

I can think of a ton of reasons - the most important one being that NI (Or any other company out there) simply does not want to waste any time, talent or resource ($$$) pouring support into ensuring any machine running Windows 7 and Native Access v1 remains viable.

The vendor cannot reach out to Microsoft for any reason now if Win 7 suddenly starts acting up against internal code. Or a security breach is enacted because of Win 7 OR NA v1 connecting to NI servers.

Or the developers who wrote Native Access v1 quit eight months ago.

Or the venture capitol group that actually owns NI - sent a memo - telling the engineers to take down this broken down NA v1 infrastructure because it is a waste of time and money.

Do all of us existing customers (who have moved forward) want to read about a ransomware attack or some other ****** on the NI network only to find out some North Korea hacker group managed to get into the network via a Native Access v1 flaw or some combo of old unsupported OS?

This stuff happens daily world wide. As banks and hospitals and government agencies get hacked almost daily - it always ends up being some obscure old code or old unpatched server that was the cause.

This is a business first and foremost. The reasons why Native Access v1 needs to disappear are obvious and it has nothing to do with being a nice guy or ensuring software you bought 12 years ago is still running today.

That said - If NI can somehow come up with a way to give every Windows 7/8 user some way to permanently activate their stuff after Feb 2025 WITHOUT needing network access - I fully support that.

But given everything that they have (and have not) been able to do with their current software - I would not be holding my breath that this is a priority.

Finally - may I remind you (and all the others who are suddenly belaboring this Win 7 thing ad nauseum) - many of these Win 7 threads have been going on for over a week now - if NA v1 was suddenly "broken" and NI was really concerned about it - I think it's fair to say that someone would have jumped in by now.

VP

@Jojo123

"Well, IF, and I mean IF NI have purposely "broken" NA1 I think that's pretty underhand. It supposed to be available till Feb next year"

All I can add is that if NA v1 was "supposed" to remain available until the very last minute of Feb 28, 2025 and something technical has gone wonky in the last week (assuming inadvertently) - you would think NI would chime in to calm the masses - but no one has.

VP

Not a blip - but I believe the other thread in here with a very involved "workaround" for this condition tells the real story. See here

https://vi-control.net/community/threads/native-access-please-come-home-na-login-issue-in-windows-7-solved.154058/page-2#post-5585201

Given this deep write up - it appears that TLS security protocols that never were part of Windows 7 have now been possibly updated/activated/enabled? on specific NI servers used for authorization and this is now shutting out Win 7 permanently. Exactly the reason that these old OSs were retired in the first place.

In terms of "transparency" - especially when it comes to securing your network - no company is going to discuss the finer points of that process in a public forum.

VP

I believe I have stated over and over again that I fully support offline authorization and continue to do so.

If/when that comes to pass - fantastic.

Until then - the choice is super simple - a user can either continue to remain with Win 7 - remain completely unsupported and (now with the TLS discovery) remain completely locked out off all their stuff or move to a modern OS with known good authorization system that we all use now and be back up and running in no time.

VP