Skip to main content
bom38l
New Participant
Nov 20, 2026 11:38 PM UTC
Question

Oculus Debug Tool v210 Incompatible with OVR Runtime v208 – ASW Disabled Setting Does Not Apply (Error -3002)

Oculus Debug Tool v210 Incompatible with OVR Runtime v208 – ASW Disabled Setting Does Not Apply (Error -3002)

Hello Meta Quest Community,

I am experiencing a compatibility issue between the Oculus Debug Tool (ODT) and the OVR Runtime when using Meta Quest Link via USB on my PC.

I am posting this because I have tried multiple troubleshooting steps, including a clean reinstall and testing the Public Test Channel (PTC), but the issue remains unresolved.

1. System and Software Versions

My current software versions are:

  • Headset: Meta Quest 3

  • Connection: Meta Quest Link via USB cable

  • GPU: NVIDIA GeForce RTX 5080 AORUS

  • CPU: AMD Ryzen 7 9800X3D

  • Oculus Debug Tool: 210.0.0.96.541

  • Meta Horizon Link / OVR Runtime: 208.0.0.84.535

2. Main Issue – Version Mismatch

When launching OculusDebugToolCLI.exe, I receive the following error:

Unable to start debug session... mismatch between installed runtime version and SDK version... built against 1.210.0

On the Stable channel, Oculus Debug Tool also displays:

Unable to connect to service. Insufficient LibOVRRT version. Requested major.minor version: 1.210; LibOVRRT version: 1.208. Error code: -3002

This indicates that ODT v210 is attempting to communicate with an OVR Runtime v208 installation.

3. ASW Setting Does Not Apply

My main objective is to permanently disable Asynchronous Spacewarp (ASW).

When I select:

(PC) Asynchronous Spacewarp = Disabled

in Oculus Debug Tool, the setting does not seem to take effect.

I also tested the Public Test Channel (PTC):

  • ODT launches successfully on PTC.

  • However, setting ASW to Disabled still does not appear to apply to the running Link session.

  • The CLI continues to report a runtime/SDK version mismatch.

In other words, PTC allows ODT to launch, but it does not resolve the actual ASW control problem.

4. Troubleshooting Already Performed

I have already tried the following:

  1. Completely uninstalled Meta Horizon Link.

  2. Removed the remaining installation files.

  3. Reinstalled Meta Horizon Link from the official installer.

  4. Tested both Stable and Public Test Channel versions.

  5. Restarted the PC and Quest 3.

  6. Tested the ASW keyboard shortcuts, including Ctrl + NumPad 1.

  7. Collected Oculus diagnostic logs and shared them with Meta Support.

Unfortunately, the same version mismatch returns after reinstalling.

5. Meta Support Response

I contacted Meta Support and provided the exact version numbers and error messages.

Support acknowledged the mismatch between ODT v210 and OVR Runtime v208, as well as the fact that the ASW settings fail to apply even on PTC.

They recommended posting on this Community Forum so the engineering team can review the issue, and submitting a formal bug report.

6. Questions for Meta Engineering

I would appreciate clarification on the following:

  1. Is Oculus Debug Tool v210 currently incompatible with OVR Runtime v208?

  2. Why does the official installer provide ODT v210 while the installed runtime remains at v208?

  3. Is this a known issue currently being investigated by the engineering team?

  4. Is there a compatible ODT version for Runtime v208?

  5. Is there a reliable workaround to permanently disable ASW until the compatibility issue is fixed?

I am not looking for generic troubleshooting steps such as reinstalling the software again. I have already performed a clean reinstall multiple times. The issue appears to be a software version compatibility problem that needs investigation.

I would appreciate confirmation from a Meta engineer or someone experiencing the exact same issue.

Thank you.

 

4 replies

Expert Contributor
Nov 21, 2026 1:53 AM UTC

​@bom38l  This has been discussed a few times already mate.  For now you just need to select the meta-link pc app public test channel (beta).  Hopefully meta will rollout an updated non-beta version soon.  Cheers 

9800x3d, rtx5090, X870E MB w/wifi7, 64Gb 6000 ram, 2x2TB SSD, 1000W PSU, Win 11pro, QPro, Q3, w/Link and Air Link, Vive Pro1 with 2x2.0 base stations, Etsy lens mod and Index Controllers
bom38l
bom38lAuthor
New Participant
Nov 21, 2026 6:45 PM UTC

Thanks mate. I've already tested the PTC, but unfortunately it doesn't fully resolve the issue.

ODT launches on PTC, but setting ASW to Disabled still doesn't take effect, and the CLI reports a runtime/SDK version mismatch.

I'm waiting for Meta to release a proper fix for the Stable version. Hopefully they address the ODT and Runtime version mismatch soon.

steve40
Honored Contributor
Nov 21, 2026 2:07 AM UTC

v2.08 PC app should update automatically to v2.10 if you have auto-update set (at least mine did). Settings>General>Automatic App Updates. You might just need to leave your PC switched on until it updates itself. Check Library>Updates to see if there is a pending update. Or switch to PTC like TomCgcmfc suggested.

bom38l
bom38lAuthor
New Participant
Nov 21, 2026 6:44 PM UTC

I appreciate your suggestion, but I have already tried this.

Automatic updates are enabled, and I also checked Library > Updates. I tested the Public Test Channel (PTC) as well.

The issue is that my installation still has:

  • Meta Horizon Link / OVR Runtime: v208.0.0.84.535

  • Oculus Debug Tool: v210.0.0.96.541

Even after a clean reinstall and testing PTC, the version mismatch persists.

The problem is not that I don't know how to update the application. The problem is that the installer provides ODT v210 while the installed runtime remains v208.

Has anyone actually managed to get both components running on matching v210 versions?