Most of your drivers can be downloaded on intel.com, I cant post links. But you can search for
"Intel® Management Engine Driver for Windows 7"
For Network "Intel® Network Adapter Driver for Windows 7 (Version: 25.0 )" or "Intel® Ethernet Adapter Complete Driver Pack Version: 25.0"
Test Intel RST drivers from the v17 platform or v18 platform there is a thread on this forum
Unsure what usb that will work have you tested Intel USB Controller 3.1 Driver 17.2.70.3
and 3.0 5.0.4.43_v2?
you can search on Intel.com for "z390" to find drivers that work for your motherbord
Hi!
Can you please send me a working link to download drivers?
Thank you,
Alex
I recall, it was three - another one besides KB2990941 and KB3087873. But maybe I recall it wrong and there are indeed only 2 NVMe hotfixes - I’ll check it out again…
AZ
I now know, which one the 3rd NVMe-Hotfix is: KB2908783
Stop Errors While Going into Hibernation on NVMe Drives with Windows 7
However, it might not be necessary or mandatory or even f*** things up - could that be the case in my actual problem? And did you read Post #391 ? You haven’t commented it yet…
AZ
thanks
[/quote]
However, it might not be necessary or mandatory or even f*** things up - could that be the case in my actual problem? And did you read Post #391 ? You haven’t commented it yet…
AZ[/quote]
Do you ask me ? What’s your question ?
Please read my Post #391! You wrote, that you integrated the drivers/hotfixes via batch file - in my post #391, I wrote that I integrated them in a different way (not via batch file/script!). Please comment that.
And please comment this
Thanks,
AZ
I followed very closely some posts on USB 3.0/3.1 drivers install on windows 7 environment, tried most of the solutions i found online but none seemed to do the job.
I would really appreciate some help on this one please. I have purchased 2 identical setups :I5-10400 comet lake processor, Intel H410M motherboards and cant manage to install Windows 7, and in an installed machine with windows 7 i can’t install the usb drivers.
The Hardware ID is:
PCI\VEN_8086&DEV_A3AF&CC_0C03
I tried adding a bunch of USB 3.0 and 3.1 drivers to windows installation media, tried some Gigabyte and MSI tools to add USB and NVMe also,
In the installed PC i tried original and modified drivers from here… but still no luck!.
Really needing your help on this one, any clues?
Thank you very much in advance,
Ricardo.
@AbsoluteZero Ok, in #391 I can comment first that thank you for mentioning that third NVMe hotfix and second, I don’t know what you exactly did and therefore I can’t say anything particular on that.
I recommend too to integrate the the one or both or all three official NVMe hotfixes into the indexes of the boot.wim file and not to integrate drivers, NVMe has just to work not to perform as good as possible with, maybe, some negative impacts on its realibility, really not worth it. Personally, I don’t integrate Samsung’s or other manufacturer’s NVMe drivers into the boot.wim and/or the install.wim indexes, I don’t want to have any negativ eimpact on the reliability, I once had that, with, I think it was a card reader driver, which fucked up the installation process, and it’s not a big deal to look up the manufacturers drivers and install them. MS’ NVMe drivers do theri job, EXCEPT in regards of the not-provided SMART-data from what I have seen.
I don’t want to go through every line of your code, but let me give you a hint on a thing I had some trouble with: One of the NVMe integration procedures needs a xcopy-command at a certain point, otherwise you get the error with the ‘missing’ driver, altought this ‘missing’ drivers is not the problem in every case, but the error message is the same.
I don’t know exactly where this xcopy-command has to be, just look at my own batch files or lookup the official instructions for integrating those NVMe hotfixes. (In the official instructions this command is not there as a line of code but as a written sentence, that’s why it took me some visits on this site to notice this damn important copy-step.
I hope this is useful for everyone, greetings from Switzerland.
Hey PatrickK,
Thanks for your response and sorry for my delayed response! (I’m constantly busy in the last days…)
Did you mean this step? (xcopy command is highlighted in bold letters)
Ratgeber: HP Desktop, Notebook und Workstation - Manuelle Installation eines Windows 7-Betriebssystems auf NVMe und Leistung
(for the english version of this article, you have to change country/language on HP website, but I couldn’t accomplish that despite multiple attempts… sorry!)
AZ
@AbsoluteZero No problem, I am busy too with my other, more important hobbies and my boring job.
Yes, the purpose is the same.
Greetings Patrick
As to my problem with Fernando USB3.0 drivers. I have two laptops Asus G751jy and Asus G752vy. And drivers 5.0.3.42 and 5.0…43 will install fine on G752vy but will refuse to do so on G751jy with error of not beeing digitaly signed. I think security keys for secure boot play a role in this. I tried to disable secure boot but it does not help, somehow Win10 reads the keys anyway. I tried deleting them without the platform key, but then Win10 refuses to boot. So I see no solution to this other that exchanging the keys in bios.
Hey,
I finally could create a functioning Win7 install image with M$'s NVMe Hotfixes and the Z390 USB Drivers (that tutorial with the "xcopy" step seemed to do the trick) - many, many Thanks for your help!
The installation process itself was flawlessly successful, but after rebooting, Win7 Setup fails to boot with the error code 0xc000000e ! Could that have something to do with the NVMe Hotfixes or even with the integrated Z390 Drivers?? CSM was enabed during installation and W10 was/is already installed BEFORE installing W7 !
AZ
Hy AZ, very cool.
I did a quick google search.
Did you delete every partition before you continued with the installation ?
So, my assumption is true? I have to install Win7 first and only then (after that) install Win10? My suspicion is, that the Win10 bootloader (I guess, it’s called winload.efi ?) is causing the trouble. I forgot to mention one thing, though: if I go to BIOS first and THEN exit BIOS to boot Win7, Windows 7 boots with success (I could already start installing all drivers), but after a restart, the problem (0xc000000e) occurs again - so, after every restart or power-on, I have to go to BIOS menu first and then exit it in order to successfully boot Win7. A weird problem, really…
AZ
I suggest this because I sometimes see that people try to install Windows into already created partitions.
I trued it a couple months ago and it worked to install Windumb 10 and after that Windows 7, maybe MS changed something, I don’t know.
Did you install both OS’ with the same CSM and MBR/GPT settings ?
@PatrickK
First off, thank you for helping people out that do not want to be poisoned by the Windows 10 virus. So on to it…
My system:
=======
CPU - i9900K
Motherboard - ASUS WS Z390 Pro
Harddrive - 2TB Crucial MX500 SSD (SATA)
1_) - Win 7 Creation
=============
I created a bootable Windows 7 image, using Rufus and your: enWin7x64_Pro_SP2.10 ISO, from 6/23/2020.
RUFUS Settings:
Partition Scheme - MBR
Target System - BIOS (or UEFI-CSM)
Use Rufus MBR with BIOS ID - Checked
File System - NTFS
2_) - BIOS Settings
============
-I enabled UEFI with CSM
-Legacy Boot only for Drives
-Disabled Secure boot
-Legacy USB Support - Enabled
-XHCI Hand-off - Enabled (For USB 3.0/3.1)
3_) - Win 7 Install
============
-Inserted the bootable Win 7 OS; using a USB 3.0 drive; within a USB 3.1 slot. (The mouse and keyboard worked the entire time.)
-I installed Windows 7 on a blank 2TB SATA SSD.
-The entire install process was about 5 minutes; the fastest install of Win 7 I have ever seen.
-The System Boots in about 7 seconds.
-No errors at all.
Now, when I started to install things, I ran into a problem where I could not apply a regedit script file. I get error:
"Cannot import __________
You can only import binary registry files from within the registry editor."
I never had this problem after a Win 7 install. And I’m not sure on how to correct it.
Hy @Freeza .
Thanks for your question, your comment is a prototype of a comment and how it is supposed to ask a question in this thread, my compliment.
I think it is the best of you post a screenshot of you error message.
I did some changes in the registry to my ISOs from this release on which, I think, are useful for everyone, for example to display the filetypes by default, I hope this is not the problem in your case.
Greetings Patrick
@PatrickK
Thank you for replying. It was my mistake, the file was not an actual registry file. I tried an actual regedit script file, and it worked without issue. So nevermind that.
However, I originally wanted to create my own Win 7 Ultimate ISO, but after weeks of reading multiple forums, watching many videos, it was overwhelming and I narrowed it down to using your ISO, as you seem to really know what you’re doing.
The fact that you selectively choose which Windows updates to install is important to me. Because I never install Windows 7 updates unless a program is asking for it or if it’s critical; I don’t want any Microsoft backdoors. I still have to research the Windows updates that you applied, but from what I’ve read from your post on the German forum, I felt confident in your selective decisions.
I also noticed you have a lot of different sizes for the ISO’s. I downloaded your deWin7x64_Ulti_SP2.10 ISO, since I really wanted Ultimate version. I assume it is in German, and I was going to change it to English during the install, but I just went with your updated Win 7 PRO English ISO.
And not that it’s a big deal, but I do actually like the Windows Desktop Preview being enabled. 
Hy @Freeza .
Yes, nevermind.
It is really nice for me to read your comment, it’s a good feeling to be understood; yes, I selected everey single update, which means I looked up everyone and decided if it’s useful or rahter not. The reason is that I don’t want to have a bloated ISO and OS installation or microsoft telemetry things or similiar, altought that startet with XP, but I try to keep the level low.
Yes, there are different sizes, depending on the architecture and if it’s the N version, which means without some media accessories. I think that, compared with others, I am pretty good at keeping sizes small, not only because I use a script to create my ISOs and not a virtual installation, but also because I extract the install.wim to a separate partition and capture it again, that reduces the size even more.
And not to forget my slim edition Windows 7, the trick is the same, but I exclude some of the largest folder in the ‘legendary’ winsxs folder.
And I, in the x64 ISOs, disable on of the two stand by modes and set the default size of the pagefile to 16MB, that saves some GBs in a done Windows installation.
Greetings Patrick