VirtualHere Client: There was a error using this device.

Hi,

i get an error when i choose a specific device, other devices work fine.

 

Details:

Host System: OS Windows Server 2022 Standard using Hyper-V

Client: OS same as host system. The client runs as a VM on the host system. 

I tried solve the general issue that Hyper-V has problems with usb passthrough (mostly only works with usb media devices).

 

 

Device

Company: FEIG ELECTRONIC GmbH

Type. Card Reader

Device Name: OBID RFID Reader with USB/CDC interface

I tried the standard Windows Driver on host system as well as the most current (i.e. 2009) drivers from the manufacturer.

The card reader is using a physical usb port, but in windows device manager it is listed under Connections (COM & LPT) using a com Port.

The device fails to connect, the VirtualHere Server Log reads:

2024-07-04 14:11:05 INFO :192.168.10.251 connected as connection 1 (Standard TCP)
2024-07-04 14:11:17 INFO :Unmanaging device 17 [0ab1:0005]
2024-07-04 14:11:18 INFO :Found Full speed device [0ab1:0005] "0x0ab1, FEIG RFID READER" at address 17
2024-07-04 14:11:19 INFO :Unmanaging device 17 [0ab1:0005]
2024-07-04 14:11:21 INFO :Found Full speed device [0ab1:0005] "0x0ab1, FEIG RFID READER" at address 17
2024-07-04 14:11:21 ERROR :Capturing USB\ROOT_HUB30\4&10420897&1&0,USB\VID_0AB1&PID_0005\2247959B,12, SetupDiEnumDeviceInterfaces failed, Es sind keine Daten mehr verfügbar. (0x00000103)
2024-07-04 14:11:21 INFO :Unmanaging device 17 [0ab1:0005]
2024-07-04 14:11:22 ERROR :Error binding device 17 [0ab1:0005] to connection 1, BIND_ERROR
2024-07-04 14:11:22 INFO :Found Full speed device [0ab1:0005] "0x0ab1, FEIG RFID READER" at address 17

some screenshots from the host system:

https://ibb.co/TcZXkF0

https://ibb.co/p43GYRx

https://ibb.co/RHXG2yN

I tried USB and COM passthrough but the device is not selectable in neither the rdp nor hyper-v advanced session settings.

If you need more information please let me know.

 

#2

Try completely uninstalling the drivers on the host (where the virtualhere server is running) and rebooting. The drivers might be conflicting and not allowing virtualhere to redirect the device. 

Otherwise if that still fails, try just plugging the device into some other linux based server running virtualhere and it will probably work because there wont be driver conflicts.

 

#3

ok i tried:

-windows default drivers

-manufacturer drivers for windows

-linux drivers (on a different computer)

 

all of them produce errors and the device can not be used. we will probably buy a new device since that latest manufacturers drivers are from 2009 and the support is officially only for 32bit systems and windows server 2003. 

 

 

 

 

#4

Yes i think you need to update to something more recent.