LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Windows 10 compatibility with applications developed in LabView

Solved!
Go to solution

I've done both without issues, it's important to use the correct DAQmx-versions though, 14.5 is the last that supports LV2011.

/Y

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 21 of 25
(1,782 Views)

Hi Baji,

I am having a similar issue as the one described on this post. I previously installed labview 8.5 on windows 10 but its not working and im not able to install labview 8.6 since it shows me an error 12 , do you know how to fix it ? could it be related to windows net framework ?

 

labview.jpg

 

0 Kudos
Message 22 of 25
(1,345 Views)

I can't tell you why it is happening, but I can tell you NI won't support that old of a version of LabVIEW in newer Windows versions.  As shown in this table the first version of LabVIEW that is supported in Windows 10 is 2015 SP1.

 

http://www.ni.com/product-documentation/53409/en/

0 Kudos
Message 23 of 25
(1,336 Views)

I never tried installing LabVIEW 8.6 on Windows 10. But I tried running LabVIEW executable on Windows 10, which built in LabVIEW 8.6 on Windows XP machine and it runs without any issues.

Balaji PK (CLA)
Ever tried. Ever failed. No matter. Try again. Fail again. Fail better

Don't forget Kudos for Good Answers, and Mark a solution if your problem is solved.
0 Kudos
Message 24 of 25
(1,317 Views)

I did install evrery LabVIEW version from 7.0 to 2015 on Windows 10 more than 2 years ago and that worked fine, you just had to make sure to always install everything for a particular LabVIEW version including all Toolkits before starting with the next higher version. However I found recently that I can't start up LabVIEW versions 8.0 to 8.6 anymore on that machine. The process simply dies very early on during startup before anything substancial can possibly be done and without any failure messages.

I'm not sure what the trouble is it could have been one of the Windows 1803 or 1809 updates or any of the many KB fixes in between or the installation of LabVIEW 2016 or 2017 since. I didn't notice until sometimes last fall as I didn't use those version at all normally.

Rolf Kalbermatter  My Blog
DEMO, Electronic and Mechanical Support department, room 36.LB00.390
0 Kudos
Message 25 of 25
(1,311 Views)