Community Manager

v2.1 PTC Release Thread

Forum|Forum|8 months ago
February 11, 2026
50 replies
4318 views

The Public Test Channel (PTC) for Horizon OS v2.1 has started to roll out.

Release Notes: https://www.meta.com/help/quest/172903867975450/

If you're seeing an issue or bug after updating to PTC v2.1:

1) For issues: Go to our Quest Forums and search for any existing thread on the issue, if you don't find one, make a new thread. Please add the tag "PTC v2.1" to the thread and in the title. This way everyone can look for PTC v2.1 issues.

2) For bugs: If you come across a bug, please post each one you spot in its own thread, to keep track of individual issues separately. Please make sure to also send in bug reports along with posting on the forums if you notice anything going wrong.

Share your impressions in the comments below and let us know if you see any issues.

We know it's tough when you run into a problem on a PTC build and want to thank you all again for testing out PTC and sharing your feedback! This feedback is extremely helpful to our engineering teams. We appreciate your interest and persistence in testing out the core functionality of software as we develop!

Show previous replies

MorpheusXII

Inspiring

I have Q2 that updated on Feb 27th to V2.1.1034 and posted here:
v85/v2.1.1034 Passthrough Loop | Meta Community Forums - 1367976
Only just read this thread so not filed properly, will add PTC v2.1 TAG as I think somehow I got this early update.
Also logged as above via headset and reddit.
+ Will add that as well as issue noted in thread above, the browser after # passthroughs/none passthrough cycles usually crashes. In fact the UI I think is crashing similar to what MS Windows does when explorer crashes, but Q2 is cycling in a loop these crashes. Forcing passthrough on via double tap stops the crashing and can then launch other apps to get out of home UI and this loop of doom. Hope makes sense.....

MorpheusXII

Inspiring

I've just installed update: v2.1 5210......150, this has resolved my problem of UI crashing within the home environment, unless passthrough was enabled manually (or by default at boot which it started to do by itself), YeeHaaa...

H

HapperHapper

New Participant

if i have a longer session with virtual desktop (or maybe other apps, did not test) and i end my session, close virtual destkop, i have often problem returning to meta home, meta home just stuck in the loading screen. (fix for me, open an fully immersed app again, close it again immediately, and then meta home usually loads).

MorpheusXII

Inspiring

I haven't tried going to an immersed app, exiting (noting at this point the Home UI still crashing for me), going back into an immersed app and exiting again. I'll test this next time I'm back in headset to see if a double entry to immersed app fixes, but I think v.low probability....

MorpheusXII

Inspiring

Entering/exiting apps multiple times x2 > x3 did not resolve my home UI crashing. However my last two usages of Q2 I entered home directly in pass through mode immediately on, this gives a stable environment.

Moriarti4

Up and Coming

I've now had 5 or maybe 6 updates to v2.1 and yet still nothing has changed since v85, I honestly believe that the single person left at the meta VR department keeps pressing the same button for something to do?? Poor soul must be so lonely in that department since Mr Z fired all his co-workers.

M

Maccyb123

Honored Contributor

Buetigame 😂 😂Hopefully you'll get it soon ☘️🤞I got v2.1.1034 this morning and got the surface kb with it. So far it's running smoothly and pass through seems a bit clearer than before. But I have a totally different build number! See pic. Meta updates are very mysterious!

B

Buetigame

Participant

Maccyb123 OK, complete build is 5194301.5590.520, coming from 5194301.5050.520 (28th Feb).
First 7 digits = main realease, following 4 digits = subversion, last 3 digits = device
- 150 = Quest 2
- 520 = Quest 3

Never seen such a version string as with yours screen - which kind of device you are using?
And gratulation that the surface keyboard comes to you too!

M

Maccyb123

Honored Contributor

Buetigame Thank you! I have the Quest 3s so that is likely the explanation! 😁

T

TheRealKrom

Inspiring

I made a new thread as suggested and changed the title to include the release but I have heard nothing am I supposed to put in a different area or something

https://communityforums.atmeta.com/discussions/OtherTroubleshooting/ptc-v2-1-both-of-my-quest-3-headsets-are-paperweights/1368411

M

Maccyb123

Honored Contributor

TheRealKrom Just read your post. It's possible that you didn't get a reply as I don't think anyone in the forum here can help you with that. There aren't any Meta employees here, and it looks like you need support from Meta directly. There is no answer we can give except return the headset that's still dead, or if it's outside the warranty period maybe send it to a third party repairer like Fix my Oculus if you're in the US or another if you're in a different country. Good luck!