That looks like a Beta test version of the imaging tool?
You might want to re-install the current version of NI Game Tools to get the latest and an up-to-date v4.0 image for the RIO.
That should clear up missing software and give you a running version.
There still seems to be something wrong with your installation.
Look at the directory
C:/Program Files (x86)/National Instruments/LabVIEW 2020/project/roboRIO Tool/FRC Images
to check the contents and dates. (Note the release date on the Game Tools webpage is incorrect and can fool you into thinking nothing has changed).
Here’s what mine looks like after the most recent (1/20) Game Tools release.
FWIW, I have always had trouble with the game tools and uninstalling them. My process now is to go into the windows program manager, remove the NI packages, reboot, go into windows program manager again, remove the other NI packages that remain, reboot again, open the windows program manager again to verify nothing else from NI is installed, check the program files (both) and program data directories for anything that might be left and delete those, and then finally, reinstall the version of the game tools that I need.
Yes, this is time consuming but it seems to work, particularly when I encounter issues.
I cannot believe that the FRC game tools is this bad.
It’s basically a fresh copy of Windows 11. The only thing on here is programming stuff for FRC, I really can’t believe that it’s this bad.
I really don’t want to reinstall windows because I shouldn’t have to and it’s a complete waste of time.
Also - Any labview tool doesn’t work on my computer. Driver station, RoboRIO imaging tool, anything that is labview based has the errors listed in the original post. Last week it was working, this week it is not.
Why is the driver station written in labview? Who’s brilliant idea was that?
The programming that is crashing is a service that reports error info to NI.
Please try to disable it according to the link above.
As for the state of the NI Package Manager or ability to install MSI installers, I assume that is something else. Forums imply that downloading the offline installer, rebooting, and installing it seems to fix it at least some of the time. Sorry I can’t be more certain about that.
