Meta Link freezes after a few seconds
After installing latest Meta Horizon Windows app update (85.0.0.239.552), the display inside headset freezes (sometimes goes black, similar to when proximity sensor kicks in, but while still wearing ...
Forum Discussion
I just purchased a Quest 3s a few days ago and havent been able to get it to connect via Link Cable to save my life. Ive tried so many different fixes on the internet and none have fixed it.
I use a AMVR Link Cable with Charging, plugged into a 3.2 USB Port on the IO of my mother board, rated for 10Gbs. Half the time the quest detects there's a USB plugged in but doesn't give the Link option. When it does give the link option I hit launch. THEN there's a 50/50 shot it freezes in the purple horizon loading screen or it loads into the desktop VR. When it loads, I open VRC for example, the game will get about 10 seconds into loading then it freezes/BlackScreens. Then I have to re attempt the whole process. Ive gotten it to work ONE time and that was 2 nights ago. Zero clue what I did differently but that shows me its possible.
I want to avoid AirLink/Virtual Desktop because I want to take advantage of my PC's specs. And also I don't have access to my router for a wired internet connection.
I know this probably inst the forum to post this in but im so fed up with trying to make this $300 paper weight to work the way its supposed to. Been stuck using an Rift S until I can get the Quest to function normally.
Hi,
Like you, I only purchased my Quest 3 a few days ago. I've been using a HTC Vive Pro 2 to date, so the whole Meta thing was new to me. With everything fully up to date on my system, it just continually crashed once I launched into the PCVR Link 'purple' screen. If I was lucky, it would work for, maybe, five minutes, but would generally freeze after 30 to 60 seconds. Frankly, I was ready to junk the Q3, until I went into this forum! As suggested by many, I downloaded and installed an older version of the nvidia drivers, dating back to January 2026 (no fancy deleting the old drivers, btw. Just a quick double click on the .exe!), and it fixed the problem. Just to satisfy my masochistic tendencies, I re-tried the latest nvidia drivers for a second time, and the problem returned, 100% of the time. I then re-reinstalled 'ye olde' v591.86, and it was back to 100% good!
Easy fix!
Quest Pro user here.
591.86 worked for me too, like you just downloaded and ran the exe - no fuss!
