Skip to main content
MetaStoreHelp
Community Manager
July 15, 2026

v2.6 PTC Release Thread

  • July 15, 2026
  • 51 replies
  • 4084 views

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

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

If you're seeing an issue or bug after updating:

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.6" to the thread and in the title. This way everyone can look for PTC 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!

    51 replies

    Honored Contributor
    July 15, 2026

    philmanagexr​ Here it is. Excellent timing my friend! 😁 

    New Participant
    July 20, 2026
    Honored Contributor
    July 20, 2026

    This thread is about v2.6 PTC. Maybe look at the v2.4 threads for more info on it. 

    NicoEng
    Up and Coming
    July 21, 2026

    Just got an update to v2.6 yesterday from v2.5 after emailing support. I am still having issues with wifi though. I have a 5ghz and 6ghz network with WPA2, when I play for example Battlemarked I can join a multiplayer game but after I select my character and press play I get a message network connection lost 

    After some experimenting an looking back at posts here I made my 6ghz an OPEN network with MAC filtering and this worked fine. I hope we can get back to using WPA2/3 again as it all seems too open to bad actors now.

    NicoEng
    Up and Coming
    July 22, 2026

    Got a small 6gb update that lets me use WPA2/3 again. Its getting better.

    New Participant
    July 22, 2026

    Hey NicoEng​ how did you trigger that update? I still have the issue, I can't connect to WPA2/3 same as you with the Quest 2. Mine got updated to v2.6 last night and I can't connect to wifi since then... 

    NicoEng
    Up and Coming
    July 22, 2026

    Well originally on the 20th I was on v2.5 and the network connection was not stable. So in the morning UK time I fired off an email to support which they replied to in the afternoon, probably morning for them. They listed a lot of stuff I tried but working through the email one of the fixes was to connect wifi and put the headset on charge for at least 40 minutes. When I checked after an hour the initial v2.6 was waiting, they didn't say they would push it out to me but the timing is a bit of a coincidence. This was the version that did not like WPA2/3. The next morning an update to a newer version of v2.6 (6mb) was available dated 21st of July. Again the timing was suspicious. I think the email to support triggered the whole thing, I hope this helps.

    New Participant
    July 23, 2026

    Since my Quest 3 updated to v2.6, I cannot do 120Hz through the Link cable anymore. On any resolution and bitrate I get constant stutters and jitters just from moving my hands on the desktop.

    I also can't do anything over 500 bitrate at 90Hz anymore. Before this update, I could easily do 90Hz at 900 bitrate, as well as 120Hz at 500 bitrate.

    Now 120Hz is completely unusable, and anything over 500 bitrate is unusable even at 90Hz.

    Has this happened to anyone else?

    New Participant
    July 24, 2026

    I'm not really sure what it means, but I'll learn over time.

    Honored Contributor
    July 24, 2026

    anchoredsoul.1​ As we don't know what you mean, we're all in the same boat. ⛴️ 

    New Participant
    July 27, 2026

    The Horizon Link mute/unmute bug still persists. 
    Since V2.5, whenever the proximity sensor registers that the headset has been taken off,  it mutes the microphone. However it does not unmute it again. So you have to manually go into settings and unmute it. 
    Meta pls fix. 

    Honored Contributor
    July 31, 2026

    What?????????     Ahh, ok you're spamming the community with an email username, you should learn English though, it's not clear what you're trying to spam.. Reported anyway. 

    NicoEng
    Up and Coming
    July 31, 2026

    Just this morning I got v2.7 on the PTC. I cant find a post about it when I checked so I don't know what it's ment to address.

    Choleni
    Honored Contributor
    July 31, 2026

    I cant find a post about it when I checked

    You'll find the release notes here:

    Meta Quest release notes | Quest Help

    So far, the release notes for PTC v 2.7 are not updated for all counties. So, use either VPN, set to an US server, or set the language to "english US".

    Participant
    August 6, 2026

    2.7 PTC makes quest pro an unusable brick. Crashing constantly, controllers dont stay in the correct place at all, overheating errors, freezing even after a full reset just a complete mess

    Honored Contributor
    August 6, 2026

    liamreed​ ​​You're on the PTC program. It's using your headset as a guinea pig to find bugs. If you want a stable experience don't join the PTC. Be patient and wait for official releases. Don't expect much sympathy. All testers have these issues.