Skip to main content
Community Manager
March 21, 2025

PTC v76 Release Thread

  • March 21, 2025
  • 161 replies
  • 38451 views

Hey Everyone,

The Public Test Channel (PTC) for Quest v76 started to roll out today for Meta Quest 2, Meta Quest Pro, Meta Quest 3 and Meta Quest 3S.

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

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

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!

 

    161 replies

    New Participant
    April 8, 2025

    I see v76 just released. Does anyone know what the build number is for the v76 public release? I'm assuming it's the same for the PTC at this point but not sure. 

     

    ConvexRook
    Participant
    April 8, 2025

    They release the buggy **bleep**?

    New Participant
    April 9, 2025

    I love the release notes:

    These features and enhancements will become available starting the week of April 8, 2025 and will be pushed to Meta Quest 3, 3S, Meta Quest Pro and Meta Quest 2 headsets.
    Worlds

    Meta Horizon Worlds is now integrated into the Horizon platform experience, making it more accessible for everyone to connect and explore. Meta Horizon Worlds will now appear as simply “Worlds”.
    Advertising ID for Horizon OS

    Your advertising ID is a unique device indicator that app developers can use to show you more relevant ads on Meta Horizon OS. You can enable or disable your advertising ID at any time by going to Settings in your headset. Advertising IDs may not be available to everyone.

     

     

    How is this anything new and says anything about bugs.

     

    Did Meta ever heard about what release notes / changelogs are supposed to tell you? How about just writing "Changed things" every month...

    Honored Contributor
    April 9, 2025

    Updated to the release version of v76.

    The most notable change is the tone notification when charging begins is gone.

    I found this to be very useful.

    Please bring this back as an option.

    Participant
    April 9, 2025

    Still haven't got access to update to public version I'm guessing it's not being rolled out to the UK yet?

    Honored Contributor
    April 12, 2025

    It means your headset hasn't updated Yet. Meta states that rollouts are not done by region. People that have multiple headsets that update a different times and different versions would seem to bear out what Meta claims.

    PenguinInChicago
    Inspiring
    April 12, 2025

    Selfie CameraSelfie Camera is back.

    Thanks, Derek aka Papal Penguin https://www.papalpenguin.com https://twitch.tv/papalpenguingaming
    April 13, 2025

    casualgodgaming  you could try Basti's repository for the latest version.

    Quest 3 .zip Firmware Update Archive

    Inspiring
    April 14, 2025

    In addition to not solving a charging issue (with Q3 off yet plugged into USB on PC), the public version of v76 now causes connection issues on various ports on my computer (that worked fine over the last year), and causes hand tracking to stop working if you enable Link and then quit Link.

    Inspiring
    April 14, 2025

    Is the Wi-Fi speed regression with the Quest Pro going to be fixed soon?  This is a serious bug, especially since you cannot roll back to V74.  The bug is present in the official V76 release and is affecting everyone with a Quest Pro, despite myself having reported it using the in-headset bug report tool with each V76 PTC release.

    I'm a little confused and frustrated as to why this bug is present in the official release, as I thought the point of PTC was to catch major issues like this before pushing out the official update.  It seems like my bug reports were totally ignored?