Forum Discussion

shichao2992's avatar
shichao2992
Explorer
4 months ago
Solved

Meta Horizon Link login always redirects to language settings page

Hi,

 

I’m having a persistent login issue with Meta Horizon Link on Windows. When I click “Log in / Create account” in the Horizon Link desktop app, it opens my browser but I am always redirected to https://auth.meta.com/language.

 

Even if I log out and sign in again successfully in the browser, Horizon Link stays on “Continue in your browser” and never finishes the login. I only see the language settings page again and again.

 

What I have tried so far:

– Synced my PC system clock and time zone (UTC+08:00, China)

– Cleared cache and cookies, and tried Incognito/Private windows

– Disabled all browser extensions, including ad-blockers and security extensions

– Tried different browsers (Chrome, Edge, Firefox)

– Repaired and reinstalled Meta Horizon Link

– I’m using a VPN, and I can log in normally on my Quest headset, the mobile app, and Meta Developer Hub with the same account.

 

However, Meta Horizon Link still cannot log in and always redirects me to the language settings page.

 

I am located in mainland China, in case that is relevant.

 

Is this a known issue with Meta Horizon Link right now? Is there anything else I can try, or can someone from Meta please help check this?

  • steve_40's avatar
    steve_40
    4 months ago

    Something is wrong with your Link installation.

    Make sure that the Windows service "QWAVE" is running and not disabled.

    Try downloading the installer again, reboot your PC then run the Link installer and select "repair" when it gives you that option.

    Btw, which headset do you have?

17 Replies

  • Choleni's avatar
    Choleni
    MVP
    4 months ago

    Hi shichao2992​ 🙂

    shichao2992 wrote:

    I’m using a VPN,

    shichao2992 wrote:

    I am located in mainland China, in case that is relevant.

    Maybe, VPN is the issue? 🤔

    Here was another user from China recently, who wasn't able to log into the link app, although he could log in to the web page, headset and mobile app just fine...... it was not exactly the same issue, though.

    Can't log into Meta Quest Link PC, stuck on "Continue in Your Browser" | Meta Community Forums - 1359740

    He is using steam vr now..... maybe thats' s an option for you too.

    Steam Link on Meta Quest

    In case you want to talk with support.... you can do that via email, chat or WhatsApp HERE

     

    • Choleni's avatar
      Choleni
      MVP
      4 months ago

      steve_40​  he said he already synced the time, but ........ maybe he have to sync it to the time of the server he uses with VPN, not to his country?🤔

      • shichao2992's avatar
        shichao2992
        Explorer
        4 months ago

        Hi Choleni​ , thank you for the suggestions and for pointing me to the right things to check (system time sync, disabling blockers, and trying a different default browser).

        Here’s what happened on my side, in order:

        Initial symptom: no matter whether I launched the login from Meta Horizon Link or opened auth.meta.com directly, the flow kept ending up on the language settings page (and the desktop app stayed stuck on “Continue in your browser”).

        I also briefly saw URLs indicating the SSO token was missing/empty (e.g. error=missing_sso_etoken / native_sso_etoken=)

        What we found during troubleshooting: there was a registry inconsistency on my PC. Oculus/Meta keys existed under

        HKLM\SOFTWARE\WOW6432Node\Oculus VR, LLC\...

        but the expected non-WOW6432Node path was missing:

        HKLM\SOFTWARE\Oculus VR, LLC\...

        This seemed to correlate with the “missing token / language page loop” behavior.

        After fixing that registry path (copying the values into the non-WOW6432Node location), the SSO flow improved: the auth.meta.com/native_sso/confirm?...native_sso_etoken=... page started showing the “Sign in as …” account selection instead of looping back to language settings.

        What is still broken: after clicking “Sign in as …”, the PC app still fails to complete login and closes/crashes, and then it goes back to being unable to proceed.

        So your advice helped us narrow it down: the issue doesn’t look like “just a browser choice” anymore. It looks like the PC client/runtime is failing during the handoff after the browser step, potentially triggered by the registry/config inconsistency (and possibly network conditions in mainland China).

        If there’s any official guidance on registry path mismatches like WOW6432Node vs non-WOW6432Node, or recommended next steps when the app can reach the “Sign in as …” page but cannot finish login, I’d really appreciate it. Thanks again.

    • shichao2992's avatar
      shichao2992
      Explorer
      4 months ago

      Hi steve_40​ , thanks for the suggestions.

      I double-checked that Windows time is correctly synced, and I also disabled browser/PC content blockers. That did help me get further in the login flow, but I’m still blocked by a crash on the PC app side

      What we found so far:

      The app initially seemed to have a registry/config detection issue: HKLM\SOFTWARE\Oculus VR, LLC\Oculus did not exist, while the values were present under HKLM\SOFTWARE\WOW6432Node\Oculus VR, LLC\Oculus.

      After copying the relevant keys from WOW6432Node → HKLM\SOFTWARE\Oculus VR, LLC, the login flow improved: opening the auth.meta.com/native_sso/confirm?...native_sso_etoken=... link shows the “Sign up as …” option correctly.

      However, once I click “Sign up as …”, Meta Horizon Link immediately crashes, and Windows Event Viewer shows the fault is OVRServer_x64.exe (version 83.0.333.349) with exception code 0xc0000409. After that, the app shows “Unable to contact Link service” / requires repair.

      So at this point it looks like the auth redirect/token step can succeed, but the local Link service/OVRServer crashes right when the app tries to consume the token.

      If you’ve seen any known fix for OVRServer_x64.exe crashing during native SSO (or any logs/diagnostic switches you recommend), I’m happy to collect and share them. Thanks again.

      • steve_40's avatar
        steve_40
        Honored Visionary
        4 months ago

        Something is wrong with your Link installation.

        Make sure that the Windows service "QWAVE" is running and not disabled.

        Try downloading the installer again, reboot your PC then run the Link installer and select "repair" when it gives you that option.

        Btw, which headset do you have?

  • Llib_Gnauh's avatar
    Llib_Gnauh
    Honored Guest
    3 months ago

    This is the solution for those of you using VPN:

    To fix the UseSystemProxy error and force the Meta Horizon (Oculus) app to utilize your Windows system proxy settings, follow these steps to manually add the missing registry values.

     

    Step 1: Open Registry Editor as Administrator

    Press the Windows Key, type regedit.

     

    Right-click Registry Editor and select Run as administrator.

     

    Step 2: Update the Native (64-bit) Path

    In the address bar at the top, paste the following path and press Enter:

    HKEY_LOCAL_MACHINE\SOFTWARE\Oculus VR, LLC\Oculus

     

    Check if there is a sub-folder (key) named Config.

     

    If it does NOT exist: Right-click the Oculus folder, select New > Key, and name it Config.

     

    Click on the Config folder to open it.

     

    Right-click in the empty white space on the right pane.

     

    Select New > DWORD (32-bit) Value.

     

    Name the new value UseSystemProxy (ensure there are no spaces).

     

    Double-click UseSystemProxy, set the Value data to 1, and click OK.

     

    Step 3: Update the WOW6432Node (32-bit) Path

    Navigate to the following path:

    HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Oculus VR, LLC\Oculus

     

    Check for a Config key here as well.

     

    If it does NOT exist: Right-click Oculus, select New > Key, and name it Config.

     

    Right-click in the right pane of the Config folder.

     

    Select New > DWORD (32-bit) Value.

     

    Name it UseSystemProxy.

     

    Double-click it, set the Value data to 1, and click OK.

     

    Step 4: Restart Services

    For these changes to take effect, the background services must reload the registry:

     

    Press Ctrl + Shift + Esc to open Task Manager.

     

    Go to the Services tab.

     

    Find OVRService (Oculus VR Runtime Service).

     

    Right-click it and select Restart.

     

    Why this helps:

    By default, the Meta PC client may try to bypass system-level proxies to establish a direct connection. In environments where direct connection to Meta's "Graph" servers is restricted, this often leads to the login crash you observed. Setting this value to 1 explicitly tells the OVRServer_x64.exe process to respect the proxy or VPN settings configured in your Windows Internet Options.

    • steve_40's avatar
      steve_40
      Honored Visionary
      3 months ago

      What are you talking about? OP already solved their problem simply be reinstalling the Link app.

  • laolian66's avatar
    laolian66
    Honored Guest
    2 months ago

    老哥我也出现了这个问题，依照你的回复我做了你做过的所有流程并把Oculus VR, LLC复制到了SOFTWARE底下，但是依旧没有改善，请问目前你解决这个问题了吗？

    • Llib_Gnauh's avatar
      Llib_Gnauh
      Honored Guest
      23 hours ago

      To fix the UseSystemProxy error and force the Meta Horizon (Oculus) app to utilize your Windows system proxy settings, follow these steps to manually add the missing registry values.

       

      Step 1: Open Registry Editor as Administrator

      Press the Windows Key, type regedit.

       

      Right-click Registry Editor and select Run as administrator.

       

      Step 2: Update the Native (64-bit) Path

      In the address bar at the top, paste the following path and press Enter:

      HKEY_LOCAL_MACHINE\SOFTWARE\Oculus VR, LLC\Oculus

       

      Check if there is a sub-folder (key) named Config.

       

      If it does NOT exist: Right-click the Oculus folder, select New > Key, and name it Config.

       

      Click on the Config folder to open it.

       

      Right-click in the empty white space on the right pane.

       

      Select New > DWORD (32-bit) Value.

       

      Name the new value UseSystemProxy (ensure there are no spaces).

       

      Double-click UseSystemProxy, set the Value data to 1, and click OK.

       

      Step 3: Update the WOW6432Node (32-bit) Path

      Navigate to the following path:

      HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Oculus VR, LLC\Oculus

       

      Check for a Config key here as well.

       

      If it does NOT exist: Right-click Oculus, select New > Key, and name it Config.

       

      Right-click in the right pane of the Config folder.

       

      Select New > DWORD (32-bit) Value.

       

      Name it UseSystemProxy.

       

      Double-click it, set the Value data to 1, and click OK.

       

      Step 4: Restart Services

      For these changes to take effect, the background services must reload the registry:

       

      Press Ctrl + Shift + Esc to open Task Manager.

       

      Go to the Services tab.

       

      Find OVRService (Oculus VR Runtime Service).

       

      Right-click it and select Restart.

       

      Why this helps:

      By default, the Meta PC client may try to bypass system-level proxies to establish a direct connection. In environments where direct connection to Meta's "Graph" servers is restricted, this often leads to the login crash you observed. Setting this value to 1 explicitly tells the OVRServer_x64.exe process to respect the proxy or VPN settings configured in your Windows Internet Options.

  • iaalmx's avatar
    iaalmx
    Honored Guest
    2 months ago

    I hit exact same issue. The symptom is you URL in browser contains "native_sso_etoken=&" which means your etoken is empty. Then it redirect to the language page.

    It turn out that OVRServer.exe is a windows service. It doesn't follow most of your proxy setting. This service get the etoken for you. When it fail, you get empty etoken. I finally get it work with proxifier. It's a paid software but it has 30 trial. Should enough for init setup. No ads, just it works for me.

    • jdnesk's avatar
      jdnesk
      Honored Guest
      8 days ago

      Hi, how do you get it work with proxifier?  The software with the proxy i set can't even let me visit websites.

  • jdnesk's avatar
    jdnesk
    Honored Guest
    8 days ago

    Just figured it out. Turned on the tun mode when you are using vpns like v2rayn, just as I did.

    The root cause was that OVRServer.exe (Meta/Oculus VR service) runs as a Windows background service and does not properly respect system proxy settings, so its authentication requests bypassed V2Ray’s normal proxy mode. As a result, the etoken request failed and returned an empty value.

     

    Enabling tun mode in v2rayN  routes all system traffic through a virtual network interface instead of relying on per-app proxy settings. After switching to TUN mode, OVRServer.exe traffic was successfully routed through V2Ray, the etoken was correctly generated, and the login issue was fully resolved without needing Proxifier.

     

    • Llib_Gnauh's avatar
      Llib_Gnauh
      Honored Guest
      23 hours ago

      Similar to yours is another solution:
      To fix the UseSystemProxy error and force the Meta Horizon (Oculus) app to utilize your Windows system proxy settings, follow these steps to manually add the missing registry values.

       

      Step 1: Open Registry Editor as Administrator

      Press the Windows Key, type regedit.

       

      Right-click Registry Editor and select Run as administrator.

       

      Step 2: Update the Native (64-bit) Path

      In the address bar at the top, paste the following path and press Enter:

      HKEY_LOCAL_MACHINE\SOFTWARE\Oculus VR, LLC\Oculus

       

      Check if there is a sub-folder (key) named Config.

       

      If it does NOT exist: Right-click the Oculus folder, select New > Key, and name it Config.

       

      Click on the Config folder to open it.

       

      Right-click in the empty white space on the right pane.

       

      Select New > DWORD (32-bit) Value.

       

      Name the new value UseSystemProxy (ensure there are no spaces).

       

      Double-click UseSystemProxy, set the Value data to 1, and click OK.

       

      Step 3: Update the WOW6432Node (32-bit) Path

      Navigate to the following path:

      HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Oculus VR, LLC\Oculus

       

      Check for a Config key here as well.

       

      If it does NOT exist: Right-click Oculus, select New > Key, and name it Config.

       

      Right-click in the right pane of the Config folder.

       

      Select New > DWORD (32-bit) Value.

       

      Name it UseSystemProxy.

       

      Double-click it, set the Value data to 1, and click OK.

       

      Step 4: Restart Services

      For these changes to take effect, the background services must reload the registry:

       

      Press Ctrl + Shift + Esc to open Task Manager.

       

      Go to the Services tab.

       

      Find OVRService (Oculus VR Runtime Service).

       

      Right-click it and select Restart.

       

      Why this helps:

      By default, the Meta PC client may try to bypass system-level proxies to establish a direct connection. In environments where direct connection to Meta's "Graph" servers is restricted, this often leads to the login crash you observed. Setting this value to 1 explicitly tells the OVRServer_x64.exe process to respect the proxy or VPN settings configured in your Windows Internet Options.

  • Llib_Gnauh's avatar
    Llib_Gnauh
    Honored Guest
    22 hours ago

    By default, the Meta PC client may try to bypass system-level proxies to establish a direct connection. In environments where direct connection to Meta's "Graph" servers is restricted, this often leads to the login crash you observed. Setting this value to 1 explicitly tells the OVRServer_x64.exe process to respect the proxy or VPN settings configured in your Windows Internet Options.