Hi, @canonkong
Can you use windows7 on threadripper 3000 systems?
How about 148C(Starship CPU USB 3.0 Host Controller)?
@ isopc1999a
Can you confirm that the USB master is 148C? If it is 148C, I can add this ID to the driver inf. AMD’s drivers have a certain generality, add the device ID can be used.
@canonkong
Sorry, that is unconfirmed information. EPYC Rome USB Controller’s Device ID is probably 148C. Please refer to the link.
https://pci-ids.ucw.cz/read/PC/1022
EPYC USB Controller is not the same as Threadripper’s one?
@bloodhand good to know, I got these drivers from a Windows 8.1 Update 1-image, tried them, and tried these from your suggested sub-foru, got the same error code, no surprise there.
@canonkong I am not into programming like C++ or something like this, but I think it is more about try and error than pro-education, not that that would not be helpful. Of course this needs testing, like on my Windows 7 ISOs, how wothout testing and try & error ?
I would not be surprised if it would be not easy to backport native usb3-drivetrs to Windows 7. I, of course, think M$ sould have done that, like they did it with SP4 für Windows 2000 in 2003 for native USB2.0-support, backportet from Windows XP’s SP1 from 2002. Or like they did with native NVMe-support: A regular Update to install/slipstream, and that’s it. This native driver appears, at least for me, not to be as good as it should be, I was not able to read SMART information off of a Samsung 970 EVO Plus. With the Samsung-driver it worked. Of course, at least some sort of native usb3-driver would be way way better than just nothing. The best would be a native driver like we know it with AHCI since Vista, for instance.
I assume by ‘perfect’ you mean to add support for those HW-IDs ? That yould be great, long live Windows 7, because it’s fun to create something and work on it than just use it.
@PatrickK
Yes，add the ID support. You can try my modded usb driver 2.0.0.49，it can work as a general usb driver that support other usb device like A36D of B360/Z390，VIA，ASMedia and more ，also can work on Nvidia USB-C，
@PatrickK
Canonkong said he will release the generic usb-c drivers in a few weeks after he gets the patent credits, if I understand correctly. I am waiting for those too to test on my ACPI\USBC000 device under win7. Under win10 I get UCSI USB Connector Manager for this device, in win 7/8.1 unknown driver. That’s because usb-c ucsi is a device class only present in win10. I truly hope that the driver canonkong will release addresses this issue accordingly. I cannot wait to be able to use an USB-C to HDMI 4k60hz with it, now i’m stuck with 4k30hz using the native hdmi.
The 2.0.0.49 driver is incredible!
What is the 2.0.0.49 driver made of? What is the original driver?
hey man, great work, i tried using this and i managed to fix the usb controller unknown devices successfully.
but i still got 2 "AMD Root Hub(xHCI)" with a yellow warning triangle.
when trying to update the driver, it says the optimal driver is already installed but yet, it says this device cant be started.
i have a third of those amd root hub(xhci) which is working, and seems to be using the same driver ?!
win 7 64bit
x570
ryzen 2700x
best regards
ah ye, actually deleting the driver(clicking the checkmark) fixed it.
any idea what H150i Platinum is ? that shows up now, i assume it has nothing todo with the usb, just thought u might know aswell 
edit, nevermind thats my liquid cooling XD
The Samsung NVMe Controller driver 3.1.0.1901 or 3.2.0.1910 will work fine with the Aorus NVMe Gen4 SSD. The Windows 7 NVMe hot fix KB2990941 must be installed for trim to work.
My emotion: OMG
So does that mean that TRIM on NVMe-Devices does not work without the NVMe hotfix and a driver like Samsung’s is not enough ? Not that I wouldn’t have that implemented on my ISOs but I am curious.
My emotion: OMG
So does that mean that TRIM on NVMe-Devices does not work without the NVMe hotfix and a driver like Samsung’s is not enough ? Not that I wouldn’t have that implemented on my ISOs but I am curious.
Trim worked on my Samsung NVMe 970 Evo with the Samsung driver, however the Aorus drive did not have trim enabled using the Samsung driver as tested with Trim Check without the Windows hot fix installed: Tweaktown article The Aorus drive works at Gen 4 speeds with Windows 7, with the exception of boot times.
@ryegrass Ok, thanks for your information, good to know. Maybe, on one day in the furutre, I will test this on myself.
Cool, thanks to link this utility from this slavic guy, those are the people that this world needs. Took a look at it and on my everyday-rig (not the ryzen-pc) TRIM apperas to be working like intended, whoohoo. :D.
is it a known issue that u cant play any games that use EAC (easy anticheat) while running those modded drivers?
ever since using those drivers, the anticheat just tells me to close "generic hacking tool" XD
i am aware that cheaters like to abuse drivers to access games protected by kernel anticheats, but a modded usb driver seems a bit strange xD
I’m a little bit confused about the newer USB drivers listed by canonkong. I have been using the originally posted 68 (2.0.0.0068) drivers on my MSI X570 Gaming Plus (Windows 7x64) for about 4 months now with no problems. Thank you canonkong! These drivers have been working well at USB 3 speeds with the minor exception that they will not detect a Logitech receiver.
What advantage(s) do the 49 (2.0.0.0049) drivers have? They appear to be an older version, and after installation, wouldn’t start on my machine.
My Configuration
8 USB 3.2 ports
3 AMD USB 3.2 eXtensible Host controllers
3 AMD USB 3.2 Root Hubs
1 AMD USB High Speed Hub
various USB 2 Hubs
I uninstalled the triangle one and rebooted but now it is showing as "unknown device" and will not be updated when I try to point to the downloaded file.
EDIT: Nvm, you were 100 % right and reinstalling it did fix it.
EDIT2: Windows 7 still will not find my USB CD-drive. :S