I hope to avoid reinstalling windows as that would mean reloading all apps and files.This article describes the class drivers, generic client driver, and the parent composite driver that are provided by Microsoft. Here is a picture of my device manager as it stands now. I am wondering if that's what the error I'm seeing is - not having that ASMedia USB root hub driver that I need for Oculus. I am wondering if that's the problem as I don't see one for 3.1? When I google device manager images randomly with some of my key search words, I do see some device managers having "ASMedia USB Root Hub" under that last USB Controllers section. One question I have is should I have a second USB root hub in the device manager USB controllers section at the bottom? The only one I have says USB Root Hub (USB 3.0). But I have 30 days and want to be sure it's not my USB root hub before I do that. Some backstory here is that I went through Oculus support for over a week and now have an RMA to send the Quest 2 back to them. I have tried it in both the USB-C port and a regular fast USB port (blue ones) with an adapter which should work (USB 3.1 GEN 2 Male to Type-C Female Adapter ).
So now the only device manager errors I have are related to ASMedia root hubs.Īll of my USB ports seem to work for typical peripherals (webcam, headphones, mouse, keyboard) except that my Oculus Quest 2 does not. I also removed the CSR bluetooth chip which boosts bluetooth because it also creates an error and I'm not using it anyway. Asus driver from 2018 and creates the error. Strangely, when I update the adapter using Driver Booster 8, it loads a driver from 2019 vs.
0 kommentar(er)
