DAQ Device Not Listed in MAX But Shows Up in Windows Device Manager

Issue Details

My devices are installing correctly and show up green with no exclamations in the Windows Device Manager but some or all do not show up in Measurement & Automation Explorer (MAX).

Why are my devices not showing up in Devices and Interfaces in MAX?
 

Solution

There are a number of possible reasons for devices that appear in Windows Device Manager, but not appearing or appearing incorrectly in MAX.

• If some devices are recognized, but others are not, it's possible that the NI-DAQmx driver is not correctly associated with the missing modules. Follow these instructions for missing device drivers to detect and resolve this issue.
• The version of NI-DAQmx installed may not be compatible. Consult the NI-DAQmx driver readme for the installed version for information on supported operating systems, supported versions of LabVIEW, and supported hardware.
• NI Device Loader service is required to correctly detect devices in MAX. Navigate to Services and ensure the NI Device Loader service is Running and set to Automatic.
• Some versions of NI-DAQmx or the runtimes of the drivers do not interface with MAX, and are intended to be used without MAX installed.  If you intend to use MAX, make sure you install a version of NI-DAQmx that includes MAX support such as DAQmx Full.
• The MAX database may be corrupted.  After backing up any configuration of custom scales or tasks in MAX, try resetting the MAX database to see if the modules are recognized.
• The installation of NI-MAX itself may be corrupted. MAX can be reinstalled by following the instructions to reinstall non-working or corrupt software.

Additional Information

For versions of NI-DAQmx that do not install MAX, necessary files for MAX to interface with the NI-DAQmx driver will also be missing. This can mean that even though the driver is working correctly, and MAX is working correctly, they cannot communicate correctly. Versions of NI-DAQmx such as NI-DAQmx Core are intended to be used by advanced users, and require API calls to configure devices and tasks.