GPIB-USB-HS Driver Error -- Windows 10 possibly after Feb Windows Update

[DavidHary]

As of 2/17/2016, GPIB-USB-HS devices (2) no longer connect on Windows 10 using NI488.2 Rev 15 from 8/15 with the 15.0.1 patch.

Using VMWare player 7.1.3, the VM sees the hardware, connects to it, lights turn on and then turn off. The VM shows 'Driver Error' unable to connect to the USB device. This was tested with two USB devices that have been working with the same configuration for some years now on Windows 7, 8, 8.1 and 10 using VMate 7.x and 12.xs 

Possibly, this is related to the latest Windows Update, 

Neither repair nor a full install of NI488.2 rev 15 fixes this.

VISA still works via TCP/IP. 

Any thoughts will be greatly appreciated. 

[ZannahBanana]

Hi DavidHary,

I'm sorry to hear that you are receiving these errors. Were you able to use the GBIB-USB-HS devices at any point after you installed the latest Windows Update?

Thanks,

Hannah

National Instruments

[DavidHary]

The GPIB-USB-HS boxes are still briked. 

I am able to talk to the instruments using TCPIP-GPIB box.

Had NI-VISA implemented VXI-11.2 this would have been a complete solution....

[aflojo]

Hi DavidHenry,

Can you check in the device manager that the latest NI-488.2 driver is assigned to the USB-GPIB-HS device? It should be under the properties of the device.

[DavidHary]

The device no longer shows under Device Manager, as far as I can tell.  

[ChristophersonJ]

Hey David, 

These cables should be supported just fine with Windows 10, as you've seen up to this point. 

Good job as well trying out reinstalling the drivers as a step. 

As you can imagine, this is a bit of a weird situation for things to stop working due to a minor system update.  Especially since your other VISA deviec still works. 

Frankly I'd expect nothing to work if anything. 

Could you verify that the Windows Update caused the issue (possibly by doing a system restore to an earlier revision)?

I'm also confused by your use of "briked".  Typically this would mean completely unresponsive (no power, no lights, etc. )

Are the devices functional on other (non-Windows 10) systems?

Thanks!

-ChristophersonJ

[DavidHary]

yep, briked is a bit overboard. still, the boxes no longer work.  the good news are that I am way too busy to play with a restore. waiting for rev 16 -- maybe it will fix this.

[DavidHary · Accepted solution]

Update: The driver is alive again.  

The latest Windows update, which was applied to the host system on 3/5/2016, restored the driver functionality under the guest virtual machine. Both host and client OS revisions are now at 10586.122.