For whatever reason when trying to pair my Quest 2 to my laptop via USB, the site tells me that I have adb.exe running. Odd. It's not there in Task Manager. So I run it in powershell and cmd, using both adb kill-server (adb is not recognized as a command in this instance), so I run taskkill /F /IM adb.exe /T instead (which tells me that the process is not found). So adb is running on another application but I don't use another application that uses adb except Unity, and that's not open. I'm going to try installing Android Studio and then killing adb and trying again.