@roman-sln If you want, you dan use my mobile slipstreaming script, it uses the option /forceunsigned in its lines, that might help you.

@canonkong Please upload the drivers soon, they would be really useful to me. (the generic USB controller drivers for xp, vista, 7, 8, 8.1)

Zitat von Ten2O im Beitrag #272

---

@canonkong Please upload the drivers soon, they would be really useful to me. (the generic USB controller drivers for xp, vista, 7, 8, 8.1)

---

Z490 chipset is very similar to Z390 chipset in shape. Device ID(Z490's USB 3.1 xHCI Host Controller) is probably 06ED.

Z490
https://www.xfastest.com/thread-240614-1-1.html
Z390
https://www.xfastest.com/thread-223309-1-1.html
Z370
https://www.xfastest.com/thread-201075-1-2.html

Hello everyone, I have a project simplix.info/win7usb3 for installing USB drivers under Win7 (please use a translator if necessary). It can integrate drivers into the system distribution, or install from WinPE into a working system, or simply install drivers on a working system. Here, the installation is not using Dism, because some versions of Intel drivers conflict with each other, instead, installation takes place in a few seconds during the second stage of system installation. Prior to Win7USB3 1.5 inclusive, I used only original drivers, but now I decided to check the modified ones from this forum. The important thing is that I have a purchased certificate, so the installation of a modified driver occurs without warning.

Win7USB3 works in two stages - first, it checks what hardware is physically present, and then installs only those drivers that are needed. If the HWID is present in several versions of the drivers, then a newer one is selected. The problem is that in the modified drivers there are HWID's, which are also in the official drivers. I have a few questions for @canonkong before I put Win7USB3 2.0 in public access:

AMD:
PCI\VEN_10DE&CC_0C0330 ;Doesn't match AMD manufacturer
PCI\VEN_1022&DEV_13ED
PCI\VEN_1022&DEV_13EE
PCI\VEN_1022&DEV_145C ;Already present in v2.0.0.60
PCI\VEN_1022&DEV_145F ;Already present in v2.0.0.60
PCI\VEN_1022&DEV_148C
PCI\VEN_1022&DEV_149C
PCI\VEN_1022&DEV_15D4
PCI\VEN_1022&DEV_15D5
PCI\VEN_1022&DEV_15E0 ;Already present in v1.0.0.12
PCI\VEN_1022&DEV_15E1 ;Already present in v1.0.0.12
PCI\VEN_1022&DEV_15E5 ;Already present in v1.0.0.12
PCI\VEN_1022&DEV_1639
 
Intel:
PCI\VEN_8086&DEV_A36D
PCI\VEN_8086&DEV_A36D&REV_10 ;Superfluous?
PCI\VEN_8086&DEV_A36D&CC_0C03 ;Superfluous?
PCI\VEN_8086&DEV_9DED
PCI\VEN_8086&DEV_31A8
PCI\VEN_8086&DEV_A1AF ;Already present in v5.0.4.43
 

Lines with comments are now excluded from the search, indicating the reasons, namely:
1) "Already present" means that instead of the modified one, the original driver of the specified version will be installed.
2) "Does not match the manufacturer" - I did not understand the criterion for adding VEN_10DE to the driver with VEN_1022, stability is questionable.
3) "Superfluous?" - I did not understand the point of adding REV_10 and CC_0C03 when they contain DEV_A36D, which is already represented as a separate line.

One member of my forum has already successfully installed a test version with hardware VEN_8086&DEV_A36D. If you want to test it, write the result of the devcon command on your motherboard:

devcon find "PCI\*"
 

Hi simplix and welcome. A pleasure seeing you around here.

I will try to answer your questions:

1. If you have access to a nice SPC to resign, you're in control. Removing/commentting out officially supported devices from INF won't impact the mod. However note that the Intel device list in your post was used in the old "unsigned" (actually not timestamped) version of the mod offered in OP. Last version offered there was the SHA2-signed (and properly timestamped) which contained only the following devices:

PCI\VEN_8086&CC_0C03
PCI\VEN_8086&CC_0C0330
 

as suggested in OP to avoid using any specific DEV ID and be more "future-proof". But as I said, if you can resign, just offer only actual, requested devices on INF, so driver fit your installation approach.

2. canonkong found that this AMD driver can handle USB-C controller present in recent Nvidia cards, hence allowing Win7 support for it. I've not personally confirmed this because I lack the required hardware. Note the device entry follows the same generic approach used for Intel PCI\VEN_8086&CC_0C0330.

3. Redundant entries, yes. Can be removed.

Regarding devcon, just note it's not a built-in Windows tool (at least on Windows 7). It comes from WDK/EWDK/SDK or other developer-aimed kits.

where to download ,thanks~

Hi! I lost the files and now I need them again. But i can't find a DL link.


Can someone share by PM? thanks!

My system is Z390 + coffee lake. Just restored from Clonezilla working old backup but now my mouse is kaputt :(

Thanks, Reducer. I decided not to add the extra lines that I commented on above. I believe that it is not safe to add an unofficial driver for any device, so now I have limited myself to the following lines:

AMD:
PCI\VEN_1022&DEV_13ED
PCI\VEN_1022&DEV_13EE
PCI\VEN_1022&DEV_148C
PCI\VEN_1022&DEV_149C
PCI\VEN_1022&DEV_15D4
PCI\VEN_1022&DEV_15D5
PCI\VEN_1022&DEV_1639
 
Intel:
PCI\VEN_8086&DEV_A36D
PCI\VEN_8086&DEV_9DED
PCI\VEN_8086&DEV_31A8
 

No problem adding new HWID's after verification. The new version of Win7USB3 2.0 is already available.

Hi PatrickK,

I installed your deWin7x64_Pro_SP2.10.iso and it works very good.
Now I tried your slipstreaming script en mobile slipstreaming x64 v1.1.zip
on en_windows_7_professional_with_sp1_x64_dvd_u_676939.iso.
Your batch file looks very well written! But it produces errors during this statement:
dism\dism /image:mount /add-driver /driver:DriverSP2.9\x64 /recurse /forceunsigned
Error message:

Zitat

---

Installing 1 of 52 - C:\Users\Admin\iso\DriverSP2.9\x64\Atheros\win7-10.0.0.336-whql\netathrx.inf: Error - An error occurred. The driver package could not be installed.
For more information, check for log files in the <windir>\inf folder of the target image.
<and so on for the next 51 packages>
Error: 5
The command completed with errors. For more information, refer to the log file.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

---

Extract from C:\Windows\Logs\DISM\dism.log:

Zitat

---

2020-05-14 22:59:32, Info DISM DISM Driver Manager: PID=14356 Driver C:\Users\Admin\iso\DriverSP2.9\x64\USB3\Texas Instruments USB 3.0 Drivers v1.16.6.0 WHQL\tihub3.inf is boot-critical. - CDriverPackage::FillInPackageDetails
2020-05-14 22:59:32, Info IsDriverPackageSigned: File [C:\Users\Admin\iso\DriverSP2.9\x64\USB3\Texas Instruments USB 3.0 Drivers v1.16.6.0 WHQL\tihub3.inf] is signed by a catalog [C:\Users\Admin\iso\DriverSP2.9\x64\USB3\Texas Instruments USB 3.0 Drivers v1.16.6.0 WHQL\tihub3.cat]
2020-05-14 22:59:32, Info DISM DISM Driver Manager: PID=14356 Signature status of driver C:\Users\Admin\iso\DriverSP2.9\x64\USB3\Texas Instruments USB 3.0 Drivers v1.16.6.0 WHQL\tihub3.inf is: SIGNED - CDriverPackage::InitSignatureStatus
2020-05-14 22:59:32, Info DISM DISM Driver Manager: PID=14356 Driver C:\Users\Admin\iso\DriverSP2.9\x64\USB3\Texas Instruments USB 3.0 Drivers v1.16.6.0 WHQL\tixhci.inf is boot-critical. - CDriverPackage::FillInPackageDetails
2020-05-14 22:59:32, Info IsDriverPackageSigned: File [C:\Users\Admin\iso\DriverSP2.9\x64\USB3\Texas Instruments USB 3.0 Drivers v1.16.6.0 WHQL\tixhci.inf] is signed by a catalog [C:\Users\Admin\iso\DriverSP2.9\x64\USB3\Texas Instruments USB 3.0 Drivers v1.16.6.0 WHQL\tixhci.cat]
2020-05-14 22:59:32, Info DISM DISM Driver Manager: PID=14356 Signature status of driver C:\Users\Admin\iso\DriverSP2.9\x64\USB3\Texas Instruments USB 3.0 Drivers v1.16.6.0 WHQL\tixhci.inf is: SIGNED - CDriverPackage::InitSignatureStatus
2020-05-14 22:59:32, Error DISM DISM Driver Manager: PID=14356 Failed to install the driver package 'C:\Users\Admin\iso\DriverSP2.9\x64\Atheros\win7-10.0.0.336-whql\netathrx.inf'. - CDmiDriverStore::Import(hr:0x80070005)
2020-05-14 22:59:32, Error DISM DISM Driver Manager: PID=14356 Failed to install the driver package 'C:\Users\Admin\iso\DriverSP2.9\x64\Atheros\win7-10.0.0.336-whql\netathrx.inf'. - CDriverPackage::InternalInstall(hr:0x80070005)
2020-05-14 22:59:32, Error DISM DISM Driver Manager: PID=14356 d:\w7rtm\base\ntsetup\opktools\dism\providers\dmiprovider\dll\driverpackage.cpp:433 - CDriverPackage::Install(hr:0x80070005)
2020-05-14 22:59:32, Info DISM DISM Driver Manager: PID=14356 Driver package C:\Users\Admin\iso\DriverSP2.9\x64\Atheros\win7-10.0.0.336-whql\netathrx.inf failed to install. (hr:0x80070005). - CDriverManager::AddDriverPackagesFromCollection
<and so on>

---

Could you please have a look? If you need more info please tell me.

@StartMeUp Wow, I am surprised, thank you for your compliment on my batch file, nice to read that, especially because you write it bold. Do you have a job or a hobby that has something to do with scripting ?
Ok, my first guess is to ask you if you run the script as administrator ?

Hi PatrickK,
thanks for your reply. I do scripting for a job, mainly using PowerShell and Python.
Yes, I ran your script with admin rights - and I read your readme file :)

@StartMeUp Cool, that makes your complement even better for me :-)
Good that you read it.
Did you notice the errir code hr:0x80070005 ? I suggest that you google that and see if you did some 'mods' on you Windows installation.
I am not really into reading log files, usually I google the error code and try what works if I think I have enough information.
Typical questions/thoughts/ideas/standard questions:

What hardware are you using?
Do you have some kind of so called 'antivirus software' installed ? If yes I recommend to uninstall it anyways.
Did you run a sfc -scannow in cmd ?
Is your RAM ok ? How about memtest86 booted from a usb flash drive, that's the way I do it before I really start to play around with a computer. (You wouldn't need to run the entire test, usually, but not alway, the ram errors occur a couple second after starting the software.

.> Did you notice the errir code hr:0x80070005 ? I suggest that you google that and see if you did some 'mods' on you Windows installation.
I already did, but until now I did not find anything useful on the web for this kind of error.

.> Typical questions/thoughts/ideas/standard questions: ...
I don't think answering these questions will help: read on :)

I made some progress: I modified your "create ISO.bat" to use "de_windows_7_professional_with_sp1_x64_dvd_u_676919.iso" along with your "Treiber2.10.7z". Everything else in the batch file remained unchanged.
Guess what? The batch file WORKED flawlessly without any errors!

But, as we know, this same batch file (i.e. your original file) does NOT work with "en_windows_7_professional_with_sp1_x64_dvd_u_676939.iso" and "DriverSP2.9".
I even tried to use your batch file with a different .iso: "en_windows_7_professional_x64_dvd_x15-65805.iso" and "DriverSP2.9". Same errors.

Do you have any idea why the "de" combo works, but the "en" combo fails?



Update:
My modified "create ISO.bat" using the combo "en_windows_7_professional_with_sp1_x64_dvd_u_676939.iso" and "Treiber2.10.7z" WORKED.

Conclusion:
There must be something wrong with "DriverSP2.9", because the combo "en_windows_7_professional_with_sp1_x64_dvd_u_676939.iso" and "DriverSP2.9" does NOT work.

To superyijia, Postcard88 and others.
#205 still has the links to download...


Here are modded Intel drivers v17 from DriverStore of fresh Windows 7 Many-in-1 setup ISOs by m0nkrus - attached.
As mirror - https://www73.zippyshare.com/v/fRzWJMbw/file.html
At least they work on old DEV_ID 8C31 (no problem with USB 2.0 I wrote before) and new 9DED at first look.