Skip to main content
New Participant
November 10, 2024
Solved

Meta Quest Remote Desktop.exe crashing in background

  • November 10, 2024
  • 86 replies
  • 19755 views

After the recent update, my cursor constantly flashes the working in the background circle. In task manager 'Meta Quest Remote Desktop.exe flashes then suspends followed by a windows problem reporting and repeat. I uninstalled the software and reinstalled it from the website and the issue started up again as soon as the install was complete. Any suggestions on how to fix this?

Best answer by Jamonster123

Delete 'RemoteDesktopCompanion.exe' from Program Files/Oculus/Support/oculus-remote-desktop

86 replies

Participant
November 27, 2024

impossible to play in vr without air link installed

Participant
November 30, 2024

Participant
November 30, 2024

Thx, that fixed it for me. Have 3 Rift-s and a Q2.

New Participant
December 2, 2024

For what it's worth I also have this issue and am uninstalling this app for now.  I see under the Windows Reliability Monitor that it's Meta Quest REmove Desktop causing the issue as others have said.  This started happening just after the big new update MS dropped.

Participant
December 2, 2024

to avoid damaging your system before completing the installation and the program launches go to the Program Files/Oculus/Support/oculus-remote-desktop folder and delete the RemoteDesktopCompanion.exe file

Participant
December 16, 2024

 

it's wrong see capture, my version is not up to date and I had the problem from the start

 

Participant
December 16, 2024

Interesting.  That wasn't my experience.  I was on 1.97.0 for quite some time and didn't experience any issues.  The second I upgraded to 1.103.0, I started experiencing this problem.  Downgrading to 1.97.0 stopped the problem for me without having to disable remote desktop.  Did you downgrade to 1.97.0 or have you never upgraded to 1.103.0?  The difference could be important.

FireHawkX
Participant
December 19, 2024

Seems like there was an update... the file got downloaded again... not the same file size... so they DID try to fix the problem... but sadly failed miserably 😉

The bug immediately came back and the ```C:\Program Files\Oculus\Support\oculus-remote-desktop\RemoteDesktopCompanion.exe``` file was running again and messing up my windows, and rss feed viewer among other things because it was cloging up the "wait chain"...

So i turned off the service once more, and renamed the file to some swear word i will not write here 😉

everything started working again immediately....

I wish someone who worked at meta actually looked at those threads and passed along important information to the dev team so that they could actually FIX the **bleep** thing! 😛

Anyway, everything works perfectly without that file so whatever i guess 🙂

Happy Holidays to everyone!

Up and Coming
December 19, 2024

Can confirm the same....file re-appeared today (2024-12-18), symptoms re-appeared.  Renamed file, now back to waiting on official fix.

Holgihood
New Participant
December 19, 2024

The same here. After the update, RemoteDesktopCompanion.exe started crashing every second again and spamming the event log. My CPU was permanently at 100%. After I renamed the file to RemoteDesktopCompanion.exe.bak, the problem was solved (at least for the moment). Hope for a fix in the near future so that the program is usable again...

Participant
December 19, 2024

A PC whose processor is constantly running at 100% is a recipe for disaster. yesterday I was playing a game for 5 hours, when I closed the game my mouse icon was flashing, I started looking at the windows log, occulus had come back while I was not even playing in vr and my software is still version 1.97.0. I don't understand what's going on but be careful with your machines.

Participant
December 19, 2024

I think what happens is when the latest update gets pushed, affecting the file that doesn't exist (as it's renamed) it simply redownloads it. Happy holidays all. 

Participant
December 19, 2024

What's bonkers here is I turned off automatic updates and it STILL updated itself anyway. That's straight-up virus territory.