Seems like the Hardware ids might not be in the inf files. not sure what that means.

@Fernando sorry didn't know you replied and I posted again and I could not tag you again.

EDIT: I see on page 107 you talking about this. I will dig deeper if possibly. Thanks.

EDIT 2: I have came across this site: https://www.overclock.net/forum/6-intel-...mus-x-hero.html and there seems to be a way to get the usb drivers possibly from the file for this motherboard. I will be digging deeper.

I installed a new Nvidia RTX2080 card in my PC and was wondering if anyone has modded the USB drivers from Win 10 to be used on Win 7? The USB type C port on the card does not function, nor will Nvidia support Win 7 with a driver to enable the port. I don’t use it, but would be nice to provide it for all the people who have the same need for the RTX series cards. See the above title description for what I am asking about.

I am on Win 7 Pro with a AX370 K3 board. Ket modded bios installed.

Thanks,

MAK

Seems that the Files are no longer available at MEGA. I Also have Hardware IDs similar to Bryant, but my MoBo is a MSI Z390.

Nope, doesn't work - see the stickied thread on USB drivers, namely the last few pages.
No one has a solution.

EDIT by Fernando: Since June 2019 there is a solution for this problem. Look >here<.

B. ASMedia USB 3.0 / 3.1 Drivers is not found by reference

@Fernando
only the 'mirror' option is working, very strange

@Fernando @Omicron
The drivers you guys supplied did not work. Sorry for not getting back sooner. There is something deeper going on, something in Windows 7 itself. I am currently investigating.

In Device Manager, at the beginning of the device tree under your user name, you can right click there and get a menu allowing you to install legacy drivers. When I activate it and choose the opportunity to install for myself, I get a window listing the available device drivers. There was no category for USB drivers.

I found out how to make it appear with a registry adjustment. If it interests you, let me know and I'll go back and track it down.

With the USB 3 devices listed, if I select one and OK the install, the window breaks up for a few seconds then simply returns to the driver window. Something has been disabled.

I am thinking a past update may have supplied a modified kernel or a system module and the hardware installer reaches a dead end. It's unusual that it simply returns to the hardware driver selection window so I am thinking Msoft has simply added a Ret instruction in the system module to send the code back with no action being performed.

@Fernando
I saw a post of yours a while back in which you complained of Intel signing their drivers with dates like 1968. Did you ever see the solution? They do it so the driver will have a certain precedence when Windows assesses which driver to load. Microsoft has been doing the same by dating their drivers as 2006.

In my recent reply, I claimed Msoft may have altered their hardware installer with a RET instruction to abort any attempt to load USB drivers. I don't know if that makes sense but it makes even less sense to not list USB drivers in their legacy devices. They seem to want sole control over which drivers get loaded and even Intel suggests you don't use the hardware installation component in Device Manager.

Zitat von gordo999 im Beitrag #1975

---

@Fernando @Omicron
The drivers you guys supplied did not work. Sorry for not getting back sooner. There is something deeper going on, something in Windows 7 itself. I am currently investigating.
In Device Manager, at the beginning of the device tree under your user name, you can right click there and get a menu allowing you to install legacy drivers. When I activate it and choose the opportunity to install for myself, I get a window listing the available device drivers. There was no category for USB drivers.
I found out how to make it appear with a registry adjustment. If it interests you, let me know and I'll go back and track it down.
With the USB 3 devices listed, if I select one and OK the install, the window breaks up for a few seconds then simply returns to the driver window. Something has been disabled.
I am thinking a past update may have supplied a modified kernel or a system module and the hardware installer reaches a dead end. It's unusual that it simply returns to the hardware driver selection window so I am thinking Msoft has simply added a Ret instruction in the system module to send the code back with no action being performed.

---

@omicron...I'm not finished yet, still at it.