@mbk1969 :
Thank you very much for your work. If the dpinst.exe method should work, it would be a big help for users, who don’t have a system with non-Intel USB ports.
It is a pity, that I right now cannot try your script (I am currently travelling and don’t have access to my usual equipment).
Just a small correction of your script: There is 1 space character too much within the name of the folder “Switch Driver - only if applicable”.
Thanks again!
@m2840 :
Please check the HardwareIDs of the device namd "Generic SuperSpeed USB Hub". Most interesting is the VendorID.
You are right - the ASMedia USB 3.1 Controller is not listed within your Device Manager. This is interesting, because the USB Controller is managing the USB Hub devices as well.
You are right - the ASMedia USB 3.1 Controller is not listed within your Device Manager. This is interesting, because the USB Controller is managing the USB Hub devices as well.
The HardwareIDs associated with the "Generic SuperSpeed USB Hub" is the following:
USB\VID_174C&PID_3074&REV_0100
I copied the name of the folder right in Explorer. And the folder was created by extracting the archive from this thread. It may be that I somehow inserted that extra space character, but it may be that archive has that folder with that extra space character.
Archive is "64bit Intel USB 3.0+3.1 Drivers v5.0.0.32 mod+signed by Fernando.rar" - I checked and it actually has that "Switch Driver - only if applicable" with extra space character before the "-".
As for bat-file, I will add logging the steps into file. It will be helpful.
Edit: Here is script with logging and steps of progress
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
@echo off
set step=updating Controller Driver...
echo %step%
echo %step% > .\update.log.txt
dpinst.exe /path ".\Controller Driver - as first" /sa /q /f
echo result code: %Errorlevel% >> .\update.log.txt
set step=updating Hub Driver...
echo %step%
echo %step% >> .\update.log.txt
dpinst.exe /path ".\Hub Driver - as second" /sa /q /sh
echo result code: %Errorlevel% >> .\update.log.txt
set step=updating Switch Driver...
echo %step%
echo %step% >> .\update.log.txt
dpinst.exe /path ".\Switch Driver - only if applicable" /sa /q /sh
echo result code: %Errorlevel% >> .\update.log.txt
set step=rebooting Windows...
echo %step%
echo %step% >> .\update.log.txt
shutdown -r -f -c "Rebooting after Intel USB3/3.1 drivers update"
echo result code: %Errorlevel% >> .\update.log.txt
It should create log file "update.log.txt" near the bat-file itself.
Edit: Btw, script can be placed either into bat- or cmd-file.
Why didn’t you take the most recent drivers v5.0.1.38 as source package?
It would be very easy for me to avoid any space character problem, if I rename the subfolders to "Controller-Driver_as-first", "Hub-Driver_as-second" and "Switch-Driver_as-third-if-applicable".
What do you think about that idea?
Thanks for the reply, which verifies, that the device named "Generic SupoerSpeed USB Hub" has been manufactured by ASMedia, but is managed by the on-board Intel USB 3.0 Controller.
This is very similar to the connection of a Microsoft USB mouse to an Intel USB port.
So you don’t need any ASMedia USB driver to get the ASMedia USB Hub device working.
Why didn’t you take the most recent drivers v5.0.1.38 as source package?
I just did not download that v5.0.1.38 bundle, sorry. I did install v5.0.0.32 bundle and it was the source of info.
It will eliminate space character problem for sure. In case you will provide dpinst.exe and bat-file with bundle archive you just need to check that names of subfolders are correct in bat-file.
I have a sudden thought: if I would use PowerShell instead of command prompt I could write PS script which is capable to search for all subfolders, which could have order part in the name (for example they could start with the number "1 -", "2 - ",…) and part for "force installation aka have disk option" or "if applicable aka browse for drivers option" (for example name could finish with "- force" or "- optional"). In that way script could make ordered list of subfolders and decide which command line parameter of dpinst.exe to use with them - for forced or for optional installation.
Edit: Of course it is no big deal - to write complicated scripts for such simple matter. And bat-files are still more familiar to wide public comparing to PowerShell known mostly to professional IT public.
@YuriyCN :
Since I now have the required time to work on problem "How to get USB support while running Windows XP on a modern Intel Chipset system?", I followed your links, but was not able to get the needed drivers downloaded.
Can you please attach a ZIP or RAR archive, which contains everything I will need? Most important for me is the original XP in-box USB driver (I need the related *.sys and *.inf file, which both can be found within the folder C:\Windows\System32\DriverStore\FileRepository).
Thanks!
Hi Fernando, there is a problem of 64-bit Intel USB 3.0 / 3.1 Driver v5.0.1.38 Mod + technology signed Fernando does not always respond to a flash drive helps to remove the device, or restart, how can I fix it? device ID PCI\VEN_8086&DEV_1E31&SUBSYS_14871043&REV_04, WIN 10 x64
@Documentary :
Your problem is caused by the fact, that only Intel chipsets from 8-Series up are supported by the original Intel USB 3.0 drivers v5.0.1.38 WHQL. The DeviceID of your on-board Intel USB 3.0 Controller (DEV_1E31) indicates, that your system has an Intel 7-Series Chipset.
When I modified the first Intel USB 3.0 drivers, I added the missing DeviceIDs DEV_1E31 (REV_00 up to to REV_04) and Z77 chipset users reported, that these modded drivers worked fine for them as well. That is why I continued to add these DeviceIDs, which natively are not supported, into the Controller INF files of all the recently released Intel USB 3.0 driver versions.
Neither you nor me can fix it. If you want to avoid this problem, you will have to use the MS in-box USB 3.0 drivers.
Hallo,
Fernando begged me to say something about this issues. I didn’t read the whole thread. I just saw that you are trying to build a cmd script.
I prefere to do this task in an other way: Modding DPinst.exe itself.
This can be done using an additional XML file called "DPInst.xml"
The content of this file should look like this:
1
2
3
4
5
6
7
8
9
10
2
3
4
5
6
7
8
9
10
<?xml version="1.0" ?>
<dpinst>
<search>
<subDirectory>Controller Driver</subDirectory>
<subDirectory>Hub Driver</subDirectory>
<subDirectory>Switch Driver</subDirectory>
</search>
<forceIfDriverIsNotBetter/>
<suppressAddRemovePrograms/>
</dpinst>
The folder should then look like this:
1
2
3
4
5
2
3
4
5
.\Controller Driver\<< driver files >>
.\Hub Driver\<< driver files >>
.\Switch Driver\<< driver files >>
.\DPInst.xml
.\DPInst.exe
This will trigger dpinst.exe to look into the given sub folders and install the drivers if, and only if there is a suitable device. Otherwise the driver will just be copied into corresponding windows folders without getting used. There are lots of other (unnecessary) switches - you can even mod the window appearance of dpinst. You might search the web by your own.
Greetings Zwulf
@Zwulf :
Thank you very much for your contribution and advice.
Questions:
1. Will your modified DPInst files work with drivers, which have been modified and signed by me?
2. What happens, when only the on-board Intel USB 3.0 Controller is supported by the related driver, but not the other Intel USB 3.0 device(s)?
3. Is it possible, that the related DPInst.exe file checks before starting the update, whether all attached drivers match the HardwareIDs of the related on-board USB 3.0 devices? If yes, how?
1.) yes if the certificate has been installed bevor
2.) Like i said: Dpinst will only install suitable drivers
3.) I’m not sure why somthing like this is necessary. If only controller and hub fits, dpinst won’t install the switch driver. There is a installAllOrNone switch. But this way most of the time you won’t install anything. I haven’t read anything about a real test mode so far. But of cause you are free to read the manual by your own.
Have a Nice Evening
Problem with using dpinst.xml is you can`t select different modes for different folders in group. Mode is either forced or not forced for whole group. So it is more flexible to use command line parameters.
You may be right, Zwulf’s method may be problematic with Mobile systems, which have unsupported Intel USB 3.0 Hub devices.
Nevertheless I was curious about how Zwulf’s method will work with my Z170 system running a freshly installed Win10 x64.
This is what I did after having created the DPinst.xml file and the driver folder as recommended by Zwulf:
- As first step I imported the Win-RAID CA Certificate.
- Then I did a right click onto the DPInst64.exe and simply executed it as Admin (no CMD or PowerShell required!).
- Immediately the install process was intiated by showing a GUI, where I was asked, if I want to install these drivers. I clicked "Yes".
- Now the driver update process started. After round about 1 minute I got automaticly access again to my keyboard and mouse, which were still connected to the Intel USB 3.0 ports.
At the same time I got this result:
- I clicked onto the "Finish" button and rebooted.
- After having rebooted I checked the in-use driver of all 3 USB 3.0 devices.
These were the results:
My conclusion:
- Zwulf's method works for me and is absolutely easy to use.
- For "normal" desktop systems with an on-board Intel USB 3.0 Controller it seems to be very safe.
- There is no need to move the input devices to any non-Intel USB ports.
@Zwulf :
Thank you very much for your xml code and the description of the procedure!
Receiving such results means that it is not a mandatory - to update Controller drivers with force option (i.e. have disk option in Device manager), right?
The installation has been forced by Zwulf’s code of the XML file.
I did not look at his text of xml-file. I was hardwired to forced installation for controller and not-forced - for hub, so I did not offer this to try.
Ok, so we can abandon script file then?
We need more test results before we can decide this. Maybe we will need your script for problematic (Mobile) systems.
@all:
For those, I want to test Zwulf’s method, I have attached an already prepared driverpack, which will be usable with Win8.1 x64 and Win10 x64.
It contains my mod+signed 64bit Intel USB 3.0 drivers v5.0.1.38 with Zwulf’s DPInst.xml file.
The driver installation can be done by simply doing a right click onto the DPInst64.exe and choosing the option "Run as Administrator".
Good luck!
EDIT: The attached driverpack has been removed, because now the download links to both (32bit and 64bit) DPInst Sets with the mod+signed Intel USB 3.0/3.1 drivers are available within the start post of this thread.
@ all:
Today I have good news for users of my mod+signed drivers!
Our Forum member Zwulf found and documented yesterday a method, which will make it much easier for you to get my mod+signed USB 3.0/3.1 drivers installed (look >here<).
It will be done automaticly by using an MS tool named DPInst. This method seems to work even with systems, which don’t have any non-Intel USB port.
For further details please look into the start post of this thread and read the content of the completely updated chapter “Modded Intel USB 3.0/3.1 Drivers”.
Maybe I will offer in the near future this new option to get my mod+signed drivers automaticly installed for all my modded drivers (big advantage: No “Have Disk” button usage required anymore).
Update of the Start Post
Changelog:
- new: 32/64bit DPInst Sets with Intel USB 3.0/3.1 Drivers v5.0.1.38 mod+signed by me (created at 01/27/2017)
- new: Guide about how to use the DPInst install method
- completely reorganized: Section "Modded Intel USB 3.0/3.1 Drivers"
Good luck with the automatic installation of my mod+signed Intel USB drivers!
Dieter (alias Fernando)