• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

++ Windows 7 + Service Pack 1 Slipstream Guide

M

Makaveli@BETA

2[H]4U
Joined
Mar 24, 2004
Messages
2,433
As some of you may know Service Pack 1 for Windows 7 has been leaked before offical release. I decided to grab a copy of the service pack and give it a run on an old unpatched build of windows 7. Happy to say the install was quick and I had no BSOD's or anything weird happen. I then decided to Slipstream the service pack into my original ISO and these are the steps I followed.

What you will need:

A. Your Windows 7 DVD or an ISO image.

B. Service pack 1 for Windows 7
http://www.softpedia.com/progDownload/Windows-7-Service-Pack-1-Download-163177.html

C. RT 7 lite (App that will integrate SP+ISO)
http://www.rt7lite.com/ (Make sure you download Beta version 2.6)

D. Hard drive space to dump image 3-4GB's

E. alittle bit of time 45mins roughly ( estimated its based on your hardware speed )

Ok so with everything covered on the list you are now ready to begin.


With RT7 Lite installed.



1. Click Browse button to browse to the Windows 7 installation ISO file or setup folder. Next you will see the extracting Image screen up this may take awhile.


2. Once the process is completed, you will then be prompted at this screen make sure you check off Slipstream service pack



** if you have an AIO version you will see this instead and you must choose.



Uploaded with ImageShack.us
3. Service Pack Slipstream window will open just browse to the location of the service pack.



4. Hit Start and wait a few mins until it says Proceed then click on Proceed

5. Once completed select Task tab in upper left corner and check off ISO Bootable then switch to ISO Bootable tab.



6. Now you can select how to create the ISO. Once you have options configured to your desire. Hit Make ISO towards the bottom and you are done.




Good Luck.
 
Last edited:
Can you do this with a modified ISO missing the EI.cfg file? So you'd have all the versions slipstreamed with SP1?
 
That is a very good question.

And i'm not sure it would work because the application does ask for which version of the OS you want to update.

I would need someone to follow the steps and test it with an ISO image missing the ei.cfg file.
 
I could if you give me a few days, maybe this weekend when I have some time I'll try that out. Maybe you could take an Ultimate image, slipstream it, THEN take out the EI file. Hmmm... that actually probably would work...

EDIT: I have both x86 and x64 discs made with the EI file taken out. I'll test it here later this week/next week.
 
Last edited:
I did this about a week ago on a test drive and it worked flawlessly. After starting up the PC with SP1 integrated and hitting WU, no updates were available.
 
Did this yesterday, but so much for 45 minutes: on this old ThinkPad T60 Core Duo T7250 w/1.5GB of RAM and a 5400 rpm drive it took about 2.5 hours to get the damned integration done and an ISO created. :D

Anyway, after hitting Windows Update the only updates were drivers, which was to be expected. There's no build number on the Desktop so it's pretty safe to assume this could be the finished product unless the testing that's still ongoing turns something up.

The one thing I noted after a fresh clean install of Windows 7 Pro x86 SP1 (integrated, from the ISO I had just made) is that the final installation is smaller by about 2GB overall than a regular non-SP1 installation is. A bit weird but, hey, whatever. ;)
 
Joe Average said:
The one thing I noted after a fresh clean install of Windows 7 Pro x86 SP1 (integrated, from the ISO I had just made) is that the final installation is smaller by about 2GB overall than a regular non-SP1 installation is. A bit weird but, hey, whatever. ;)
Click to expand...

That has to do with superseded updates/winsxs folder.
 
You are probably right staknhalo but I do also believe the speed of the machine and HD is a big factor.
 
I think staknhalo means that the reason I noted the difference in size was related to the WinSxS folder where Windows 7 (and Vista) keeps multiple copies of updates, drivers, etc.

My point (just to clarify) was that if I do a clean install of Windows 7 Pro x86 (using the RTM version) on this ThinkPad T60 I have, it'll be 10.2GB after the installation is done, before I install anything and before I hit Windows Update - that's the OS itself, not counting the page file or the hibernation file (which I disable). It also doesn't count System Restore and restore points because I disable that and delete them as well. I've done it so many times for testing purposes that I know almost to the bytes how much space the OS takes.

Now, contrast that with the RTM + SP1 integrated install I did: same system, same situation, only the integrated OS being the difference, that 10.2GB installation shrank to 8.3GB - that's a big chunk of space and a considerable drop that I caught. I've seen other people make note of it as well on other forums discussing SP1.

This isn't meaning that I installed RTM then installed SP1 on top of it, this is a clean install of my freshly created Windows 7 Professional Service Pack 1 x86 integrated DVD.

Nearly 2GB shaved off a clean install... that's pretty impressive stuff indeed. ;) And I'll admit I was tempted to try and remove some additional stuff using RT Seven Lite but decided nope, that would be ironically contradictory considering I'm the guy that started the whole Leave it alone thing a few years back. :p
 
ah my bad thought he was just referring to the time for completion.

Glad it worked out for you cause windows update is a PITA on a fresh install :)

Now if we could only get one of the mods to make this a sticky....
 
Not sure it'll get to that point without a lot more people participating, and since SP1 still isn't "official" - even if what we're currently using is the final build that Microsoft will be distributing sometime soon - this is effectively considered one big beta project for all the parties involved.

We'll see what happens... guess I should have made a 64 bit ISO while I was at it, but I'm not running Windows 7 Pro x64 at the moment to be able to create one. Bleh.
 
That is a good point.

Is the offical release still slated for March?

And yes not being able to create a 64bit slipstream while on a 32bit OS will be an issue for some.
 
It's expected in March, on Windows Update, but it might be available on Technet/MSDN a few weeks prior.
 
Have you seen any major improvements in the SP? Not really sure what is being changed or fixed.
 
There are no feature changes in SP1 for clients, for Server 2008 R2 it adds RemoteFX and Dymanic memory. The main advantage is it bundles all the updates till now.

I'm waiting for the integrated iso to leak (or show up on msdn).
 
People are under this impression that a service pack does something extraordinary and it doesn't. The primary reason for a service pack is to provide Admins and such with a single installable "file" that's actually just all the patches released by Windows Update prior to the previous one, or in the case of Service Pack 1, it's a collection of every patch and hotfix released on Windows Update since Windows 7 was released/RTM status.

The benefit for me is that now I've created an x86 SP1 integrated disc, I can do the install and don't have to spend 30 mins to an hour or longer (if that much) "hitting" Windows Update after I do the installation, that's about it really.

If you took every patch/hotfix that's on Windows Update for Windows 7 (and of course Windows Server 2008 since they share a codebase) and rolled it up in one file, that's what Service Pack 1 is...

As for improvements, well, it does seem a bit snappier. I did one of my simple benchmarks (command line version of Geekbench32 from years ago) and got 9% higher scores than the RTM build but, that could be a fluke overall since I didn't do a series of runs then average it out for the best score). The OS seems fairly snappy, maybe a bit more responsive than the previous install I just wiped to do this, but then again a fresh clean install always has that kind of snappy responsiveness. The old install was barely 37 days old...
 
And as mentioned before, due to the horrible design of WinSxs, a fresh install of an integrated iso (integrated with a SP or individual patches) will take up less space and likely be faster than applying the patches manually. Once a component is in the OS, Windows will never get rid of it, which is why the component cache keeps growing without bounds and why an integrated iso is better since the pathces update a lot of system dll's.
 
One thing I noticed about SP1 is regardless of if you simply install it or you slipstream and clean install, on the first boot after install, you get a .net optimization service that runs for about 15-20 minutes and uses a bit of CPU cycles. After it's finished and you reboot, you still get the .net optimization service but it's not hogging all of the CPU anymore.
 
Tried this and it worked, though the slipstream process was kinda slow, took like 40 minutes but I'm glad I now have an ISO file that has SP1 slipstreamed on it. Is it me or does the USB bootable does not work? I tried creating a bootable USB and it never boots up, had to use another different technique to create a bootable USB.
 
I honestly haven't tried the usb bootable in this app yet. I've always used the guide that was created by another poster in this forum and that has worked flawless for me.

I may give it a try to see if I run into your issue.
 
No problem the least I could do being a part of the [H] forum. I've learned so much on this forum over the years it has made me into a better IT guy. And we must all give back to the community which has allowed us to grow.
 
From my experience, the only fool-proof 100% reliable (meaning I've created over 100 USB sticks this way) so far of making a proper Windows 7 USB installation stick is with the Microsoft Windows 7 USB DVD Download Tool (gotta love that ridiculous name they chose). There are other methods, sure, but I've had failed file copies, unbootable media, etc - all sorts of errors from the dozen or so other ways that I've tried.

The only one that has never failed on me so far is that Microsoft tool, so it's the only one I recommend. You can find it here if you don't have it already:

http://store.microsoft.com/help/iso-tool

One issue, however:

If you're running an x86 version of Windows 7 and you're attempting to create an x64 version of the USB installation stick, that tool will complain because it's missing a file (that's on x64 versions by default). All you have to do is this to resolve it:

- open the Windows 7 x64 ISO you're using as the source for the USB stick - you don't have to extract the whole ISO, just open it with a tool like UltraISO or WinRAR (I use WinRAR for such purposes)
- go into the \boot directory
- find the bootsect.exe file and extract just that file someplace, like the Desktop, etc
- manually copy that bootsect.exe file into the following directory (assuming that you're running Vista or Windows 7, of course):

C:\Users\<username>\AppData\Local\Apps\Windows 7 USB DVD Download Tool

Once that file is copied there, you can create an x64 USB installation stick (with a 64 bit version of Windows 7) while running the tool on on a 32 bit version.

I don't muck with the ei.cfg anymore, I only install Windows 7 Professional anymore - Ultimate is a bit larger and offers nothing that I'm interested in.

I will continue to use this 'custom' SP1 integrated DVD I made till Microsoft drops a proper SP1 integrated ISO on MSDN or Technet and then use that one - I'm sure if I do a binary file compare between that official ISO when it appears and the one I created there will be some differences, and I'm always interested in keeping things as "stock" as possible anymore. Will probably just wait on an official x64 ISO too, not interested in that long arduous process of creating another integrated ISO on this old slow ass T60... :D

Looking back on this I realize it shouldn't be an issue for x64 users anyway: they can't create an x64 ISO on x86 Windows using RT Seven Lite... gotta be running Windows 7 x64 to do it which means the Microsoft USB tool would work without issues anyway, but but but... :p
 
I was just wondering about the ei.cfg because I work on many OEM machines and have to reload them and what not so I need multiple versions. Once MS does release a proper one on technet, I'll be using these as well. Just saves that much more time for me.
 
Well, if you're mucking around with OEM machines that can boot off a USB stick, it's far easier to edit the ei.cfg file on the USB stick in a few seconds than having to maintain an inventory of multiple installation DVDs, I'd think. I have one Technet ISO burned for each version (x86 and x64) and I use one USB stick for all my installs, editing the ei.cfg as required.

The issue I'm concerned with is that RT Seven Lite makes some alterations to files when it creates a specific edition ISO that won't be exactly the same as the "official" ISO from Microsoft, hence me knowing that this was just an exercise and not a serious thing at this point. I won't use this SP1 integrated installation USB stick (or the ISO I created) for client machines, only my own hardware for the testing until that official ISO appears.
 
there was an update KB976902 is a specific "update to allow future updates to Windows 7 and Server 2008 R2"

the official release must be imminent now
 
The integrated iso's have leaked.

MICROSOFT.WINDOWS.7.ULTIMATE.RTM.WITH.SP1.X86.RETAIL.ENGLISH
BUILD: 7601.17514.101119-1850
7601.17514.101119-1850_x86fre_client_en-us_Retail_Ultimate-GRMCULFRER_EN_DVD.iso
SIZE: 2,563,039,232 byte
SHA-1: 92C1ADA4FF09C76EC2F1974940624CAB7F822F62
MD5: 24F3A45D43D7C532AA3126CC094C61BD
CRC: C2966895


MICROSOFT.WINDOWS.7.ULTIMATE.RTM.WITH.SP1.X64.RETAIL.ENGLISH
BUILD: 7601.17514.101119-1850
7601.17514.101119-1850_x64fre_client_en-us_Retail_Ultimate-GRMCULXFRER_EN_DVD.iso
SIZE: 3,319,478,272 byte
SHA-1: 1693B6CB50B90D96FC3C04E4329604FEBA88CD51
MD5: 56A26636EC667799F5A7F42F142C772D
CRC: 8589EE18

There is also OEM and VLK iso's out there.
 
Build number is slightly off the one I have (which this image is from) but I'm guessing it's still considered the same:

win7sp1buildinfo.png


which works out to 7601.17514.101119-0522 (5:22AM vs the 6:50PM represented by 1850 in the "official" one). Most likely they finished the actual SP1 builds early in the morning, then built the integrated ISOs later the same day (November 11, 2010). Been "finished" for quite some time, geez... :)
 
Damnit! Why did the official integrated ISO's have to leak the day after I tore my PC apart. Going to have to download on a backup PC (this one).
 
I've seen like 19 "sources" for these so far and every one of them is simply untrustworthy (my opinion) so, even in spite of the MD5/SHA1 checksums I see being published, I'll wait for my second round installation until I can get these direct from Microsoft this time...

A bunch of "7n1" ISOs already out where someone tampered with the ei.cfg and I'm not gonna take a chance. If it's not from Microsoft direct and I can't get the checksums from Microsoft direct, forget it.
 
Theres only 1 site I get my leaks from, all I can say is it's Russian. Every leak from 7 alphas all the way to this leak have been released and legit from him. It's the only place I would trust tbh.
 
You must log in or register to reply here.
Back
Top