OMG @PatrickK with your ISO I didn't got the repair thing!! I can't believe it! Though it keeps recognizing I have two Windows installed so I get that black screen and have to chose one, at least though I don't get to repair.

About the certification you wrote to me : "A the integration I use the option /forceunsigned" I don't understand what you mean, sorry I have very little knowledge, there is an option somewhere I missed or that's dism line? Thank you again for all your help in this thread and with your files.


edit: because I'm kind of mentally downgraded after so many hours and made the post more clear in my bad English, also I want to take back I was still getting certifications problems, nope, got rid of them too with that iso!

edit2: about the force unsingned... even if it's not a problem anymore since I used your iso, I was doing it wrong all the time with Dism command lines and I've seen too late (now that I'm editing after many hours) there is a Dism GUI, it could have been useful for me, I could have got it right with that at least xD.

[NOW SOLVED, it was something simple I was unaware] I don't know, it doesn't make sense to me, with @PatrickK iso installed there is no issue of repair anymore and it DOES recognize all the drives but I keep getting black screen after restart with 2 Windows to chose from and all my drives but one are empty, no idea why I keep getting that "double Windows" now that I can see all my drives and only one has data. At this point it's useless I take off those drives, there is nothing in them and the issue is not related to them as I initially thought.


EDIT: disabled from BIOS the Windows Boot Manager boot option and now it seems EVERYTHING WORKS! I can restart and no more black screen with double Windows and other crap

and with @PatrickK ISO I also dont get the certification freaking black screen anymore!! Damn I'm so happy I can't believe it! Thank you PatrickK you really are a gem of a user and been so helpful! I can now (after some sleep) get to the rest of this "nightmare" with all other drivers though this is huge, at least it's working and no more of those nasty problems.

THANK YOU

There is a serious mistake in "SHA256 Signed modified intel IO/USB3.1 driver 32/64bit" because of "PCI\VEN_8086&CC_0C03" line.
On old chipsets with EHCI present (dev_id 8C31, for example) driver installation makes all USB (including 2.0) unworkable.

@VK Great, sounds good to me, everything seems to work for you.
For you big thank you, you are very welcome, I am pleased by your success and you rcompliment calling me a gam. :-))
This thing with the option /forceunsigend was just for your information on how i handle unsigned driver to avoid problems with them.

Greetings from me.

Zitat von NewcomerAl im Beitrag #228

---

There is a serious mistake in "SHA256 Signed modified intel IO/USB3.1 driver 32/64bit" because of "PCI\VEN_8086&CC_0C03" line.
On old chipsets with EHCI present (dev_id 8C31, for example) driver installation makes all USB (including 2.0) unworkable.

---

Zitat von VK im Beitrag #222

---

Hi all and thank you for this thread and drivers.

I have huge problem running W7 Ultimate, my MoBo is z390 Gigabyte Aorus Master and I have no PS/2, only usb. I got all the drivers from both links by @canonkong (THANK YOU for what you did, you are truly amazing) :

---then I used NTLite to put them on ISO,
---though during the OS installation it keeps telling me the iusb3hcs.sys is not certificated.
---I then run F8 to pick "disable driver signature enforcement" and then I can complete the installation.

The problem is as soon as I restart the pc it starts with a Windows Repair process and then during the repair I get stuck and have no way to interact, no mouse or keyboard active.


This thing is driving me crazy, it's days now I'm trying to solve. I have no much experience and have no idea of Dism to force unsigned.


The setup from @aladinsinbad (thank you!) I downloaded from here seems to work perfectly, though that's W7 Professional version and I can't upgrade to my version.


Please I'm freaking desperate, if anyone has a clue or hint for my case please, it would be immensely appreciated. Sorry for my English.

---

@valcugen Thank you so much for the help, it's greatly appreciated. I have solved now thanks to @PatrickK, very skilled user who shared his iso and that's been hella awesome, especially for someone like me with little knowledge, so far everything is working and the system is absolutely stable. I'm not done yet and still installing programs and moving data, though I'm running heavy applications too and so far it's completely fine. I'm saving your post though, such clear tips and walkthrough are pure gold for me to say the least, truly, huge thanks for the help!

Do these drivers work on the B365 22nm chipset? Ive got the Biostar utility for w7 and it works but the drivers are both DriverVer=08/18/2016,5.0.0.32, can i use the drivers in post no1 instead?
According the the original post at anandtech "While Intel’s B365 PCH is a part of the 300-series chipset family, the chipset is essentially a holdover from Intel's earlier 200 series chipsets, and has much more in common with them"

Edit - i'll do a test build in a day or 2, try installing these over the top ov the biostar ones, if they install i'll try adding them to an image and see what happens.

hi
i did used - en mobile slipstreaming x64 v1.1 for integration in win7.iso and now thinkig and compatibility will this iso for z370 и only for H310/B360/H370/Q370/Z390/HM370?

@Wu-Tang You do not tell what model of motherboard you are using, but if I look, for example, at the Z370 HD3-OP (rev. 1.0), you won't need to use my script, you could use the tool that Gigabyte has put there to download, so called 'Windows USB Installation Tool', this will integrate one of the two original Intel USB3 drivers. But, at least on that model, I guess you would not have to do any modifying, because it is not needed to just install Windows 7, it is equipped with USB2.0 ports and you could use those. But, if you used my script, Windows 7 will have the right USB3 drivers 'built' into it and you would have useful updates built into it and therefore would not need to do any automatied updates in the installation (most of the updates are not helpful for Windows 7 to do its job).

sry
its - https://www.asus.com/ru/Motherboards/ROG...specifications/
yes, i did read about tools by vendors for integrate usb 3.0 into iso for install on z370 (tools by asus,giga, msi etc) but i want to use iso modded by your script to not do a lot of different iso.
i learn your project - very good, different drivers for any chips, kb for nvme and others, good job.
but i want to know list of chipsets, where i can to install my iso with integration drivers by your script?
for z390 will install modded drivers, true? and for z370/z270 etc installing orig drivers, true?

about updates, i don't use wu a long time, im use about 10 years update pack by my colleague - https://blog.simplix.info/update7/ all testing by many people - http://forum.oszone.net/thread-257198.html its the best updatepack for windows7 in my opinion

ps how to paste nickname in answer?

@Wu-Tang Thank you very much for your appreciation, this pleases me.
With this it is poosible to install on the chipsets that canonkong mentions in the title, this one and the AMD-one too.
On the very most of other chipsets modifying would not be necessary to do an installation because of the USB2.0 ports available. But with USB3 drivers the installation process is a bit faster, i like this factor everytime I install Windows 7. And it makes our lives a bit easyier, especially if it comes to networking.
Yes, on Z390 an others mentioned in the title Windows 7 will use these modded drivers, on other chip(sets) it uses other drivers. Unfortunately we need to do this, because Windows 7 never had the luck to get the native USB3 support that we know since Windows 8 from 2012, damn Micro$oft, but don't worry, here we are with our enthusiasm and knowledge baby.

In your case, Z370, Windows 7 will use one of the official Intel drivers, and another of the two from Asmedia for its Amsedia chips, the device manager will you show that.

Nice to hear that you don't use the integrated Windows update function.

You just tipe the @-sign and start to type and click on the username that you are looking for, that's it.

Good luck on your project, I would like to see a screenshot from the screen that Windows shows you if you press Windows+pause.

@PatrickK

Zitat von PatrickK im Beitrag #237

---

With this it is poosible to install on the chipsets that canonkong mentions in the title, this one and the AMD-one too.
On the very most of other chipsets modifying would not be necessary to do an installation because of the USB2.0 ports available. But with USB3 drivers the installation process is a bit faster, i like this factor everytime I install Windows 7. And it makes our lives a bit easyier, especially if it comes to networking.
Yes, on Z390 an others mentioned in the title Windows 7 will use these modded drivers, on other chip(sets) it uses other drivers. Unfortunately we need to do this, because Windows 7 never had the luck to get the native USB3 support that we know since Windows 8 from 2012, damn Micro$oft, but don't worry, here we are with our enthusiasm and knowledge baby.

---

Zitat von PatrickK im Beitrag #237

---

In your case, Z370, Windows 7 will use one of the official Intel drivers, and another of the two from Asmedia for its Amsedia chips, the device manager will you show that.

---

Zitat von PatrickK im Beitrag #237

---

Nice to hear that you don't use the integrated Windows update function.

---

Zitat von PatrickK im Beitrag #237

---

You just tipe the @-sign and start to type and click on the username that you are looking for, that's it.

---

Zitat von PatrickK im Beitrag #237

---

Good luck on your project, I would like to see a screenshot from the screen that Windows shows you if you press Windows+pause.

---

@Wu-Tang Cool, thanks for the screenshot.

What canonkong's driver does is to support chipsets that do not have official usb drivers by the manufacturer, that includes USB2 and USB3.0/3.1/3.2 ports that are provided by the chipset; it doesn't matter if USB2 or 3.x or whatever, if they are all provided by the chipset they use all the same chip and the same driver. On Z390 and 'similar' Windows 7 cannot use its built-in USB2 drivers because these USB2 ports are provided by the chipset and an other driver is required to make them to work.
For example we can take a look on an ASRock Z390M Pro4. On that model I test my Windows 7 ISOs before releasing (and others, of course), and that motherboard has 10 USB ports but in the device manager you will see just two entries in the USB section, two if I remeber correctly, and that's it, there are not like one entry for a controller and a hub for every two USB ports like it is pretty common on motherboards that use dedicated USB3 chips for its USB3 capability. More and more components are moving from dedicated chips into the chipset/CPU, nothing new.

Re post no233(mine), B365(22nm) chipset. Created another w7 test build and installed with the biostar drivers added to ntlite(having extracted them from a previous test). I extracted the signed and non signed drivers and manually updated within Device Manager, Host and Hub are now v5.0.5.55 and both are signed, great :).

@canonkong added the v5.0.5.55 signed drivers to an untouched w7 Pro 64bit iso with ntlite(boot and install wim), setup and install runs fine, mouse and kb into back panel IO usb2 ports, usb3 key in IO usb3 port. System didnt show usb3 key after logon, had to unplug and plug in for it tobe seen by the system, apart from that everything is fine so far. Please amend your OP to show the drivers work on the 22nm B365 chipset(you only state the B360). Great work and thank you for these drivers. :) If you need any hardware ID's etc, be specific what parts you want from a driver details drop down menu and i will post them.

Edit - In my opinion the smoothest method was to use the (extracted)Biostar drivers slipstreamed with NTLite then update to your drivers post logon using Device Manager.