This has worked for me and I have had zero issues with instability, driver errors etc, anything that would harm the integrity of the average PC. This involves no regedits and only a single .bat.
reposting from my post on reddit ____
Okay. One idea. BIG idea. It's worked for me well.
BIG IDEA. needs more validation.
go
into device manager. check 'show hidden devices' and view devices by
connection. Scroll down to any hidden (greyed out) Quests, XRSP
interfaces, or ADB interfaces (if you are sideloading), and uninstall
them. Not the drivers, just them. They may be hidden in usb trees as
they should be. If you use an external, it may be under a PCIE bus, like
mine is there. Then reboot, then try to connect to link AFTER you open
the oculus app.
I have had some
spottiness but I think I figured out how to get it to work about 90% of
the time. The other 10% I just can't figure out. I need more validation
first before I can suggest this to other people for sure; it may just be
a device issue on my end, but I think that the continual in and out of
all these USB ports creates too many dead devices that confuses the
controllers + the oculus app. If you clean them up, it has a much easier
time detecting the oculus and enumerating it.
They will look like this.
Then do this. But not the red part.
https://i.imgur.com/UnoXsyu.png
Now go into services.msc (from ctrl-r, or run menu, or search) and set Oculus VR Runtime Service and Oculus VR Library (if it isn't already). I couldn't do this with virtual desktop because it patches itself automatically to fix the service missing error and it was so annoying that it worked that quickly. First time I've seen that really, he's a good dev.
Now create a .bat script that does the following
Net Start "OVRService"
Net Start "OVRLibraryService"
I will not provide a .bat for security purposes. Research what those commands mean if you don't know what they do. If you believe me, they simply start the service requested- in this case, the Oculus Runtime and Library services.
save
this in a notepad and make it a .bat. If you are not very windows friendly you may need to enable see file extensions to truly make it a .bat and not a ovrservice.bat.txt
See on the right hand side below.
Make that a
shortcut on your desktop or anywhere to this .bat. Put it somewhere easy to find. Anytime there is an issue, reboot both
devices, and then run that .bat, THEN connect link. You may need to
fiddle with the cable to find the right side, if using an elbow etc. Note: without clicking the .bat, no oculus software will run and will give you authentication errors if it does. Remember the .bat.
If
you delete all excess devices before doing all this (just before
running the .bat) I believe it fixes almost every issue. This will start
the services clean and be able to pick up and enumerate the device without any interference. I think this is simply a Windows flaw and not so much a Link issue- aside from the Link obvious issues.
I will note this does not have 100% success with me, and some days I'm just unsure why it took an extra hour or 2 reboots for it to finally kick in. I've had plenty of long cabled sessions since then though, so I know it's at least a proof of concept of device issues.
