Xbox One Wireless Adapter for Windows - Unknown USB Device (Invalid Configuration Descriptor)

- Sony Bravia X950G
- Android TV

- Windows 11 desktop


When using VirtualHere, the dongle does not work (it was working some months ago though).
The dongle works when connected directly to the PC (I tried, just in case the dongle was the issue).

The VH Client recognizes the device ("XBOX ACC (In use by you)") but it's not possible to get it working after as the device is not recognized " Unknown USB Device (Invalid Configuration Descriptor).


It might be fixable, can you plug the xbox dongle into the bravia and then run VirtualHere app and in the VirtualHere App menu can you click System Messages Copy to Clipboard and paste into this thread here?

In reply to by Michael



Sorry for the bad copy/paste, that's the best I was able to do (picture, than copy paste from it with iPhone):

(I sent you the screenshot by email so its clearer)



09-18 11:48:31.421

9460 20033 I vhusbd

: Sun Sep 18

11:48:31 2022 LOG_INFO

Using configuration /data/user /0/

com. virtualhere.androidserver/files/config.ini

09-18 11:48:31.481 9460 20033 I vhusbd

: Sun Sep 18 11:48:31


Server licensed to=ancf466ee68db8076b

max devices=unlimited

09-18 11:48:31.481 9460 20033 I vhusbd

: Sun Sep 18 11:48:31 2022


Using large URB's

09-18 11:48:31.481

9460 20033 I vhusbd

: Sun Sep 18 11:48:31 2022


Listening on all network interfaces at TCP port 7575 (IPV6


009-18 11:48:31.482 9460 20033 I vhusbd : VirtualHere USB Server is CTRL-C to stop

09-18 71:48:32.414 9460 20027 W NsdServiceInfo: Key lengths > 9 are discouraged: ancf466ee68db8076b

09-18 11:48:32.438 9460 20033 I vhusbd

: Sun Sep 18 11:48:32 2022


Found High speed device [Oe8d: 7668] "MediaTek Inc.,

Wireless_Device" at address 3002

109-18 11:48:32.441 9460 20033 I vhusbd : Sun Sep 18 11:48:32 2022


Found Super speed device [0000:0000] "UQUEST, LTD." at

address 5003

09-18 11:48:32.441 9460 20033 I vhusbd

: Sun Sep 18 11:48:32 2022


Empty descriptor for device at address 50031

09-18 11:48:33.014 9460 9460 D virtualhere-daemon: Already licensed and already have valid license

09-18 11:48:33.076 9460 9523 D virtualhere-daemon: mdns service sucessfully registered

09-18 11:48:37.802 9460 20033 I vhusbd

: Sun Sep 18 11:48:37 2022


Thanks for the log, yes it looks ok, i think its actually an Android bug in the Sony TV. Whatever recent update they did seems to have broke it.

In reply to by Michael


No system update from Sony since at least a year. I only received some app updates through the Google Play Store but nothing from Sony.


Is there another USB port you could plug the dongle into in your TV. Does it have a few usb ports?

In reply to by Michael


Sadly, it's the same result with the second USB port :(


Hi all,

I am suddenly experiencing the same issues here. I havent used my PC for gaming in a little bit since getting a Steam Deck. However, when I tried connecting my Xbox One Controller today, Windows could not recognise the device, in the same way as described by the OP. The only major change in that time is upgrading Windows 21H2 to 22h2, which may be the issue.

Connecting the dongle directly to the PC works just fine, the error only happens when connecting to the Xiaomi MiBox 4S (which I used almost only for VitrualHere these days).


(p.s. random side note - every reboot of the MiBox causes VirtualHere to lose license tho I've been living with that issue for more than a year now).


Interesting...i will see if i can find the change made between 21H2 and 22H2 to the xbox dongle driver...


I plugged my xbox dongle into my Android 13 Pixel 4a (5G) phone and ran the virtualhere app 4.4.5 (i recently updated it in the Play Store) and it does work ok.

I am running Windows 11 22H2

I notice that occasionally when redirecting the dongle via virtualhere it will drop off the USB bus and re-appear a few seconds later. To get around this in the virtualhere client right click on XBox ACC and select Auto-Use Device


Thank you for your replies here. :)

I tried again after updating both the Android device and the Windows Client software. I still have the same issue.

Additionally, I dual boot Windows 11 22H2 (a clean install, I set this up in the last few days) on the Steam Deck. It is also having the issue. Later today I will see if the issue exists on a Windows 10 Laptop.

In general, I dont think that the Android device is the issue here since it appears that the dongle is completely recognized on the Android side of things. The device has not had any updates this year. (Xiaomi seem to have abandoned the MiBox :( ). Its most likely a Windows 11 issue, although clearly not affecting everyone since you could get the dongle working just fine.

This could require MS acknowledging the issue and publishing updated drivers. I know that some drivers can be problematic in different ways on Windows 11 22H2 (e.g. Sound drivers for Steam Deck needed updating to work on 22H2 as the old ones would cause BSOD).

I tried on the Windows 10 Laptop and it has the same problem. Now I'm unsure what can be causing it since nothing else changed in our network environment..

Any other device connects perfectly but the main reason I am using VirtualHere is to connect my Xbox one controller and have the ability to use the 3.5mm Headphone Jack when I am using my PC from my TV (VirtualHere is the only interface I've ever used that has no noticeable audio or controller latency). If I was not forced to use headphones so much, I could just use the controller over regular Bluetooth, which does not support audio.


Can you download the XBox Accessories app from the microsoft store and use that to update to the latest firmware on your controller(s). That might be worth a try.

My controller is running 5.15.3168.0


Thanks for the tip.

I have been able to update my controller firmware when the dongle is connected to my PC directly.

However, the dongle does not have any update to its firmware, and is still not recognised correctly by Windows over VH (so the controller never gets to connect in the first place).

Do you think it would be of any help if I was to share logs from the Android Device or from Windows?


In the virtualhere android app at the top right of the screen click the menu button then select System messages, does it say anything about xbox ACC in there?


Here is the only lines relating to the Xbox Device:


Its in image form as its a bit challenging to copy text on a TV Android device. Hope this works.


I am reminded that I had an issue with a Logitech Unified Receiver (which still works perfectly even today!). I wonder if this issue may be similar?


Yes thats what i was thinking might be the issue. It might have detected it as a High speed device when its really only a full speed device. But actually your android is detecting the correct speed. So im not sure of the issue sorry, i dont have any more ideas at the moment


It is surprising that I have this issue suddenly since everything worked as intended for years.

Would you have an older version of the VirtualHere Software (Both Android and PC)? Maybe rolling back several versions would be of benefit to me.

I am also trying to work out how long ago we upgraded our network router - could that potentially cause issues that affect only one attached device? (My guess is not).


As my primary use is for using the Xbox Dongle is to be able to connect headphones to the controller with low latency - would you have any suggestions for how I can still use headphone that playback my PC audio?


Thank you very much! This version works for me! :)


To compare the System Logs, the Xbox Wireless Adaptor is listed here as "High Speed Device" in the server version that worked instead of "Full Speed Device" in the server version that did not.


Maybe it is worth noting, I have the older larger version of the device from 2015 and not the smaller revision from 2019.


Very interesting, i would not have suspected that. OK i will put this fix in the official build at the play store...


OK ive pushed this fix to the Play Store now as build 1060 (4.4.5) when you get that give it a try and it should resolve the issue (also note that @vhsauce)


I had opened an issue recently about the xbox adapter not working. At the time neither of mine worked as i have both the original and new smaller one.

As of today the older one works with the android app but the new one still says unregognised device.

You said it was a windows driver error, but whatever you did here fixed it for the older model.


In the virtualhere client can you right click on the new one (that doesnt work) and select Properties and tell me the Vendor ID and Product ID. Thanks


Thanks, ive fixed the bug and pushed it to the Play Store so you should get an update soon.


I can confirm after updating to the latest Android play version the smaller dongle works again.

The light shows on it correctly and the controller connected with no warning or issues.


Great! Thanks for letting me know


I cannot get the newer-style Xbox Wireless Adapter to work on my NVIDIA Shield Pro 2019 (Android OS 9.1.1.) The USB dongle never lights up when plugged into the Shield, although it works fine when plugged into my Windows 11 PC.

My Shield runs VirtualHere USB Server version 4.4.5 (build: 1061.) Should this build have all the latest fixes?


Its not related to virtualhere, i think you have some usb port problem. Try another usb port


The same thing happens on both of the Shield's USB ports. I made some progress, though.

  1. Reboot NVIDIA Shield
  2. After reboot, open the Android USB Server and allow it to access the Xbox Wireless Adapter
  3. Windows USB Client will see the Android Hub, but not the Xbox Wireless Adapter
  4. Physically unplug and plug the Xbox Wireless Adapter into the Shield
  5. Windows USB Client will now see the Xbox Wireless Adapter

Is there a way to avoid physically plugging the Xbox adapter whenever I reboot the Shield? Separately, can I avoid having to click the "Allow VirtualHere USB to Server to access XBOX ACC?" popup each time I reboot the Shield?


OK i think it might be an android issue. The dongle is going to sleep, replugging it wakes it up. There is no way around that.


Also make sure you have the latest XBox drivers/firmware on your PC. E.g using the XBox accessories Microsoft store app while the dongle is directly plugged into your PC.


It's strange because the Shield definitely sees the dongle upon boot (i.e. right after the OS loads, I get a pop-up about allowing VirtualHere USB Server to access the dongle.)

I did find a workaround to replugging:

  1. Set Shield's USB ports to turn off whenever the Shield goes into sleep mode (available in the Shield's System settings)
  2. Reboot the Shield
  3. After the Shield boots, you'll get the pop-up about allowing the USB server to access the dongle. While you can grant access, the client won't see the dongle yet.
  4. Put the Shield in sleep mode
  5. Wake up the Shield. You'll get another pop-up about allowing the USB server to access the dongle. This time, granting access will allow the client to see the dongle.

In my limited testing, you need to let the Shield sleep for 1-2 minutes before step 5. If you wake it too quickly, you won't get the pop-up in that last step.


Wow, what an inconvenience, i think you should maybe send an email to nvidia saying that their USB port power saving feature is not working properly.