ADB device list empty

How did you solve it? Any guidance?

1. Open Device Manager
2. Find "Interface ADB" and  "Interface XRSP"
3. Click the right mouse "Interface ADB"
4. Сlick on the menu "Update Driver"
5. In the window, click "Browse my computer for driver software"
6. In new window, click "Let me pick from a list of device drivers on my computer"
7. Search "Oculus VR, LLC." and click
8. Choose "Oculus ADB Interface"

for the Interface XRSP to do the same BUT choose "Oculus Bootloader Interface"

now QUEST drive in Windows Explorer

then I change "Oculus ADB Interface" to "Oculus Composite ADB Interface"

Thanks @rfvcx, that worked. Only difference for me is "Oculus" didn't show as an option in the initial devices list, had to choose "Android Phone" and then in the next step, in the drop-down menu there was the option for Oculus VR LLC as you described. Selected those drivers and worked fine. 

Might be worth updating the Documentation for non-Win10 users.

Wait mine is all messed up. If I don't have Quest plugged in I don't see any of those options. If I plug Quest in, I see 'Other Devices' and sub-item '!ADB Interface'. The properties say driver not installed. If I try and install by selecting appropriate folder, says can't find drivers. I re-ran Codeworks and everything shows 'no action required'.
Edit: O...M...G....with much fussing about finally got it working, thanks.

Unfortunately it's still not working for me in Windows 8.1. The XRSP Interface shows up as a WinUsb Device.  If I deselect the "Show compatible hardware" option I don't get any Oculus options.

Do you get any "Android Phone" or similar options? The Oculus VR LLC option was inside a "Samsung Phone" hardware option as in my case a Samsung Phone was the first devices ever used for ADB. It might look different on your machine based on if another ADB option was preinstalled.

I finally got Win 8.1 working - I had to turn developer mode off to get it to show Oculus Bootloader Interface as an option for the XRSP Interface.  Then after switching back to developer mode both interfaces showed under Other Devices and I could choose the correct driver for each one.  Big thanks for everyone's help on this.

Whoa, just wanted to say thank you. I was struggling with this for a few hours now. 

TamToucan said:

Like so many I can't get the drivers to work after the latest update. Windows 8.1 and when I plug in my Quest device manager only shows 'Other Devices - XRSP interace' and 'Portable Devices - MTP' there is no ADB Interface.

If I turn off developer mode and connect then the Quest prompts to allow access and again all I see is XRSP and MTP. The XRSP has no driver installed. If I try and update the driver and point it at the latest Quest ADB driver it says it could not find the driver for the device.

Basically no matter what I try I can't get an 'ADB Interface' to appear in device manager to try and manually select the driver.

Any tips? Thanks.

For me it was enough to see the XRSP Interface. Then I would install a driver from my own machine by right-clicking XRSP Interface and choose to update driver. Then "browse my computer for driver software" and "let me pick from a list of device drivers on my computer", and pick "Oculus Bootloader Interface" from the "Oculus devices" category. This only works when XRSP has no driver installed and isn't already part of the USB controllers or USB devices etc in the device manager. Otherwise you can only select from a small amount of drivers.

I didn't need to install any new ADB drivers then. And I left it at that. I've had 4 Oculus Quest devices in the meantime and they all have the same problem that gets temporarily fixed by this.

Then suddenly the one I'm using will stop working after unplugging it for some reason (charging, customer request etc) and at some point hours or a day later (either unplugging, plugging, rebooting etc) work again.



A new problem I have is that Windows 10 won't see the Oculus Quest at all. No beep, no pop-up, no asking for permission in the quest, no unknown or known devices in the device manager. This leaves me with rebooting everything multiple times, changing cables, and switching normal and developer mode multiple times etc till it shows mercy and pops up for no reason.

This is super disruptive to working with the Quest, where is an official statement regarding this problem? Is Oculus not looking at the developer forum at all?