Making slipstreamed Windows 7 AIO multilanguage with updates

[todda7]

Hello.

I'm trying to make an ISO containing all Windows 7 versions (32 and 64-bit, Starter to Ultimate) and with the latest updates slipstreamed.

Including languages is easy using DISM. I have to do it for each version (index:1 -> index:5).

However, this becomes a problem when I'm trying to include hundreds of packages, as I have to do it for index:1, index:2, ..-> index:5 both for 32- and 64-bit.

Why do I have to include the updates for ALL versions?

Can I get around this problem using vLite?

Edited June 26, 2010 by todda7

[untermensch]

Hello.

I'm trying to make an ISO containing all Windows 7 versions (32 and 64-bit, Starter to Ultimate) and with the latest updates slipstreamed.

Including languages is easy using DISM. I have to do it for each version (index:1 -> index:5).

However, this becomes a problem when I'm trying to include hundreds of packages, as I have to do it for index:1, index:2, ..-> index:5 both for 32- and 64-bit.

Why do I have to include the updates for ALL versions?

Can I get around this problem using vLite?

I wrote a script to do this, it's primary purpose was to "pre-activate" a Windows 7 install DVD but it grew to also install drivers, updates, setup background customization

and a few more things.

[link removed]

updated the scripts on 07/06/2010 a little more user friendly now.

Edited July 7, 2010 by cluberti
warez - link removed

[urie]

Hello.

I'm trying to make an ISO containing all Windows 7 versions (32 and 64-bit, Starter to Ultimate) and with the latest updates slipstreamed.

Including languages is easy using DISM. I have to do it for each version (index:1 -> index:5).

However, this becomes a problem when I'm trying to include hundreds of packages, as I have to do it for index:1, index:2, ..-> index:5 both for 32- and 64-bit.

Why do I have to include the updates for ALL versions?

Can I get around this problem using vLite?

I wrote a script to do this, it's primary purpose was to "pre-activate" a Windows 7 install DVD but it grew to also install drivers, updates, setup background customization

and a few more things.

[link removed]

Is this not the preactivation kit from MDL.

[grabben]

So it seems

There some scripts here to integrate updates and other things..

[untermensch]

Hello.

I'm trying to make an ISO containing all Windows 7 versions (32 and 64-bit, Starter to Ultimate) and with the latest updates slipstreamed.

Including languages is easy using DISM. I have to do it for each version (index:1 -> index:5).

However, this becomes a problem when I'm trying to include hundreds of packages, as I have to do it for index:1, index:2, ..-> index:5 both for 32- and 64-bit.

Why do I have to include the updates for ALL versions?

Can I get around this problem using vLite?

I wrote a script to do this, it's primary purpose was to "pre-activate" a Windows 7 install DVD but it grew to also install drivers, updates, setup background customization

and a few more things.

Is this not the preactivation kit from MDL.

yes this is the preactivation kit I posted on MDL

there is no way to get around updating each and every edition in install.wim but with the scripts

you can do something else for the hour it will take to get the job done.

Edited July 7, 2010 by untermensch

[cluberti]

From the readme in the downloaded (link removed) zip file, emphasis mine:

[introduction]

this pre-activation kit is appropriate for systems with

a BIOS mod or systems that require a bootloader to activate.

when the script runs it first checks if the system is activated

if not it installs a certificate for the OEM present in the BIOS

then checks if the system activated, if not then installs a

bootloader with an Acer SLIC and installs an Acer certificate

then reboots the system.

note: bootloader is zsmin v0.97, keys are installed with DISM

After reviewing the contents of the pack, while it would be fine on an actual OEM system, the installation of the WindSLIC bootloader (aka a variant of the "paradox crack" bootloader and SLIC pre-activation key method) on non-OEM systems to bypass activation is a rules violation (1.a ).

Second, the pack includes .torrent links to download Windows ISOs themselves as well as links to downloading MS patches and hotfixes from a location other than Microsoft, which would also be a violation of forum rules (1.b ).

Last but not least, it's also redistribution of Microsoft files originally found in the WAIK, which is also a violation of forum rules (1.b ). There are other things in here of questionable validity as well, but given this is already at three strikes, the user is banned and the download link removed. If you want to warez Windows on your own time, so be it - we are not the internet police. However, we do not allow discussions of or links to such things here, as posted VERY CLEARLY in the forum rules.

[user untermensch banned].

[todda7]

I didn't have time to download nor take a look at the script, but if it's just a batch script with DISM commands then I can do without it. The whole reason for creating different versions on the same ISO is so I can have it with me on a USB stick when reinstalling the operating systems of friends, family and my own computers so I don't want nor need any pre-activation script (it would defy the purpose of having different versions on the stick so I can use legal serials which usually comes with the laptops etc.)

If it's not, then would someone with the script please tell me how it operates regarding slipstreaming updates?

Thank you for your time.

[grabben]

You could also have a offline update script that you just run from the usbstick instead of integrating updates to each version..

[cluberti]

If you use something like MDT to build the installation media, it will apply updates and hotfixes (and other msp packages) during the initial install if they apply to that OS install.