Saturday, January 4, 2025

Warning Issued For Meta Quest 3, Quest 2 And Quest 3S Owners

Must read

Meta has issued a statement regarding a serious software issue affecting Quest 3, Quest 3S and Quest 2 VR headsets.

A software bug has caused some headsets to stop booting properly.

Users over at the Meta Quest forums have complained their headsets have effectively been bricked, making them useless.

ForbesMeta Quest 3S Review: 3 Highlights And The Most Important Flaw

“We’ve discovered a software update issue that caused some Quest 2/3/3S headsets to be unresponsive and unable to start up correctly. We are actively working on resolving the issue for all users, but in most cases, you are now able to use your device normally,” reads Meta’s statement on the issue.

“If you have a device that is still unresponsive, we’re here to help.”

Posts over at the Community forums suggest you are more likely to encounter the issue if you have not used your Meta Quest in a while, and find it requires a software update when you pick it back up again.

The issue arises during this update process, causing the headset to become unresponsive.

Right now it may be sensible to wait for a further announcement from Meta before using a headset that has been sat dormant for a while.

One complicating factor is the state these headsets are left in when they are subject to this issue won’t be easy to rectify with a further update, as they do not reach the point at which you could start such a process.

“Quest 2 or 3 users, please reach out to us to get support,” reads the Meta statement, referring of course to those who have affected headsets.

For Quest 3S owners, Meta has instated a devices returns program. You can login to your Meta account over at the Help Center website to see if your device has been affected.

The issue for owners of the older headsets is they are less likely to be under warranty, so could potentially be left entirely out of pocket. One affected Quest headset user writes they were merely offered a small discount on a new model after their one stopped working.

I have approached Meta for additional comment on the issue.

Latest article