Integrate7 script – automatically slipstream updates and drivers up to 11/2023!

You need to login to view this posts content.

 

Surely setupcomplete.cmd.
You should use wusa command, eg:

Code:

copy /b /y "%~dp0hotfixes\ndp48-kb5020621-%ImageArchitecture%.exe" "%~dp0DVD\Updates" >nul 2>&1
copy /b /y "%~dp0hotfixes\Win7AndW2K8R2-KB3191566-%ImageArchitecture%.msu" "%~dp0DVD\Updates" >nul 2>&1
....
echo start /w "" "%%CDROM%%\Updates\ndp48-kb5020621-%ImageArchitecture%.exe" /q /norestart>>"%~dp0DVD\sources\$oem$\$$\Setup\Scripts\SetupComplete.cmd"
echo start /w "" wusa "%%CDROM%%\Updates\Win7AndW2K8R2-KB3191566-%ImageArchitecture%.msu" /quiet /norestart>>"%~dp0DVD\sources\$oem$\$$\Setup\Scripts\SetupComplete.cmd"

should work.

 

Yes, my idea was to create CLEAN OS, not all-in-one garbage.
I have integrated only things that are absolutely necessary (ie. hotfixes, generic drivers). Without generic drives the OS wouldn't be installable at all, as it is imposible to install or boot Windows 7 on modern systems without integrated USB3 drivers and disk controller drivers.
Any other drivers could be installed later, so there is no need to integrate them.

The only exception is video driver on modern UEFI class 3 machines, as described --> here <--. because Windows 7 does not contain generic UEFI GOP video driver (ie. Microsoft Basic Display Driver, which is available on Windows 8 and later).
On these systems integrating video driver is necessary or you will have blank screen during and after install.

Telemetry and bloatware are also removed, because I am sure that almost nobody on the earth needs spies in their systems.

 

I cannot believe that I have to explain such things.

Let's take some examples.

1. Some time ago, heavily modified Windows was very popular in my country. Entire UI has been changed.
And it worked, but after updates were installed entire UI became messed up and inconsistent (half of UI were Microsoft original and half of UI were custom-made).

2. Some time ago, I downloaded modified Win10. But something were broke and driver updating from WU were not working and several other things.

3. Some people integrate unnecessary third party tools or drivers which are conflicting each other (I experienced drivers conflicts and it isn't just theory).

4. Some people makes poorly tested modifications which brakes OS consistency.

etc, etc. over-modifications which I am trying to avoid.

 

do you remember my last suggestions some days ago for which you said bla bla bla to me . now say did you succeed in installation of win7 on your hardware ?

 

The script integrates Microsoft generic NVMe drivers, so any controller should work work after installation.
BUT! Official Microsoft generic NVMe drivers for Win7 cannot be integrated to installer (ie. to boot.wim file). They simply don't work, because Microsoft has f**ked up something with them
So vendors specific NVMe drivers are integrated to installer, instead of generic ones.

This could cause issues however. If integrated vendor specific NVMe drivers doesn't cover your hardware, you will be unable to install Windows 7 on your machine.
The solution is to add your drivers to installer manually (see add_these_drivers_to_Installer folder) or use Win10 installer instead - as described here.

Alternatively, you could remove all NVMe drivers and try these generic drivers (backported from Win8) instead.

PS. Windows 7 supports IDE and AHCI out of the box, without any additional drivers needed. Only Intel Rapid Storage Technology, RAID, NVMe, etc require additional drivers.
AHCI could require vendor specific drivers however, if you want more efficient power management on some laptops.

 

You need to login to view this posts content.