Oculus Rift CV1 Boot-Loop and Error in Debugger since last Meta Quest Link update

[donotsue]

Hi there,

(not more then 2 or 3) weeks ago there was again a software update of the Meta Quest Link. Since then I see every second the loading icon on my mouse cursor. After looking into my task manager I realized, that OculusClient.exe is consuming high power.

Even that, the Meta Quest Link software starts everytime and cosums constantly much power, too. I can stop it, yes, but seconds after it starts again by itself, even if I don't touch my Oculus Rift CV1. When Meta Quest Link is started (or closed, in all cases) I see periodically every second the loading icon at my mouse cursor and my PC is running high it's fans, since last updated.

I watchted into the console of C:\Program Files\Oculus\Support\oculus-diagnostics\OculusDebugTool.exe to see, what the problem is.

So ... just to get save, that it is not a hardware failure, I restored an old backup of my PC with the driver/Meta Quest Link BEFORE it was updated some weeks ago. No periodical loading, VR keeps idle when it's not been touched, Meta Quest Link just starts, if I set up the VR on my head, everything nice and dandy. Then the autoupdate of Meta Quest Link kicked in to the actual current Version of NOW and the same Error above came back.

Following console output comes repeatedly every second (when the loading circle icon gets visible) and Meta Quest is running:
04/12 02:37:03.568 {INFO} [AppTrackerManager] Adding new tracker: 8068 (oculus-remote-desktop)
04/12 02:37:03.568 {INFO} [LifeCycle] Adding Core Tracker: 8068 (oculus-remote-desktop)
04/12 02:37:03.568 {INFO} [LifeCycle] updateSDKFocus focusedTrackerPid: 848 (oculus-dash)
04/12 02:37:03.568 {INFO} [LifeCycle] Inactive Focus: 848 (oculus-dash)
04/12 02:37:03.568 {INFO} [LifeCycle] Already Focused: 0 (Unknown)
04/12 02:37:03.568 {INFO} [LifeCycle] onCoreTrackerExit::launchRemoteDesktop() End
04/12 02:37:03.569 {INFO} [LifeCycle] addCoreTracker::onExit() End
04/12 02:37:03.569 {INFO} [AppTrackerManager] Removing tracker: 13908 (oculus-remote-desktop)
04/12 02:37:03.569 {INFO} [PackageLocation] Install path: C:\Program Files\Oculus\\Support
04/12 02:37:04.922 {INFO} [os/process] PID 8068 exited; exit code: 3221225501/0xc000001d STATUS_ILLEGAL_INSTRUCTION
04/12 02:37:04.922 {INFO} [AppTracker] Tracker 8068 dispatching finish thunk, exit code 3221225501
04/12 02:37:04.922 {WARNING} [ApplicationPackage] App oculus-remote-desktop has exited with error: 3221225501
04/12 02:37:04.924 {INFO} [PackageManager] No core updates needed.
04/12 02:37:04.924 {DEBUG} [Library] Running autoupdate.
04/12 02:37:04.924 {INFO} [PackageManager] Updates check finished.
04/12 02:37:04.924 {INFO} [LifeCycle] addCoreTracker::onExit() Start
04/12 02:37:04.924 {INFO} [LifeCycle] Removing Core Tracker: oculus-remote-desktop
04/12 02:37:04.924 {INFO} [LifeCycle] App exited unexpectedly: oculus-remote-desktop
04/12 02:37:04.924 {INFO} [LifeCycle] updateSDKFocus focusedTrackerPid: 848 (oculus-dash)
04/12 02:37:04.924 {INFO} [LifeCycle] Inactive Focus: 848 (oculus-dash)
04/12 02:37:04.924 {INFO} [LifeCycle] Already Focused: 0 (Unknown)
04/12 02:37:04.924 {WARNING} [LifeCycle] Remote Desktop crashed, restarting...
04/12 02:37:04.924 {INFO} [LifeCycle] onCoreTrackerExit::launchRemoteDesktop() Start
04/12 02:37:04.924 {INFO} [LifeCycle] Launching Package: oculus-remote-desktop
04/12 02:37:04.924 {INFO} [PackageLocation] Install path: C:\Program Files\Oculus\\Support
04/12 02:37:04.924 {INFO} [os/process] Launching app with path [C:\Program Files\Oculus\Support\oculus-remote-desktop\RemoteDesktopCompanion.exe], args [], launchDir [false], detached [false]
04/12 02:37:04.928 {INFO} [os/process] Waiting for pid 2872
04/12 02:37:05.354 {DEBUG} [AppTracker] No corresponding library item for Appid 7904568142944560

Please META, don't break my loved and enjoyed toy. Please fix this, it was running before and since last update it just makes me sad, and yes, I checked it, there is no hardware failure on the VR. Diligently and faithful I update my drivers everytime ...

My specs:

Win 10, NVidia GTX 980 Ti, Intel Xeon CPU E5-1650 0 @ 3.20GHz, 32 GB Ram. It's good enough to play games like Alyx or Beat Saber ...

Any clues by the way, while hoping, that Meta will fix this last update (Version der Meta Quest Link-App 71.0.0.451.524 (71.0.0.451.524))?
Sorry for my poor English 😞

[donotsue · Accepted solution]

Aha ...

https://communityforums.atmeta.com/t5/Get-Help/Oculus-Rift-restarting-after-I-shut-it-down/m-p/12645...

shows a solution, but that's not a nice one 😞 The old Oculus SW and the new Meta Quest Link was working before last update and now it doesn't do, what "positive user experience" means.

In short:

- Rename C:\Programme\Oculus\Support\oculus-remote-desktop\RemoteDesktopCompanion.exe to RemoteDesktopCompanion.old
- Didn't use the batch file to stop Oculus VR Runtinme service or changed it's startup to manual

Result:
- No periodic loading circle when Meta Quest Link is running or is closed
- No high power consumption visible in the task bar
- No periodic error messaging in the console

But for real ... Sometimes I have to explain my employer, why we cannot code everything like we want, ignoring the "positive user experiences", because we are not a well known big company with lots of money ... Sorry to say that, but fact is, that there was a time where the old Oculus SW worked as expected and made many people happy. Now (especially users of the Oculus Rift CV1) sit with tears and fears in front of the pc, when the Meta Quest Link wants to update again something 😞 When the Meta Quest Link forced me, to register an account to use a hardly self-owned hardware, that was a hard evil to bear. But now, the feeling of loosing features, like working software for an expencive hardware, and no possibility to just roll back to older versions, is ... FEAR ... no positive user experience, sorry but that in fact are the results.

Sorry to say that, Meta. Please don't stop or shut down working hardware remotely and make it possible to be able to download the older driver versions, especially for the good old Oculus Rift CV1, that still spends so much happiness. The feeling of having a hardware, knowing that it can work, is not nice paired with the feeling, that the maintainer can shut it down remotely. It just feels like payed much for an item, that still is not mine, but the maintainers.

Sorry for my poor English and thanks for your attention.

Hope it will be fixed in the future, like it worked before in the past ...

[donotsue]

18.12.2024, Meta update again, same error again, and same solution again -> renaming C:\Programme\Oculus\Support\oculus-remote-desktop\RemoteDesktopCompanion.exe to RemoteDesktopCompanion.old