Skip to main content
New Participant
September 5, 2026
Question

Dev Mode won't enable - "Unexpected Error" / "Unable to enable developer mode" in MQDH (Quest 2)

  • September 5, 2026
  • 4 replies
  • 167 views

Adding another data point to the ongoing Developer Mode enablement / "Unexpected Error" investigation (ref: investigation 1140973032424639), because I appear to be a textbook case and I've run out of steps the documentation asks for.

Toggling Developer Mode in the Meta Horizon phone app returns "Unexpected Error - please make sure your headset is connected to Wi-Fi and updated to the latest OS version." It is on Wi-Fi. OS is up to date. The error fires, every time, and has for weeks.

I ruled out the obvious things first:

  • Developer organization created; I'm the admin.
  • Account verified with SMS two-factor - after the SMS system made me request the code four times, which turned out to be a fitting preview of the day.
  • Headset on the latest public OS build.
  • Headset shows Connected (green) in the app; correct account signed in across the headset, the app, and the dashboard.
  • App permissions (Nearby Devices, Location), phone Bluetooth, and Location services all enabled.
  • Cleared the app cache, full power-cycled the headset and phone, logged out and back into the app. No change.

Then I tried Meta Quest Developer Hub. Same wall. Device Setup detects the headset, shows the correct account and "Connected to Bluetooth," then dies on "Unable to enable developer mode on headset." Good connection, right account. Whatever is broken lives on the server side of the fence.

For completeness I tried to complete Org Verification via Admin Verification, on the theory it might be the missing unlock. The ID scanner has now rejected six clean, well-lit photos in a row, so I can't even finish that step to test the theory.

I opened a support ticket a few weeks back. It was auto-closed in three days with no human contact.

  1. Please attach this to the existing Developer Mode enablement investigation so it's counted.
  2. If there's a known server-side reset or workaround for accounts stuck in this state, I'd genuinely appreciate it.
  3. If this is just pending a system-update fix, even a rough timeline would save a lot of people a lot of evenings.

Device: Meta Quest 2, latest OS (exact build available on request). MQDH latest version. Happy to provide serial, account email, and exact build numbers privately to staff. Thanks for reading.

4 replies

New Participant
September 14, 2026

Circling back. This is a serious bug, I would argue that my device is non-functional in the absence of dev mode enablement, would like to know whether this bug is being addressed.

steve40
Honored Contributor
September 14, 2026

Have you done the credit card for ID thing? Because you need to.

New Participant
September 14, 2026

You mean license? I did all the ID steps in the admin verification process. As I mentioned above, the process fails every time I attempt it.

New Participant
September 30, 2026

Same issue. Any response from Meta?