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. 

[MetaQuestSupport]

Hey @DrSwarm, We hope that the troubleshooting was some help. If you find that you are still having issues please let us know. We would love to help! 

[NathanSudo]

@DrSwarm did you ever get things working on your desktop?

Can you confirm if you have an external video card? 

We've seen some conflict it seems with different GPUs. 

That may be why it works on your Surface but not on your desktop.

[BlameChris]

I'm trying to use remote desktop on my desktop (Ryzen 5950X, RTX 3090, Win 11), whenever I run the application on Windows 11 I get to the "Continue with Meta account" button, click it which opens a browser window where I click to authenticate, then the app moves back to the "Go to your headset to connect" screen. After a few moments (usually when I try to click to connect to the PC which now shows in my devices within the Remote Desktop menu), it will bump me straight back to the "Continue with Meta account" screen.

My PC gets added to the list but is never available to connect.

The remote desktop app works perfectly on my Surface Book 3 laptop, it's just my desktop PC that doesn't seem to work.

Here's what I've tried:

• Reinstalling the Meta Quest Remote Desktop app.
• Restarting the PC
• Restarting the Quest 3

What can I do to fix this? I can't even really troubleshoot the issue as the app keeps kicking me to the continue with account option so fast.

[BlameChris]

I am having an issue with one of my computers when trying to use the Remote Desktop application.

While it works just fine on my laptop (Surface Book 3, running win 11) it doesn't work on my desktop (also running win 11). For some reason after I authenticate my meta account in the browser window after about 15-20 seconds it will log me out. During this short window the pc is never accessible in my headset, but the PC is added to the list of devices I can use remote desktop with.

I've tried reinstalling the program, tried rebooting the headset and the pc with the issue. Tried clicking "Not you?" and signing in again. I've also tried reinstalling the app after deleting all the folders from the AppData and user folders on my computer.

I'm really not sure what to do beyond this or how to fix it, can I get some help on this?

It's so reliable I was able to record it and turn it into a gif... 

 

[BlameChris]

@NathanSudo I'm not the person who made this topic, but I have the exact same issue. I have a working system (Surface Book 3, with a 1650m gpu) and a non-working system (Desktop, with a 3090 gpu). Both on the same network and the same OS (Win 11). The log in works, on both, on the desktop however I am logged out moments after logging in and can never connect to my Quest 3.


I also cannot submit a bug report while logged in as I get an error message telling me to try again.

[NathanSudo]

@BlameChris Sorry to hear you are having this issue, I can confirm that this issue has been reported directly to the Horizon Workrooms team and although I don't have any answers yet -- I'm doing my best to raise the issue and hopefully get some answers.  If you have time to test things out, can you try the Remote Display app from your app library and see if that connects on the Desktop that's having the issues?  Some members of the Workrooms community are also experiencing this issue and a few have reported that Remote Display works fine while Workrooms doesn't -- with the same Remote Desktop app installed on the desktop. 

I'd be curious about your experience, the more data we can get the better hopefully the Meta team can resolve the issue!

[BlameChris]

@NathanSudo When I run the Remote Display App on the headset I see the Desktop, but it's always shown as Not Available. Even if I start the Remote Display App, then try to login on the Meta Quest Remote Desktop app, it doesn't show as available even before the Remote Desktop app sends me back to the "Continue with Meta account" login.

[BlameChris]

Having tried to look more into it, I found that I can't submit a bug report from inside the application. Even if I click through to the bug button before I am logged out, it gives me an error when trying to submit.

I did however find some log files in an Oculus folder in my AppData folder, something called xr2ds_2023-10-31_23.15.51.txt which had some interesting log info in it:

31/10 22:53:30.087 {DEBUG}   [CrashReporter] Started breakpad server.
31/10 22:53:30.090 {INFO}    [Watson] Main.cpp:389 User default locale name: en-US
31/10 22:53:30.090 {DEBUG}   [Watson] Main.cpp:478 WatchDogObserver::Run: Starting watchdog thread
31/10 22:53:30.090 {INFO}    [Watson] Main.cpp:403 Updating locale to en_US
31/10 22:53:30.099 {INFO}    [Watson] Main.cpp:503 Launch Watson ...
31/10 22:53:30.099 {INFO}    [Watson] Main.cpp:521 ****************************************************************
31/10 22:53:30.099 {INFO}    [Watson] Main.cpp:529 *** Watson 1.15.0.14.301 Session Start ***  2023-10-31 22:53:30  OS Version: 6.2 (9200),   PID: 38128  Xr2ds build timestamp: Oct 10 2023 18:46:59
31/10 22:53:30.129 {INFO}    [Watson] ApplicationTelemetry.cpp:40 Application telemetry initialized with: app_version 1.15.0.14.301 computer_id {CFDFA7CC-6351-4BD1-A842-CD2AD45DD854} application_session_id {8C39767F-8BE2-4AB3-B5A9-3069CA9FB63F}
31/10 22:53:30.129 {DEBUG}   [Watson] ApplicationTelemetry.cpp:48 Initializing application telemetry with app token
31/10 22:53:30.142 {INFO}    [Watson] LocalCache_win.cpp:74 Could not read item with tag=Meta Quest Remote Desktop Reinstall from credential vault: status=0x490
31/10 22:53:30.158 {INFO}    [Watson] Main.cpp:694 Automatic updates enabled. Timer should be ticking now...
31/10 22:53:30.158 {INFO}    [Watson] Main.cpp:300 [UpdaterTelemetry] want to auto-check for updates, but server not running, so won't
31/10 22:53:30.158 {INFO}    [Watson] Settings.cpp:80 Failed to open settings json C:\Users\chris/oculus_virtual_desktop_settings.json
31/10 22:53:30.158 {INFO}    [Watson] Main.cpp:1819 starting process...
31/10 22:53:30.158 {DEBUG}   [Watson] ApplicationTelemetry.cpp:112 Application sendTelemetry
31/10 22:53:30.171 {DEBUG}   [Watson] ApplicationTelemetry.cpp:200 Application sendTelemetry success
31/10 22:53:30.171 {INFO}    [Watson] Main.cpp:1858 Log level is set to DEBUG
31/10 22:53:30.171 {INFO}    [Watson] ServerImpl.cpp:124 Xr2ds library version: 1.15.0.14.298
31/10 22:53:30.173 {!ERROR!} [Watson] ServerImpl.cpp:2161 Could not create status callback: server not initialized.
31/10 22:53:30.173 {INFO}    [Watson] Main.cpp:1905 preparing settings...
31/10 22:53:30.174 {INFO}    [Watson] LocalCache_win.cpp:74 Could not read item with tag=Meta Quest Remote Desktop Server from credential vault: status=0x490
31/10 22:53:30.174 {DEBUG}   [Watson] ApplicationTelemetry.cpp:112 Application sendTelemetry
31/10 22:53:30.174 {DEBUG}   [Watson] ApplicationTelemetry.cpp:200 Application sendTelemetry success
31/10 22:53:30.174 {DEBUG}   [Watson] ApplicationTelemetry.cpp:112 Application sendTelemetry
31/10 22:53:30.175 {DEBUG}   [Watson] ApplicationTelemetry.cpp:200 Application sendTelemetry success
31/10 22:53:30.175 {!ERROR!} [Watson] Main.cpp:2492 Unable to delete value from regitsry: 5
31/10 22:53:30.175 {INFO}    [Watson] Main.cpp:2072 StartMorstanAfterInstall is: true
31/10 22:53:30.175 {INFO}    [Watson] Main.cpp:2077 Launch Morstan UI. Error: 12
31/10 22:53:30.219 {INFO}    [Watson] Main.cpp:2227 Server is not running anymore. Kill the MMAStatus check thread
31/10 22:53:30.219 {DEBUG}   [Watson] MMAStatus.cpp:31 MMAStatus::shutdown
31/10 22:53:30.219 {INFO}    [Watson] Main.cpp:2108 process started
31/10 22:53:30.220 {INFO}    [Watson] ServiceLauncherListener.cpp:55 Started service launcher listener thread...
31/10 22:53:30.220 {DEBUG}   [Watson] Main.cpp:478 WatchDogObserver::Add Watchdog: AppMainMsgLoop
31/10 22:53:30.309 {DEBUG}   [Watson] ApplicationTelemetry.cpp:288 Data {"data":[{"results":[true]}],"errors":null,"error":null}
31/10 22:53:30.415 {DEBUG}   [Watson] ApplicationTelemetry.cpp:112 Application sendTelemetry
31/10 22:53:30.416 {DEBUG}   [Watson] ApplicationTelemetry.cpp:200 Application sendTelemetry success
31/10 22:53:31.410 {DEBUG}   [Watson] ApplicationTelemetry.cpp:112 Application sendTelemetry
31/10 22:53:31.410 {DEBUG}   [Watson] ApplicationTelemetry.cpp:200 Application sendTelemetry success
31/10 22:53:31.411 {INFO}    [Watson] Main.cpp:1195 Deleting cached RTC token
31/10 22:53:31.411 {DEBUG}   [Watson] ApplicationTelemetry.cpp:112 Application sendTelemetry
31/10 22:53:31.412 {DEBUG}   [Watson] ApplicationTelemetry.cpp:200 Application sendTelemetry success
31/10 22:53:31.412 {!ERROR!} [Watson] LocalCache_win.cpp:111 Could not delete item with tag=Meta Quest Remote Desktop Server from credential vault: status=0x490
31/10 22:53:31.412 {INFO}    [Watson] Main.cpp:1197 Deleting cached Morstan token
31/10 22:53:31.412 {DEBUG}   [Watson] ApplicationTelemetry.cpp:112 Application sendTelemetry
31/10 22:53:31.412 {DEBUG}   [Watson] ApplicationTelemetry.cpp:200 Application sendTelemetry success
31/10 22:53:31.412 {!ERROR!} [Watson] LocalCache_win.cpp:111 Could not delete item with tag=Meta Quest Remote Desktop from credential vault: status=0x490

And it goes on (but I don't want to paste the whole file here), there's loads of errors. What is Watson, what is Morstan and xr2ds? Are these maybe causing the issues?

[NathanSudo]

@BlameChris Thanks for that extra info on the Remote Display, I was curious if it worked differently than Workrooms for you but it seems like it also doesn't work properly 😭

I saw your other thread with more info from the logs, I'll try to pass that along to the Workrooms team in case that's helpful too. 

Let's hope they figure this out soon, it can be very frustrating when it's not working on the device you were hoping to use but it's good you've got one that does work in the meantime.

I'm still suspecting it's something specifically related to certain GPUs, from the most part it seems to be consistent but not sure yet.  

This has been a bit of an ongoing issue for a subset of people but the more data we get hopefully it will help Meta resolve the issues. 
 

[NathanSudo]

@BlameChris Sorry to see you are having this issue, it does appear to be a pretty consistent and reliably produced issue, nice work on capturing a GIF of it... although I know it's so annoying when you really want to get things working!

I've passed this along to some contacts on the Workrooms team who hopefully can direct your log files and info to the best place to be helpful to those looking into this issue.  

Let's hope it gets resolved soon in an upcoming release whether it's related to Remote Desktop/ Remote Display, the Quest in general, Workrooms or even something within Windows!

It has seemed to be in some way related to specific graphic cards as far as I can tell but I haven't heard anything official if it's a known issue related to video cards or something else. 

Please feel free to report anything else you find here if you keep experimenting! In the Workrooms community we've had a number of people report this and try a lot of things trying to get it working as well but so far nothing is reliably solving the problem.  So glad you've got at least one device working with it but I'm sure in some ways that can be more annoying if the device you were hoping to use with it most was the Windows device 😞

Hope to see you in the Workroom being product soon. And please feel free to drop by the Workrooms Commuinty meetup on Fridays 10 am Eastern US,  if you have time.