08-15-2016 09:20 AM
The compaitibility chart shows LV 2013 to be NOT compatible with Windows 10. The earliest version of LabVIEW to support Windows 10 officially is LV 2015.
08-15-2016 09:23 AM
Interesting, we have been running Windows 10 for over a year on multiple machines with hundreds of apps.
08-15-2016 09:46 AM - edited 08-15-2016 09:48 AM
@oldmanXJ wrote:Interesting, we have been running Windows 10 for over a year on multiple machines with hundreds of apps.
I said, "officially". I've seen people successfully run LV 7.1 on Windows 10. The problem with running unoffically supported LV/Windows combinations is that... well... it's not supported. And it's likely that no one will be able to explain any weird problems you might have, because of the additional issue of incompatibility in the first place.
Being that you've been using LabVIEW for twenty years, I'm sure you've seen this chart before.
08-17-2016 08:32 AM
Like I said, I installed and removed LV several times on this machine, using the link to NI that they gave me. Out of desperation I removed LV and reinstalled it using the original DVDs and updated from there.
It appears that may have fixed the problem.
08-30-2016 09:37 PM
Having the same problem of Labview error 44 corrupting programs on Windows 10 machine. Good to know that a CAR has been filed to fix it. Very annoying. Lost a whole day of work due to this.
08-31-2016 10:18 AM
What version of LabVIEW are you running? I'm running 13
09-22-2016 10:41 AM
Can anyone with NI provide an update on CAR 597858?
09-23-2016 09:10 AM
Thanks for checking back in on this. I looked up the CAR and it is still open and assigned to our R&D software engineers. As of right now there is no target date or target release version. However, there have been more reports from other customers running into this same issue, so it should be moving up in priority for R&D. All I can say is that the CAR number will be listed (597858) in the bug fixes portion of the readme in the patch that it will be a part of.
Regards,
Jason O
Applications Engineer
National Instruments
04-11-2017 12:31 PM
I upgraded to version 15 and I am still seeing the problem. My boss is about to throw LV out the window.
04-11-2017 12:38 PM
As a recap. Here is the type of error I am getting. LabVIEW: Failed to load dynamic library because of missing external symbols or dependencies, or because of an invalid file format. The file 'XXXX.vi could not be loaded. This happens now that the file is corrupted.
I keep getting an error from time to time that says I don't have permissions to access the drive when I go to save the program after an edit. I can cancel the save and ignore the error and try again and it saves it. That is a pain, but having it corrupt the file on the network drive really sucks. My IT guy is getting tired of pulling the file back out of the backups.