Solved Create patched ISO from existing up-to-date installation?

[PatrickGSR94]

I have parts on order for 2 new workstations that I will be putting together soon. I dread the thought of having to continually run Windows Update multiple times from a fresh SP1 install. Being that my workstation is fully up to date, is there any way to create a fully patched ISO from my machine's installation, to use for installing Win7 on my 2 new workstations? This is an office environment with a Win Server 2012 R2 domain.


I've read several how-to articles on creating patched ISO files, but most of those are at least 2 years old, and it seems like it would be easier just to use the update/hotfix files already on my workstation to create the ISO instead of having to download a bunch of files from the internet.

 

[Paul Black]

Hi PatrickGSR94,

I dread the thought of having to continually run Windows Update multiple times from a fresh SP1 install. Being that my workstation is fully up to date, is there any way to create a fully patched ISO from my machine's installation, to use for installing Win7 on my 2 new workstations?

There are a couple of ways to achieve this.

[1] SIW2 has put together an excellent utillity [7UPDATER] where you can integrate drivers and WU into the install.wim. It is quite a long thread but I think you will find it useful. It really is quite easy and you will end up with a fully updated ISO in which to use. You can update just one image, or all images. The size of the updated ISO will obviously be too big to fit onto a DVD so you will need to burn it to a USB for installation.

Here is the link to the thread I have mentioned => Update your Win 7 installation media.

[2] If you have an installation DVD, you can copy the files to the HDD, mount it, and fully update it with drivers and WU using DISM++. Again, the size of the updated ISO will obviously be too big to fit onto a DVD so you will need to burn it to a USB for installation.

DISM++ is a FREE implementation tool that has the ability to perform Windows Updates [WU]. Some of the advantages [but not all] are:

[1] The GUI is very easy to understand and use.
[2] It is much faster than M$’s WU because it uses a different engine.
[3] It downloads the latest WU DB from the M$ servers, scans your OS, and then lists the updates available.
[4] It doesn’t install superseded updates like M$ does.
[5] It gives you the option of what you want to install.
[6] The pre-ticked updates are what is recommended and are similar to the WU critical and recommended updates. The un-ticked updates are similar to the WU optional updates.

[7] It warns you if an update:

• Includes telemetry.
• Has known issues with certain hardware.
• Needs exclusive access.
• Is suspect.
• Your OS doesn't need it.
• Has any other known issues.

[8] It doesn’t require re-booting between updates.
[9] It can be used to either update an install.wim image OFFLINE, or to update the LIVE OS.

I hope this helps!

 

[samuria]

You could create a disk image and use that then change serial number after if you have imaging that multi casts you can do all ocs at once

 

[PatrickGSR94]

You could create a disk image and use that then change serial number after if you have imaging that multi casts you can do all ocs at once

Wouldn't that basically replicate my installation with software and everything? I don't want to image my current workstation's system drive, as these will be new systems for different users, with different software installed. I was just hoping to create an ISO of my current Windows installation with all the installed updates and hotfixes, instead of having to try to download certain ones but not others. My current installation is suitable for our office, so it would be nice to just replicate the updated OS, without the installed software.

 

[SIW2]

The practical way to do that is to integrate the updates into installation media.

Update your Win 7 installation media.

Wouldn't that basically replicate my installation with software and everything? I don't want to image my current workstation's system drive, as these will be new systems for different users, with different software installed. I was just hoping to create an ISO of my current Windows installation with all the installed updates and hotfixes, instead of having to try to download certain ones but not others. My current installation is suitable for our office, so it would be nice to just replicate the updated OS, without the installed software.

 

[Paul Black]

Hi PatrickGSR94,

I was just hoping to create an ISO of my current Windows installation with all the installed updates and hotfixes, instead of having to try to download certain ones but not others.

I gave you two methods of doing this in my previous post!
The first method I gave you is the same as SIW2 [the author/creator of the utility] has given you above!

 

[PatrickGSR94]

Hi PatrickGSR94,



I gave you two methods of doing this in my previous post!
The first method I gave you is the same as SIW2 [the author/creator of the utility] has given you above!

I guess I wasn't clear about what you posted. Is the utility taking the updates installed on my machine currently to create the ISO? Or is it downloading the various updates from Microsoft or elsewhere?

 

[SIW2]

I guess I wasn't clear about what you posted. Is the utility taking the updates installed on my machine currently to create the ISO? Or is it downloading the various updates from Microsoft or elsewhere?

If you had bothered to look at the post you have been linked and pointed to several times, it tells you.

 

[Paul Black]

Hi PatrickGSR94,

I guess I wasn't clear about what you posted. Is the utility taking the updates installed on my machine currently to create the ISO? Or is it downloading the various updates from Microsoft or elsewhere?

NO, the utility is not taking the updates installed on your machine currently to create the ISO.

7UPDATER gets the WU DB from a third-party provider.
DISM++ gets the WU DB from the M$ servers.

Basically, you need a Win 7 ISO or installation DVD. Then you use one of the two methods stated above to integrate the WU's. Finally, you burn the updated ISO to a USB for installation.

I, along with many people here have used both of the two methods mentioned without problems.

I hope this helps!

 

[PatrickGSR94]

If you had bothered to look at the post you have been linked and pointed to several times, it tells you.

Man come on, I skimmed it over a little bit but I don't have time right this second to read through all 14 pages. I definitely appreciate the work you've done with that tool and will probably make use of it. No need to get all worked up or pissed off about it.

 

[SIW2]

It is on the first post at the link.




There is no known method of using your currently installed updates in the way you want.

It used to be possible on Vista to utilize the cab files from software distribution folder. It can't be done that way on win7.

The download is not that big, approx 700mb, as stated in the photo.

 

[PatrickGSR94]

Thanks, that's what I needed to know. I will look into your utility for my upcoming installations.

 

[Megahertz07]

Can you give us the specs of your new workstations?
Installing win 7 on new MoBo isn't that easy as Win 7 installation disk doesn't have the needed drivers. 7UPDATER can add the drivers to Win 7 installation disk.

My suggestion (if the Workstations has same hardware)
- Add the drivers to the Win 7 installation disk using 7UPDATER.
- Do a clean install. On BIOS, disable secure boot and fast boot. On a new MB you can install as Legacy- MBR or UEFI- GPT. To install as Legacy- MBR boot the in 7 installation disk as Legacy. To install as UEFI- GPT boot the in 7 installation disk as UEFI.
- Once you have installed on one workstation and it comes to the point to enter the user name, DON'T. Enter Audit mode (can guide you on), install all drivers and updates. For the updates, use ++Dism. When done shut down and clone the disk to the other two disks. Use Macrium Software | Macrium Reflect Free or Download Free Windows Backup Software
- When you boot again, you will be back to Oobe, asking to enter the user name.

 

[PatrickGSR94]

My last workstation build (listed at bottom left) installed Win7 as normal, except I ended up having to disable UEFI on the Asus mobo after the installation. New builds are as follows:


ASUS Prime H370M LGA1151 (300 Series)
Core i7-8700 Coffee Lake 6-core 3.2 GHz
Crucial MX500 500 GB SSD
G.SKILL Ripjaws V DDR4 32 GB total
GTX 1050 Ti 4GB GDDR5

 

[Megahertz07]

Some Coffee Lake chipsets doesn't have USB 3.x drivers for win 7. Don't know if it's the case of H370M.
SIW2 is the expert and will guide you.

 

[PatrickGSR94]

The mobo has 2x USB 2.0 ports in addition to the 3.0 and 3.1 ports, so I can run KB/mouse off of those. I don't recall any issues getting the USB 3.x ports on my last build to work in Win7, as it also has 2.0 ports on the rear panel.

 

[Megahertz07]

M$ is trying to kill Win 7. And Intel joined M$ making it hard to install Win 7 on a new MB.
Z, H and B 97 were the last chipsets that you could install Win 7 without adding drivers. It's COMPLETELY different on a Coffee Lake MB.
Even if you have USB 2.0, if the hardware is the H370M they won't work on Win 7, unless there is a driver for it.

Not sure if there is a win 7 driver for GTX 1050 Ti (it does for the GTX 1050)
NVIDIA DRIVERS GeForce Game Ready Driver WHQL

 

[PatrickGSR94]

well that sucks, I've been reluctant to move to 10 because of all the telemetry stuff on it. I already ordered 2 licenses of Win7 through Newegg, should I try to return them and go Win 10 Pro?

 

[Paul Black]

Hi PatrickGSR94,

well that sucks, I've been reluctant to move to 10 because of all the telemetry stuff on it. I already ordered 2 licenses of Win7 through Newegg, should I try to return them and go Win 10 Pro?

Only you can answer that. It depends what the office strategy is!

 

[PatrickGSR94]

Well I don't really care to deal with trying to force an unsupported OS to work on a newer proc/mobo.


I guess what I meant was, try to return the Win7 licenses (if Newegg will even do that) and get Win10 Pro licenses, or try to install/activate Win7 and then do Win10 upgrades. At this point I'm not sure what will be more cost effective.