Can't login to Meta Horizon Link

You need to be logged in to your Meta Quest account (headset) first.

When you click the "log in" button in the Link PC app, it should show your Meta Quest profile in your browser:

If you don't see this, then you need to go to Meta Quest and log in on that page:

It will send a verification code to your email (or maybe require 2FA if you had that set up, I think).

Then I think you should be able to log in to the Link app and get the first login screen I showed above.

If that doesn't work, try logging out from Meta Quest and logging back in.

If you do manage to get the Link PC app logon screen to appear, then when you click your profile, it will show a strange screen saying "continue in your browser"... but you are already in your browser (!!!) so just wait a few seconds and the screen should disappear and the Link PC app window will appear with you logged in. The previous logon screen will still be open in your browser. Don't click on it, just close it, as you are already logged in.

Thanks steve_40​. As described above, logging out first results in the error message of "Something went wrong...", and logging in results in a redirect to the language page. I tried your instructions but I can't get past the "Continue in Your Browser" dialog in the Meta Horizon Link app.

Thanks! My issue was related to content-blockers. I'm now able to log in.

VPN issue 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.

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.

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.

The path HKEY_LOCAL_MACHINE\SOFTWARE\Oculus VR, LLC\Oculus does not exist for me. HKEY_CURRENT_USER\Software\Oculus VR, LLC\Oculus exists and so does KEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Oculus VR, LLC\Oculus.

This may be why it is not working for me (I am having the exact same issues as OP, being logged in takes me to the language page and not being logged in gives the same error as OP)

I have tried disabling all extensions, using different browsers (Chrome, Edge, Firefox) and nothing has worked.