Test Stand version selector FAILS for 64 bit unregistered file

[prcngwsas]

New install of Test Stand 2025 Q3, the selector fails to register the 64-bit version ( NI PM indicates it's installed) with the multiple files NOT registered (see attached screen shot)

Is there a way to re-register these files short of a full remove and reinstall? 

Thanks for any help.

[Oli_Wachno]

Out of curiosity: those files are available in the locations which are mentioned in the error dialog?

Since you are using the version selector, I suspect you have multiple versions of TestStand installed... what is the behaviour if you switch version using the version selector?

[prcngwsas]

Thanks for the response-

The files are in the locations in the error message. I completely uninstalled all test stand versions indicated in the NI PM and re-installed ONLY test stand 64-bit ( as shown in NI PM) and I still get the same error.

It's also interesting that the Test Stand Deployment utility has a broken arrow and lists an error for missing "TSInitWindowsCommonControls:C" in VI "Deployment Utility Splash Screen" - TestStand.vi

I hope these errors are not related to the plethora of security "tools" installed on the laptops we use.

[Oli_Wachno]

This sounds indeed pretty screwed up...

Though it's a lot of work, I'd recommend wiping everything NI software related form the PC (including NIPM) and reinstall.

And always reboot if the installer asks you to

[prcngwsas]

Ah, the move to HI orbit and nuke'em approach. Unfortunately that tends to take DAYS over wifi and that's all the link speed available.

It's interesting that if you look at the Test Stand selector screen it shows a 2025 Q3 version already active yet when a launch attempt is made the ".. not active.." error message appears. 

Weird.

[Oli_Wachno]

---

@prcngwsas wrote:

Ah, the move to HI orbit and nuke'em approach.

[...]

---

Ah... yes... since according to my experience, trying to tinker a screwed up installation usually takes longer than doing it the proper way.

Yet that's just me, maybe someone else ( or NI Support) can help with this. Guess there are some logs somewhere.

To speed installations up, I do recommend to download the NI Packages and NOT use the online installers, especially given a slow internet connection, since this can be done overnight.

I have seen "unexplainable" issues on corp computers with security stuff installed especially when going over bandwidth limited VPN connections.

[prcngwsas]

Well an uninstall/re-install of Test Stand did NOT fix this issue, Having to re-image a laptop to "fix" an issue isn't something I'd call a "proper way" to fix a software issue. It's usually a quick "fix" for these types of issues, however there are other software packages on this machine that are extremely hard to just re-install ( Rockwell tools as an example) so nuking the entire machine is a last resort.

Looking at the pile-o-stuff that is left on a machine after a full ( via Package Manger and individual uninstall invocations) uninstall of [supposedly]all NI software I'd venture a guess the testing of installs/uninstalls hasn't really been done very well.

There are tons of files, services, and registry entries all just dangling after trying to uninstall everything. 

Thanks for you help.

[santo_13]

A better approach I have taken recently is to use VMs in Hyper-V, which makes it easy to restore the state and work around install/uninstall issues.

[prcngwsas]

I agree and if I could I would,BUT in our highly secure corporate environment that’s a difficult thing to do.