Meta Quest Remote Desktop Login Loop Windows 10

[DrSwarm]

Hello Everyone!

I have been trying to get Meta Quest Remote Desktop to work for my windows 10 pc for a while now and noticed many people seem to have the same problem as me but no solution. I currently can get it to work on my Microsoft Surface Pro 7 on windows 11 but really want it to work on my other pc. 

My issue is I open the app, it asks to login, edge takes me to the login page. I log in. It appears to connect similarly to what it looks like on my surface, but then after a few seconds asks me to login again. I've tried a ton of things to get this to work but no luck (used firefox browser, uninstalled app, uninstalled oculus app, disabled all firewalls, changed monitor resolution, ect)! Any ideas are greatly appreciated. 

[same.agha.2023]

نعم شكرا لك 

[H_i_R_e_Z]

I've had a response from Meta who asked me to remove services, uninstall things etc etc. Nothing has worked. I have however been doing some experimentation with a number of PCs I have...

The one that doesn't work (An Office machine at my girlfirends house) - It's a Gen3 i7 Dell 7010 with an Nvidia 1050Ti. I removed the GPU and tried with the onboard Intel graphics. Still won't work. It has loads of other things installed - OpenVPN, Citrix etc.

Test machine - An identical Dell 7010 with Intel HD 4000 graphics. I did a clean install of Windows 10 21H2. Meta Remote Desktop app still looped. Had an AMD GPU to hand (can't recall which one), made no difference.

Test machien no 2 - an HP office macine with a 2nd Gen i5 and onboard graphics. Didn't work - login loop.

Main Gaming PC - 8th Gen i5 in a Gigabyte board with an NVidia 3700. Works fine.

2nd Gaming PC - A Gigabyte motherboard with a 6th Gen i7 and an Nvidia 980. Works fine.

Macbook pro 2015 - 6th Gen i7. works fine.

Macbook pro 2012 - 3rd Gen i7 gets stuck. it doesn't loop, just stuck saying "Loading..."

---

So, what have I learned? Removing the Nvidia GPU didn't fix the issue. Machines older than a 6th Gen CPU didn't work. I'm beginning to wonder if the problem is because of something the CPU doesn't support, and it acutally has nothing to do with the Graphics card at all.

[Mikernet]

Just decided to try this and I'm getting a login loop, and the computer does not show up in Workrooms.

[Tonybb8]

Hi @NathanSudo, Until now, I did not receive any other instructions to submit the report.  And one more, I downloaded the new version of the Meta Quest Remote Desktop (1.33.0.2.70), the login loop still the same and cannot submit the feedback report.

Can you or support team to tell us that what system requirements to login suceessfully for PC version (not mac). e.g hardware and software OS.

Thank you!

[Eschekt]

Same as everyone else here... login loop and "no available devices" screen before send back to login loop. This is on Win 11 with a hardwired Quest 3 that's showing up as active in the Oculus app. 

[NathanSudo]

Hey everyone,

Sorry you are having these issues!

Quick Update for everyone here, thanks for trying these things and trying to submit the report to Meta.

I've also alerted the Workrooms team to the issue with submitting reports, I'm disappointed to hear the new 1.33.x version hasn't resolved this issue but I haven't been able to get confirmation that this version was intended to solve it so I'm hopeful to hear more soon.

As soon as I hear more, I'll be in touch. We've been testing the update with the Workrooms Community and finding the same results as most of you.

I don't know if it's worth following the extra instructions because there's only one member who did find the additional troubleshooting steps helped them but it seems that's a very rare issues and solution.

If you want to help the issue please submit your problem to the main Meta support to receive a case/ticket id and DM that to me. Most people submitting to support aren't getting helpful answers but I'm trying to stack up the case IDs and send them to the Workrooms/Remote Desktop team so they can be aware of how many people are having the issue and hopefully prioritize this issue.  I can't guarantee any results at this time but it may help. 

@BlameChris and others have submitted detailed reports to the team and I've tried to get those escalated to the right team as it sounds like another person in this thread is also trying to do do the same but until the engineers get to the bottom of this I'm not sure what's causing the issue for some of you, the pattern seems very unclear.

At first, I thought it was video card related but some have removed the video card and had the same issues.

So it may be something else unrelated, but the number of people with this issue is growing so I hope we can get a solution for this soon.

When I hear more I'll post back. Sorry you are all having this issue!

[POINTY_009]

This is not resolved at all.  People are still experiencing issues and Meta's support is laughable.  I was asked to reconnect my network when explaining the OculusLogGatherer could not collect/compress all of the logfiles.

The issue is clear when looking into the %APPDATA%\Oculus\morstan logfiles.  Most with login loop will likely find an issue such as the below indicating an error when attempting to initiate RTC server, so there's nothing for the headset to connect to.  Exactly why and what is unsopported as per the error msg is unclear, but that, at least for me is why it logs on and off again.

[info][Morstan][2023-12-15T14:42:23.111Z] ["Attempting to start RTC server..."]
[info][Morstan][2023-12-15T14:42:23.115Z] ["getStatus response: ","DISCONNECTED","Server is in its initial disconnected state"]
[error][Morstan][2023-12-15T14:42:23.837Z] ["ERROR: Server (RTC) failed to start with Xr2ds error: UNSUPPORTED"]

[DaftThoughts]

I am having the issue as well. The remote desktop feature on the meta workrooms has never worked for me. I really want it to work, and I've tried several of the "accepted fixes" but nothing seems to work. I've tried it from 3 different computers on 2 different networks and I get the same "Continue with Meta account" loop and my headset never detects the computer. It's ok if you don't fix it. I've signed up for "Immersed Pro" and it just works like a charm. I'm really happy with how easy it was to set up. Alternatively, I'm so frustrated with how much time I've spent trying to get horizon workrooms to work that I don't want to spend more time without some serious help.

[POINTY_009]

Meta's support is pretty horrendous to be honest.  I got the usual canned response, bounced from one support member to another asking the same irrelevant questions like. 'Have you installed the app'  (No mate didn't bother installing as I knew it simply wouldn't work because I'm psychic) I mean, come on.  Makes me wonder if the support staff even read the tickets properly, if they do, then they're desperately short on training.  Then they provide the off the shelf, delete everything, re-install, let's take them a few times around the block to see if they get bored and give up hastling support, tactics and request logfiles from you're entire system including aspects which are completely irrelevant to the core issue, so instead of providing a company like Meta with who knows what from my personal computer, I said, nah, I'll find something which does work until Meta has the capability of debugging an app properly, without the need for all that BS.  Can we expect better from a data mining company?

[Barag0n]

I am having the same problem. It is very sad to see that this has not been fixed yet. I've had this issue about a year ago and gave up trying to get it to work. Today I've tried one more time with a clean Windows 11 installation and still no luck. I always get the same error as @POINTY_009 in the logs:
[error][Morstan][2023-12-27T19:32:16.912Z] ["ERROR: Server (RTC) failed to start with Xr2ds error: UNSUPPORTED"]