A few days ago, my Meta Quest Link software on the computer updated to version76.0.0.452.315, and since then, the streaming has been constantly freezing on the black screen icon or disconnecting immediately after connecting, stuck in an endless loop of connecting and disconnecting. I tried everything: switching computers, replacing the headset, changing the streaming cable, updating the OS, reinstalling the software... nothing worked.
Yesterday, I attempted to useVirtual Desktop (VD)for streaming instead, but VD doesn’t support Quest’s multimodal features, forcing me to reconsider returning to Meta Quest Link.
Then something strange happened: because I had used VD’s runtime, Meta Quest Link prompted me to set the Quest runtime as default. After following the instructions, Meta Quest Link suddenly started working again. I tested this fix on different computers and could consistently reproduce the solution. I thought the issue was resolved—but clearly, I celebrated too soon.
Today, when I launched Meta Quest Link, the streaming failed again... I repeated yesterday’s steps ("use VD streaming" → "set Quest runtime as default"), but it no longer worked.
Just as I was getting extremely frustrated, I tried changing Meta Quest Link’s language to English. Streaming still failed. Then, I received an update notification. After applying the update, the streaming issue was magically fixed...
But here’s the odd part: the version number remained76.0.0.452.315, identical to the pre-update version.
Now I’m completely unsure why the problem occurred in the first place, why it started working again, or what exactly I did right or wrong during this process...
During the troubleshooting period, I contacted official support and submitted logs, but they claimed the logs "looked normal."
Even though the issue is resolved now, my development work was stalled for days.
I strongly urge Meta to stop forcibly pushing unstable updates.This kind of unpredictability only harms developer confidence.
If possible, could Meta Quest Link implement a"developer-stable branch"(similar to Unity’s model), stop forced updates, or allow developers to roll back to older versions? This would prevent unnecessary disruptions to critical workflows.
Honestly, contacting official support is a waste of time! As usual Meta being irresponsible, with forced unready updates... but honestly what to expect fromt them? 1 in 1000 messages are actually responded by them here in the forums.
Yes. As to the version: The version number is just a string. The real thing that matters is the "Bundle Version Code", which I have no clue if they show us.
