Forum Discussion

rholt51's avatar
rholt51
Honored Guest
2 months ago

Meta Quest Link "can't find Link server..." maybe a fix?

i have a Q3 and a Dell Windows 11 PC. i've been plagued with the Link not connecting most of the time and finally getting it to link after many reboots of everything including my brain!!!!!

the other day, Meta Support chat guy suggested that i download and run the  MQL (Meta Quest Link) installer app and choose "Repair" on the 1st menu. i did so and IT WORKED!!!! ... until the next time i powered on my Q3 and went to Link. same prob. i tried the same fix and it worked again. 

the next time i tried it(yesterday) it did not work. indeed, the MQL software would not install saying it "cant find the Link server". i spent literally HOURS (more than 6) scouring the internet and AI and trying every fix i could find that sounded the least bit plausable. 

FINALLY last night i came up with a solution for the reason the app would not load...

FIX ***********          **************

at some time during yesterday (or the night before) i turned my microsoft "One Drive" on. for some unknown reason, Windows "moved" my "Downloads" folder from

"C:\[user]\Downloads"

to

"C:\[user]\OneDrive"

all i did was copy the install file from OneDrive to my Desktop and the install ran GREAT! 

it did NOT, however, fix my connect problem. i still have to run t he "Install/Repair" process each time i want to use LINK after a Q3 Power-On.

i'll be looking into why the path change happened, but i hope this helps all those who may be in limbo trying to get this program installed, again.

Russ from Ocala, Fl, USA

2 Replies

  • steve_40's avatar
    steve_40
    Expert Trustee

    One Drive seems to cause havoc with a number of software programs on PC. Family Tree Maker is one of them that I have.

  • Had a similar “why is this happening” moment on my PC where nothing worked until I moved an installer out of a synced folder. While testing network stuff on another project, an IP Stresser actually ran super clean, so I knew the issue wasn’t my connection.