Quest Link makes continuous connecting/disconnecting noise With Quest 3 On v66 PTC

[viyuuu]

Hi, so quest link isnt working since i updated to v66 ptc. And i cant go back to v65, i turned off the ptc and factory reset multiple times but no. Its just stuck on v66. When i connect my link cable to my PC it sometimes doesnt connect, and when it does, it just rapidly connects and disconnects with windows plug in-out sound. But it doesnt stop charging. I tried it with multiple cables and PCs, none of them worked. And i dont think there is something wrong with my Quest 3 because im taking good care of it and and im not using it often. Idk what to do, i need some help.

Headset version

 

Link app version ( i tried with v66 too but it didnt work, i could just easily quit from ptc on PC)

 

[MetaQuestSupport]

Hey there, @Zsozsa and @klondorthedestroyer! Hope you're doing well! We just wanted to touch base and ensure you've been able to get Meta Quest Link working as normal on your Quest 3 headsets. If there's anything else you need assistance with, don't hesitate to reach back out. We're here to help make sure you're all set!

[Zsozsa]

The same problem. It works for a while then pc link gets broken. Now I got "General device problem" error message. 

[ShiroTenko]

Hey everyone, can y'all try out this troubleshooting step to see if it helps?

1. Disconnect the Link cable from the computer
2. Disconnect your computer from the internet
3. Backup any necessary content. You can find steps on how to do so by clicking here.
4. Reboot into Safe Mode. You can find steps on how to do so by clicking here.
5. Uninstall the Oculus PC app using the Control Panel. You can find steps on how to do so by clicking here.
6. Delete all Oculus folders from the following folder: C:\Program Files
7. Remove any Oculus folders from the following locations:
   1. C:\Users\YourUserProfile\AppData
   2. C:\Users\YourUserProfile\AppData\Local
   3. C:\Users\YourUserProfile\AppData\LocalLow
   4. C:\Users\YourUserProfile\AppData\Roaming
   5. C:\OculusSetup-DownloadCache
8. Restart your computer in normal mode
9. Reconnect your computer to the internet
10. Install the Oculus PC app again using the setup tool from our website here
11. Reconnect the Link cable and re-test the headset

Let me know how it goes!

[ShiroTenko]

Just wondering, did this help anyone? I would love the feedback from y'all. Thank you!

[Zsozsa]

---

@ShiroTenko wrote:

Just wondering, did this help anyone? I would love the feedback from y'all. Thank you!

---

I tried you advised but no avail. It worked for a while (almost  for one hour) then the disconnection occurred again. The Oculus app recommened using a usb 3 port for it saw the used port as usb 2. But just after one hour... It drives me crazy. I'm thinking to get a used G2 again. That worked flawlessly for two years not just for three months. And nothing has changed in my pc setup not regarding the windows and gpu updates. And of course the quest 3 update, v66. I can connect the beginning of my suffering to the download of this version. 

[ShiroTenko]

Hey @Zsozsa! Did you try to check on your GPU's manufacturer's website to see if there was a new update, and maybe your pc as well?

[Zsozsa]

I checked everything and if there was a new update I installed it. But the final result is the same. After aprox. 1 our it disconnected again. 

[ShiroTenko]

Thanks for letting me know! By any chance is this only with the link cable or with air link as well?

[peevedpenguin]

Hi guys, same issue here but on quest 2 after updating to v66 earlier today. I have tried the ideas above with no luck on either link or airlink. In the meta PC app using either method shows the headset to have a general device problem. Any more ideas on a potential fix?

[TheAntiSocializer]

Hey everyone! Just wanted to jump in here and hopefully get you all pointed in the right direction. 

It is nice to see that @ShiroTenko has already provided some troubleshooting above. I think the next best course of action here though, if those steps don't help out, would be to try and reach out to @MetaQuestSupport through private message. That, or you can jump right to a support ticket where they can get a look into your logs and check the backend of things.