I was using a trial version of 2015 and then purchased and installed Labview 2017 Full from the downloads page. At 98-99% complete, a dialog prompt asked for a location for hardware drivers as the installer could not find them (there was a text message in Red font). I suspended the install and started a new install of Ni-Daq driver support intending to continue the main installation. The Ni-Daq install started but asked that I complete the pending install, which I was forced to skip the previous request to install the Hardware support. Upon completing the Ni-Daq install, I opened my project from a working build (source) folder and now have errors. I am guessing I need to configure the missed step but could not find the "Configuration" section to point at the Hardware drivers. Do I need to uninstall 2017 and try again or can I configure Labview now?

The LabVIEW installer assumes (incorrectly) that you are installing from media and have the Device Drivers media on hand. It is OK to skip installing Device Drivers and complete theLabVIEW installation. Then you can download Device Drivers and install them as a second step. Device Drivers 16 of course predates LabVIEW 2017 so, it cannot install support for LabVIEW 2017. Device drivers 17.0.1 Does support multiple LabVIEW versions from 2017 back to....2014 There is one version of Device Drivers and it supports both 32 and 64 bit application development environments. There are a few oldeer DAQmx devices that cannot run in a 64bit enviornment (These are all listed in the DAQmx ReadMe) I wonder why they named it that?

LabVIEW

Labview 2017 FULL Installation, Hardware Configuration, Ni-Daq

Solved!

Actually, there's a trend you may notice that the past couple NIWeek DAQmx releases of the x.0 (ie, 15.0, 16.0, 17.0) added only new ADE support, such as for the new version of LabVIEW or LabVIEW NXG. Then, the x.1, x.5, etc releases added new hardware support. And of course, bug fixes and improvements all along the way. So, the 17.1 release was a complete and planned release.

Now I wouldn't say this is a "rule" or something to live by, but I'd take it as a nice tidbit of knowledge. 🙂

As Jeff·Þ·Bohrer mentioned, the readme is a great first stop for these sorts of questions for the driver releases!

16.0 Readme: