(Resolved) Known Issue - V62/63 USB-C Debris/Water Warning

Just to add to the statistics, I also randomly get this very same warning message.

I've had to abandon work because of this ridiculous issue that hasn't been addressed in weeks. I use my Quest 3 for work. What is going on? Why is the Oculus software so bad? It's been one of the worst software experiences I've ever had. In the last 2 years of use I've had nothing but issues. Airlink is broken. The link cable is the most unstable and random VR interface I've ever used. I had to switch to Virtual Desktop to have a decent VR experience. 
Why can't we roll back these broken updates? Why is Meta support so bad? Why are there 100s of posts about this issue for weeks and no response from one of the largest and most powerful tech companies on earth? 
If you're going to spend such a huge amount of resources on creating the hardware I simply can't understand why you can't create a piece of software that isn't like a beta. Virtual Desktop was created by a guy in his bedroom as a part-time hobby project and it is FAR, FAR superior to your unreliable software. Or should I say THREE pieces of software(yes, for some bizarre reason we need the software installed on 3 separate devices. 
What an absolute JOKE Meta 'support' is. Meanwhile, we all just have to wait around for the AI generated bs asking us 'did you switch off and on the device?' I'm losing money and work hours here. Please either fix this issues or let us roll back to v60. 

And YES, it is a software issue specifically related to v62. Power off the headset, full shutdown, and it charges. Turn it back on and the v62 bug stops it from charging. 

Just an update on my interaction with support:

1st contact asked for a screenshot of the issue (not possible, though we have all seen the same error message) and whether I was using the Meta Quest 3 Elite Strap with Battery (I'm not).

2nd message (and different person) thanked me for the link to the forum, and answered my question as to whether I could rollback to v60, and he indicated that was not possible.  He also said they were troubleshooting for exact issue I reported, but that it was never previously reported with an update.  The rest of the message went into great detail on how to use a toothbrush to clean my ports out and dry out the unit.  Um, I guess he saw the forum link, but didn't bother to read any of it?

3rd message (again a different person), suggested a factory reset.  I've already factory reset, so that isn't the issue.

Anyway, the messages seemed scripted/canned to me, and I kinda question whether I'm emailing an AI agent.

As for my testing, yesterday I did try fully charging again to 100% and ran for a brief while with the OEM charger plugged in, and then switched to the INIU cable with power going through that for a while including some gaming with no issue, but it wasn't a very long test.  I was more deliberate today when using the INIU cable by first putting power to the cable, then connecting to the headset, then the PC, then turning on the headset, and so far no errors.  Of course, I'm not confident that it won't happen again.

Please fix this. This is urgent and I might potentially lose my job. I need to have my work shipped by tomorrow and this update came out of nowhere. I cannot ship my booth in a broken state. Please let me roll back!!

I have some issue since 1 week

ALways get Liquid or debris has been detected.....

try 2 cable with same result, this deconnect PCVR session and its really frutrating

Also often a get flash of mixed reality in game

And often the tracking is offset and the only way to resolve its to restart de headset

Only 3 week I have this headset and I'm seriously think about returning it

Heard back from the AI support again. 

"Miguel from Meta Store Support here. 

Thank you for getting back to us. 

Would you please confirm with us if the issue is only when trying to use the cable and if the AirLink works? 

Looking forward to hearing from you. 

Best regards,"

My response was Airlink works but the error still pops up when charging. The error occurred directly after doing the V62 update. And of course I attached a link to this thread. 

At this point it is more helpful to find people who don't experience the issue and ask them about their setup.

To un-bend a fork, you must also hold the other side where it isn't bent.

I guess our setup is more specific than what we think. For example,

I use developer mode, i have tried to charge my quest with an Asus rog laptop power brick on PD, I use the oculus link cable with the meta logo on it. My quest come from my local country while my link cable is parallel imported.

(Side note: if meta is putting it at such low priority, it must mean that they are confident about our problems not making to the news. The flip side of it is that we can find many people who DON'T have such problem, so we can compare what they have and what we have, and narrow down the problem space so we pinpoint the conditions that make our misery. I know i am doing their job, but what can i do? sit?)

Anyone know when you buy a new Quest 3, during the innitial setup do you have to connect to the internet? And more important, iff so will it update to v62?

Iff this does not get solved, ill return it because this is not the expected experience that Meta promised.

Small update on my side tonight,  I have the same issue as everone with the V62 update. I run my quest 3 with the Kuject powered cable for sim racing in PCVR

I did roughly a 3h session in ACC, i try to keep de battery percentage below 80% as mentioned in older message this might fix the issue. I started at 79% but didn't plug the power brick in the cable to lower the battery pecentage a little bit more. I did 1h like that drop the pecentage to 60% and no issue at all.

After that i plug the power brick in the cable for the next 2 hour endend at the same 60% at the end of my 2h race and still zero sign of the alarm.

At this point i'm pretty confident that if you keep the battery pecentage under 80% you won't get the alarm since it was almost impossible to play yesterday with the battery a 85-90%.

I still need to test if i get the alarm if i charge over 80% and play with the headset.