NI USB DAQs Not Recognised/Configurable In NI MAX After Windows Update

[Rob_Fenn]

Hello all,

After the most recent Windows 10 update last night;

2019-11 Cumulative Update for Windows 10 Version 1809 for x64-based Systems (KB4523205),

one of our LabView PCs (running LV 2015, and the only one to have received the update so far) now does not recognise any of our PCI and USB DAQs in NI Device monitor nor NI MAX, though they are still present in Windows Device Manager:

No NI devices detected, yet USB DAQ is 'seen' but unconfigurable.

If I right-click and 'Delete' the remembered instance of a USB DAQ device from NI MAX and then plug it in again, the DAQ does then appear and is recognised, but with a spurious identification name (not the usual default 'Dev1' as expected) and is completely uneditable/unconfigurable (example shows a USB-6002 which has been deleted from NI MAX and then replugged):

USB and PCI DAQs showing spurious names, and duplication of PCI.

I've tried updating drivers, NI VISA (version 18.5 as I'm running LV 2015) and NI MAX, but the operation is still the same.

This new Windows update includes: "Updates to improve security when using external devices (such as game controllers, printers, and web cameras) and input devices such as a mouse, keyboard, or stylus." which makes me think that it has messed up the association and reduced the ability of the USB DAQs and NI MAX to communicate.

Anyone else been hit by this update? Or know a way to get NI MAX to re-recognise these DAQs?

Cheers for any help you can give,

Rob

[psuedonym]

Go into Windows 10 and disable Fast Boot.

See if that makes a difference.

[Rob_Fenn]

Thanks for the suggestion psuedonym,

I just checked the power settings and unfortunately I've already got Fast Startup turned off.

[psuedonym]

Can you rollback the Windows update?

That can definitively confirm that it is the culprit.

[Bob_Schor]

You have a whole lot of USB devices plugged in there.  The pattern you see when you "remove" then reattach the device and get a \VID identifier is often a driver issue, for example for a multi-port USB Hub that acts as a USB "concentrator".  If you've got such a device, see if you can update its driver(s).

Bob Schor

[Rob_Fenn]

Thanks Bob. I've not got a lot of USB devices plugged in; usually I only have only one or two plugged in at a time in my day to day use of LabView - but NI Max remembers and keeps a settings profile for each NI DAQ I've ever connected to the PC. The red crosses over the DAQ icons indicate that they're not currently plugged into the PC (or have not been recognised as one of the saved setting profiles).

In my first photo, you can see I've got a USB6002 plugged in, randomly assigned a gobbledygook name by NI Max (rather than the expected default 'Dev' name), recognised but unuseable. This USB6002 is actually the same one that would normally be associated with the setting profile at near the very top "NI USB-6002 "CAST_Node_Iso" ", but NI Max is now not associating this settings profile with the hardware as seen plugged in, assigned a gobbledygook name, and unuseable in the settings window. 

It's doing this for all DAQs attached, even the PCIe one.

[Rob_Fenn]

Thanks psuedonym, rolling back the update was going to be my last call into getting this sorted. I've had to resort to this now, and have seemed to rectify the situation by uninstalling and blocking that update which caused all this annoyance in the first place.

The Microsoft update at fault appears to be this one: KB4523205 

(Details: https://support.microsoft.com/en-gb/help/4523205/windows-10-update-kb4523205)

Once uninstalled using the Windows 10 update uninstall process, it has to be "hidden" from the updates list or else it will just get downloaded again as soon at Windows performs anther update. To "hide" the update, one has to allow the update process to find the update again, and then download a separate Windows 'Show Or Hide Updates Tool' from Microsoft which allows you to customise the potential download list and block/"hide" that particular prospective update from being performed.

(Source: https://support.microsoft.com/en-us/kb/3073930)