Windows 11 and LV 2015

[PaulG_CS]

Anyone have any experience with Windows 11 running LV 2015? We've been running Win 10 with no issues but I am NOT assuming I won't have problems moving to IT-mandated move to Win 11. I also realize my situation may be too much of an outlier to expect a favorable outcome. 😁

[billko]

I think there's a fair chance it will work, but it's not a supported config, of course...

[Kyle97330]

We have tried LabVIEW 2016 on Windows 11 on exactly one PC and it worked OK.  Not exactly the same situation, but close.  Our IT isn't pushing 11 very hard... we're still using 7 on a number of PCs because there is some old hardware on them not supported in 10 (32-bit drivers only).  If you do run into issues, consider checking to see if your IT department would consider remaining on Windows 10 but with very strict firewall settings (such as only allowing connections on whitelisted sites and ports, for example).

As a general guess, but not something I can give a specific example on, I would venture that there is a high chance of success in getting the basic development environment running, but the likely areas of problems are going to be more likely to come up if you use specialized devices that connect more "closely" to the PC.  By that I mean GPIB/serial/Ethernet devices are very likely to work fine as long as the bus connection works, but if you have USB/PCIe/etc. devices it's less likely since those connect directly and are a lot more dependent on the device drivers not having interoperability issues with the OS.

[Intaris]

If you're doing any FPGA development that needs IPCores to be compiled on ISE-compatible targets, anything above Windows 7 seems to be problematic.

Generation of the IPCores returns with an error.

I maintain a VM with Win7 and my FPGA development tools for this very reason. AFAIK, Vivado-supported targets are not affected. So this makes it a corner case, but one I've been unable to resolve to date.

[PaulG_CS]

I'm not doing anything with FPGA or anything else that complicated, fortunately. Just a bunch of DAQ systems running 2015 and connected to the network for data transfer. The most current version of NI DAQ we can use is 18.5.

[RTSLVU]

---

@PaulG_CS wrote:

I am NOT assuming I won't have problems moving to IT-mandated move to Win 11. I also realize my situation may be too much of an outlier to expect a favorable outcome. 😁

---

Not an outlier at all. I just went through this with our IT and had them roll my development laptop back to Windows 10. But in my case it was not LabVIEW itself but an instrument driver that was not compatible with Windows 11. The company who provided it said they were not going to fix it because the instrument was obsoleted last year.    

Our IT also balked at the idea of not having the latest and greatest Windows version. I explained to them that our company has spent hundreds of thousands of dollars on this test equipment and the chances of them spending that much money again simply because your department does not want to support an "old OS" is less than zero. 

A similar argument might work for you. If not, tell them that if it doesn't work they will have to make it work. Even if that means they will have to buy LabVIEW 2023 and take on the associated yearly subscription fees out of their department budget.  

Trust me when it comes down to $$$ decisions and policies can be changed quite easily. 

[santo_13]

I do resonate @RTSLVU's comments.

Escalate the consequences of not being able to use your DAQ System just because IT chose to upgrade. Now, if the DAQ system is critical for your work, your managers will get IT to bend backwards or if they can't they will either upgrade their DAQ system or live without the DAQ system.