Not able to logging in with Meta Quest Remote Desktop

[grozeille]

I just upgraded Meta Quest Remote Desktop on my PC: 3.15.0.2.113

But during the logging in process, it asks me to continue on my browser, which I do, but when I did it on the browser nothing happen in the app.

I tried to change the default browser in Windows (Chrome and Edge), or uninstall (and clean %APPDATA%) and re-install, but nothing worked.

What's strange is that this process works with the Meta Quest Link app (I'm able to logout and logged in again).

Here is the logs:

[MetaQuestSupport]

Hi there!

Thanks for reaching out to the Meta Support Team. We understand you're having trouble logging in to the Meta Quest Remote Desktop. We want to get this sorted as soon as possible so you can get back to your VR workplace!

We appreciate the troubleshooting steps you've taken so far, this is very helpful. Please could you send us a private message so we can look into this more closely with you?

[grozeille · Accepted solution]

OK, I found the issue myself.

When I do the authentication, the Javascript is trying to run the app through a custom URL:

I checked which app is associated to that com.oculus.rd:// URL protocol in the Windows registry:

It's using the old path before Oculus was renamed to Meta (Oculus Remote Desktop).

Which is a different path after the upgrade:

By changing the path in the registry (regedit), it's fixing the issue.

[MetaQuestSupport]

Hey there, @grozeille. Thank you for sharing your fix. We hope that will help anyone else who has similar issues. If you run into any more problems down the line or just have any general question for us, please feel free to reach out to us again!

We hope you have a fantastic day.
 

[djtaylor74]

Thank you for this solution - it solved my problem which arose when upgrading from a previous version of the app.  I'm not sure why that registry entry hadn't been updated, but your solution definitely has worked!  I've added a link to here in the Horizons Workrooms Community group on Facebook.

[StevenRP_]

Hello,

I am having the same issue, I have reinstalled, tried changing my default browser and checked the Registry. After August, I found myself in this same login loop. However, oddly enough, the Meta Link Desktop app allowed me to connect for a while before it got another update. And, the Windows Mixed Reality Link seems to work now, but I prefer to use my Quest Pro rather than the Quest 3 for work. Has any one else found a solution? Could this be in part that I am using the Windows 11 Dev channel? 

[pebsg]

Hello @MetaQuestSupport 

I had the same issue with Chrome or Edge not opening automatically the app after logging in, I changed the "Windows registry" and now it opens the app. However, it remains as nothing had happened and doesn't seem to recognize I already logged in.

Any solution?

Thanks.

[chibmaster.2025]

I downloaded the meta remote desktop app from the link sent from my quest 3. I opened the app clicked log in and it sends me to the browser, I log in via the browser it sends me back to the app it load with the message logging in for two seconds and then it displayes an error page.

I am not sure what is hapening here as I am logged in correctly on my phone, pc and the quest 3.  I'm not sure how to fix this i've checked my registry and everything seems a okay. No typos in my registry and it's the same name as the target property on my on the application so I'm not sure what's wrong here.

Any solution would be helpful

thanks

[fuzzybelvedere]

My apologies, fairly new at this... what lines am I changing and to what?
Everything matches what's shown but the "com.oculus.rd://link/frl_login?token="... am I pasting that into the target section of the shortcut properties tab or in the REG_SZ (modify) section?

[zerobell.lee]

Geez, you're super genius! And I also surprised Meta team forgot changing registry values even it is so basic that children can notice this task. The worse thing, even though you've posted the best solution of this issue, still they hasn't patch with software upgrade until now.

This issue possibly can occur only on old users' PC, who has been using "Oculus Quest", not "Meta Quest". I was one of them, and I actually tried remote desktop with my co-workers several times. and this comes so ridiculous to me. People who has been interested with Meta's potential for a long time were ignored by Meta.

Anyway, thank you for your good works.