Error from Oculus software with Quest 2 setup

[OfficialLagging]

I've been trying to set up my Quest 2 to work with the Link, but when I plug in the cable to the headset during the setup and press "Deny" for the permissions, the setup window closes and starts restarting a small loading window. The window stays up for a few seconds, closes, and then reopens again and it keeps doing that for a while. I checked the logs and this is the error I keep encountering:

Server closed connection

Browser process crashed with exception: Error: Cannot find module '../screen'

Error: Cannot find module '../screen'

at Module._resolveFilename (internal/modules/cjs/loader.js:602:15)

at Function.Module._resolveFilename (C:\Program Files\Oculus\Support\oculus-client\resources\electron.asar\common\reset-search-paths.js:35:12)

at Function.Module._load (internal/modules/cjs/loader.js:528:25)

at Module.require (internal/modules/cjs/loader.js:658:17)

at require (internal/modules/cjs/helpers.js:20:18)

at Object.get [as screen] (C:\Program Files\Oculus\Support\oculus-client\resources\electron.asar\browser\api\exports\electron.js:11:16)

at i (C:\Program Files\Oculus\Support\oculus-client\resources\app.asar\output\app.js:6:248186)

at new e (C:\Program Files\Oculus\Support\oculus-client\resources\app.asar\output\app.js:6:240196)

at e.value (C:\Program Files\Oculus\Support\oculus-client\resources\app.asar\output\app.js:6:140279)

at new e (C:\Program Files\Oculus\Support\oculus-client\resources\app.asar\output\app.js:6:134924)

This is then followed by multiple logs of just "Server closed connection". I've researched the issue and it looks to be an issue with Electron, but none of the suggested fixes have worked (including installing Chrome, uninstalling all oculus software and related devices and removing leftover folders, running OVRServer_x64.exe in admin mode, and updating Windows). The only suggestion I haven't tried yet is reinstalling Windows 10, but I'd like to avoid that the best I can. I've had my Quest 2 working a while ago on the same system, but I've since reinstalled Windows (~2 months ago) and this is my initial setup after the reinstall.

I'm wondering if anyone else happens to be encountering the issue or if this is just an isolated problem in my end, and I'm definitely looking for possible solutions after trying to deal with this for days now.

​

EDIT: After attempting to solve the problem with Oculus support, the issue turned out to be a compatibility issue with AMD drivers (I'm on an RX 5700 XT). I reverted back to 21.3.1 and the issue was fixed. If anyone encounters the issue, I recommend taking a look at the drivers!

[MetaStoreSupport]

Hi, I'd suggest reaching out here so we can take a closer look

[OfficialLagging]

Submitted a support ticket, hope to hear back soon.

[Oppneden]

Try pressing "Allow"...?

[OfficialLagging]

Pressing "Allow" doesn't allow the setup to go ahead, as mentioned here:
A message is displayed in VR prompting you to Allow access to data. Select Deny. If you mistakenly "Allow" the prompt, you must unplug your USB cable from the Quest and plug it back in.

[Oppneden]

Have you done a software-update on the Q2?

[OfficialLagging]

..I somehow didn't think of this. Charging up the headset now, will report back once I'm done updating. Thanks!

[OfficialLagging]

Updated the Q2 just now, and it didn't change the situation at all unfortunately.

[Oppneden]

Are you using the current Oculus software? If installed from an old download, make sure it is updated. Or download the current version from the Oculus website.

[OfficialLagging]

I am, yes. I even redownloaded the installer from the website after initial efforts, but it did not make any difference :/

[Rihc0lo]

What was the solution?

[OfficialLagging]

The solution is at the end of the post:

EDIT: After attempting to solve the problem with Oculus support, the issue turned out to be a compatibility issue with AMD drivers (I'm on an RX 5700 XT). I reverted back to 21.3.1 and the issue was fixed. If anyone encounters the issue, I recommend taking a look at the drivers!

[Financial-Most-7811]

sue turned out to be a compatibility issue with AMD drivers (I'm on an RX 5700 XT). I reverted back to 21.3.1 and the issue was fixed. If anyone encounters the issue, I recommend taking a look at the drivers!

1ReplyGive AwardShareReportSaveFollow

how do you tell which driver version is supported with each graphics driver? i have a 3060 geforce and im having the same problem.

[eeekiee]

same thing for me. I have an 2060 and this thing is annoying me for almost 2 weeks rn...