A VR headset sits on a desk beside a computer displaying device authorization and setup controls.
Setting up a Meta Quest headset for development from a Windows PC takes a developer account, a phone toggle, a USB driver and a data cable. This guide covers each step, plus what to check when adb devices comes up empty. It also fixes a few things older tutorials get wrong, starting with the name of the tool.

A VR headset sits on a desk beside a computer displaying device authorization and setup controls. The tool is now called Meta VR Developer Hub​

Many guides, including the shattered.io walkthrough that prompted this piece, still say "Meta Quest Developer Hub" (MQDH). Meta's current documentation calls it MVDH, with downloads for macOS and Windows. It was called Oculus Developer Hub before that. The name has changed twice, but it is the same desktop companion app.

The Windows listing that shattered.io cites is build 6.5.2, dated September 16, 2026. I could not verify a newer Windows installer, so check the download page for what is current. Version numbers in older tutorials, such as "4.0 or later for Quest 3", are historical and no longer a useful guide.

Prerequisites​

Meta's device-setup page is specific about what must be true before Developer Mode will switch on:

  • A registered Meta developer with a verified Meta account.
  • You are at least 18 years old.
  • The device has no device-level restrictions that prevent enabling developer mode.
  • Membership of a developer team on the Meta Horizon Developer Dashboard, created or joined before you can enable the mode.

Verification is usually quick. A community guide from VR Content Lab says you only need to do one of two things: turn on two-factor authentication, or add a credit card. Meta's own documentation lists verification requirements for publishing Store apps separately. For local sideloading, the team and verified account above are what matter.

You also need a USB-C cable that carries data, not one that only charges. A Windows PC with the headset's USB driver installed completes the list.

Step 1: Enable Developer Mode in the phone app​

Developer Mode is not a Windows setting. It lives in the Meta Horizon mobile app. Meta's steps are:

  1. Open the Meta Horizon app on your phone.
  2. Tap the headset icon in the toolbar.
  3. Tap the paired headset item.
  4. Tap Headset Settings.
  5. Tap Developer Mode and switch it on.

If the toggle is missing, the usual cause is an account mismatch. The headset's Meta account must be the one on the developer team. Meta also notes the app may ask you to join a developer team first.

Step 2: Install the Oculus ADB driver on Windows​

Windows needs a driver before ADB can see the headset. Meta's page says to install the Oculus ADB Drivers (Windows only) so that ADB can communicate with your device to push builds. The older documentation describes the procedure:

  1. Go to the Oculus ADB Drivers page and click Download.
  2. Unzip the downloaded file.
  3. Right-click the .inf file and select Install.

The VR Content Lab guide offers a pragmatic rule. It says to install the driver only if SideQuest, Quest Games Optimizer, MQDH, or adb devices can't detect your Quest. Both approaches are reasonable. Installing it up front costs a minute, and skipping it costs an hour of head-scratching if the headset doesn't show up.

Step 3: Install MVDH and Android Platform Tools​

Download MVDH for Windows from Meta's developer download page and sign in. Meta says to use the same Meta developer credentials you used to log in on the headset.

For command-line work, install Android Platform Tools so adb is available. Meta's browser-debugging page lists this as a prerequisite. MVDH ships with its own ADB, but a separate copy on your PATH is handy for scripting. That second copy is also the source of the most common ADB annoyance, covered below.

Step 4: Connect and authorize USB debugging​

Connect the headset to the PC with the USB-C data cable and put the headset on. Meta's quick-start guide says the device will prompt you to allow USB debugging, and you must accept this on the device, not on your PC. Choose the "always allow from this computer" option if you want the approval to persist. Then verify the connection:

adb devices

Meta's documentation says the headset should appear in the output with the status device. If it shows unauthorized, the prompt is still waiting inside the headset. If the list is empty, check your cable, drivers, and that USB debugging was accepted.

Step 5: Install an APK​

With the headset authorized, you can install a prebuilt APK:

adb install path\to\your-app.apk

Meta's documentation says apps installed this way don't appear in the main app grid. After at least one such install, an Unknown Sources tab appears in the headset's Library. Developer Mode lets the headset install and debug apps from outside the Meta Horizon Store. It is not a jailbreak, and the documentation doesn't present it as one.

Only install builds you made yourself or got from a publisher you trust. An APK runs with whatever permissions you grant it.

Fix: the headset keeps appearing and disappearing​

Meta's troubleshooting section covers a flaky adb devices list. The cause is competing ADB installations, for example the one bundled with MVDH and the one from your SDK, each restarting the other's server. Meta's fix is to check which ADB executable your shell finds first. On Windows, run where.exe adb instead. If the first result isn't the copy you want, prepend the SDK's platform-tools directory to your PATH. Using one ADB binary consistently, or one tool at a time, stops the tug-of-war.

Performance work: what the 6.5.2 release changed​

Anyone using the Performance Analyzer should know what changed in the Windows 6.5.2 release, which Meta's release notes describe. These details are not in older tutorials.

  • Trace capture was redesigned around named presets, including CPU Low Overhead, GPU Surface and Metric, and Render Pass Diagnosis.
  • GPU profiling is a per-device opt-in and is off by default.
  • Heavy-overhead presets warn before capture.
  • Metrics work again on current Horizon OS versions, including Quest 3. Charts on v57-and-newer systems had shown dashes or empty graphs.
  • Wi-Fi ADB file renaming and connection-status reporting were improved.

If graphs are blank, updating both Horizon OS and MVDH is a sensible first step. This is a version-specific fix, not universal behavior.

Reading the numbers​

Meta's OVR Metrics guidance gives frame budgets of about 13.9 ms at 72 Hz, 11.1 ms at 90 Hz and 8.3 ms at 120 Hz. Meta's general guidance says apps must hit a minimum of 72 FPS. Quest 3 and 3S also support 90 and 120 Hz. The target therefore depends on the refresh rate you are testing, and a Quest 3 session is not automatically running at 120 Hz.

Meta recommends the Basic metrics preset for ordinary checks. The Advanced preset adds overhead and can misrepresent final performance. Tracing has the same effect, so take headline numbers from an untraced run.

One known issue: Meta's developer issue tracker confirms that on Quest 3, OVR Metrics Tool has shown invalid CPU/GPU levels of 7 and 8, while MVDH has reported -1 for those fields. Meta lists the investigation as ongoing. Rely on frame timing, not those level labels.

Quest 2 and Quest Pro: legacy, not unusable​

Meta's November 2, 2026 developer announcement says Quest 2 and Quest Pro reach the end of feature development with v213:

  • v2.13 is the final OS release and v213 the last supported SDK version.
  • New OS features, platform capabilities and APIs after that are limited to Quest 3, Quest 3S and newer devices.
  • Quarterly security patches and critical bug fixes continue through the end of 2027.
  • New app submissions supporting those devices remain possible through December 2027.
  • PC VR via Link continues.

Developers who still support these headsets should keep them in their test matrix. They remain valid targets, but without new platform features.

Lock down when you finish​

Developer Mode is a convenience that widens your attack surface:

  • Turn Developer Mode off in the Horizon app when a project ends, especially on a household headset.
  • Run adb kill-server to stop the background ADB process on the PC.
  • Avoid enabling network debugging on untrusted networks.
  • Remove sideloaded apps you no longer need with adb uninstall <package name>.
  • Keep disk encryption on for any PC holding an authorized ADB key.

Caveats on the source guide​

The shattered.io piece adds a Python audit script, a Wi-Fi ADB routine, a Linux udev rule, hardware price tables and warranty and parental-control statements. I could not independently confirm those against Meta's documentation. Its "60 minutes" is the author's estimate, not a Meta figure. Treat those parts as one author's workflow, and check Meta's current documentation before relying on them.

The core path is short: verify the account, flip the toggle, install the driver and tools, approve the prompt in the headset and install your APK. Most failures come from a charge-only cable, a missed prompt or two competing ADB copies.

 

References

  1. Meta Quest Developer Hub: 12 Steps, 60 Min (2026) - shattered.io shattered.io 2026-11-16T18:18:48+00:00
  2. Get Started with Meta VR Developer Hub developers.meta.com
  3. How to Enable Developer Mode on Meta Quest — VR Content Lab vrcontentlab.com