Brand new Sandisk Ultra 3.0..when trying to use Virtualhere to recognize the USB through Shadow I'm getting a "There was an error using this device" message. Windows then shuts down my USB and says it malfunctioned. Here's a log if it helps..
2020-05-02 21:36:44 INFO :Found High speed device [0781:5581] "SanDisk, Ultra" at address 7
2020-05-02 21:37:14 ERROR :CreateFile failed while completing capture of device USB\ROOT_HUB30\5&358E0DD4&0&0,USB\VID_0781&PID_5581\010170AE252E228FEA4391991EE14E34B62789A293FB087BF97FA315708DB74C874B0000000000000000000035AE76F8FF0A34008155810738A8C1FA,7, The system cannot find the file specified. (0x00000002)
2020-05-02 21:37:14 INFO :Unmanaging device 7 [0781:5581]
2020-05-02 21:37:14 WARNING :Failed to locate root devnode when rescanning, 13
2020-05-02 21:37:14 ERROR :Error binding device 7 [0781:5581] to connection 1, BIND_ERROR
2020-05-02 21:37:27 INFO :Found High speed device [0000:0000] "0x0000, 0x0000" at address 8
2020-05-02 21:37:27 ERROR :Empty descriptor for device at address 8!
2020-05-02 21:37:27 INFO :Unmanaging device 8 [0000:0000]
2020-05-02 21:37:27 ERROR :Empty descriptor for device at address 8!
.
1. Unplug the disk
2. Plug it back in
3. In the virtualhere client, right click on the disk and select Custom Event Handler... and paste in this line exactly as is
onReset.$VENDOR_ID$.$PRODUCT_ID$=then press OK.
4. Now try to use the disk via virtualhere
(Note it will be quite slow so give it time)
I have the same error as
I have the same error as above. I tried the suggestion above but it didn't resolve it.
other slow USB drive working fine. This SanDisk initially worked, but I had to keep unplugging and plugging it back in each day I turned on my computer.
Then stopped altogether with the "There was an error using this device" and hasn't worked since. I swapped drives and the other has worked perfectly, it is just very slow.
2020-12-09 15:12:57 INFO :Found Super speed device [0781:5583] "SanDisk, Ultra Fit" at address 9
2020-12-09 15:13:22 INFO :Set custom event "onReset.0781.5583="
2020-12-09 15:13:25 INFO :Device 12 [13fe:6300] UNBOUND from connection 1
2020-12-09 15:13:28 ERROR :CreateFile failed while completing capture of device USB\VID_2109&PID_0812\9&2F7AA3DB&0&4,USB\VID_0781&PID_5583\4C530001311211105181,1, The system cannot find the file specified. (0x00000002)
2020-12-09 15:13:29 WARNING :Failed to locate root devnode when rescanning, 13
2020-12-09 15:13:29 ERROR :Error binding device 9 [0781:5583] to connection 1, BIND_ERROR
2020-12-09 15:13:31 INFO :Unmanaging device 9 [0781:5583]
.
Stop and exit the server and try this beta build of the server
https://www.virtualhere.com/sites/default/files/usbserver/4.2.2/vhusbdw…
I installed the new server
I installed the new server file, and now the Client can't see any of the USB devices. It can't seem to talk to the server side, I have double checked the IP and port number is correct. Is there a Client version that go with this new server build?
Below is server log.
2020-12-11 16:09:43 INFO :Server Driver up-to-date (1.0.1)
2020-12-11 16:09:46 INFO :Listening on all network interfaces at TCP port 7575 (IPv6 dual-stack)
2020-12-11 16:09:47 INFO :Tickled device USB\VID_8087&PID_0029\8&6654480&0&4 when getting prod/vend strings
2020-12-11 16:09:47 INFO :Found Super speed device [13fe:6300] "UFD 3.0, Silicon-Power64G" at address 1
2020-12-11 16:09:47 INFO :Found High speed device [046d:0843] "0x046d, Logitech Webcam C930e" at address 2
2020-12-11 16:09:47 INFO :Found Full speed device [046d:c335] "Logitech, Gaming Keyboard G910" at address 3
2020-12-11 16:09:47 INFO :Found Full speed device [8087:0029] "0x8087, 0x0029" at address 4
2020-12-11 16:09:47 INFO :Found Full speed device [0b0e:0422] "0x0b0e, Jabra SPEAK 510 USB" at address 5
2020-12-11 16:09:47 INFO :Found Full speed device [046d:c08c] "Logitech, G PRO Gaming Mouse" at address 6
2020-12-11 16:09:47 INFO :Found Full speed device [1462:7c35] "MSI, MEG X570 ACE" at address 7
2020-12-11 16:09:47 INFO :Found Super speed device [0781:5583] "SanDisk, Ultra Fit" at address 8
.
The client is the same. The log looks ok. Is it working ok now?
No, I can not get the client
No, I can not get the client to see the host side. When I run the released version of the host, I can see it. But I can't see it in the beta version.
Can't seem to paste an image into here. It just shows 2 lines both saying Connecting to USB hub..
I found the log.
I don't know what 172.20.16.1:7575 is... That isn't listed in the "specify Hubs" screen (or the .ini file), but in the log it is trying to connect to it.
Might be something from your beta testing? 192.168.1.20 is the correct IP address of the host.
2020-12-12 17:28:17 INFO :Could not connect to 192.168.1.20:7575
2020-12-12 17:28:18 INFO :Could not connect to 172.20.16.1:7575
This is the vhui.ini
[Transport]
EasyFindId=2HnX2aXi5t5wLATtsSotsR
EasyFindPin=DiLXn
[General]
MainFrameWidth=400
MainFrameHeight=250
MainFrameX=819
MainFrameY=413
[Settings]
ManualHubs=192.168.1.20:7575
When I change back to the released version I have this
2020-12-12 17:34:36 INFO :VirtualHere Client 5.1.2 starting (Compiled: Nov 17 2020 16:25:22)
2020-12-12 17:34:36 INFO :Client OS is Windows 10 (build 19042), 64-bit edition
2020-12-12 17:34:36 INFO :Using config at C:\Users\Shawn\AppData\Roaming\vhui.ini
2020-12-12 17:34:36 INFO :IPC available at \\.\pipe\vhclient
2020-12-12 17:34:36 INFO :Auto-find (Bonjour) on
2020-12-12 17:34:36 INFO :Auto-find (Bonjour SSL) on
Below is the log of the failed connection to the USB SanDisk Drive from the released version, if that helps.
2020-12-12 17:38:44 INFO :Drivers are up-to-date
2020-12-12 17:38:44 INFO :Connected to the VirtualHere Client Driver (Version 2)
2020-12-12 17:38:45 INFO :In file ../src/msw/window.cpp at line 594: 'SetFocus' failed with error 0x00000057 (The parameter is incorrect.).
.
The beta server is completely identical except for a single driver so the networking setup etc is identical.
Be sure to run the beta server from the same directory as your current virtualhere server so it uses the same config.ini file. Do you know what 172.. is? That appears to be a private address like 192.. Are you running a vpn or something, perhaps you are running another virtualhere server somewhere with that ip address and its finding it.
My other guess is that virtualhere server vhusbdwindk64.exe is not in your windows firewall setup so its not letting it through. Usually it asks to allow it through however...
OK thanks for looking at this
OK thanks for looking at this. I will just keep using the released version,