cancel
Showing results for 
Search instead for 
Did you mean: 

Oculus Quest Appears on PC but Won't Show any Folders on PC

Shadowmask72
Honored Visionary
When I connect Quest to PC it just shows up as a portable device "quest" in device manager and Windows Explorer. The folder is empty on windows. Currently what I have to do is go to the Phone APP and toggle developer mode OFF then ON again for the message to appear in the headset about accepting the connection. I have updated the drivers (see support message below) but each time I need to connect it requires this dance with the phone app. This is pretty unfeasible seeing as it's not my phone and I don't always have access to it. Any suggestions please?

If your Oculus Quest headset is not appearing as a drive on your Windows PC:

  • Make sure that you use the included USB cable from your Oculus Quest package.
  • Make sure that you select Accept in VR from your headset to allow your computer to access files on your headset.
  • Update your device driver:
    1. From your PC desktop, right-click on This PC or My Computer.
    2. Select Computer.
    3. Select Manage.
    4. Select Device Manager.
      • If you can't see the Manage option, just select Device Manager directly.
    5. Click the next to Oculus Devices or Portable Devices to expand your options.
    6. Right-click on Quest and select Update Driver.
    7. Select the Browse my computer option, then the Let me pick from a list option.
    8. Select MTP USB Device and then select Next to complete the update.


System Specs: MSI NVIDIA RTX 4090 , i5 13700K CPU, 32GB DDR 4 RAM, Win 11 64 Bit OS.
20 REPLIES 20

one3rdnerd
Protege
I'm having the same issue here. With Developer mode on I'm unable to see any of the files on the Quest when connecting to my PC via USB. 

I have to

1 turn developer mode off on the iphone
2 connect to the PC again
3 accept the permissions notification in the headset

Having to use 3 devices to resolve something that should just work once plugged in is annoying.

Once a device is given permission I shouldn't have to do it every time I connect and go through the above 3 steps.

Please fix 🙂 

Nikorasu
Adventurer
Mine does this too, but I've never had to worry about it, because running SideQuest seems to fix it. If I plug in my Quest, and the folders don't show up, I can just run SideQuest, which does something that resets the connection and shows the folders. Easier solution, works for me at least.

rmib200
Explorer
I downloaded the ADB files from the Oculus web and then right click on the .inf file, click install, and it fixed for me.

bigballs42069
Honored Guest
when i go to device manager it dosent show oculus devises or portable devises

WilsonInVR
Protege

alecz said:

Thanks! This is annoying, hopefully it gets fixed soon.



Yes, agree. Im on NEW Ver 11 update and mount drive still works sometime and have to disable/reenable Developer mode.. a few times a day

Danniego
Explorer
can confirm loading sidequest makes quest available in file explorer. thx for the tip!

Grim2025
Explorer
I haven't been able to get my quest to even show up on my pc or the 3 others i've tested with. Its like the quest doesn't want to communicate with anything now. I'm unsure how to fix but gotten with support and hope they have an answer for me. 

krog9999
Honored Guest
(Linux) It worked one day, then the next it did not. Turning off Dev Mode would prompt the "Allow data from this computer", but SideQuest would not connect until I turned back to Dev Mode. Then, SideQuest said to allow data inside Quest -- but since Quest was in Dev Mode, it no longer gave me the prompt !! But I found this page helpful:
dev.to/jarroo/android-device-debugging-on-linux-mint-error-insufficient-permissions-for-device-udev-requires-plugdev-group-membership-369
which was helpful in pointing to this page that explained it:
The key is to add the device (not your users) to the udev rule. I was able to verify with 'adb devices'.
Then when I connected, it had a new prompt, "Allow debugging from this computer?" with a tick box for "always". 'adb devices' showed my Quest device in the list. Now SideQuest was able to connect. I hope this solves the problem for me going forward, and hope it can help someone else too.

reynosotkyle
Honored Guest


When I connect Quest to PC it just shows up as a portable device "quest" in device manager and Windows Explorer. The folder is empty on windows. Currently what I have to do is go to the Phone APP and toggle developer mode OFF then ON again for the message to appear in the headset about accepting the connection. I have updated the drivers (see support message below) but each time I need to connect it requires this dance with the phone app. This is pretty unfeasible seeing as it's not my phone and I don't always have access to it. Any suggestions please?

If your Oculus Quest headset is not appearing as a drive on your Windows PC:

  • Make sure that you use the included USB cable from your Oculus Quest package.
  • Make sure that you select Accept in VR from your headset to allow your computer to access files on your headset.
  • Update your device driver:
    1. From your PC desktop, right-click on This PC or My Computer.
    2. Select Computer.
    3. Select Manage.
    4. Select Device Manager.
      • If you can't see the Manage option, just select Device Manager directly.
    5. Click the > next to Oculus Devices or Portable Devices to expand your options.
    6. Right-click on Quest and select Update Driver.
    7. Select the Browse my computer option, then the Let me pick from a list option.
    8. Select MTP USB Device and then select Next to complete the update.


I turned on "sidequest" while the quest was plugged in, which automatically allowed access to the files. Apparently dev mode messes it up, but the sidequest software makes it right again. Unk why. 

DeepThinkr
Honored Guest
Another issue I noticed that exhibits this behavior is if you use the Oculus Link software. 
You have to shut off the app on the PC and then disable it in the Quest 2 HMD.
Once disabled you can go and toggle (a couple times maybe?) Enable Usb connection dialog and then connect the headset.
Worked for me.