LabVIEW executable on Win 11 and Measurement Computing USB 2418

[LVNinja]

I created an application with LabVIEW 2020 32 bit on windows 10 using a Measurement Computing USB 2416. 

The computer is now upgrated to Win 11 and the application no longer works. 

I generated a new exe version with LabVIEW 64 bit on Windows 11, but it still doesn't work.

I can run it with LabVIEW development but not with Exe. 

Anyone has faced similar issue ? 

Does .NET has anything related to this issue ?

[AnalogKid2DigitalMan]

I came across this once on a new PC where an older version of .Net was used by the program.

That version was available on the PC but not active, I think I had to go into Windows 'Features' to bring it alive.

YMMV.

-AK2DM

[RTSLVU]

It's been a long time since I used MCC DAQ devices but I remember they needed proprietary MCC DAQ software (Instacal?) to be installed and the DAQ device configured in it before LabVIEW development environment or executable could "see" the MCC DAQ device.

Have you tried reinstalling or upgrading the MCC DAQ software on the target machine?

[LVNinja]

Hi 

Thank you for your message. Yes I reinstalled Instacal, but the executable now shows a broken arrow and would not run. 

[Eric1977]

---

@RTSLVU wrote:

It's been a long time since I used MCC DAQ devices but I remember they needed proprietary MCC DAQ software (Instacal?) to be installed and the DAQ device configured in it before LabVIEW development environment or executable could "see" the MCC DAQ device.

Have you tried reinstalling or upgrading the MCC DAQ software on the target machine?

---

Instacal is correct. Here's the page for ULX for LabVIEW and accompanying documentation.

I have a USB-TEMP DAQ device that I've always wanted to hook up & use but I have not had a project come along that would use it.

[LVNinja · Accepted solution]

FIXED Issue:

Re-Installed the latest Instacal and Drivers. 

Updated the windows to use the .net 3.5 and olders 

Copided the DLL to the same folder as the main application. Before, it was stored in a separate folder. 

Executable works now. 

Thank you all for colaboration.