Win 11 Labview 2021SP1 DLL Error 13

[ngthai]

Win 10 Labview 2021SP1 Dll is working fine.

I have another laptop running Win 11 on the exact same labview program, but got error #13. Is this because Win 11 or because I did something wrong when installing Labview 2021 SP1 on the Win 11 machine? Could any help me fix this? Thank you

Error 13 occurred at Call Library Function Node in NGAPA_DLLMapNodes.vi->GPC Acquisition.vi

Possible reason(s):

LabVIEW: (Hex 0xD) Failed to load dynamic library because of missing external symbols or dependencies, or because of an invalid file format.
=========================
Shareable board exclusively owned.

[rolfk]

That’s not a LabVIEW error but your DLL has external dependencies that are not present on your Win11 system. From whom is that DLL? Do you know what compiler and its version was used to create it?

[ngthai]

Thanks. Didn't know that simple thing. Thought that DLL compiled in Win 10 would be OK.
I re-complied my DLL in Win 11 (nothing changed) and now Labview working fine

[ngthai]

Hello @Rolfk (Rolf Kalbermatter) and every one,

I still need help.

Labview 21.0.1f2 (32 bit), linked to DLL (compiled from Visual Studio 2022 C++ in Win11 machine) - they all work fine in this machine, which is Win 11 Pro, 22H2, OS build 22621.819.

I then built an installer.

However, when running that installer to another machine Win 11 Pro, 21H2, 22000.1219

my built-application would throw an error on the new DLL.

I manually replaced that new DLL with my old DLL (from the previous Win 10 version), and it worked.

What's going on here?

Please help.

[ngthai]

For some reason, my new question didn't show up. Show I'm posting again:

Hello @Rolfk (Rolf Kalbermatter) and every one,

I still need help.

Labview 21.0.1f2 (32 bit), linked to DLL (compiled from Visual Studio 2022 C++ in Win11 machine) - they all work fine in this machine, which is Win 11 Pro, 22H2, OS build 22621.819.

I then built an installer.

However, when running that installer to another machine Win 11 Pro, 21H2, 22000.1219

my built-application would throw an error on the new DLL.

I manually replaced that new DLL with my old DLL (from the previous Win 10 version), and it worked.

What's going on here?

Please help.

[rolfk]

Your Visual Studio 2022 installed a new C/C++ runtime library (V14.30 or newer) on your machine too (or it may be even present in Win11 22H2 maybe). But your Win11 21H2 does not have that version installed (It contains tools compiled with Visual Studio so there is a Visual C Runtime but since it was released before Visual Studio 2022 was available they were compiled in Visual Studio 2019 and there would be a version of Visual C runtime 14.20 to 14.29 present on it).

While the C/C++ runtime is upwards compatible since Visual Studio 2015, they still need to be present in AT LEAST the version that was used to compile an exe or DLL.

Your DLL knows to what C runtime it was linked to at build time and will refuse to load if not at least that version is present (and may refuse to load if Microsoft ever switches to a new major version 15.x and only that one is available).

Make sure to install the version of the C Runtime installer mentioned on this page under 2015, 2017, 2019, 2022 for the platform and bitness your DLL was created for. It contains the latest C runtime, at this moment 14.34.

[ngthai · Accepted solution]

Thank you for your solution.

It turned out Visual Studio 2022 V143 build is the culprit as you mentioned.

I uninstalled VS2022 and installed VS2019, which use V142 build. Now everything works in all machines, Win 10, Win 11.

[rolfk]

---

@ngthai wrote:

Thank you for your solution.

It turned out Visual Studio 2022 V143 build is the culprit as you mentioned.

I uninstalled VS2022 and installed VS2019, which use V142 build. Now everything works in all machines, Win 10, Win 11.

---

This is still no guarantee that it will work on every machine if you ever intend to distribute it to users! What Visual C runtime is installed on which system does depend on which Visual C version was used to build the tools for Windows. But it also depends on which other applications may or may not be installed on the system. Every professionally developed application will have an installer and this installer will ALWAYS launch the according Visual C Runtime installer that the developer knows his application to require because of the Visual Studio version (s)he used. If the same or a newer one is already installed, it will simply silently skip the installation, otherwise it will upgrade the installation.