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

[AllenInIowa]

UPDATE:

It appears to be something that has changed on my development system -- possibly a change in Windows 11.

Using our version control, I went back in time to the last time the installer worked -- 1.17.9008 -- and rebuilt it. Since I built then checked it in, it remembered it was at 9008 and built a new 9009 version.

That version also gives the DLL error.

So the build I did on that day originally, works, but going back to those files and building today, does not.

I believe Windows 11 is not a supported platform for CVI/2017 and CVS/2019, and was not even supported on 2020 until they released a patch. Maybe we are out of luck.

[AllenInIowa]

---

@rolfk wrote:

You still haven't answered what NIPM version is on your system. The change could come from some NI component that was updated for whatever reason. Did you install or upgrade any software from NI recently? Even a small driver could have caused this.

---

I do not know what NIPM means in this context.

We have LabWindows/CVI 2017, and a patch for it. I have never seen any updates to it as long as I have worked here.

[Scott_Richardson]

The product being installed are under directories under C:\Users\User\Desktop\CVITest\TestInstaller32\Volume\bin\. The dp directory is your program, and everything else is an NI product. The lower numbered directories usually contain metauninstaller, eula, dotnet, vcruntime, cvirte, etc.

If you look at the "..\supportfiles\customResource0009.dll" file, what is the file version in Details tab of Explorer Properties?

Not finding the DLL might be due to security protection software. Any software worth noting?

The DLL is not signed and it is being loaded into an elevated process. You could look at Windows Events, specifically Application, and Security events to see if something shows up?

You are copying the file to the system, could the file be locked in some way; see if there is any restriction in the Properties of the file in Explorer?

[AllenInIowa]

Well, 2020 seems to be not an option. Trying to install it produces "Coult not find product 'ni-cvi-2020_20.0' 😉

What a fun day.

[Scott_Richardson]

Are you running the CVI installer via the ISO, or using NIPM Browse Products, or the online installer?

CVI 2020 should install NIPM, did that install or is the require version already installed?

[AllenInIowa]

I downloaded the installer they gave me -- an online one. It fails. I manually ran the package manager (that got installed) and was able to select 2020 from that, and it's been installing away ever since. I'll soon know if this produces a working version.

Looking at the earlier build's Distribution Kit settings is identical to what i have selected today, other than version and Product/company name text, and which .hex files we include. I am fairly confident at this point it is an issue with changes that happened on my system.

I need to find a system here I can clean install Windows 10 on and see if it works there.

[AllenInIowa]

Installing LabWindows 2020 and building the installer also does not work, so that's not a solution.

Worst case is I'll have to see if I can reset my PC back to default Windows and install LabWindows clean and see if that works.

[AllenInIowa]

S.W.T. Confirmed!

"Strange Windows Things" are what drove me to Mac back in the early 2000s, and this seems to be one. I uninstalled everything from my laptop that was NI related (first using the NI package manager, then removing the package manager). I found nothing left that had "National" or "Lab" in my Add/Remove Programs.

I installed fresh, and then created the User Interface Template project, and enabled a Distribution Kit for it.

When I try to run that on the fresh systems, I get the DLL error.

When I do the same steps (install LabWindows fresh) on my Windows/Arm system, and then build the same template project, that installer runs just fine on the fresh systems.

So . . . my PC is messed up. I am hoping to find a solution before I have to talk to our IT person and explain I need to reset everything and then they have to reinstall whatever monitor/scanners they put on them.

[AllenInIowa]

MORE INFO:

Hmm, one off thing. Even after removing all the NI stuff, and then reinstalling from two downloaded zip files (2017, then the 2017 patch), I see it has the "2020f3" runtime.

When I install those same two zip files on a fresh PC, they show the 2017 runtime. I have had the 2020 evaluation on my laptop before, but I do not understand why it is still there after an install via the NI Package Manager.

This is a difference, though I don't know why that would have changed on its own. I tried the 2020 eval out way before that.

[AllenInIowa]

And, when I manually download the NI Package Manager (it does not appear to be part of 2017), I can find in the list the "Shared Runtime" being 2020f3 version. I never installed that -- just the zip files. I am manually removing that (which takes off LW2017) and then will try to add LW2017 back using the Package Manager and see if that does anything.

I would just like to get rid of the 2020f3 and see if that fixes this issue. The other computer I installed the same zip files on shows the 2017 version.