Meta Quest Remote Desktop.exe crashing in background

Participant

no idea what that even is 🙂

i presume you mean when i click on a link in my rss program that is frozen because of the remote-desktop.exe? ... nope, nothing visual to indicate its being stalled... sometimes i double click on it multiple time... and after 30sec or a random amount of time, they all open up when it gets "un-stalled"

C

captqbec

Participant

That was the original complaint here.

The blinking cursor.

As if Windows was always busy.

Look at first post.

Participant

oh lol... true! its been so long i had forgotten about that! 🙂

I kinda joined in the thread back in "11-19-2024 05:34 AM" When i first noticed the problem... even though its not "precisely" the same problem... i kinda think its the same... except that in my case its my RSS feed that gets stalled, which does not have any visual side effect... in the original poster case it was most likely a more important windows component like explorer.exe or something else causing that visual bug and subsequent crash.

Participant

Another update to the file this morning... and another freeze of my process... another deletion of the remote-desktop file... why the heck is that file sooooo problematic?!? And WHY is it always in use even when you are NOT doing anything remotely close to remote desktop?!?!

Up and Coming

Still happening here with my last v77 partial update. I think that makes the last 7 or 8 updates that have all immediately crashed and I need to rename the remotedesktopcompanion.exe to prevent it being endlessly present/crashed.

Honest to God the standard of Meta software is dreadful. Would I recommend anyone to buy a Meta headset ? - probably not. Please just fix the basic issues first before adding stuff so your customers can actually use their gear. Sorry to say I can see a class action coming if this persists much longer...

Up and Coming

OK so I'm sick of this. I've made a crash dump following yet another f**ked update to the remotedesktopcompanion.exe , run it through a hex editor and made a text file of what I think is helpful to finding the issue. Now in my quick unskilled reading of the file there seems to be a whole lot going on there - a cascade of issues and violations. This pc was win 7 and was upgraded to win 10 legally. It does not have TPM being older hardware. It does have 2 graphics cards.

I can supply the full dmp as a 7z txt file at 34mb or the cut down file at 78kb 7z - can't seem to attach it here. Your choice to reply to me or not Meta

Participant

Same for me... i keep them all as a memento to find out how long it takes them to freakin fix their bugs!! 🙂

Pretty crazy 🙂

spider853

New Participant

Can you please fix your s**t Meta? It's just so annoying at this point, I want to delete all the products related to this...

Participant

I just noticed that the file had been updated (again) and was running.... for the past 6 days! and somehow I havent had any bugs or freeze or errors since... so "MAYBE" its been fixed? (at least it seems to be the case for me - and possibly others as well)...

Up and Coming

Lucky you....if true 🙃

I am soooo fed up with Meta's software not working. I absolutely regret buying into this crap.

It's highly likely I will never spend any more money on their VR even if they get it half working again. Lesson learned - Meta s*cks at VR.

As users we have multiple simultaneous issues now that are seriously impacting the ability of customers to use their headsets.... and Meta just hides.

At this point I want to break someone's face for their managerial incompetence... 😠

later 🖖

Up and Coming

...and no cigar for the latest v78 companion.exe either... 👎

hmmm maybe that's a coders joke calling it a companion.exe - i.e. being endlessly stuck with a pop up saying it crashed... hadn't considered that...

sbdykes

Up and Coming

Wanted to update with some latest observations.

Several updates ago (in April) this issue was resolved* for me. Seeing as how many others are still having issues, I decided to scrutinize my windows events log and see if anything interesting showed up.

What I discovered is that RemoteDesktopCompanion.exe is, in fact, still crashing for me when the oculus service(s) start up. I see after the last update it crashed 11 times, consecutively. What is NOT happening is it being stuck trying to restart continually/infinitely. Thus it seems the "fix", for me at least, seems to be simply giving up trying to start it after some number of attempts.

So, while the problematic infinite restart doesn't happen, RemoteDesktopCompanion is still crashing/inoperative.

spider853

New Participant

So I didn't do any low level investigation but I have a new idea why this may happen and why Meta is clueless of this, or just ignores this... This might have to do with older processors that might not support some new SIMD instructions that they might use in the new builds. I don't remember exactly which SIMD instruction set was missing from my processor that I couldn't run Valorant but it was probably AVX2 or AVX-512, or some SSE newer version. You can have a look with CPU-Z if you have these supported, but if your processor is 7+ years older then it might not support it.

Just a thought.

If this is the case I think Meta should do 2 versions to support older hardware...

sbdykes

Up and Coming

I finally decided to dig in and disassemble RemoteDesktopCompanion.exe using Intel's XED to see what's going on. spider853 is exactly right. The disassembly reveals that RemoteDesktopCompanion.exe is using both AVX2 and AVX512 instructions. Just as two small examples:

XDIS 14000bb34: AVX2      AVX2       C4C37D38042401           vinserti128 ymm0, ymm0, xmmword ptr [r12], 0x1

XDIS 14001f4ff: AVX512    AVX512EVEX 62F16548FE1DB7D4FFFF     vpaddd zmm3, zmm3, zmmword ptr [rip-0x2b49]

Obviously, I can't speak as to the intentionality of enabling those instruction sets for this executable. However, given that the original Rift had a minimum system requirement of a Core i3-6100, which only supports AVX2 (not AVX512), this seems like a simple mistake in project configuration, as one would not want to mistakenly break the system software for people running supported hardware.

Personally, I am running an ancient Core i7-2600k, which supports neither AVX2 nor AVX512. However, my DK2 still works great in every aspect, it is simply RemoteDesktopCompanion that is problematic.

Unless there is some compelling reason that requires these AVX2/512 instructions, the fix should simply be to set the generated instruction set to be SSE2. In Visual Studio 2022, this is done here:

Note that "Not Set" defaults to SSE2.

Up and Coming

Yes this could be the issue. Unfortunately I don't have an old remote desktop archived to compare with. My 4930k processor only supports AVX old tech by today's standards but still a decent pc for my needs - until this. Should we submit a bug report petitioning for a fix along these lines? We'll need it before October I think else they will declare all older hardware redundant as a matter of course and regardless of whether Meta actually needs it.