CVI/2017 new installer issues (customResource0009.dll not found, but is there) - suddenly showing up on LTSC and Windows Arm.

[rolfk]

You can have zig runtime installations next to each other. And they don't automatically get removed and are usually not even listed itself, since they can and usually are a dependency of some other compiled LabWindows app. That could be anything you installed and was at some point created with LabWindows. And that developer might have gone to great lengths to try to hide that they used LabWindows for it.

There were for instance NI Max versions that included test panels that were in fact created as LabVIEW or LabWindows executables. And somewhere around 2020/2021 the according Installer Framework of NI had a change that simply prevents creating installers that can be still installed on Windows 7 and 32-bit Windows OSes. It doesn't matter that you use LabWindows 2017, if any NI software from 2021 or later is installed, the according framework is updated and your LabWindows Installer Creater lost its ability to create Windows 7 or older compatible Installers. Even just upgrading NI Package Manager to a version newer than that is enough. And in order to install NI software of a certain version your NI Package Manager has to be that version or newer.

[AllenInIowa]

Thanks, Rolf! This matches a theory I was testing today:

1. Why does the 2020f3 show up? Where did it come from? Sometime earlier, I installed some NI stuff to get GPIB drivers for reading a power meter. THAT may be where this was introduced, and that was earlier in the year, and the installer builds went bad earlier in the year.

2. Fresh install always shows 2017, and those work. The 2020 shared library seems to be the culprit.

After removing all the files with NI Package Manager, then uninstalling AGAIN (I do not believe I did anything different), another fresh install of LabWindows 2017 now shows the 2017 shared runtime.

That installer looks like it will work -- but I am waiting for our embedded PC to reset to defaults to fully confirm.

If this is the case, then I think the NI GPIB stuff was where things went wrong.

Would us upgrading to the 2020 release prevent this from happening?

[AllenInIowa]

No luck. Even getting my laptop to show the 2017 shared runtime, and building that, it produces an installer that won't work.

Time to Reset my PC...

[AllenInIowa]

Resetting my PC and reinstalling has our installer working again on fresh systems.

S.W.T.s really bug me ("strange windows things").

[Scott_Richardson]

Glad you have a workaround, sorry we couldn't figure out the root cause.

[AllenInIowa]

---

@Scott_Richardson wrote:

Glad you have a workaround, sorry we couldn't figure out the root cause.

---

Paraphrasing Douglas Adams…

”Ah, this is obviously some strange usage of the word ‘workaround’ that I wasn’t previously aware of.” 😉