Problems Updating 2016 FRC LabVIEW

[HSi]

My team is trying to install the 2016 version of FRC LabVIEW. We have the base LabVIEW installed on all our computers but can only get the FRC update suite on one.

On one computer, we ran the installation as instructed by FRC on wpilib.screenstepslive.com and chose to view the updates when another window (from NI) popped up afterward. The window allowed us to choose which updates to install to complete the update. The last part of the process was unreasonably slow and then showed messages that files/directories could not be found and asked if we wanted to continue without them.

On another computer, the second window didn't even come up, so when we opened LabVIEW, there was still no FRC update. We repeated the update several times and tried rebooting, but it still didn't work.

What should we try besides uninstalling the whole program and starting from the beginning?

[Mark McLeod]

Turn off any anti-virus or other security apps that may interfere.
Run the install as administrator.

[Greg McKaskle]

I suspect that the window that popped up about updates is the NI Update Service. You are not required to install any of those updates unless FIRST specifically states they are needed. That tool exists so that industrial customers who have paid for updates know what is available and what is recommended for security or safety reasons.

I don't think any of the updates have been needed for FRC, and last year, they actually broke vision. Sorry this is confusing.

If you launch LV and see FRC 2016 on the Getting Started window, you are good to go.

Greg McKaskle

[wolfeman]

I'm having a similar problem on one Windows 10 system.
The base labview installation succeeded but the FRC 2016 update
is not working at all.

Error dialog says:

The "NI FIRST Robotics Competition LabVIEW update" installation has failed with the following error:

The system cannot find the file specified.

Continue?

Each part of the update fails with the exact same error if I continue.
Would be really nice if the message specified the file it was looking for ;-)

The installer does create some logs (attached). I don't see any smoking
guns...