strel

Updated! The new version integrates the fixes you submitted, and other new features. Now it gives freedom to install whatever updated framework version without being bothered by the update system, as it happens since KB951847 family update was realeased to add nothing new. Now it actually support absolutely all updates up to date even restricted ones. Now win 2K users can install 2.0 SP2 in his/her systems. Actually they could have done this with the previous version and 3.5 SP1 full redist, though it wasn't documented. And about KB928416 problem, it seems it has been fixed by MS since KB951847 was released, at least I can't reproduce it again. So I didn't include the fix I have to that issue in this version. But I want you to confirm this point to include it if necessary. Enjoy!

Search in the links above, use google bar for this forum. For .NET you have SNMsynth among others.

nLite add-ons doesn't get installed on first logon, use RunOnce section for this purposes. See too RunOnceEx/RunOnceEx from CD and GUIRunOnce methods. And the Timeline to understand when each one is triggered.

With winnt32.exe /unattend:<answer file> you can specify different answers files. And you can change the product key of the installed windows. Use google to search the forum.

So you trigger vista intalling from installed vista in the internal HDD of the desktop PC, but after copying files I suppose it has to boot the new system from USB drive to complete... Anyway, this may interest you.

You don't need to slipstream SP2 and then SP3, just SP3. Not sure if this has something to do with it but since file proceeds from D:\i386\asms\..., is ASMS Compression option in Advanced Settings of Hotfix Add-ons and Updates section of nLite enabled? Maybe is causing you problems.

In the Unattended windows guide you'll find plentiful of information about installing methods. Keep an eye too on RyanVM page, besides the update packs you may find useful for you, there's a switchless installers subforum with software you can integrate in your CD with nlite; and visit too the applications install subforum and nLite add-ons subforum of this site. And WinAddOns.com

Sorry, my fault. In SNMsynth.cmd substitute line 21: FOR /F "TOKENS=3" %%I IN ('VER') DO IF /I "%%I"=="2000" (SET WIN2K=YES) ELSE IF /I "%%I"=="XP" (SET WINXP=YES) ELSE IF /I "%%I"=="2003" (SET WIN2K3=YES) ELSE ECHO ERROR: This script is only for using under win 2K/XP/2K3.&PAUSE&EXIT with this: FOR /F "TOKENS=3,4" %%I IN ('VER') DO IF /I "%%I"=="2000" (SET WIN2K=YES) ELSE IF /I "%%I"=="XP" (SET WINXP=YES) ELSE IF /I "%%J"=="5.2.3790]" (SET WIN2K3=YES) ELSE ECHO ERROR: This script is only for using under win 2K/XP/2K3.&PAUSE&EXIT I can't test it, but it should work.

I answer you here.

Essentially similar to jfx solution: try Silent .NET Maker synthesized.

2 Joely P Thx. I extend your gratitude to Tomcat and all the people who helped with this script. 2 atolica KB951847 completes the set: 2.0 SP2 + NDP20SP2-KB958481-x86 + 2.0 SP2 langpack + 3.0 SP2 + NDP30SP2-KB958483-x86 + 3.0 SP2 langpack + 3.5 SP1 + NDP35SP1-KB958484-x86 + 3.5 SP1 langpack with those parts you don't have installed, so actually doesn't add anything new, just different registry values.

Because this should be added to registry to avoid the family update KB951847.

This is what you're looking for: dotnetfx35setup.exe /qb

Oh OK, that's the web bootstrapper. See this..

What do you call "3.5 SP1 (2.82MB)"?

2 simurqq You can do it this way, but build installers, not add-ons (or extract installers from add-ons), and you can merge all-in-one or use individual installers. But you have to keep install order 2.0 SP# then 3.0 SP# then 3.5 SP# then 1.1, this order is kept by the merged installer/add-on. 2 George King Install 3.0 SP# is a prerequisite to install 3.5 SP#, seem you missed it in your addon. To hide KB951847 at the moment you have to install 2.0 SP#+3.0 SP#+3.5 SP# and use this registry values. 2 xenos You should have read carefully the instructions in .ini file. This will work for you for example: PROCESS_DNF1=YES PROCESS_DNF2= PROCESS_DNF35_DNF2=YES PROCESS_DNF35_DNF3=YES PROCESS_DNF35_DNF35=YES ... OUTPUT=ADDON MERGE_FRAMEWORKS=YES ... With these settings and the files you listed, you are building an AIO nlite add-on that installs at T-13. And to avoid KB951847 add registry values of the link in George King's answer above. 2 tmservo Maybe you're looking for this.

Yes, it should install seamlessly. The last thing you need is to add this values in the registry, after installing all the frameworks, to avoid win/ms update prompting you to install useless KB951847. And about NDP1.1sp1-KB######-X86.exe files, NDP1.1sp1-KB867460-X86.exe is the SP1 for .NET 1.1 and NDP1.1sp1-KB928366-X86.exe and NDP1.1sp1-KB947742-X86.exe are hotfixes for the SP1. But NDP1.1sp1-KB867460-X86.exe is not acting as a SP, so installed .NET 1.1 SP1 appears in Add Remove Programs as 1.1 SP0 + KB867460 hotfix (when installed from ms installers not hidding the hotfixes in the list), as if it was only a bunch of hotfixes packed in a single file, what a SP actually is, but not a new version step, what a SP actually should be too. This means too it doesnt matter the order you install NDP1.1sp1-KB######-X86.exe files.

2 srwx Add this to registry. 2 kerrisis You need to install 3.0 SPx in order to install 3.5 SPx, is a prerequisite. I suggest you to use updated versions of the frameworks, so I'd build installers for 2.0 SP2, and 3.0 SP2.

2 Geej SNMsynth is not missing anything for 3.5 SP1. I got the same installed size of 27 MB. The discrepancy with installed sizes arises from the different way Acheron patched 3.5 SP1 msi. One of the process reports erroneus installed size, but the results are equal. 2 Stoner81 KB951847 >=248 MB file includes 2.0 SP2,+3.0 SP2+3.5 SP1+KB958481+KB958483+KB958484+X86-en-ochelper_21f0eb887bce203dee7e4309f525b454bb63b7be.exe (101 KB) and optionally langpack. ...ochelper... is a manager for installing KB951847 from update system. So KB951847 doesn't add anything if you used SNMsynth installer(s) to install all the above except ...ochelper... Don't know why the update refuses to install but probably because of the reason you pointed. If you installed all the above except ...ochelper... , you can use Acheron' solution simplified to avoid win/ms update prompting you to install KB951847. 2 SipTomi Thx for your encourage and your fix, I'll include it in the next update.

With 2.0 SP2+3.0 SP2+3.5 SP1+hotfixes (KB958481,KB958483,KB958484) installed from SNMsynth installers, I was getting 16MB, KB951847 file, but recently 248 MB file with the same circumstances (don't know why), in win/ms update, not detecting the hotfixes, and to avoid this you can use Acheron' solution simplified until I include it in the script.

WOW, very elegant. Let me see... as you told me installshield for msi modification, so you can trigger install without setup.exe and without ADDEPLOY=1; and custom uninstall entries for 3.5 SP1. Then WiMakCab.vbs to compress in one msi file each FX and each langpack. Then applying hotfixes patches to msi files (I didn't know all this very specifical updates, thx). And then building this inf file. And even encapsullating all this in a SFX file. Right? I thought you wanted to build a unique msi file for GPO installing. In the KB928416 section, you're using mickmack's solution to avoid 3.0 SP2 language problem. From my experience this should be enough: HKLM,"SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.0\Setup\1043","InstallSuccess",0x10001,01,00,00,00 HKLM,"SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.0\Setup\1043","Version",0x0,"3.0.04506.30" HKLM,"SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.0\Setup\Windows Presentation Foundation\NL","Version",0x0,"3.0.6920.0" The unresolved problem now with KB951847 is that we're prompted to download and install complete 3.5 SP1 redistributable packet if we don't want the whole packet and have only 2.0 SP2, or 2.0 SP2 and 3.0 SP2 installed among FXs from 3.5 SP1 redist. So KB951847.inf solution only avoids update prompting for installers including 2.0 SP2+3.0 SP2+3.5 SP1 FXs merged, or after installing these FXs version from single installers.

Acheron, it works great man . Thx. But there's an excess of values and makes KB958481 and KB958483 arise in Add/Remove Programs. To keep them hidden, like they were before KB951847 was published, and avoid win/ms update prompting to donwload and install KB951847, it's enough with this: KB951847.inf [Version] Signature = "$Windows NT$" [DefaultInstall] AddReg = KB951847.AddReg [KB951847.AddReg] ;KB958481 HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504","State",0x10001,01,00,00,00 ;KB958483 HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37","State",0x10001,01,00,00,00 ;KB958484 HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85","State",0x10001,01,00,00,00 or in the form of KB951748.reg REGEDIT4 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504] "State"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37] "State"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85] "State"=dword:00000001

2 ferk Thx. I got confused with the documentation. 2 geromichi I see. Versions are the same. If you don't have all single 3.5 SP1 redist frameworks installed, update prompts you to download the whole 248 MB packet including .NET 3.5 SP1 redist and if you have installed a langpack other than the one correponding the language of system (except for english system) it includes langpack too.

OK, I've seen it, I got confused with the documentation. I continue in SNM synthesized thread.

That is updating .NET 3.5 redistributable with .NET 3.5 SP1. It's simple, use SP1, and you will not have this update listed.