lol I'm everywhere really XD. Or maybe nerds like us have similar taste, desire and ways of act that makes it easier for us to bump into each other lol.

I don't think that private collection of possibly working windows 7 7700 will ever leak. Especially now that Win 7 is gonna be the next XP.

Just grabbed a ASRock X299 itx and Z370 itx. Those are gonna sell for a high premium. Maybe I should also grab a X399 as well. A friend of mine who's working for lenovo in China told me that they ran out of 6th gen and 7th gen things while still have piled 8th gen and also those with 8086 A36D controller aren't gonna sell easily.

@bulka
The Intel 5.0.4.43 drivers cover 300-series chipsets, but they are for Win 7 and Server 2008. Intel has announced they are not releasing USB 3 drivers for Win 8 or 10, leaving it to Microsoft.

The DEV_A36D in the string you supply is for the Intel USB 3.1 xHCI USB controller.

I have my B360 300-series chipset running fine on Win 10 Pro. All USB ports work fine.

For Win 7 it's a different matter.

Your HM370 chipset is a 300-series chipset and the device A36D is the correct xHCI controller for your chipset. If you look at the end of the string you will see it's marked Rev_10. I think that's where the problem may lie for Win 7.

There have been revisions of the basic chipsets like your H370 and my B360. If you look in Device Manager under system devices, you should see a device called a 300 series LPC controller with the number A304 for the H371 chipset. Mine is an A308 for the B360.

The Intel drivers you listed are for a 300 series running Win 7 but apparently an older version. Intel has apparently not issued drivers for those models on Win 7.

It has been explained in Fernando's thread on USB devices that drivers are replaced by Windows depending on a ranking applied to the driver installed versus the one you are trying to install.

@Omicron

Zitat von Omicron im Beitrag #1987

---

Not quite, I (and you) won't get a hub device to show up because the xHCI driver doesn't load to begin with.

---

@Omicron
I may have read the stack backwards hence the dependency. That's thanks to Microsoft who are representing the stack is it would be represented in a computer. They show the hubs at the top whereas logic would have them at the bottom as a trickle-down effect.

Most drawings I have encountered re computers show the host (system) at the top with the peripherals at the bottom.

Need more time to analyze this.

Heh, MS gave Blizzard access to a set of libraries that allows for DX12 on Windows 7, if only they would release that xHCI hotfix :P

Zitat von Omicron im Beitrag #1998

---

Heh, MS gave Blizzard access to a set of libraries that allows for DX12 on Windows 7, if only they would release that xHCI hotfix :P

---

@RMSMajestic

Well that's interesting, looks like the repack mentioned on MDL but didn't know it had DX12 packages in it. Might try to extract them. I doubt MS would ever release an xHCI driver on their own, an internal leak of Intel's A36D would indeed be more likely as you are implying.

@RMSMajestic

Zitat von RMSMajestic im Beitrag #1999

---

I think some mobo manufacturer would have access to the xHCI hotfix/A36D driver. Just hoping for them to be too eager to promote the sales and release that. But I'm not sure if it's likely to happen. Given that even B365 has been released but no drivers for B360

---

Hi @Fernando,
I am very happy to join this forum, and found this thread.
Can you please give me a usb 3.0/3.1 driver for my PM?
My system :
GA-Z390 UD, Coffee Lake

PCI\VEN_8086&DEV_A36D&SUBSYS_84DB103C&REV_10
PCI\VEN_8086&DEV_A36D&SUBSYS_84DB103C
PCI\VEN_8086&DEV_A36D&CC_0C0330
PCI\VEN_8086&DEV_A36D&CC_0C03

Win7 x64

Thanks

I kinda wish there's an option for me to disable USB 3 completely and have a somewhat usable system (I don't consider Winbugs 10 usable). Is there any possibility for modifying the BIOS/UEFI for that?
Again, just saying. I'm not at all a fan of USB 3. For 10 freaking years they still yet haven't solved interference with 2.4Ghz and it's driving me nuts. I personally prefer eSATA much more.

If there's a driver released for B360 motherboards then it shoudl work with Z390 and all other mobile chipset. Since they all have the same hardware ID fro USB controller. (H310 v2 and B365 are different stories). Z370 do have USB3 drivers for W7 but it's an older controller

Hi @Fernando

I am very sorry to hear this result... It seems that I can only choose to use win10 which is more problems and more instability.

But I still have to say that I am much appreciate your unpaid and enthusiastic help to us and help a lot of people. thank you

First of all, thank you for this Forum. I have searched many web pages before getting to this one, and I feel this time I may get an answer for my problem.

I am having serious problems with EMI:
My system has a touchscreen, a keyboard and a mouse connected to the PC through an USB hub. During work time, the hub gets disconnected and reconnected several times, due to the EMI, until it eventually is not recognized by Windows; what is more, sometimes unplugging and replugging the USB connector does not solve the problem and I must restart the machine. I have tried many things to reduce the EMI, but it is not possible to completely remove it, thus a software solution is needed.

Is it possible to change the drivers behaviour with the installation of your USB 3.0/3.1 modded drivers? Am I missing something important and it cannot be done? Which drivers should I be changing? At first, I thought the only solution was to get the source code of the drivers (.sys files) and change them, but now it seems to me that I can change their behaviour by modifying the .inf file. Is it correct? Can anything be done to make Windows not discard the devices after many unplugs and replugs?

I have tried all I could find regarding regedit, Device Manager, devcon.exe… but none seems to recover the system after Windows has decided the devices are faulty.

Is it possible to get the source code for the drivers?

Thanks in advance

[My system:
Windows 7 Embedded (WES7P). I have tried it with and without the Convenience Rollup Update WES7. I have also checked it with Windows 10, and the problem persists.
Intel i5-4570S. 8Gb RAM
USB hub: Hub D-Link DUB-H4 rev D1 (https://eu.dlink.com/uk/en/products/dub-h4-4-port-usb-2-hub). Not powered, as powering it seemed to increase the disconnections
Keyboard: I am using a custom keyboard, but have tested several commercial ones, and they all have the same (mis)behaviour.
Screen: Elo Screen with touchscreen. I have tested some other screens, and the (mis)behaviour is similar (but not equal).
Mouse: Trackman Marble, from Logitech.]

I am using the default drivers from Windows, and later have tried to update them in the Device Manager, but no update has been done.

@Fernando
Thank you for your answer .

I am afraid I have already tried to keep my system as far as possible from the EMI, but it seems it is not possible to completely remove it.
With Linux, I was able to dig into the source code and change some timeouts. This way, I corrected the EMI problem in that system.
That is why I wanted to modify the. sys or. inf files.. Is it possible to get the source code for the drivers? Which drivers would I need to work on?

Thanks in advance