Forum Discussion
'Connection dropped by windows 11 5001' error :(
When I see the icon above my Windows 11 keyboard and press connect, my laptop screen goes blank for a few seconds and I get the error 'Connection dropped by windows 11 : 5001' error :(
I have unpaired and repaired the windows laptop and I have run the Meta setup.msi several times... the connection just keeps dropping.
I am using a MS Surface Pro X, connected to my Meta Quest 3 512gb running the Latest V72 PTC.
I checked the compatibility and all looked good on install on both devices.....
22 Replies
- ijotamaxCopper Contributor
SonicXHello,
Let me tell you something, when I updated to v72 I had several problems and one of them was error 5001, what I did was completely uninstall both Windows and Mix Reality from the Quest 3 because when you delete it from Windows 11 on Bluetooth devices it does not delete from the Mix Reality application at least in my case, then you have to delete both parts and then start the process again and that was the only way I could get it to work and avoid the error.
By the way, I still have not updated to version v74 and I don't have that update
- SonicXCopper Contributor
After update my quest 3 to V74 and latest remote desktop APP, got (ID: -5001.5) error code.
- ijotamaxCopper Contributor
Hello, Let me tell you something, when I updated to v72 I had several problems and one of them was error 5001, what I did was completely uninstall both Windows and Mix Reality from the Quest 3 because when you delete it from Windows 11 on Bluetooth devices it does not delete from the Mix Reality application at least in my case, then you have to delete both parts and then start the process again and that was the only way I could get it to work and avoid the error. By the way,
I still have not updated to version B 74
- ijotamaxCopper Contributor
Hello, Let me tell you something, when I updated to v72 I had several problems and one of them was error 5001, what I did was completely uninstall both Windows and Mix Reality from the Quest 3 because when you delete it from Windows 11 on Bluetooth devices it does not delete from the Mix Reality application at least in my case, then you have to delete both parts and then start the process again and that was the only way I could get it to work and avoid the error.
By the way, I still have not updated to version v74.
- Johnny4Copper Contributor
I'm experiencing same issue on Surface Pro 9 with SQ3 processor. Could root cause be related to "unsupported hardware"?
- bdunawayCopper Contributor
Wanted to add my voice to this issue as well. My PC is a Dell Ultra 7 CPU/GPU, which includes Arc GPU. Getting the same error 5001 message. 1080P RDP should be easily possible with this GPU. I'll try to find diagnostics information for to gather more details.
I'm willing to be patient, it is Christmas after all, but hoping this will evolve and get better. Using RDP out of immersive mode with other applications is an amazing way to work.
- ijotamaxCopper Contributor
Finally I can get it working but in a single resolution of 1920x1080, before I could change the resolution but now I can't. What I did was unpair the devices, then I generated the QR in that window on the top right is the configuration icon, I clicked and in the next window the quest 3 appeared paired and what I did was unpair, I closed the window and started the process again and at that moment it worked.
- JonLyons
Microsoft
Thank you all for reporting these issues! Error -5001 is a high-level connection error and can be caused by multiple things. We're looking into these reports as they come in and your feedback is helpful! For folks who haven't already, the best way to help us investigate these is by sending feedback through Feedback Hub which includes additional diagnostic information for us. You can find instructions here:
About Windows Mixed Reality Link - Microsoft Support
Domdedomdomdom , we believe your specific issue is related to your Surface Pro X PC. Unfortunately, that specific model is running an older ARM SoC that we don't currently support, and seems to cause this issue. From the link above, we support ARM SoCs that meet the Copilot+ PC requirements. More details are available here: Copilot+ PC hardware requirements - Microsoft Support- DomdedomdomdomCopper Contributor
Thanks Jon.... While its a solution, its not great for me! I will delete the software and stick to the better Remote Desktop App, that has worked out since launch.... #VirtualDesktop
- DomdedomdomdomCopper Contributor
Thanks Jon, I have sent the feedback through the hub with diagnostics @ today 21-12-24 5pm GMT the same issue occurs. My fallback is now and has always been the remote desktop app on meta... But if we can get this working it would potentially be slicker.....🤔
- kkohlmann55Copper Contributor
This error I do not think has anything to do with ARM as you stated it is a "high-level connection error.
For me I am running the Surface Studio Laptop 2 and also have this issue. Can you please provide more steps for troubleshooting...- JonLyons
Microsoft
Yes, -5001 can be caused by many different issues. In the case of Surface Studio X, it's a result of being on unsupported hardware. For hardware that meets our minimum requirements like Surface Studio Laptop 2, it's likely something else.
Basic troubleshooting steps include making sure you're on supported hardware (see link above) and running the latest graphics drivers.
I don't have specific additional troubleshooting steps at this time, other than to encourage folks who hit this to follow the instructions above to file feedback in Feedback Hub. While we may not be able to respond individually to everyone, we use that feedback to investigate and fix issues as we continue to release updates. Thank you for reporting!
- DomdedomdomdomCopper Contributor
And no reply from MS support...... 🤔
- DennisMcDCopper Contributor
I'm in the same boat. Finally got v72 installed on my Quest3. Followed the instructions, registered properly and PC shows up as an option, but always fails with error 5001. I'm on the same subnet, rebooted both devices, uninstalled and reinstalled, re-paired, tried with/without Windows firewall, everything. Hoping someone has an answer!
- loribeeincaCopper Contributor
Having the same problem -5001 error. :(