AFAIK these devices are no Intel USB 3.0 Controllers. So the addition of the related HardwareIDs to the INF file of the latest mod+signed Intel USB 3.0 driver woldn’t work.
Why do you want to update their driver?
You do not understand the true test , they are identified as a Windows driver , and I want to establish a family from Intel. Sorry for my english , I’m doing machine translation .
Why don’t you search yourself for usable Intel drivers for USB 2.0 Controllers?
It is a good idea, Fernando , thank you very much for your help , let your project develops. As would be more people like you …
Hello,
I need Windows 10 drivers for VIA VL800 chipset.
Is there any modified package available?
I found your forum here: http://forum.giga-byte.co.uk/index.php?t…g97834#msg97834
@gudinko :
Welcome at Win-RAID Forum!
Not yet from my side.
Please look into your Device Manager and post the HardwareIDs of your on-board USB 3.0 Controller (right click onto it > "Properties" > "Details" > "Property" > "HardwareIDs").
Thanks or the interesting link.
By the way: When I modify and digitally sign drivers, I do that for the members and visitors of the Win-RAID Forum and not for those of any other Forum.
By the way: I do not like it, when drivers or BIOS modules, which have been modified by me, are offered and hosted within other web sites without having even asked me. This way I don’t get any feedback, which is absolutely necessary for me, when I want to optimize the offered drivers or BIOS modules.
Regards
Dieter (alias Fernando)
Not yet from my side.
Please look into your Device Manager and post the HardwareIDs of your on-board USB 3.0 Controller (right click onto it > "Properties" > "Details" > "Property" > "HardwareIDs").
Thanks for your response Fernando.
Here are the HardwareIDs: http://i.imgur.com/Ka4QUeC.png
This is the USB 3.0 card with the VL800 chipset: http://www.via-labs.com/product_show.php?id=51
And here are the latest (v4.90A) drivers (not compatible with Win 10 though): http://www.via-labs.com/driver.php
Could you perhaps make a modified Win10-compatible package for this one?
EDIT by Fernando: Blank lines and unneeded parts of the fully quoted post removed (to save space)
- Your link leads to a page, where the installer of the VIA USB 3.0 drivers v6.1.7600.4903 dated 10/31/2014 are listed (as *.EXE file). The latest USB 3.0 drivers are v6.1.7600.5101 dated 08/29/2015 and the related download links are within the start post of this thread.
2. Neither the v6.1.7600.4903 nor the v6.1.7600.5101 VIA USB30 drivers do support the HardwareIDs you have posted. Obviously both driverpacks are only usable with VIA USB 3.0 Controllers, which are implemented into a mainboard, but not with an add-on PCIe card.
So you should ask the manufacturer of your add-on PCI/PCIe card for a suitable Win10 driver.
Well, the manufacturer probably doesn’t care… I bought the card from a Chinese ebay seller long time ago.
Can I add the hardware IDs myself? And if so, how exactly?
You can try it, but you have to make sure, that it is a VIA USB 3.0 Controller, which is on your PCIe card.
The modification itself is quite simple: Just open the *.inf file with notepad and add the missing HardwareIDs of your device.
You can try it, but you have to make sure, that it is a VIA USB 3.0 Controller, which is on your PCIe card.
The modification itself is quite simple: Just open the *.inf file with notepad and add the missing HardwareIDs of your device.
There are 2 *.inf files in the Win81/x64 folder. What exactly do I add and in which *.inf file? I don’t want to do any mistakes.
Also, the "unrecognized" device in the Windows 10 device manager is the USB controller, not the USB Hub. I can’t find the Hub anywhere else.
You can forget your idea to modify the related *.inf file of the VIA USB 3.0 Controller driver (it is the file named "xhcdrv.inf").
I just found out, that the HardwareIDs you had posted do not belong to the USB 3.0 Controller, but to the Chinese Xbox 360 Wireless Receiver.
For details look >here<.
This lets me think, that the on-board USB Controller works fine, but the "missing driver" message you got is caused by the Chinese Xbox, which is obviously connected to any of your USB ports.
You’re right. I disconnected it just in case, but my USB3 ports still don’t function.
I don’t see any VIA Labs controller in the Device Manager either. What gives?
The best is to post a screenshot of your Device Manager after having expanded the section "Universal Serial Bus Controllers".
I disconnected the XBOX360 controller dongle temporarily and the VIA USB 3.0 controller appeared all of a sudden after a reboot! Thanks a lot for your help.
It is fine, that it works now (no extra modded drivers required).
You’re welcome!
Since I have a system with onboard VIA VL800 USB3, the 5101 (5.10A) drivers are actually for Windows XP - Windows 7. The installer says so, the included inf are only Win7 and nothing is installed under newer operating systems (8.x and 10). The older ones at VIA website (4.90A) support all OS (before Win10 of course as they are from 2014). For Windows 10, the drivers need to be installed manually because the installer does not seem to actually install anything. They do work just fine after manual installation though.
Why don’t you search yourself for usable Intel drivers for USB 2.0 Controllers?
Hello Fernando. I tried to update the device with the help of Chipset_Intel_10.1.1.34, it declared support for Intel (R) 7 Series / C216 Chipset Family USB Enhanced Host Controller - 1E2D ID PCI \ VEN_8086 & DEV_1E2D & CC_0C03 and Intel (R) 7 Series / C216 Chipset Family USB Enhanced Host Controller - 1E26 ID PCI \ VEN_8086 & DEV_1E26 & CC_0C03, but in the end they are not updated. Is it possible to do this. Current driver Microsoft 10.0.10586.0
help me
ECHOLINK EL-2015 OST-GX5605-AV2018-V02 DDR2_512mbit
software
@Documentary :
1. You are obviously searching for an USB 2.0 driver, but the topic of this thead is about Intel USB 3.0 drivers.
2. The Intel Chipset Device INF files are no real drivers, but just text files, which tell the OS, that the related device is from Intel and doesn’t need a driver.
3. Why do you want to change the driver, if the generic USB 2.0 driver is working fine?
@imtiaz_2007 :
Welcome at Win-RAID Forum!
Since I don’t know about what you are talking and what your post has do do with the topic of this thread, I cannot help you.
Regards
Dieter (alias Fernando)