Is it possible to integrate SP1 into Windows 7 with Wintoolkit?

[mesmer]

Is it possible to integrate SP1 into Windows 7 with Wintoolkit? 

 

I added the sp1.exe from Silent installs with the switch '-X86.exe windows6.1-KB976932 / quiet / nodialog / norestart'

 

but not install anything

[bphlpt]

Don't try.  Instead download an ISO with SP1 already integrated.  See here.  Use that as the source for your builds.

 

Cheers and Regards

[mesmer]

Thank you very much, but I have a oem dvd I would like to integrate, it if possible.

[bphlpt]

AFAIK, no it is not possible.  (But I could be wrong.)

 

Cheers and Regards

[mesmer]

I'm afraid you're not wrong. I will look for other ways.

 

thanks

[bphlpt]

I have seen that other programs, such as perhaps RT7Lite, have said that they are able to do that, at least on a retail ISO, I'm not sure about OEM.  But be aware that that app has not been updated in years, and implements the function through somewhat of a hack.  I know others have had success with it, but personally I would not trust it, especially if you are trying to maintain the "purity" of the OEM ISO.

 

Would it be possible to add the relevant parts of the OEM ISO to the SP3 ISO I pointed to above, so you have the same essential results, but use more up to date tools?  Just an idea.

 

Cheers and Regards

[mesmer]

I've also tried rtlite but is only able to handle a version of windows 7 at once. also modifies the number of the build of sp1 for other than the usual.?!!

So it is not a very good option. 

 

It sure would be easier to add the relevant parts oem dvd. I guess that would be the oem certificate but I don't know which and where they are

[bphlpt]

You're beyond my knowledge level now, I know just enough to be dangerous, so hopefully someone else will offer you more information.  Good luck.

 

NOTE:  You'll probably need to know exactly what the differences are between the OEM and a "standard" install disc so you will be able to tell someone else what exactly you need to move over.

 

Cheers and Regards

[mesmer]

Well, the oem dvd basically differs oem license and the specific theme of the signature. Otherwise it is equal to a standard dvd. 

 

I hope someone can illustrate me 

 

thanks for you help bphlpt 

[Legolash2o]

Download an ISO via Win Toolkit then following the following link:

 

https://www.sctxca.org/suncity/clubs-groups/sites/computer/sigs/win7/articles/Win7_Retail-to-OEM.htm

 

In the sources folder open ei.cfg with notepad

 

 

[EditionID]

Ultimate

[Channel]

Retail

[VL]

0

 

Change retail to OEM: I'm pretty sure you can just delete the ei.cfg either way

 

 

[EditionID]

Ultimate

[Channel]

OEM

[VL]

0

You made need to change 'Ultimate' to 'HomeBasic', 'HomePremium' or whatever version you have.

[mesmer]

but the key is the need to introduce via wintoolkit  or manually?

[Legolash2o]

With Windows 7 you provide the key after Windows Installation if you need. Just make sure to select the right version the key is for.

[abbodi1406]

Integrating SP1 require manual method and some steps

 

if you can handle those steps, then i can provide you with tutorial

[mesmer]

would be very grateful to you. 

would be a very useful tutorial.

[abbodi1406]

First of the all, the tutorial is not mine, it's from a german site http://www.gtkdb.de/index_17_1534.html, so all credits goes to him.
second, i didn't try or test it if it's working or not

Requirements:

- Windows 7 x86 install DVD.
- working Windows 7 x86 or x64 system with 15 GB of free space.

open the command prompt as administrator and continue with the following steps:

1. create a directory for the contents of the Windows 7 x86 install DVD.

2. Copy or extract the DVD contents to the created directory. (example if you DVD drive is E:)

3. create a few more working directories.

4. Copy or move the SP1 file windows6.1-KB976932-X86.exe to C:\Win7_x86_Slipstream folder
5. Extract the SP1: (the extracting will be done in the background, use task manager to moniter the process)

6. copy windows6.1-KB976932-X86.cab to C:\Win7_x86_Slipstream\extract

7. you need to extract those files:

8. you have to make changes in three files with notepad:
First:

Find the following section in the file and change allowedOffline from false to true and save the changes

Second:

Find the following section in the update.mum and change allowedOffline from false to true here too.

Third:

locate the following section and change targetState from absent to installed.

9. Now you need to get info about the available images in Windows 7 DVD:

select which image (index) you want to integrate SP1 to it (usually you choose the higher edition), if it has only one image then choose index 1
10 . Then mount the corresponding image in the install.wim in the directory C:\Win7_x86_Slipstream\mount.

11. Now integrate The Service Pack 1:

12. save the changes to the install.wim

You can repeat the operation for all indexes (mount/integrate/unmount)

Finally, create a bootable ISO image from the contents of the C:\Win7_x86_DVD

mkdir C:\Win7_x86_DVD

xcopy E:\*.* /E /F C:\Win7_x86_DVD

mkdir C:\Win7_x86_Slipstream C:\Win7_x86_Slipstream\temp C:\Win7_x86_Slipstream\extract C:\Win7_x86_Slipstream\mount

C:\Win7_x86_Slipstream\windows6.1-KB976932-X86.exe /X:C:\Win7_x86_Slipstream\temp

copy C:\Win7_x86_Slipstream\temp\windows6.1-KB976932-X86.cab C:\Win7_x86_Slipstream\extract

expand C:\Win7_x86_Slipstream\extract\windows6.1-KB976932-X86.cab -F:* C:\Win7_x86_Slipstream\extractexpand C:\Win7_x86_Slipstream\extract\NestedMPPContent.cab -F:* C:\Win7_x86_Slipstream\extractexpand C:\Win7_x86_Slipstream\extract\KB976933-LangsCab*.cab -F:* C:\Win7_x86_Slipstream\extract

notepad C:\Win7_x86_Slipstream\extract\Windows7SP1-KB976933~31bf3856ad364e35~x86~~6.1.1.17514.mum

<mum:packageExtended xmlns:mum="urn:schemas-microsoft-com:asm.v3" allowedOffline="false" projectionPeakDisk="304" langProjectionPeakDisk="322" sqmBuildNumber="7601" sqmAttemptAppid="101457923" sqmResultAppid="101457924" sqmPoqexecAppid="101457925"/></package>

notepad C:\Win7_x86_Slipstream\extract\update.mum

<mum:packageExtended xmlns:mum="urn:schemas-microsoft-com:asm.v3" allowedOffline="false" projectionPeakDisk="304" langProjectionPeakDisk="322" sqmBuildNumber="7601" sqmAttemptAppid="101457923" sqmResultAppid="101457924" sqmPoqexecAppid="101457925"/></package>

notepad C:\Win7_x86_Slipstream\extract\update.ses

<Tasks operationMode="OfflineInstall">     <Phase>         <package id="Windows7SP1-KB976933~31bf3856ad364e35~x86~~6.1.1.17514" targetState="Absent"/>     </Phase> </Tasks>

dism.exe /get-wiminfo /wimfile:C:\Win7_x86_DVD\sources\install.wim

dism.exe /mount-wim /wimfile:C:\Win7_x86_DVD\sources\install.wim /index:1 /mountdir:C:\Win7_x86_Slipstream\mount

dism.exe /image:C:\Win7_x86_Slipstream\mount /add-package /packagepath:C:\Win7_x86_Slipstream\extract

dism.exe /unmount-wim /mountdir:C:\Win7_x86_Slipstream\mount /commit

Edited March 23, 2014 by abbodi1406

[mesmer]

ok, no problem. I'll try and report back here if it works for me or not. 

 

Thanks for the link and translation 

[Shandra]

I tried that manual and afterwards WTK recognizes that .wim as SP1, and a VM Install of it was functional - haven't tried it any further as there is some ununderstandable Thread over at RyansVM which I do not comprehend and somehow sounds like "does those persons in any way know what they are talking about" but at least leaves some doubts towards this method (As long as I do not understand how this whole nt6 package stuff works). And what puzzles me is that it the method above only consideres the KB976932 cab and ignores the prerequisite to install sp1 (KB976902) on a freshly installed Pre-SP1 Win7. But as that one is also removed from the installed updates list if one issues a "dism /online /cleanup-image /spsuperseded" that my not be a problem after all. As an alternative I tried it the SysPrep way yesterday, but the resulting install.wim I got from that installed fine as a VM, but when I tried to add further updates to it via WinToolkit it was only recognized as "beeing corrupt" :/ 

[Legolash2o]

Have you tried post 10?

 

http://www.wincert.net/forum/topic/12091-is-it-possible-to-integrate-sp1-into-windows-7-with-wintoolkit/?p=106027

[Shandra]

Leogolash2o: Oops, Sorry - though my system is a Win7 (SP1 build) I should have said that I am currently trying to prep-up my Dreamspark Licence of Server2k8R2 - and thats only a preSP1 .img (and using an eval iso via MSDN/Technet as a base ain't an option as that one can't be upgraded to retail). Anyway I was more curious about the possibility if (and how) it can be done then being in need of it 

And an erata to my previous post:  I am not sure what happened during that install where both the sp and prerequisite-KB where removed from the installed update list (maybe I just messed up my memory between the dism-preped_sp1 and regular pre-sp install); The various installs I tried today removed none of those entries, and if i added the /hidesp option to the cmd-line only the SP1 entry was removed. The dism-preped iso starts up with no entries in the updates list, and as far as I remember a Win7 SP1 install is listing the KB976902 as installed (?). So maybe the way quoted by abbodi has to be modified in some way? I will play around with it this evening (as said out of curiousity) and afterwards, to be on the sure side, just doing a regular install for activation.

Edited March 26, 2014 by Shandra

[Shandra]

As predictable, adding the SP1 package after KB976902 is a no go because of the pending state for the KB integration. Maybe I am a bit over-paranoid here, as it seem all (?) of the KB*02 files are also in the expanded SP1.cab directory, though there are some differences in the update.mum of those two:

>> from update.mum KB*02

  <update name="976902-10_neutral_PACKAGE">
    <package integrate="hidden">
      <assemblyIdentity name="Package_for_KB976902_RTM" version="6.1.1.17514" language="neutral" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35"/>
    </package>
  </update>

>> from update.mum KB*32
  <update name="976902-0_neutral_PACKAGE">
    <package integrate="isolate">
      <assemblyIdentity name="Package_for_KB976902" version="6.1.1.17514" language="neutral" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35"/>
    </package>
  </update>

 Now lets compare some dism /get-packages information for various installs/wims (Server2k8 std - Dreamspark.img/MS_Eval.iso):
 
- All Images where listed as: Image Version: 6.1.7600.16385
- To keep the list short I removed the install date information from the following lines 
- for better comparison I put each listed package from the various sources interleaved and colour-coded (pre_SP1,  SP1_added, SP1_Installed¹, SP1_Eval)
1: Sp1_installed means a regular install of pre_SP1 and then executing the offline SP1 Installer followed by a dism /online /cleanup-image /spsuperseded without /hidesp 

Package Identity : Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385
State : Installed
Release Type : Foundation
Package Identity : Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7600.16385
State : Uninstall Pending
Release Type : Foundation
Package Identity : Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514
State : Installed
Release Type : Foundation
Package Identity : Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514
State : Installed
Release Type : Foundation 
Package Identity : Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514
State : Installed
Release Type : Foundation
 
Package Identity : Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~en-US~8.0.7601.17514
State : Install Pending
Release Type : Language Pack

Package Identity : Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~en-US~8.0.7601.17514
State : Installed
Release Type : Language Pack

Package Identity : Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~en-US~8.0.7601.17514
State : Installed
Release Type : Language Pack
 
Package Identity : Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~~8.0.7601.17514
State : Install Pending
Release Type : Feature Pack

Package Identity : Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~~8.0.7601.17514
State : Installed
Release Type : Feature Pack

Package Identity : Microsoft-Windows-InternetExplorer-Optional-Package~31bf3856ad364e35~amd64~~8.0.7601.17514
State : Installed
Release Type : Feature Pack
 
 
Package Identity : Microsoft-Windows-Server-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7600.16385
State : Installed
Release Type : Language Pack
Package Identity : Microsoft-Windows-Server-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7600.16385
State : Uninstall Pending
Release Type : Language Pack
Package Identity : Microsoft-Windows-Server-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514
State : Install Pending
Release Type : Language Pack

Package Identity : Microsoft-Windows-Server-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514
State : Installed
Release Type : Language Pack

Package Identity : Microsoft-Windows-Server-LanguagePack-Package~31bf3856ad364e35~amd64~en-US~6.1.7601.17514
State : Installed
Release Type : Language Pack
 
Package Identity : Package_for_KB976932~31bf3856ad364e35~amd64~~6.1.1.17514
State : Install Pending
Release Type : Service Pack
Package Identity : Package_for_KB976932~31bf3856ad364e35~amd64~~6.1.1.17514
State : Installed
Release Type : Service Pack
 
Package Identity : Package_for_KB976902~31bf3856ad364e35~amd64~~6.1.1.17514
State : Installed
Release Type : Update
Package Identity : Package_for_KB976902~31bf3856ad364e35~amd64~~6.1.1.17514
State : Installed
Release Type : Update

 

Except from the fact that there are 4 packages unique to the Eval (I spared them from the comparison), the only real difference (not taking into account that the dism'end SP1 updates being in a pending state for uninstall/install) is still KB976902.

Even if that is added as a package after the integration of SP1 it won't be installed during setup (why should it if those files are also in the SP1.cab). Even further integrations with Wintoolkit seem to be functional, but there I only tried the integration (with the selection of IE11/IE11 prerequisites, general and security updates from WTs alphawaves' Downloader [downloaded KB2461631/2732500/2773072 couldn't be integrated]) and i havent tested the resulting iso so far.

 

As one who has no full understanding of the processes involved my bet now on KB976902 and the dism integration of SP1 would be that it will be functional at this time, but there must be a reason why M$ let it be installed before KB976932 and is not removing it from the installed updates list. Even if i have no idea why the SP.cab includes the KB.cab files in this case, I would assume that M$ sees a reason to let the KB still be uninstallable/becoming superseded after SP1 and that this method of SP1 integration may just be functional until the time where they offer an update that supersede that KB - but thats just my feeling at this moments.

Edited March 27, 2014 by Shandra

[Kelsenellenelvian]

And thusly those kind of issues are why we don't slipstream sp1, it is super messy and leaves dual packages, invalid packages and extra files.

[Shandra]

Leaves dual packages? Strictly speaking it does not(!). The install of SP1_added .wim results in a System where dism /online /get-packages get you the same output as for SP1_installed, just with the exception of the missing KB976902-package entry. No dual entries/packages to be found;

Wouldn't make sense anyway, as the dual listing (setup order) clearly states package a_v1 is to be deinstalled then a_v2 to be installed. That is, as far as I understand it, the regular way with the deployment via dism (one of the basics/fundamental differences why we can't do it the nt5 way anymore and are not going to get a fresh install with <no updates listed and no backup files> on HDD). 

E.g. if you integrate IE11 via WinToolkit and query the resulting .wim, you will see that first the packages for the old IE are being listed as uninstall pending followed by the new IE package with its install pending. 

Edited March 27, 2014 by Shandra

[Legolash2o]

As I said, just download an official SP1 ISO and convert it to OEM.

[Shandra]

Yup - best option for the OP - though I would assume that by just changing the ei.cfg one has to use the provided OEM Key from the Sticker. A better way would IMHO include the transfer of the needed files (as mentioned in Post #7)  from the original OEM DVD/install image that are needed so that the OEM Setup installs with the default OEM Key (which is different from the unique one on the sticker) and recognizes the bios SLP-key information to autoactivate Win on the OEM Hardware. For XP those would have been the OEMbios.**_  and wpa.dl_ files from the OEM CD, I don't know what would provide the corresponding information on Win7 OEM .wims. I am not sure what e.g. Dell is charging for a SP1 Install Media replacement and if that wouldn't be a better choice then to further investigate in this slipstreaming variant.

Edited March 27, 2014 by Shandra

[Legolash2o]

I reckon as long as he installs an OEM copy with his key from his sticker, he can activate fine.