Installer does not work on different PC

[JulianNL]

I have created an installer, which is working on my PC. I have used Labview 2022 Q3 (32-bit) on a Windows 10 pc.

When I try to install the application on a NUC (windows 11), the installer does not work.

The error is:

.\source\MetaInstaller\ConfigInfo.cpp(2506): InstallerError 10007

Fatal Error. Unable to load a resource DLL. 

Unable to load the custom resource file "File path" because Windows error 126: The specified module could not be found. while attempting to load the resource DLL "same file path"

When I searched for the file, I found the file at this location.

I tried to install the software with an error log according to Creating an Error Log File for a Software Installation - NI

But this does not generate a error log.

[Bob_Schor]

What is a "NUC"?  Why not install Windows 10 (which has a "sure" history of working with all "recent/current? versions of LabVIEW?  [In the "old days" (pre Q3), many seasoned LabVIEW experts waited until the SP1 version was released to install the "latest LabVIEW" ...].

Bob Schor

[ZYOng]

Running Executables or Installers on Different Windows Versions

Installers and executables are only guaranteed to work on the operating system they are built on.  For example, a Windows 10 installer or executable may not work as expected on a different Windows version (e.g. Windows XP, Windows 8, or Windows 7).

[JulianNL]

A NUC is a kind of pc. You can google for pictures if you want. Currently, I installed Windows 10 on the NUC, but it didn't work. I was able to install the program with the same installer on a different PC today. 

[JulianNL]

Does this also apply for building on windows 10 enterprise and installing on windows 10 pro?

[RTSLVU]

Well there's nothing special about a NUC, I would guess it's Windows 11 that is causing you grief. I can't say that I have tried installing an executable built on Windows 10 on to a target machine running Windows 11. But I have built on Windows 11 and installed on Windows 10 without issue.

Try rebuilding your installer.