NI-MAX duplicate entries in Software tree

[ErikL68]

Has anyone else run into this issue? Strangely, it's only the newer elements that are duplicated, and some are not (notably NI-MAX's entry). Everything is working fine, but this is concerning. NI-MAX version 2025 Q3.

I've performed a Reset on the Configuration Data (from the Tools menu in NI-MAX) and restarted the PC, but the duplicates remain. And I didn't see any notifications in the Known Issues for MAX (MAX and System Configuration Known Issues and Bug Fixes - NI) though it doesn't appear any entries for MAX beyond version 20 exist.

I've got multiple PCs exhibiting this, including a few with minimal installs (DAQmx, VISA, 2025 Q3 64-bit Runtime, and only other elements that were packaged with these).

Any suggestions? I hate to just ignore it.

Thanks,
Erik

[alexderjuengere]

Has anyone else run into this issue?

yes.

probably irritating but unrelevant.

I believe to remember this kind of conduct has been around for a few years (~2023), but I might be wrong

[Bob_Schor]

---

@ErikL68 wrote:

Has anyone else run into this issue?

---

I can also answer "Yes", but can add a little more information.

My installation on my personal Laptop which has LabVIEW 2024 Q3 (64-bit) as the only version of LabVIEW installed has a Software listing in MAX that looks similar to Erik's.

But wait, there's more ...

At work, our IT folks have some "scanning" software that they run every Monday that "looks for vulnerabilities" and asks us to remediate them.  One of my colleagues keeps getting flagged with LabVIEW patches (I'm doing this from memory, but something like "LabVIEW Runtime 2024 Q3 Patch 4").  What's strange about it is that NIPM shows that Patch 4 and Patch 6 are installed, so I "reasoned" that if we used NIPM to remove Patch 4, the problem would go away.  It didn't.  I honestly think this is a bug in the "monitoring" software IT is using, but that's a difficult argument to make!  

It is difficult to "pin down" the IT folks who are worried about protecting the network and don't understand software development (particularly not a graphical data-flow system like LabVIEW).  I also don't know whom to contact at NI to ask for assistance in removing "traces" of patches that I "uninstalled" through NIPM, but still show up on the "Scan for vulerabilities" routine that IT is running (software whose name I don't know).

Bob (Frustrated) Schor

[softball]

Hi

Just a guess. Could the root of the problem be related to multiple patches released in July 2025 to fix a CIN security problem :

https://www.ni.com/en/support/security/available-critical-and-security-updates-for-ni-software/code-...

Affected Products

Product Version	Mitigation
LabVIEW 2025	Upgrade to LabVIEW 2025 Q3 or later from NI Package Manager or Software Downloads
LabVIEW 2025 Q1	LabVIEW 2025 Q1 Patch 3 – In Work
LabVIEW 2024	Upgrade to LabVIEW 2024 Q3 Patch 4 or later from NI Package Manager or Software Downloads
LabVIEW 2023	Upgrade to LabVIEW 2023 Q3 Patch 7 or later from NI Package Manager or Software Downloads
LabVIEW 2022	Upgrade to LabVIEW 2022 Q3 Patch 6 or later from NI Package Manager or Software Downloads
LabVIEW 2021 and prior	Not in Mainstream Support

NI of course needs to comment on such an issue.

Regards

[Bob_Schor]

---

@softball wrote:

Affected Products

Product Version	Mitigation
LabVIEW 2025	Upgrade to LabVIEW 2025 Q3 or later from NI Package Manager or Software Downloads
LabVIEW 2025 Q1	LabVIEW 2025 Q1 Patch 3 – In Work
LabVIEW 2024	Upgrade to LabVIEW 2024 Q3 Patch 4 or later from NI Package Manager or Software Downloads
LabVIEW 2023	Upgrade to LabVIEW 2023 Q3 Patch 7 or later from NI Package Manager or Software Downloads
LabVIEW 2022	Upgrade to LabVIEW 2022 Q3 Patch 6 or later from NI Package Manager or Software Downloads
LabVIEW 2021 and prior	Not in Mainstream Support

---

Good call, @softball.  The affected PC was running LabVIEW 2024, so we got patches for 2024, 2023, and 2022.  Unfortunately, there were multiple patches listed for some of the LabVIEW versions (i.e. applying the Patches apparently didn't remove the earlier versions, or maybe the "Patch" was what was being flagged).  On my machine, I did a "complete uninstall of LabVIEW 2024" followed by a complete reinstall, but I was reluctant to suggests this to my colleague, and also had trouble explaining that "we should have fixed it, but the fix didn't remove the "flags" that signaled the problem".

I'm definitely going to read the link you kindly provided, and will talk again with the IT folks here.

Bob Schor