Hi there,
I use to use Meta quest Link and even Air link between my PC and my Oculus quest 1
Suddenly when I turn on my PC and launch the Meta quest link app, I have the following message
"Impossible to access at the link service"
Try to repair the app, repair impossible
I have tried uninstall the meta quest link ap and reinstall it
Restart computer
Switch off firewalls and antivirus
Nothing worked so far
Can you help me..
Thanks
A few people have been reporting similar issues recently. It might be a new bug. You might need to wait for a hot fix. I won’t have access to my PC for a couple of days, but then I’ll be able to check if Link is still working or not.
Hey there Rirouro,
We came across your post while browsing through our Community forums and we want to thank you for bringing this to our attention.
So that our amazing software engineers can get on the case ASAP, please submit a bug report of this issue, including as much information as you can.
If you continue to experience this issue, please get in touch with us privately here by selecting our name, navigating to our page and clicking 'Send a Message' - we're here to help!
Now as I have reset my occulus as factory settings, I'm locked on the update 1 of 2 complete abd cannot do anything from the mobile app or esle..
So I cannot submit a bug report as now even my occulus won't work either
Why all of this suddenly ?
Thanks for your help..
Hello there Rirouro!
We saw that you are having issues with your headset being stuck in an update, and would like to offer our help with getting you back into the Metaverse.
If you would please send us a private message, using our profile in the right top corner, making sure you are signed in, so we can have a closer look into this with you.
We hope to hear from you soon and wish you a wonderful day!
The problem is with the Fixer.exe which normally is used to perform diagnostics on the oculus service before launching Link.
Make sure the service is running and launch Link from the client.exe in the Oculus\support\oculus-client folder. This used to be Oculus-Client.exe. You can either rename client.exe or change whatever shortcuts that point to Oculus-Client.exe, e.g. the Meta Horizon Link on the desktop.
Fixer is screwed up and doesn't handshake with the service even if it is up and running properly so it gives the error message.
Identical experience, meta quest 2, win10, crashlog:
[Info] [12/6/2025 2:28:17 PM] SUCCESS! Installed driver: Rift S USB Driver
[Debug] [12/6/2025 2:28:17 PM] -------------------------------
[Debug] [12/6/2025 2:28:17 PM] Installing driver
[Error] [12/6/2025 2:28:17 PM] Exception thrown that wasn't caught locally: Unable to load DLL 'DaybreakNative.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
at Daybreak.Core.Native.GetDefaultAudioDevice()
at OculusDriverInstaller.RemoteAudio.Install()
at OculusDriverInstaller.Installer.Install()
at OculusDriverInstaller.EntryPoint.Run(String[] args)
at OculusDriverInstaller.EntryPoint.Main(String[] args)
[Fatal] [12/6/2025 2:28:17 PM] Unable to load DLL 'DaybreakNative.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)
at Daybreak.Core.Native.GetDefaultAudioDevice()
at OculusDriverInstaller.RemoteAudio.Install()
at OculusDriverInstaller.Installer.Install()
at OculusDriverInstaller.EntryPoint.Run(String[] args)
at OculusDriverInstaller.EntryPoint.Main(String[] args)
Error Code: DllNotFoundException
Install Step: Unknown
Sub Install Step: Exception thrown that wasn't caught locally
Severity: Fatal
Line Number: 110
Caller: Main
ODI Version: 1.21.5.0
File Path: D:\full-fbsource\arvr\projects\oculus_pc_infra\Support\OculusDriverInstaller\OculusDriverInstaller\EntryPoint.cs
Frankly, i'm beyond frustrated. This is fresh install of Windows. The overall experience is just laughable.
