Skip to main content
Honored Contributor
May 23, 2024
Question

Known Issue - V65 - V67 USB-C Debris/Water Warning

Not a solution - Marking for visibility

Known Issue

Hello everyone!

I have observed that a significant number of users are still encountering the USB-Debris error even after the V64 fix was distributed to everyone. Consequently, I have taken the initiative to inform the team and create this fresh post in order to distinguish between those who faced the issue in the previous post and those who are currently experiencing it on V65-V67.

We would greatly appreciate if everyone could please provide the following information:

  1. What's the full version number of your headset? (62.0.0.####### or likewise)
    • Quick Settings > System > Software Update
  2. What's the full version number of your PC app? (62.0.0.####### or likewise)
    • General > Scroll down to the bottom of the page.
  3. Is your PC app on PTC?
  4. Are you enrolled in Quest PTC?
  5. Any potential workarounds?
  6. Which headset is everyone using? Is this only happening with the Quest 3 currently, or is anyone experiencing the same thing on their Quest 2 and Pro

I'll do my best to keep you all updated as soon as I find out anymore information!

Update 5/26/24

Hey everyone, a little update for you - our awesome engineers are on top of this issue. Don't forget to send in your detailed reports and share any info you have, especially if this problem is new to you. Your input is super valuable!

Update 6/6/24

I just wanted to give everyone a quick update that there haven't been any major changes yet. However, I want you all to know that I'm actively monitoring this thread every day and passing on any information that users provide to the engineering team.

Update 6/11/24

The engineering team would like me to gather the serial numbers of the headsets of all those affected. Please send me a private message with your serial number.

Please do NOT send your serial number in this or any thread publicly.

Update 7/3/24

Thanks to all who sent in their Serial numbers. Our engineers are still looking into this matter and are working hard to resolve it in an future software update.

Update 7/9/24

We appreciate all those who have provided their serial numbers. If you are still encountering the issue even after updating to V66, please reach out to our support team via private message here for further troubleshooting assistance.

This topic has been closed for replies.

111 replies

New Participant
July 13, 2024

Just updated OS.

1. V67. 67.0.0.648.356.621284304

2. 67.0.0.206.355

3. No

4. No

5. Lower amperage cables have the problem less frequently, but can not keep my Quest 3 fully charged and playable.

6. Quest 3.

Sadly, updating from v66 to v67 did not help. I PM'd my serial number 2 weeks ago.

Tried a factory reset, did not help.

 

New Participant
July 14, 2024

Bought two new Oculus Meta Quest 3 512Gb headsets in Switzerland last week, they both have the USB debris false positive issue, even when the Oculus Link Cable (genuine, bought together) is simply connected to a USB charger. Upgrading to V67 didn't change anything. Where can I send the 2 serial numbers?

Participant
July 15, 2024

I recently had this problem. Initially, it occurred infrequently (about ten days ago), but it has become more frequent since then, to the point where it hardly charges at all. I have always used the official Meta Quest charger (except recently to see if the problem was with the charger, which it wasn’t). It refuses to charge even when turned off, except sometimes when I replace the USB cable, but this doesn’t last long. I have always taken good care of my Meta Quest, which I bought a few months ago (about 5-6 months). It has never been dropped, and there have never been any debris or water in the USB port! In short, I only have 10% battery left, and it refuses to charge…

Participant
July 15, 2024

Hello everyone!

After surprisingly reading all the literature on this subject, I am wondering... I have this problem with the Quest 3 that I bought new just 4 months ago and have always taken great care of.

Either the USB problem is software-related, but I am surprised that it hasn’t been resolved after all this time, or it is hardware-related, which would imply a significant issue that we could call the "Meta usbCgate problem." It is therefore important to determine which series have been affected.

It would be interesting to know how long you have had this problem and if any of you have managed to solve it permanently... This information does not appear in the messages.

It goes without saying that a replacement with a new device is mandatory if a hardware problem affects a particular series. Our means of pressure are limited but real: just report this problem on all major sales platforms and in journalistic reviews of the Meta Quest 3. If necessary, write to certain VR magazines or even create a dedicated website and promote it.

I have no doubt that Meta is doing its best to address this problem, and the Meta Quest is an excellent product. However, it is essential to explain to us the reasons for this issue because otherwise, it is a product whose lifespan does not exceed a few months for some users and loses all its value. Maybe the USB port is too fragile, or the sensor has a hardware bug? In short, I can't speak for them, but it is crucial to shed light on this matter so that the community can maintain its trust in Meta!

Participant
July 15, 2024

After various tests and trials, I realize that the problem is different if I use low-power chargers. At that moment and only then, it accepts to charge for now. But as soon as I use the official charger or other chargers (33W, for example), the same problem occurs; nothing happens... Among those encountering the USB test problem, can you try with very low-power chargers and let us know your results? The issue does not seem to come from the USB port as indicated but rather from the acceptance of the charger's power in relation to the battery...

Participant
July 15, 2024

Well, in fact even with  low-power charger, the pb still occur few minutes later when using it and it refuse to charge if i use it for few minutes. May be all this is related to the temperature ? It's very very strange...

New Participant
July 16, 2024

I've given up and manually switched to an old driver v57, and reset the firmware on my Quest 3. Of course, you have to prevent the Quest 3 from updating, but there is good information online about how to do that. With the old driver v57, this error message still appears but much, much less frequently. I race online, and this problem is critical. Why can't they make this error message transparent so that the game you're playing remains visible? That would immediately solve the problem.

New Participant
July 19, 2024

Got my new quest 3 a couple of days ago. Took it out of the box, installed the update and then experienced this issue straight away. This is my second unit (the first one didn't have this issue but a stuck pixel). Should I simply return it and get another unit? 

1. 67.0.0.648.356.621284304

2. 67.0.0.206.355

3. No

4. No

5. No

6. Quest 3

Participant
July 21, 2024

V68 has not solved the issue

Participant
July 23, 2024

I'am not sure that the V64 fix or the V65/66/67/68 have solved any issue for anyone ! I haven't found any message in the previous post that say "great fix, i haven't got the usbC pb any more"...Still not charging for me with regular charger only the lowest one (it took hours to charge the quest 3 !). I think this is a big problem...Months of delay for a critical error, i don't understand why no one is complaining...

Up and Coming
July 23, 2024

We are complaining, we submitted out bug reports  we asked for help and we are ignored.

Participant
July 23, 2024

To everyone still battling this problem - I have been dealing with it from one day to another since the OS upgrade to v62. It got progressively worse with the v65/66 upgrade.

Since I could no longer attach any cables during use (and even charging when completely powered off became pretty much hit an miss), I finally managed to get the AI customer service to send me a return label to get it fixed/replaced.

Long story short, my (refurbished) replacement unit seems to be okay so far. I assume some of their USB-C ports or temperature sensors are simply faulty or oversensitive and no number of submitted error logs or or serial numbers (or waiting for software updates) will fix the issue if it still persists.

Participant
July 24, 2024

Started the replacement process yesterday. Hopefully I get a good one and not someone else’s problem. Mine is pristine except for this error. They said if I’m still getting the error with v68, then it needs replaced. 

Participant
July 25, 2024

After futile attempts to reboot, I took my Quest 3 to the warranty service since it still refused to charge with a conventional charger and was giving me the USB debris/water bug. We'll see if the new one has the same problem.

Up and Coming
August 11, 2024

(snip)