We also run into issues where the system path has been changed by the dev for some components (e.g. Node.js) but is not the same as the path that we check for our updates, which causes challenges when running updates.
This pathing issue is both a Mac issue (where they edit their .bash profile and install paths e.g. VMware put node in /opt instead of the default location and then the installer went into loop checking for node updates and installing) and Windows issue (where IT redirects installs from the user directory to some other path that they standardize on an NFS share for all end users)
I think we need more details here. Are they installing multiple Node.js installations? Does this mean they're pointing at a specific install in the prefs but we're not honoring it? Are we just not picking up existing installs?