Forum Discussion

Torsten1970's avatar
Torsten1970
Honored Guest
3 months ago

USB connection problems with Meta Quest 3s solved (Firmware 79)

Since the update to firmware 79, I was no longer able to connect my Quest 3s to my Windows PC. I used the same cable and tried two different PCs with identical settings. Sideloading was not possible without Windows connection. Nothing worked.

The solution turned out to be very simple:

I bought a new cable for the PC connection (USB 3.2 Gen 1).
When connecting the Quest to the PC, I used to always press the notification “Allow USB connection.” Now you must not do this anymore. Just plug in the cable, and the Quest connects immediately.

If you want to use the USB drive function, you should tap the message in the notification manager on the Quest, and a USB drive connection will be established.

Just to complete the picture: I installed the ADB drivers both from the Meta website and from the Oculus package. I tried normal installation as well as installation in safe mode. I ran scripts from other posts that kill and restart the ADB server, ran the applications in admin mode, and tested different boot sequences (Quest off, connect, PC on, Quest on … etc.). I also reinstalled developer mode and restarted the Quest multiple times. None of that worked for me.

In the end, the solution was extremely simple! I hope this helps you as well

2 Replies

  • Maccyb123's avatar
    Maccyb123
    Expert Trustee
    3 months ago

    Advice like this is very valuable to a lot of people. Kudos to you for taking the time to explain it so clearly.👏👏👏👏👏👏

  • QNeo's avatar
    QNeo
    Honored Guest
    3 months ago

    the answer is half correct, and thank you for that.

    But if you have a good usb port on your Quest, you shouldn't have any problem at all. If you have the issue you just described, it's a weak usb port on your Quest. And yes you can workaround by choosing between ADB (for sidequest) or MTP (for your pc). It works, but it's not normal that you need to do this. 

    This said, you should try with another cable first, because the cable CAN be the issue as well. I have one Quest who has this problem and three who work perfectly, so in my case it's not the cable, it's the Quest.