Microsoft Xbox adapter for windows - shows in client but can't be used

Submitted by Benoire on #1

Hi

Trying to get my new xbox one controller adapter working with virtualhere when running windows. With my two nvidia shields, the adapter passes through to the W10 client without issue and works great. On windows 10 running the latest windows server, the dongle shows up in the client but I can't actually get the client to use it... selecting use device doesn't do anything menaing that I cannot pass through the adapter and eventually get an error stating it cant use the device. Is this a problem with the new MS adapters or just user error?

Thanks

Chris

Submitted by Michael on Fri, 2020/01/17 - 13:09

#2

On the virtualhere server click Settings->View Server log does it show any errors in there when you try to use the dongle?

Submitted by Benoire on Fri, 2020/01/17 - 13:32

#3

When the server loads it finds this:

2020-01-17 16:26:44 INFO :Found High speed device [045e:02fe] "Microsoft Inc., XBOX ACC" at address 5

Eventually the client times out and the server log states this:

2020-01-17 16:31:04 ERROR :DiInstallDevice failed, This operation returned because the timeout period expired. (0x000005b4)
2020-01-17 16:31:08 ERROR :Error binding device 5 [045e:02fe] to connection 1, BIND_ERROR

Submitted by Michael on Fri, 2020/01/17 - 13:50

#4

Ok it's not going to work with the windows server

Submitted by Benoire on Fri, 2020/01/17 - 16:33

#5

Not at all or just not right now with the current release?

Submitted by Benoire on Fri, 2020/01/17 - 20:44

#7

Thanks, this now passes the device in to the remote client:

2020-01-17 23:36:36 INFO :Found High speed device [045e:02fe] "Microsoft Inc., XBOX ACC" at address 1
2020-01-17 23:36:36 INFO :Device 1 [045e:02fe] BOUND to connection 1

But the controller won't connect to the adapter now once passed through. Once I disconnect the the adapter from the remote PC, the controller will connect as per normal.

Looked at pairing the adapter to the controller when connected remotely but the adapter pair light doesn't come on. Something is potentially blocking the adapter, despite it showing as being passed through.

Submitted by Benoire on Sat, 2020/01/18 - 05:32

#8

Tried again this morning after rebooting both machines, again the device passes through 'ok' but Device Manager on the remote machine indicates a code 10

This device cannot start. (Code 10)

{Operation Failed}
The requested operation was unsuccessful.

So the windows 'server' is doing something with the adapter which is causing problems with virtualhere.

Michael - if you want to trouble shoot further, where should I look as the VH server logs show everything working.

Submitted by Michael on Sat, 2020/01/18 - 10:25

#9

One last try, in the virtualhere client right click on the XBOX dongle and select Custom Event Handler... and paste in this line

onReset.$VENDOR_ID$.$PRODUCT_ID$=

Then unplug and replug the dongle. Now try to use it via virtualhere again.

If that still doesnt work then we've basically tried all the options and its not going to work with virtualhere windows server unfortunately.

Its not possible to determine why because its internal to the dongle. I think you need to use a linux (or android) based device as the virtualhere server.

Submitted by Benoire on Sat, 2020/01/18 - 14:43

#10

Nope, doesn't solve it still won't work. Whatever the device is doing in the host windows environment is clearly not a normal USB type thing as everything else works fine and the adapter works perfectly in my 2 nvidia shields with the android virtualhere application. Shame as it would have made remote gaming better; I'll just use my shield in the lounge as its local to the laptop and works fine.

Thanks for trying though!

Chris