Zitat von Fernando im Beitrag #1875

---

By the way - the biggest surprise for me was, that it was no problem for me to replace the original Win10 in-box USB 3.0 drivers by drivers (= *.SYS files) with the identical code, but with different names, different INF files and a third party digital signature.
It was not even necessary to disable the driver signature enforcement or to force the installation by using the "Have Disk" button.

---

Zitat von Fernando im Beitrag #1875

---

It was not even necessary to disable the driver signature enforcement or to force the installation by using the "Have Disk" button.

---

Zitat von Omicron im Beitrag #1876

---

Posting this per request: The most recent 1809 xHCI generic drivers also do not work under Windows 7 (didn't even get to the hub or switch phase,) the xHCI driver itself again fails with "The driver may be corrupted or missing. (Code 39)." This same error occurs with the 1607, 1507, or 8.1 drivers.

---

Zitat von Fernando im Beitrag #1879

---

Which specific bytes should I try to change in which manner?

---

Zitat von Mov AX, 0xDEAD im Beitrag #1877

---

You somehow breaked signing protection system, so anyone now can create selfsigned "ring0 viruses" for 64 Oses )
p.s. but it still need rights to import cert to root/trusted storage
p.s. Omicron is probably right, signature stored in catroot storage. if you hve free time, change some byte in any string inside *.sys, resign and check

---

Zitat von Omicron im Beitrag #1881

---

I'm wondering if someone might try starting up a generic MS driver and seeing what functions it calls (the additional ones you mentioned as part of 8 and up) and seeing if implementing these might make them work (sort of like the people doing the Windows 2000 extended kernel project.)

---

Zitat von Mov AX, 0xDEAD im Beitrag #1882

---

i tried win8 driver on win7 some time ago, matching import is not enough, ms usb3.x driver uses some implemenation of api on win8+.
so on win7 x32 i got kernelfault where all functions are exported from kernel/hal. i dont dig deeper

---

@JoeyImage
May be can you try the last ASMEDIA USB 3.x driver v1.6.55.1 available on station driver ?
@Fernando
I have installed and do use ASMEDIA USB 3.x driver v1.16.55.1 (25th october 2018) version without any problem on my Sabertooth X99 mboard, W10 x64 machine.

Hi everyone.
First off, I'd like to say thanks to Fernando for this page.
I recently just got a USB 3.0 to HDMI converter off of ebay to extend to a second monitor. First monitor works just fine as it has since i've had it.
I tried connecting the second monitor to the USB-HDMI converter device but I get an error "The xHCI controller for this port cannot display high resolution" - I've already upgraded the host controller with @Fernando 's instruction on the page and I can see the Renesas USB3.0 controller in the Device Manager section. I do get an output when I reduce the monitor resolution to say 1024x800 though but the monitor screen just goes blank when I increase it past that. Is this a problem with the device I bought or my PC can't output 1080P to two different monitors?
PC Spec below:
Intel® Core™ i5-2520M CPU @ 2.50GHz
HP 8460p Elitebook
Microsoft Windows 10 Pro (64-bit)
Device is a USB3.0 to HDMI converter that uses Fresco Logic software installation file.

Thanks in advance for any tip/suggestion.

@Fernando, it is DEV_0194.