LabWindows/CVI

cancel
Showing results for 
Search instead for 
Did you mean: 

Ensuring the Continued Support and Stability of LabWindows/CVI

This is exactly what I was afraid of.

It's a number-bump release just to keep $$$ contracts alive.
People who sign the checks don't care; they just need a piece of paper that confirms what they want or need to believe.
But we developers aren't the ones signing the checks — we're the ones who actually have to use the product every day, and blowing smoke in our eyes isn't going to work.

I knew where this was going the moment it asked me to install the ancient Windows 8.1 SDK.

Prove me wrong.
I'll be happy to be proven wrong and eat my words.




Carlo A.
Megaris srl
Italy

Message 51 of 66
(2,528 Views)

I see many of us have been actively working to move away from LabWindows. If this 2026 release does extend the life a bit, I wanted to ask about the subscription versus buy-out options. Since the yearly cost would take about 3-4 years to match the buy-out price, it seems better to subscribe and have support available for the next year or so as we continue migrating away from the product.

What happens at the end of the year? Does it deactivate? And if so, I assume anything built with it should continue to run?

0 Kudos
Message 52 of 66
(2,497 Views)

Still in trial mode (LabWindows/CVI 2026).


It actually worries me, because I'm already encountering new bugs... after just a few minutes of use.

 

Uncorrected :

- C:\Program Files (x86)\National Instruments\CVI2026\toolslib\toolbox\menuutil.h :

  line 100 : #define MU_PutFileListInIniFile MU_GetFileListFromIniFileAnsi

- And (same library) file names text, with encoding issue, in the "Recent" menu :

  C:\Users\Public\Documents\National Instruments\CVI2026\samples\toolbox\menudemo.cws 

 

New :

- Into an UIR file, add a picture control : Try to load an image, JPEG file and "An unspecified error has occurred, probably due to corrupted data".

  Others file types seemOK.

 

To be continued in the next episode.


Certified LabWindows/CVI DEVELOPER (2004)
LabVIEW since 5.01 | LabWindows/CVI since 4.01
0 Kudos
Message 53 of 66
(2,491 Views)

Still wondering if I should install it, but the initial reactions seem very disheartening to say the least.

Rolf Kalbermatter  My Blog
DEMO, Electronic and Mechanical Support department, room 36.LB00.390
0 Kudos
Message 54 of 66
(2,446 Views)

@rolfk wrote:

Still wondering if I should install it, but the initial reactions seem very disheartening to say the least.


I’m also a bit disappointed — the backend still relies on Clang 3.3, a compiler released over thirteen years ago.

Screenshot 2026-07-29 22.52.41.png

0 Kudos
Message 55 of 66
(2,404 Views)

Based on what I read from you it seems to me that this "new" release is dead code.

Vix
-------------------------------------------
In claris non fit interpretatio

-------------------------------------------
Using LV from 7
Using LW/CVI from 6.0
0 Kudos
Message 56 of 66
(2,388 Views)

So one week after the unexpected/anticipated/... release of CVI 2026Q3 on the download page we, the users, are discussing if there are any new features or bug fixes... But still there is no official announcement, no list of changes, bug fixes...

What happened to our new product manager, Xavier?

 

So somehow it looks like a re-compilation of previous code which has at least one benefit - the same old CVI now installs on newer versions of Windows, too. This is certainly a good thing, if it's worth the price tag...? But who knows, maybe the developer was running out of time and had to postpone all the good new features to version 2026Q4 😁

 

Message 57 of 66
(2,372 Views)

Hello friends

 

Below are NI official replay about readm, FYI

 

I am not feel satisfied, because 

 

1 The all reply no details info, such as which driver be updated;

2 The reply like is NI R&D general replay, may be more is polite replay, NOT Engineer accuary replay;

3 And, This time release is only one time no release notes in the past 20 years release history, I think NI R&D software leader / product leader / quality leader should be held responsible for this accident(Its right from software engineering side it is), or may be NI no people care for this CVI product line;

 

Summay, This is signal we are like CVI users wait 6 years but no result, I personal decidedly switch to open source source for future project.

 

YOAFAFA_0-1785919839867.png

 

0 Kudos
Message 58 of 66
(2,132 Views)

I followed your link and got this:

Screenshot 2026-08-07 092503.png

 

Not exactly a good presentation some week after the announcement...



Proud to use LW/CVI from 3.1 on.

My contributions to the Developer Community
________________________________________
If I have helped you, why not giving me a kudos?
Message 60 of 66
(1,997 Views)