My recent experience is the same: I've just seen that really it downloads only 16,80 MB and if you verify the update files before their installation then you will see that they are EXACTLY the same that are in the "old" Family Update.
On the other hand if you re-install the old ones ("NDP20SP2-KB958481-x86.exe", "NDP30SP2-KB958483-x86.exe" and "NDP35SP1-KB958484-x86.exe" - that's 2.0 SP2, 3.0 SP2 and 3.5 SP1 update) before to pass through Microsoft Update then MU does not require anything.
It seems that MU suddenly does not recognize the "synthesized" updates: strange issue (for now).
When I will have time I will try to create two single synthesized executables (one with 3.5 SP1 and another one with its Family Update) and to install they separately one after another...
Full Version: Silent .NET Maker synthesized 20091105 - W2K/XP/2K3 x86
That's what I tried to explain with my bad level and my bad english sorry.
I do not think more that is a smart way to install in nLited deployments the executable one after another, furthermore it's obviously impossible to join the three Family Update in a single one (otherwise would have already done Microsoft!); probably it would be enough to add the support for the new release that could provide a complete solution at least for FX 3.5 SP1 latest Family (Compatibility) Update included.
The latest "Microsoft .NET Framework 3.5 Service Pack 1 and .NET Framework 3.5 Family Update (KB951847) x86" (248 MB) for Windows Server 2003, Windows Server 2003, Datacenter Edition and Windows XP includes the following executables:
X86_IA64_AMD64-all-dotnetfx35_3dce66bae0dd71284ac7a971baed07030a186918.exe (231 MB)
X86_IA64_AMD64-all-ndp20sp2-kb958481-x86_04fcde4b28dd4f6db7548831d35d1c6bf38e1335.exe (8,56 MB)
X86_IA64_AMD64-all-ndp30sp2-kb958483-x86_2b03b54c0972c16ab6ce75f42ac4877af87ce844.exe (6,91 MB)
X86_IA64_AMD64-all-ndp35sp1-kb958484-x86_8b5036b48590c52e3edba8e297cd3017b7a3043c.exe (1,35 MB)
that are EXACTLY the same of the old ones; plus
"X86-en-ochelper_21f0eb887bce203dee7e4309f525b454bb63b7be.exe" (101 KB), then the experts will have to work...
BTW: I've just tried the latest AIO one from RyanVM.net and it works so fine (with no MU further update request), but however I still would prefer a self-made one.
The latest "Microsoft .NET Framework 3.5 Service Pack 1 and .NET Framework 3.5 Family Update (KB951847) x86" (248 MB) for Windows Server 2003, Windows Server 2003, Datacenter Edition and Windows XP includes the following executables:
X86_IA64_AMD64-all-dotnetfx35_3dce66bae0dd71284ac7a971baed07030a186918.exe (231 MB)
X86_IA64_AMD64-all-ndp20sp2-kb958481-x86_04fcde4b28dd4f6db7548831d35d1c6bf38e1335.exe (8,56 MB)
X86_IA64_AMD64-all-ndp30sp2-kb958483-x86_2b03b54c0972c16ab6ce75f42ac4877af87ce844.exe (6,91 MB)
X86_IA64_AMD64-all-ndp35sp1-kb958484-x86_8b5036b48590c52e3edba8e297cd3017b7a3043c.exe (1,35 MB)
that are EXACTLY the same of the old ones; plus
"X86-en-ochelper_21f0eb887bce203dee7e4309f525b454bb63b7be.exe" (101 KB), then the experts will have to work...
BTW: I've just tried the latest AIO one from RyanVM.net and it works so fine (with no MU further update request), but however I still would prefer a self-made one.
The AIO from ryanvm still asks for the kb951847 article in MU
however it asks to dl that article the article size is 248 mb but it infact only downloads
X86_IA64_AMD64-all-ndp20sp2-kb958481-x86_04fcde4b28dd4f6db7548831d35d1c6bf38e1335.exe (8,56 MB)
X86_IA64_AMD64-all-ndp30sp2-kb958483-x86_2b03b54c0972c16ab6ce75f42ac4877af87ce844.exe (6,91 MB)
X86_IA64_AMD64-all-ndp35sp1-kb958484-x86_8b5036b48590c52e3edba8e297cd3017b7a3043c.exe (1,35 MB)
those 3 files for a total of 16.9mb
if you were able to use the latest ryanvm AIO and have 0 updates ready for download via MU can you please explain how to do so because I have tried with RyanVM AIO it installs at t-13 the dotnets install but i am still asked to download 16.9mb worth of files via MU
can you please explain to me how you used RyanVM AIO and have 0 updates on MU
however it asks to dl that article the article size is 248 mb but it infact only downloads
X86_IA64_AMD64-all-ndp20sp2-kb958481-x86_04fcde4b28dd4f6db7548831d35d1c6bf38e1335.exe (8,56 MB)
X86_IA64_AMD64-all-ndp30sp2-kb958483-x86_2b03b54c0972c16ab6ce75f42ac4877af87ce844.exe (6,91 MB)
X86_IA64_AMD64-all-ndp35sp1-kb958484-x86_8b5036b48590c52e3edba8e297cd3017b7a3043c.exe (1,35 MB)
those 3 files for a total of 16.9mb
if you were able to use the latest ryanvm AIO and have 0 updates ready for download via MU can you please explain how to do so because I have tried with RyanVM AIO it installs at t-13 the dotnets install but i am still asked to download 16.9mb worth of files via MU
can you please explain to me how you used RyanVM AIO and have 0 updates on MU
Here's a quick fix for KB951847 showing up on Windows Update after manually building the .NET installer.
KB951847.inf
KB951847.inf
CODE
[Version]
Signature = "$Windows NT$"
[DefaultInstall]
AddReg = KB951847.AddReg
[KB951847.AddReg]
;KB958481
HKLM,"SOFTWARE\Classes\Installer\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches","C3CFBEEB1B8483A43A5C18AB91FDF504",0x0,":SP1.1;:#SP1.1"
HKLM,"SOFTWARE\Classes\Installer\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches","Patches",0x10000,"C3CFBEEB1B8483A43A5C18AB91FDF504"
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504",,0x10
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504","MSI3",0x10001,01,00,00,00
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504","State",0x10001,01,00,00,00
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504","Uninstallable",0x10001,00,00,00,00
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504","LUAEnabled",0x10001,00,00,00,00
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504","PatchType",0x10001,00,00,00,00
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504","DisplayName",0x0,"KB958481"
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504","MoreInfoURL",0x0,"http://www.microsoft.com/"
;KB958483
HKLM,"SOFTWARE\Classes\Installer\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches","E54DA494170E9184E8511E40F1FB0F37",0x0,":SP1.1;:#SP1.1"
HKLM,"SOFTWARE\Classes\Installer\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches","Patches",0x10000,"E54DA494170E9184E8511E40F1FB0F37"
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37","MSI3",0x10001,01,00,00,00
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37","State",0x10001,01,00,00,00
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37","Uninstallable",0x10001,00,00,00,00
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37","LUAEnabled",0x10001,00,00,00,00
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37","PatchType",0x10001,00,00,00,00
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37","DisplayName",0x0,"KB958483"
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37","MoreInfoURL",0x0,"http://www.microsoft.com/"
;KB958484
HKLM,"SOFTWARE\Classes\Installer\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches","2F2AEE7ADCFB45A45A57B7187A686E85",0x0,":SP1.1;:#SP1.1"
HKLM,"SOFTWARE\Classes\Installer\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches","Patches",0x10000,"2F2AEE7ADCFB45A45A57B7187A686E85"
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85",,0x10
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85","MSI3",0x10001,01,00,00,00
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85","State",0x10001,01,00,00,00
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85","Uninstallable",0x10001,00,00,00,00
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85","LUAEnabled",0x10001,00,00,00,00
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85","PatchType",0x10001,00,00,00,00
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85","DisplayName",0x0,"KB958484"
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85","MoreInfoURL",0x0,"http://www.microsoft.com/"
Signature = "$Windows NT$"
[DefaultInstall]
AddReg = KB951847.AddReg
[KB951847.AddReg]
;KB958481
HKLM,"SOFTWARE\Classes\Installer\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches","C3CFBEEB1B8483A43A5C18AB91FDF504",0x0,":SP1.1;:#SP1.1"
HKLM,"SOFTWARE\Classes\Installer\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches","Patches",0x10000,"C3CFBEEB1B8483A43A5C18AB91FDF504"
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504",,0x10
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504","MSI3",0x10001,01,00,00,00
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504","State",0x10001,01,00,00,00
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504","Uninstallable",0x10001,00,00,00,00
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504","LUAEnabled",0x10001,00,00,00,00
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504","PatchType",0x10001,00,00,00,00
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504","DisplayName",0x0,"KB958481"
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504","MoreInfoURL",0x0,"http://www.microsoft.com/"
;KB958483
HKLM,"SOFTWARE\Classes\Installer\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches","E54DA494170E9184E8511E40F1FB0F37",0x0,":SP1.1;:#SP1.1"
HKLM,"SOFTWARE\Classes\Installer\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches","Patches",0x10000,"E54DA494170E9184E8511E40F1FB0F37"
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37","MSI3",0x10001,01,00,00,00
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37","State",0x10001,01,00,00,00
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37","Uninstallable",0x10001,00,00,00,00
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37","LUAEnabled",0x10001,00,00,00,00
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37","PatchType",0x10001,00,00,00,00
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37","DisplayName",0x0,"KB958483"
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37","MoreInfoURL",0x0,"http://www.microsoft.com/"
;KB958484
HKLM,"SOFTWARE\Classes\Installer\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches","2F2AEE7ADCFB45A45A57B7187A686E85",0x0,":SP1.1;:#SP1.1"
HKLM,"SOFTWARE\Classes\Installer\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches","Patches",0x10000,"2F2AEE7ADCFB45A45A57B7187A686E85"
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85",,0x10
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85","MSI3",0x10001,01,00,00,00
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85","State",0x10001,01,00,00,00
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85","Uninstallable",0x10001,00,00,00,00
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85","LUAEnabled",0x10001,00,00,00,00
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85","PatchType",0x10001,00,00,00,00
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85","DisplayName",0x0,"KB958484"
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85","MoreInfoURL",0x0,"http://www.microsoft.com/"
QUOTE (anthonyaudi @ Feb 1 2009, 09:49 PM) 
can you please explain to me how you used RyanVM AIO and have 0 updates on MU
Simply running "NetFXAIO.exe" at first logon rather than using it as Add-on (so furthermore no error will appear in Event Viewer).
If you read again the linked thread about RyanVM.net the discussion is in progress.
However I see now that seems to be finally reached a fix here (I have not yet tried it)...
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
or in the form of KB951748.reg
. 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
CODE
[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
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
CODE
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
[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
@strell, thanks for your improvement!
My final script for dutch language looks like this and passes Windows Update
install.inf
I have modified the msi to remove the setup files and custom uninstall entries. No other modifications except for merging the following hotfixes:
Filesizes for reference (XP SP3) as displayed in Add/Remove Software Panel
.NET 2.0 SP2 22.7 MB msi, 185,00 MB installed
.NET 3.0 SP2 22.7 MB msi, 169,00 MB installed
.NET 3.5 SP1 8.8 MB msi, 58,94 MB installed
Languagepacks
.NET 2.0 SP2 NLD 1,9 MB msi, 6,18 MB installed
.NET 3.0 SP2 NLD 1,5 MB msi, 3,88 MB installed
.NET 3.5 SP1 NLD 1,0 MB msi, 1,50 MB installed
My final script for dutch language looks like this and passes Windows Update
install.inf
CODE
[Version]
Signature = "$Windows NT$"
[DefaultInstall]
RunPreSetupCommands = NetFX20.Install:1,NetFX30.Install:1,NetFX35.Install:1
[DestinationDirs]
;All users application data directory
NetFX.CopySetup = 16419,".NET Framework"
[NetFX.CopySetup]
"install.inf"
"NetFX30SP2_x86.msi"
"NetFX30SP2_x86_nld.msi"
"NetFX35SP1_x86.msi"
"NetFX35SP1_x86_nld.msi"
[NetFX20]
RunPreSetupCommands = NetFx20.Install:1
CopyFiles = NetFX.CopySetup
[NetFX30]
RunPreSetupCommands = NetFx30.Install:1
[NetFX35]
RunPreSetupCommands = NetFx35.Install:1
AddReg = Uninstall.Reg,KB951847.AddReg,KB928416.AddReg
[NetFX20.Install]
;Microsoft .NET Framework 2.0 SP2
"msiexec /i ""%01%\NetFX20SP2_x86.msi"" /qb-! ALLUSERS=1"
;Microsoft .NET Framework 2.0 SP2 dutch language pack
"msiexec /i ""%01%\NetFX20SP2_x86_nld.msi"" /qn ALLUSERS=1"
[NetFX30.Install]
;Microsoft .NET Framework 3.0 SP2
"msiexec /i ""%01%\NetFX30SP2_x86.msi"" /qb-! ALLUSERS=1"
;Microsoft .NET Framework 3.0 SP2 dutch language pack
"msiexec /i ""%01%\NetFX30SP2_x86_nld.msi"" /qn ALLUSERS=1"
[NetFX35.Install]
;Microsoft .NET Framework 3.5 SP1
"msiexec /i ""%01%\NetFX35SP1_x86.msi"" /qb-! ALLUSERS=1"
;Microsoft .NET Framework 3.5 SP1 dutch language pack
"msiexec /i ""%01%\NetFX35SP1_x86_nld.msi"" /qn ALLUSERS=1"
[Uninstall.Reg]
;Fix .NET 3.5 SP1 uninstall information
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{CE2CDD62-0124-36CA-84D3-9F4DCF5C5BD9}","SystemComponent",0x10001,00,00,00,00
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{101738D7-D805-37A9-BB91-1F2C351782BF}","SystemComponent",0x10001,00,00,00,00
[KB951847.AddReg]
;KB958481
HKLM,"%INSTUSERDATA_KEY%\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504","DisplayName",0x0,"KB958481"
HKLM,"%INSTUSERDATA_KEY%\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504","LUAEnabled",0x10001,00,00,00,00
HKLM,"%INSTUSERDATA_KEY%\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504","MSI3",0x10001,01,00,00,00
HKLM,"%INSTUSERDATA_KEY%\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504","MoreInfoURL",0x0,"http://www.microsoft.com/"
HKLM,"%INSTUSERDATA_KEY%\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504","PatchType",0x10001,00,00,00,00
HKLM,"%INSTUSERDATA_KEY%\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504","State",0x10001,01,00,00,00
HKLM,"%INSTUSERDATA_KEY%\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504","Uninstallable",0x10001,00,00,00,00
;KB958483
HKLM,"%INSTUSERDATA_KEY%\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37","DisplayName",0x0,"KB958483"
HKLM,"%INSTUSERDATA_KEY%\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37","LUAEnabled",0x10001,00,00,00,00
HKLM,"%INSTUSERDATA_KEY%\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37","MSI3",0x10001,01,00,00,00
HKLM,"%INSTUSERDATA_KEY%\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37","MoreInfoURL",0x0,"http://www.microsoft.com/"
HKLM,"%INSTUSERDATA_KEY%\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37","PatchType",0x10001,00,00,00,00
HKLM,"%INSTUSERDATA_KEY%\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37","State",0x10001,01,00,00,00
HKLM,"%INSTUSERDATA_KEY%\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37","Uninstallable",0x10001,00,00,00,00
;KB958484
HKLM,"%INSTUSERDATA_KEY%\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85","DisplayName",0x0,"KB958484"
HKLM,"%INSTUSERDATA_KEY%\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85","LUAEnabled",0x10001,00,00,00,00
HKLM,"%INSTUSERDATA_KEY%\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85","MSI3",0x10001,01,00,00,00
HKLM,"%INSTUSERDATA_KEY%\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85","MoreInfoURL",0x0,"http://www.microsoft.com/"
HKLM,"%INSTUSERDATA_KEY%\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85","PatchType",0x10001,00,00,00,00
HKLM,"%INSTUSERDATA_KEY%\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85","State",0x10001,01,00,00,00
HKLM,"%INSTUSERDATA_KEY%\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85","Uninstallable",0x10001,00,00,00,00
[KB928416.AddReg]
;KB928416
HKLM,"SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.0\Servicing\Windows Workflow Foundation\NL",,0x0
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 Communication Foundation\1043","InstallSuccess",0x10001,01,00,00,00
HKLM,"SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.0\Setup\Windows Presentation Foundation\NL","InstallSuccess",0x10001,01,00,00,00
HKLM,"SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.0\Setup\Windows Presentation Foundation\NL","Version",0x0,"3.0.6920.0"
HKLM,"SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.0\Setup\Windows Workflow Foundation\NL","InstallSuccess",0x10001,01,00,00,00
[Strings]
INSTUSERDATA_KEY="SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18"
Signature = "$Windows NT$"
[DefaultInstall]
RunPreSetupCommands = NetFX20.Install:1,NetFX30.Install:1,NetFX35.Install:1
[DestinationDirs]
;All users application data directory
NetFX.CopySetup = 16419,".NET Framework"
[NetFX.CopySetup]
"install.inf"
"NetFX30SP2_x86.msi"
"NetFX30SP2_x86_nld.msi"
"NetFX35SP1_x86.msi"
"NetFX35SP1_x86_nld.msi"
[NetFX20]
RunPreSetupCommands = NetFx20.Install:1
CopyFiles = NetFX.CopySetup
[NetFX30]
RunPreSetupCommands = NetFx30.Install:1
[NetFX35]
RunPreSetupCommands = NetFx35.Install:1
AddReg = Uninstall.Reg,KB951847.AddReg,KB928416.AddReg
[NetFX20.Install]
;Microsoft .NET Framework 2.0 SP2
"msiexec /i ""%01%\NetFX20SP2_x86.msi"" /qb-! ALLUSERS=1"
;Microsoft .NET Framework 2.0 SP2 dutch language pack
"msiexec /i ""%01%\NetFX20SP2_x86_nld.msi"" /qn ALLUSERS=1"
[NetFX30.Install]
;Microsoft .NET Framework 3.0 SP2
"msiexec /i ""%01%\NetFX30SP2_x86.msi"" /qb-! ALLUSERS=1"
;Microsoft .NET Framework 3.0 SP2 dutch language pack
"msiexec /i ""%01%\NetFX30SP2_x86_nld.msi"" /qn ALLUSERS=1"
[NetFX35.Install]
;Microsoft .NET Framework 3.5 SP1
"msiexec /i ""%01%\NetFX35SP1_x86.msi"" /qb-! ALLUSERS=1"
;Microsoft .NET Framework 3.5 SP1 dutch language pack
"msiexec /i ""%01%\NetFX35SP1_x86_nld.msi"" /qn ALLUSERS=1"
[Uninstall.Reg]
;Fix .NET 3.5 SP1 uninstall information
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{CE2CDD62-0124-36CA-84D3-9F4DCF5C5BD9}","SystemComponent",0x10001,00,00,00,00
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{101738D7-D805-37A9-BB91-1F2C351782BF}","SystemComponent",0x10001,00,00,00,00
[KB951847.AddReg]
;KB958481
HKLM,"%INSTUSERDATA_KEY%\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504","DisplayName",0x0,"KB958481"
HKLM,"%INSTUSERDATA_KEY%\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504","LUAEnabled",0x10001,00,00,00,00
HKLM,"%INSTUSERDATA_KEY%\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504","MSI3",0x10001,01,00,00,00
HKLM,"%INSTUSERDATA_KEY%\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504","MoreInfoURL",0x0,"http://www.microsoft.com/"
HKLM,"%INSTUSERDATA_KEY%\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504","PatchType",0x10001,00,00,00,00
HKLM,"%INSTUSERDATA_KEY%\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504","State",0x10001,01,00,00,00
HKLM,"%INSTUSERDATA_KEY%\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504","Uninstallable",0x10001,00,00,00,00
;KB958483
HKLM,"%INSTUSERDATA_KEY%\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37","DisplayName",0x0,"KB958483"
HKLM,"%INSTUSERDATA_KEY%\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37","LUAEnabled",0x10001,00,00,00,00
HKLM,"%INSTUSERDATA_KEY%\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37","MSI3",0x10001,01,00,00,00
HKLM,"%INSTUSERDATA_KEY%\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37","MoreInfoURL",0x0,"http://www.microsoft.com/"
HKLM,"%INSTUSERDATA_KEY%\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37","PatchType",0x10001,00,00,00,00
HKLM,"%INSTUSERDATA_KEY%\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37","State",0x10001,01,00,00,00
HKLM,"%INSTUSERDATA_KEY%\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37","Uninstallable",0x10001,00,00,00,00
;KB958484
HKLM,"%INSTUSERDATA_KEY%\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85","DisplayName",0x0,"KB958484"
HKLM,"%INSTUSERDATA_KEY%\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85","LUAEnabled",0x10001,00,00,00,00
HKLM,"%INSTUSERDATA_KEY%\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85","MSI3",0x10001,01,00,00,00
HKLM,"%INSTUSERDATA_KEY%\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85","MoreInfoURL",0x0,"http://www.microsoft.com/"
HKLM,"%INSTUSERDATA_KEY%\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85","PatchType",0x10001,00,00,00,00
HKLM,"%INSTUSERDATA_KEY%\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85","State",0x10001,01,00,00,00
HKLM,"%INSTUSERDATA_KEY%\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85","Uninstallable",0x10001,00,00,00,00
[KB928416.AddReg]
;KB928416
HKLM,"SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.0\Servicing\Windows Workflow Foundation\NL",,0x0
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 Communication Foundation\1043","InstallSuccess",0x10001,01,00,00,00
HKLM,"SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.0\Setup\Windows Presentation Foundation\NL","InstallSuccess",0x10001,01,00,00,00
HKLM,"SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.0\Setup\Windows Presentation Foundation\NL","Version",0x0,"3.0.6920.0"
HKLM,"SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.0\Setup\Windows Workflow Foundation\NL","InstallSuccess",0x10001,01,00,00,00
[Strings]
INSTUSERDATA_KEY="SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18"
I have modified the msi to remove the setup files and custom uninstall entries. No other modifications except for merging the following hotfixes:
CODE
NDP20SP2-KB958481-x86.exe
NDP30SP2-KB954743-x86.exe
NDP30SP2-KB954744-x86.exe
NDP30SP2-KB958483-x86.exe
NDP35SP1-KB958484-x86.exe
NDP30SP2-KB954743-x86.exe
NDP30SP2-KB954744-x86.exe
NDP30SP2-KB958483-x86.exe
NDP35SP1-KB958484-x86.exe
Filesizes for reference (XP SP3) as displayed in Add/Remove Software Panel
.NET 2.0 SP2 22.7 MB msi, 185,00 MB installed
.NET 3.0 SP2 22.7 MB msi, 169,00 MB installed
.NET 3.5 SP1 8.8 MB msi, 58,94 MB installed
Languagepacks
.NET 2.0 SP2 NLD 1,9 MB msi, 6,18 MB installed
.NET 3.0 SP2 NLD 1,5 MB msi, 3,88 MB installed
.NET 3.5 SP1 NLD 1,0 MB msi, 1,50 MB installed
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:
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.
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:
CODE
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"
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.
it's getting a bit confusing for me... I tried yesterday's script (20090111?) and windows update wants me to install .NET 3.5 SP1 with hotfixes. I had to manually apply the patches for 2.0-3.5 in order to get rid from that entry in windows update.
Do you plan to do this?
Do you plan to do this?
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.
QUOTE (Acheron @ Feb 3 2009, 08:57 AM)
Filesizes for reference (XP SP3) as displayed in Add/Remove Software Panel
.NET 2.0 SP2 22.7 MB msi, 185,00 MB installed
.NET 3.0 SP2 22.7 MB msi, 169,00 MB installed
.NET 3.5 SP1 8.8 MB msi, 58,94 MB installed
.NET 2.0 SP2 22.7 MB msi, 185,00 MB installed
.NET 3.0 SP2 22.7 MB msi, 169,00 MB installed
.NET 3.5 SP1 8.8 MB msi, 58,94 MB installed
Just to confirm (check around) what is the expected filesize shown at Add/Remove panel for .Net 3.5 SP1? I got mine at 27.80MB installed only.
I'm wondering if I'm missing out something since your size is 58.94MB installed.
(My .net slipstream is as follow (XP Pro English):
1.1 - using Roger Spear Pack
2.0 SP2 using .NET Maker synthesize cmd script (I build a standalone pack and install at T13)
3.0 SP3 & 3.5 SP1 , using .NET Maker synthesize cmd script , merged at RunOnceEx/GUIRunonce
Plus your latest KB951847 registry patch (thanks for this), in exe format applied after 3.0 SP3 & 3.5 SP1 has completed installation.)
The 1st 2 programs installed filesize are same as yours, only .NET 3.5 SP1 is different.
==Edit: add screenshot==
See below what I mean. Does anyone getting around 28MB for this item? The thing is that MS Update does not says I'm missing something.
.
QUOTE (strel @ Jan 30 2009, 02:50 AM)
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.
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.
Hi dude so if we use the full redist of 3.5 SP1 then it dont really matter on this update or is it actually needed? I tried to update mine via IE7 like normal and it wouldnt install is it because it is already installed?
Hi strel,
It's a great topic!
I've downloaded your file and started to use with dotnetfx 1.1 + hotfixes + langpack and dotnetfx 3.5 SP1 + Family update + langpack, all hungarian versions.
My INI settings are:
After running your script, it produced these files in OUT1 folder:
DNF11it.exe, 11.8 MB
DNF20SP2hu.exe, 17.8 MB
DNF30SP2hu.exe, 15.4 MB
DNF35SP1hu.exe, 15.2 MB
I realised that DNF11it.exe has an abbreviation for Italian language in the filename, so I went through your command file and realised a tiny - but important - discrepancy. Details are here:
You can check a whole table for locales and codes on this MS page: http://www.microsoft.com/globaldev/nlsweb/default.mspx
If I may suggest, correct this lines in your code, as italian and hungarian users will have incorrect filenames.
Today I will include these installers in my unattended XP installer on VirtualBox and inform you about results.
Good work, nice codes, continue with this enthusiasm!
It's a great topic!
I've downloaded your file and started to use with dotnetfx 1.1 + hotfixes + langpack and dotnetfx 3.5 SP1 + Family update + langpack, all hungarian versions.
My INI settings are:
CODE
PROCESS_DNF1=YES
PROCESS_DNF2=
PROCESS_DNF35_DNF2=YES
PROCESS_DNF35_DNF3=YES
PROCESS_DNF35_DNF35=YES
PROCESS_DNF3_RGBRAST=YES
PROCESS_DNF3_WINIMAGING=YES
PROCESS_DNF3_MSXML6=YES
PROCESS_DNF3_XMLPSSC=YES
PROCESS_LNG_DNF1=YES
PROCESS_LNG_DNF2=
PROCESS_LNG_DNF35_DNF2=YES
PROCESS_LNG_DNF35_DNF3=YES
PROCESS_LNG_DNF35_DNF35=YES
OUTPUT=
MERGE_FRAMEWORKS=
VERBOSITY=SILENT
COMPRESSION_RATIO=low
PROCESS_DNF2=
PROCESS_DNF35_DNF2=YES
PROCESS_DNF35_DNF3=YES
PROCESS_DNF35_DNF35=YES
PROCESS_DNF3_RGBRAST=YES
PROCESS_DNF3_WINIMAGING=YES
PROCESS_DNF3_MSXML6=YES
PROCESS_DNF3_XMLPSSC=YES
PROCESS_LNG_DNF1=YES
PROCESS_LNG_DNF2=
PROCESS_LNG_DNF35_DNF2=YES
PROCESS_LNG_DNF35_DNF3=YES
PROCESS_LNG_DNF35_DNF35=YES
OUTPUT=
MERGE_FRAMEWORKS=
VERBOSITY=SILENT
COMPRESSION_RATIO=low
After running your script, it produced these files in OUT1 folder:
DNF11it.exe, 11.8 MB
DNF20SP2hu.exe, 17.8 MB
DNF30SP2hu.exe, 15.4 MB
DNF35SP1hu.exe, 15.2 MB
I realised that DNF11it.exe has an abbreviation for Italian language in the filename, so I went through your command file and realised a tiny - but important - discrepancy. Details are here:
CODE
:GETDNF11LNG
IF /I "%DNF11LNGSTR%"=="0404" SET DNF11LNGSTR=tw
IF /I "%DNF11LNGSTR%"=="0405" SET DNF11LNGSTR=cs
IF /I "%DNF11LNGSTR%"=="0406" SET DNF11LNGSTR=da
IF /I "%DNF11LNGSTR%"=="0407" SET DNF11LNGSTR=de
IF /I "%DNF11LNGSTR%"=="0408" SET DNF11LNGSTR=el
IF /I "%DNF11LNGSTR%"=="040B" SET DNF11LNGSTR=fi
IF /I "%DNF11LNGSTR%"=="040C" SET DNF11LNGSTR=fr
IF /I "%DNF11LNGSTR%"=="040D" SET DNF11LNGSTR=hu, wrong, correct value is: 040E
IF /I "%DNF11LNGSTR%"=="040E" SET DNF11LNGSTR=it, wrong, correct value is: 0410
IF /I "%DNF11LNGSTR%"=="0411" SET DNF11LNGSTR=ja
IF /I "%DNF11LNGSTR%"=="0412" SET DNF11LNGSTR=ko
IF /I "%DNF11LNGSTR%"=="0413" SET DNF11LNGSTR=nl
IF /I "%DNF11LNGSTR%"=="0414" SET DNF11LNGSTR=no
IF /I "%DNF11LNGSTR%"=="0415" SET DNF11LNGSTR=pl
IF /I "%DNF11LNGSTR%"=="0416" SET DNF11LNGSTR=br
IF /I "%DNF11LNGSTR%"=="0419" SET DNF11LNGSTR=ru
IF /I "%DNF11LNGSTR%"=="041D" SET DNF11LNGSTR=sv
IF /I "%DNF11LNGSTR%"=="041F" SET DNF11LNGSTR=tr
IF /I "%DNF11LNGSTR%"=="0804" SET DNF11LNGSTR=cn
IF /I "%DNF11LNGSTR%"=="0816" SET DNF11LNGSTR=pt
IF /I "%DNF11LNGSTR%"=="0C0A" SET DNF11LNGSTR=es
GOTO :EOF
IF /I "%DNF11LNGSTR%"=="0404" SET DNF11LNGSTR=tw
IF /I "%DNF11LNGSTR%"=="0405" SET DNF11LNGSTR=cs
IF /I "%DNF11LNGSTR%"=="0406" SET DNF11LNGSTR=da
IF /I "%DNF11LNGSTR%"=="0407" SET DNF11LNGSTR=de
IF /I "%DNF11LNGSTR%"=="0408" SET DNF11LNGSTR=el
IF /I "%DNF11LNGSTR%"=="040B" SET DNF11LNGSTR=fi
IF /I "%DNF11LNGSTR%"=="040C" SET DNF11LNGSTR=fr
IF /I "%DNF11LNGSTR%"=="040D" SET DNF11LNGSTR=hu, wrong, correct value is: 040E
IF /I "%DNF11LNGSTR%"=="040E" SET DNF11LNGSTR=it, wrong, correct value is: 0410
IF /I "%DNF11LNGSTR%"=="0411" SET DNF11LNGSTR=ja
IF /I "%DNF11LNGSTR%"=="0412" SET DNF11LNGSTR=ko
IF /I "%DNF11LNGSTR%"=="0413" SET DNF11LNGSTR=nl
IF /I "%DNF11LNGSTR%"=="0414" SET DNF11LNGSTR=no
IF /I "%DNF11LNGSTR%"=="0415" SET DNF11LNGSTR=pl
IF /I "%DNF11LNGSTR%"=="0416" SET DNF11LNGSTR=br
IF /I "%DNF11LNGSTR%"=="0419" SET DNF11LNGSTR=ru
IF /I "%DNF11LNGSTR%"=="041D" SET DNF11LNGSTR=sv
IF /I "%DNF11LNGSTR%"=="041F" SET DNF11LNGSTR=tr
IF /I "%DNF11LNGSTR%"=="0804" SET DNF11LNGSTR=cn
IF /I "%DNF11LNGSTR%"=="0816" SET DNF11LNGSTR=pt
IF /I "%DNF11LNGSTR%"=="0C0A" SET DNF11LNGSTR=es
GOTO :EOF
You can check a whole table for locales and codes on this MS page: http://www.microsoft.com/globaldev/nlsweb/default.mspx
If I may suggest, correct this lines in your code, as italian and hungarian users will have incorrect filenames.
Today I will include these installers in my unattended XP installer on VirtualBox and inform you about results.
Good work, nice codes, continue with this enthusiasm!
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.
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.
QUOTE (strel @ Feb 9 2009, 01:34 PM)
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 of KB951847 from update system. So the update 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.
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 of KB951847 from update system. So the update 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.
Thanks m8 for your rapid answer as always
Im going to update to the current version and rebuild my AIO installer with the new updates and stuff. Thanks for all your hard work strel as always m8! Ive updated now all ran smooth as silk!EDIT - Love being able to make nLite addon for this m8 awesome job simply awesome!
QUOTE (strel @ Feb 9 2009, 09:34 PM)
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.
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.
Thanks for the confirmation. Cheers!
i use SNMsynth to integrate all in one, and output this file: DNF11cn20SP2cn30SP2cn35SP1cn.exe; after installing manually i meet this problem as 0nline.
how to solve this problem?
only install they separately?
QUOTE (0nline @ Jan 30 2009, 03:36 PM)
My recent experience is the same: I've just seen that really it downloads only 16,80 MB and if you verify the update files before their installation then you will see that they are EXACTLY the same that are in the "old" Family Update.
On the other hand if you re-install the old ones ("NDP20SP2-KB958481-x86.exe", "NDP30SP2-KB958483-x86.exe" and "NDP35SP1-KB958484-x86.exe" - that's 2.0 SP2, 3.0 SP2 and 3.5 SP1 update) before to pass through Microsoft Update then MU does not require anything.
It seems that MU suddenly does not recognize the "synthesized" updates: strange issue (for now).
On the other hand if you re-install the old ones ("NDP20SP2-KB958481-x86.exe", "NDP30SP2-KB958483-x86.exe" and "NDP35SP1-KB958484-x86.exe" - that's 2.0 SP2, 3.0 SP2 and 3.5 SP1 update) before to pass through Microsoft Update then MU does not require anything.
It seems that MU suddenly does not recognize the "synthesized" updates: strange issue (for now).
how to solve this problem?
only install they separately?
I've been bashing my head against this script for a couple of days now trying to get one particular problem sorted, and wondered if someone could offer some insight please?
I'm trying to create a fully automated, nlite-based XP SP3 install disk, including the base .NET framework packs (No Language packs, patches etc). It all seems to work perfectly through the script, however when I test the final disk, the .NET 3.5 pack simply isn't installed. These are my current _SNMsyntn.ini settings:
This results in three .7z files (DNF11, DNF20SP1, and DNF35SP1). I tell nlite about them at the "Updates" stage, do a little customization on the OS side of things, and tell it to build the ISO. The finished result is an autoinstalling OS with drivers pre-installed, but only .NET 1.1 and 2.0 in Add/Remove Programs. I've tried various permutations in the .ini file (Such as combining 1.1 and 3.5, fully combining all three into a single output file etc), and various other factors (Like changing their order in the nlite Updates page) with no success. I've even tried using the original .NET 3.5 instead of the SP1 version to no avail. Every single time, Add/Remove Programs (and the Registry agrees) only contains .NET 1.1 and 2.0. Can anyone offer me any advice on where I might be going wrong please?
Thanks in advance.
Ps. In case it may make a difference, the contents of my SNMsynth folder are as follows:
I'm trying to create a fully automated, nlite-based XP SP3 install disk, including the base .NET framework packs (No Language packs, patches etc). It all seems to work perfectly through the script, however when I test the final disk, the .NET 3.5 pack simply isn't installed. These are my current _SNMsyntn.ini settings:
CODE
PROCESS_DNF1=YES
PROCESS_DNF2=YES
PROCESS_DNF35_DNF2=
PROCESS_DNF35_DNF3=
PROCESS_DNF35_DNF35=YES
PROCESS_DNF3_RGBRAST=YES
PROCESS_DNF3_WINIMAGING=YES
PROCESS_DNF3_MSXML6=YES
PROCESS_DNF3_XMLPSSC=YES
PROCESS_LNG_DNF1=
PROCESS_LNG_DNF2=
PROCESS_LNG_DNF35_DNF2=
PROCESS_LNG_DNF35_DNF3=
PROCESS_LNG_DNF35_DNF35=
OUTPUT=ADDON
MERGE_FRAMEWORKS=FULL
VERBOSITY=SILENT
COMPRESSION_RATIO=LOW
PROCESS_DNF2=YES
PROCESS_DNF35_DNF2=
PROCESS_DNF35_DNF3=
PROCESS_DNF35_DNF35=YES
PROCESS_DNF3_RGBRAST=YES
PROCESS_DNF3_WINIMAGING=YES
PROCESS_DNF3_MSXML6=YES
PROCESS_DNF3_XMLPSSC=YES
PROCESS_LNG_DNF1=
PROCESS_LNG_DNF2=
PROCESS_LNG_DNF35_DNF2=
PROCESS_LNG_DNF35_DNF3=
PROCESS_LNG_DNF35_DNF35=
OUTPUT=ADDON
MERGE_FRAMEWORKS=FULL
VERBOSITY=SILENT
COMPRESSION_RATIO=LOW
This results in three .7z files (DNF11, DNF20SP1, and DNF35SP1). I tell nlite about them at the "Updates" stage, do a little customization on the OS side of things, and tell it to build the ISO. The finished result is an autoinstalling OS with drivers pre-installed, but only .NET 1.1 and 2.0 in Add/Remove Programs. I've tried various permutations in the .ini file (Such as combining 1.1 and 3.5, fully combining all three into a single output file etc), and various other factors (Like changing their order in the nlite Updates page) with no success. I've even tried using the original .NET 3.5 instead of the SP1 version to no avail. Every single time, Add/Remove Programs (and the Registry agrees) only contains .NET 1.1 and 2.0. Can anyone offer me any advice on where I might be going wrong please?
Thanks in advance.
Ps. In case it may make a difference, the contents of my SNMsynth folder are as follows:
CODE
7za.exe
7zSD.sfx
dotnetfx.exe
dotnetfx35.exe
NetFx20SP1_x86.exe
README.TXT
SNMsynth.cmd
_SNMsynth.ini
7zSD.sfx
dotnetfx.exe
dotnetfx35.exe
NetFx20SP1_x86.exe
README.TXT
SNMsynth.cmd
_SNMsynth.ini
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.
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.
Ok, guys, I want to share my own experince from what I've read in this thread and my understanding of making separate merged installers. Your methods may be different since my requirements are different from yours! Simple as that
I will highly appreciate your comments as I'm a complete newbie in .NET processing although have a good experince with unattended XPCD. After my first post here (page 4), I've decided to take some time to read about your thoughts and problems in order to ask less questions (my post was toooo long. Thanks strel for patience reading it!) but to make a complete merged installer(s) for my unattended setup with no errors whatsoever.
So, what I wanted from the synthesis was (I don't use any language packs since I'm comfortable with default English versions of .NET):
1) To compile a merged framework for .NET 1.1 w/ all hotfixes.
Why I need a separate installer for .NET 1.1? Because I've read above that .NET 3.5 causes two tiny Event Viewer erros when installed at T-13 ("svcpack method", or when using full merge/AIO installer). Therefore, I thought it would be a good idea to compile .NET 1.1 to be used with n-Lite (svcpack) and then create a separate merged installer for 3.5 w/ all hotfixes to use at first logon (I prefer "RunOnceEx method"). Since the latter pack (231Mb) contains .NET 2.0 SP2, 3.0 SP2 and 3.5 SP1, I didn't feel a need to merge 1.1 and 2.0, and this assumption also made me confident about the method I've chosen. It also implied that I would have two (2) runs for compilation - i) .NET 1.1 full; ii) .NET 3.5 full.
Ok, now to realise the first step, I have put the following files into a temporary folder with required .ini and .7z files, as instructed by strel on page 1: dotnetfx.exe; NDP1.1sp1-KB867460-X86.exe; and NDP1.1sp1-KB928366-X86.exe. Then, I've edited the script as follows:
In this configuration I've been able to compile .NET 1.1 with all hotfixes.
2) To compile a merged framework for .NET 3.5 SP1 Full Redistributable w/ all hotfixes.
This time I used these files (dotnetfx35.exe; NDP20SP2-KB958481-x86.exe; NDP30SP2-KB958483-x86.exe; and NDP35SP1-KB958484-x86.exe) and have changed the script as follows and re-run "SNMsynth.cmd":
After running SNMsynth.cmd twice, I got two folders (OUT1 and OUT2) with individual n-Lite addons inside: DNF11.7z (.NET 1.1+hotfixes) and DNF20SP230SP235SP1.7z (.NET 3.5 SP1+hotfixes). Although I've not tested them during setup, I'm (a bit) sure that this meets my requirements and will install seamlessly. However, I would like to clarify two questions based upon Caspean's post re: .NET 1.1 above:
i) does it mean that hotfixes for 1.1 are hotfixes and not SP (sorry if it sounds stupid when one cannot distinguish between a hotfix and a SP but they both contain "sp" in their names)?;
ii) if not, does NDP1.1sp1-KB928366-X86.exe supersede/contain NDP1.1sp1-KB867460-X86.exe?
Hope this helps! Anyone to comment/deny/approve my method? Appreciated!
I will highly appreciate your comments as I'm a complete newbie in .NET processing although have a good experince with unattended XPCD. After my first post here (page 4), I've decided to take some time to read about your thoughts and problems in order to ask less questions (my post was toooo long. Thanks strel for patience reading it!) but to make a complete merged installer(s) for my unattended setup with no errors whatsoever.
So, what I wanted from the synthesis was (I don't use any language packs since I'm comfortable with default English versions of .NET):
1) To compile a merged framework for .NET 1.1 w/ all hotfixes.
Why I need a separate installer for .NET 1.1? Because I've read above that .NET 3.5 causes two tiny Event Viewer erros when installed at T-13 ("svcpack method", or when using full merge/AIO installer). Therefore, I thought it would be a good idea to compile .NET 1.1 to be used with n-Lite (svcpack) and then create a separate merged installer for 3.5 w/ all hotfixes to use at first logon (I prefer "RunOnceEx method"). Since the latter pack (231Mb) contains .NET 2.0 SP2, 3.0 SP2 and 3.5 SP1, I didn't feel a need to merge 1.1 and 2.0, and this assumption also made me confident about the method I've chosen. It also implied that I would have two (2) runs for compilation - i) .NET 1.1 full; ii) .NET 3.5 full.
Ok, now to realise the first step, I have put the following files into a temporary folder with required .ini and .7z files, as instructed by strel on page 1: dotnetfx.exe; NDP1.1sp1-KB867460-X86.exe; and NDP1.1sp1-KB928366-X86.exe. Then, I've edited the script as follows:
CODE
PROCESS_DNF1=YES <------ to compile a full 1.1 installer only; other settings remain untouched.
PROCESS_DNF2=
PROCESS_DNF35_DNF2=
PROCESS_DNF35_DNF3=
PROCESS_DNF35_DNF35=
PROCESS_DNF2=
PROCESS_DNF35_DNF2=
PROCESS_DNF35_DNF3=
PROCESS_DNF35_DNF35=
In this configuration I've been able to compile .NET 1.1 with all hotfixes.
2) To compile a merged framework for .NET 3.5 SP1 Full Redistributable w/ all hotfixes.
This time I used these files (dotnetfx35.exe; NDP20SP2-KB958481-x86.exe; NDP30SP2-KB958483-x86.exe; and NDP35SP1-KB958484-x86.exe) and have changed the script as follows and re-run "SNMsynth.cmd":
CODE
PROCESS_DNF1=
PROCESS_DNF2=
PROCESS_DNF35_DNF2=YES <------ to include NDP20SP2-KB958481-x86.exe.
PROCESS_DNF35_DNF3=YES <------ to include NDP30SP2-KB958483-x86.exe.
PROCESS_DNF35_DNF35=YES <------ to include NDP35SP1-KB958484-x86.exe.
PROCESS_DNF2=
PROCESS_DNF35_DNF2=YES <------ to include NDP20SP2-KB958481-x86.exe.
PROCESS_DNF35_DNF3=YES <------ to include NDP30SP2-KB958483-x86.exe.
PROCESS_DNF35_DNF35=YES <------ to include NDP35SP1-KB958484-x86.exe.
After running SNMsynth.cmd twice, I got two folders (OUT1 and OUT2) with individual n-Lite addons inside: DNF11.7z (.NET 1.1+hotfixes) and DNF20SP230SP235SP1.7z (.NET 3.5 SP1+hotfixes). Although I've not tested them during setup, I'm (a bit) sure that this meets my requirements and will install seamlessly. However, I would like to clarify two questions based upon Caspean's post re: .NET 1.1 above:
i) does it mean that hotfixes for 1.1 are hotfixes and not SP (sorry if it sounds stupid when one cannot distinguish between a hotfix and a SP but they both contain "sp" in their names)?;
ii) if not, does NDP1.1sp1-KB928366-X86.exe supersede/contain NDP1.1sp1-KB867460-X86.exe?
Hope this helps! Anyone to comment/deny/approve my method? Appreciated!
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.
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.
strel, thank you very very much, mate!!! You have demonstrated another example of patience reading through my confusing sentences 
The last question - can I also use these settings, if I want to install FULL .NET package (1.1+2.0+3.0+3.5) at first logon phase, NOT T-13:
It looks like I connect two pieces of settings together, as shown above, to make a single full installer this time. What I want to achieve is to get a single installer which installs at first logon and has no errors in Event Viewer. As the logic suggests, this scheme should also work and prove true since "5 is a product of 2+3 OR 3+2 - the order of items doesn't matter"!
The last question - can I also use these settings, if I want to install FULL .NET package (1.1+2.0+3.0+3.5) at first logon phase, NOT T-13:
CODE
PROCESS_DNF1=YES
PROCESS_DNF2=
PROCESS_DNF35_DNF2=YES
PROCESS_DNF35_DNF3=YES
PROCESS_DNF35_DNF35=YES
PROCESS_DNF2=
PROCESS_DNF35_DNF2=YES
PROCESS_DNF35_DNF3=YES
PROCESS_DNF35_DNF35=YES
It looks like I connect two pieces of settings together, as shown above, to make a single full installer this time. What I want to achieve is to get a single installer which installs at first logon and has no errors in Event Viewer. As the logic suggests, this scheme should also work and prove true since "5 is a product of 2+3 OR 3+2 - the order of items doesn't matter"!
Sorry, double post 
I created .net 2-3.5 addon with all updates and langpack, but windows update show langpack for 3.0 (Installation fail....) and family update. Is there a way, how disable show these updates? I think via registry tweak....
Hi I've downloaded all relevant .NET files plus hotfixes and got 7za.exe and SNMsynth.zip all extracted into the single folder.
I'm not entirely sure what I should change with the INI file, I have a slipstreamed XP SP3 image (x86) and want to add ALL .NET versions.
Please can you tell me what I need to change to make this work right! I plan to use nLite to slipstream all these and then add IE7, WMP11 and dX Nov 08 to the nlite install.
I am using:
_SNMsynth.ini
7za.exe
7zSD.sfx
dotnetfx.exe
dotnetfx35.exe
NDP1.1sp1-KB867460-X86.exe
NDP1.1sp1-KB928366-X86.exe
NDP20SP2-KB958481-x86.exe
NDP30SP2-KB958483-x86.exe
NDP35SP1-KB958484-x86.exe
SNMsynth.cmd
If you could upload an edited .INI I would be very grateful, or just to say if I need any changes. Thank you.
Regards
Xenos
EDIT: I don't need any language packs I just use plain old english, should simplify it a bit.
I'm not entirely sure what I should change with the INI file, I have a slipstreamed XP SP3 image (x86) and want to add ALL .NET versions.
Please can you tell me what I need to change to make this work right! I plan to use nLite to slipstream all these and then add IE7, WMP11 and dX Nov 08 to the nlite install.
I am using:
_SNMsynth.ini
7za.exe
7zSD.sfx
dotnetfx.exe
dotnetfx35.exe
NDP1.1sp1-KB867460-X86.exe
NDP1.1sp1-KB928366-X86.exe
NDP20SP2-KB958481-x86.exe
NDP30SP2-KB958483-x86.exe
NDP35SP1-KB958484-x86.exe
SNMsynth.cmd
If you could upload an edited .INI I would be very grateful, or just to say if I need any changes. Thank you.
Regards
Xenos
EDIT: I don't need any language packs I just use plain old english, should simplify it a bit.
In all seriousness, isn't there just a .CAB out there for those of us who don't really want to waste a few hours Come on, someone has to have a working .CAB out there I had one, but lost my **** NAS over the last weekend, so now I'm rebuilding plugins. But there was, at one point, a pretty brilliant AIO add on for all the dot.net's.
Come on, someone has to have a working .CAB out there I had one, but lost my **** NAS over the last weekend, so now I'm rebuilding plugins. But there was, at one point, a pretty brilliant AIO add on for all the dot.net's.
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:
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.
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:
CODE
PROCESS_DNF1=YES
PROCESS_DNF2=
PROCESS_DNF35_DNF2=YES
PROCESS_DNF35_DNF3=YES
PROCESS_DNF35_DNF35=YES
...
OUTPUT=ADDON
MERGE_FRAMEWORKS=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.
strel... im sure there are many peeps like me that randomly search across the web and these forums trying to find answers and methods of creating a personalised unattended install. i thought i would not leave silently and give you feedback, thankyou very much.
i have been trying to merge .net 2 to my slipstreamed xp sp3 cd using nlite for a few days now. before this i had never used (or heard of) nlite and i have very limited experience with computing... i stumbled across this forum during my research and spent days reading threads, downloading, installing, following guides, copying, pasting, getting lost, head scratching, head aching... until i eventually stumbled across this thread. i read through your instructions carefully and hey presto... job done! though i'l admit that i messed up the first time (i was getting errors from nlite stating it was an unexpected type of hotfix) because i was putting the exe file in the nlite setup instead of the zip file
so basically i thought rather than just use the info and move on i thought id stop by and say thanks... now im off to try and work out why my security update add-ons keep corrupting my install and how to include the WGA malarky on the disc!
Joel
i have been trying to merge .net 2 to my slipstreamed xp sp3 cd using nlite for a few days now. before this i had never used (or heard of) nlite and i have very limited experience with computing... i stumbled across this forum during my research and spent days reading threads, downloading, installing, following guides, copying, pasting, getting lost, head scratching, head aching... until i eventually stumbled across this thread. i read through your instructions carefully and hey presto... job done! though i'l admit that i messed up the first time (i was getting errors from nlite stating it was an unexpected type of hotfix) because i was putting the exe file in the nlite setup instead of the zip file
so basically i thought rather than just use the info and move on i thought id stop by and say thanks... now im off to try and work out why my security update add-ons keep corrupting my install and how to include the WGA malarky on the disc!
Joel
@strel
Why does "Microsoft .NET Framework 3.5 Service Pack 1 and .NET Framework 3.5 Family Update (KB951847) x86" show up in WU even if I installed the full package created using your latest SNMsynth.cmd?
WU downloads just these three: NDP20SP2-KB958481-x86, NDP30SP2-KB958483-x86, NDP35SP1-KB958484-x86 (=KB951847 - family update suite), a little over 17 mb.
I tested this on two different machines. I used net 3.5 SP1 plus those three patches mentioned above.
Any ideas?
Thanks.
Why does "Microsoft .NET Framework 3.5 Service Pack 1 and .NET Framework 3.5 Family Update (KB951847) x86" show up in WU even if I installed the full package created using your latest SNMsynth.cmd?
WU downloads just these three: NDP20SP2-KB958481-x86, NDP30SP2-KB958483-x86, NDP35SP1-KB958484-x86 (=KB951847 - family update suite), a little over 17 mb.
I tested this on two different machines. I used net 3.5 SP1 plus those three patches mentioned above.
Any ideas?
Thanks.
Because this should be added to registry to avoid the family update KB951847.
@strel
You're the man.
You're the man.
@strel
Sorry mate fo not reading the posts above.
Are those registry keys just a workaround or those patches do really get installed?
Sorry mate fo not reading the posts above.
Are those registry keys just a workaround or those patches do really get installed?
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.
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.
QUOTE (kbench @ Mar 11 2009, 08:23 PM)
Your description says that it is supported for Windows 2003 Server. However when I execute SNMsynth.cmd
I receive an error message that says
ERROR: This script is only for using under windows 2000/XP/2003. Press any key to continue.
...
I receive an error message that says
ERROR: This script is only for using under windows 2000/XP/2003. Press any key to continue.
...
Sorry, my fault. In SNMsynth.cmd substitute line 21:
CODE
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:
CODE
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.
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!
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!
Hello Strel,
I can't find _SNMsynth.ini in the new package. There is a _SNMsynth.cmd, do we use this instead?
I can't find _SNMsynth.ini in the new package. There is a _SNMsynth.cmd, do we use this instead?
This is because I messed things with the .zip file. It's been fixed now.
Redownload.
Redownload.
AVG reports "potentially malicious HackTool.GOS" inside KB951847_FIX.mst" file 
(in the Binary.KB951847_FIX executable in the .mst file).
Is it a false positive ?
(in the Binary.KB951847_FIX executable in the .mst file).Is it a false positive ?
[quote name='seebee' post='842244' date='Mar 14 2009, 01:51 AM']AVG reports "potentially malicious HackTool.GOS" inside KB951847_FIX.mst" file (in the Binary.KB951847_FIX executable in the .mst file).
EDIT:
IT WAS A FALSE POSITIVE!.
But Nowadays the .mst file doesn't include an .exe file embedded anymore.
(in the Binary.KB951847_FIX executable in the .mst file).EDIT:
IT WAS A FALSE POSITIVE!.
But Nowadays the .mst file doesn't include an .exe file embedded anymore.
The file _SNMsynth.ini contains the following:
After start SNMsynth.cmd I receive an error:
To previous version SNMsynth.cmd of such error does not occur.
What is the problem?
CODE
PROCESS_DNF1=YES
PROCESS_DNF2=
PROCESS_DNF35_DNF2=
PROCESS_DNF35_DNF3=
PROCESS_DNF35_DNF35=
PROCESS_DNF3_RGBRAST=YES
PROCESS_DNF3_WINIMAGING=YES
PROCESS_DNF3_MSXML6=YES
PROCESS_DNF3_XMLPSSC=YES
PROCESS_LNG_DNF1=YES
PROCESS_LNG_DNF2=
PROCESS_LNG_DNF35_DNF2=
PROCESS_LNG_DNF35_DNF3=
PROCESS_LNG_DNF35_DNF35=
OUTPUT=
MERGE_FRAMEWORKS=
VERBOSITY=
COMPRESSION_RATIO=
PROCESS_DNF2=
PROCESS_DNF35_DNF2=
PROCESS_DNF35_DNF3=
PROCESS_DNF35_DNF35=
PROCESS_DNF3_RGBRAST=YES
PROCESS_DNF3_WINIMAGING=YES
PROCESS_DNF3_MSXML6=YES
PROCESS_DNF3_XMLPSSC=YES
PROCESS_LNG_DNF1=YES
PROCESS_LNG_DNF2=
PROCESS_LNG_DNF35_DNF2=
PROCESS_LNG_DNF35_DNF3=
PROCESS_LNG_DNF35_DNF35=
OUTPUT=
MERGE_FRAMEWORKS=
VERBOSITY=
COMPRESSION_RATIO=
After start SNMsynth.cmd I receive an error:
To previous version SNMsynth.cmd of such error does not occur.
What is the problem?
Thx gora.
I left a few posibilities uncovered in a conditional statement, it's fixed now.
I left a few posibilities uncovered in a conditional statement, it's fixed now.
I've reuploaded cause I forgot to change ECHO ON to ECHO OFF at the beggining of the file. Those 2 of you who downloaded can change it manually or redownload... or show everything the script executes going by.
F***
It's not my day, wrong encoding. Sorry.
Please redownload.
It's not my day, wrong encoding. Sorry.
Please redownload.
Not important, but I reuploaded again to correct a cosmetic issue in the error message for the absence of 7za.exe
Thx ferk
Thx ferk
QUOTE (strel @ Mar 13 2009, 08:09 PM)
IT IS A FALSE POSITIVE!
AV is failing identifying the 2 .vbs inside this file in the form of .exe files:
and
So don't worry.
AV is failing identifying the 2 .vbs inside this file in the form of .exe files:
CODE
Dim blnRunning, colProcesses
blnRunning = True
Do Until Not blnRunning
Set colProcesses = GetObject( "winmgmts:{impersonationLevel=impersonate}" ).ExecQuery( "Select * From Win32_Process Where Name = '" & "mscorsvw.exe" & "'" )
WScript.Sleep 100
If colProcesses.Count = 0 Then
blnRunning = False
End If
Loop
Set WshShell = CreateObject( "WScript.Shell" )
WshShell.RegWrite "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\InstallProperties\LocalPackage", WshShell.ExpandEnvironmentStrings( "%SYSTEMROOT%\Installer\39d37.msi" ), "REG_SZ"
WshShell.RegWrite "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504\State", "1", "REG_DWORD"
WshShell.RegWrite "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0DC1503A46F231838AD88BCDDC8E8F7C\InstallProperties\LocalPackage", WshShell.ExpandEnvironmentStrings( "%SYSTEMROOT%\Installer\39d3e.msi" ), "REG_SZ"
WshShell.RegWrite "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37\State", "1", "REG_DWORD"
WshShell.RegWrite "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5\SP", "1", "REG_DWORD"
WshShell.RegWrite "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\InstallProperties\LocalPackage", WshShell.ExpandEnvironmentStrings( "%SYSTEMROOT%\Installer\39d44.msi" ), "REG_SZ"
WshShell.RegWrite "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85\State", "1", "REG_DWORD"
Set WshShell = Nothing
blnRunning = True
Do Until Not blnRunning
Set colProcesses = GetObject( "winmgmts:{impersonationLevel=impersonate}" ).ExecQuery( "Select * From Win32_Process Where Name = '" & "mscorsvw.exe" & "'" )
WScript.Sleep 100
If colProcesses.Count = 0 Then
blnRunning = False
End If
Loop
Set WshShell = CreateObject( "WScript.Shell" )
WshShell.RegWrite "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\InstallProperties\LocalPackage", WshShell.ExpandEnvironmentStrings( "%SYSTEMROOT%\Installer\39d37.msi" ), "REG_SZ"
WshShell.RegWrite "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\DC3BF90CC0D3D2F398A9A6D1762F70F3\Patches\C3CFBEEB1B8483A43A5C18AB91FDF504\State", "1", "REG_DWORD"
WshShell.RegWrite "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0DC1503A46F231838AD88BCDDC8E8F7C\InstallProperties\LocalPackage", WshShell.ExpandEnvironmentStrings( "%SYSTEMROOT%\Installer\39d3e.msi" ), "REG_SZ"
WshShell.RegWrite "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37\State", "1", "REG_DWORD"
WshShell.RegWrite "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5\SP", "1", "REG_DWORD"
WshShell.RegWrite "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\InstallProperties\LocalPackage", WshShell.ExpandEnvironmentStrings( "%SYSTEMROOT%\Installer\39d44.msi" ), "REG_SZ"
WshShell.RegWrite "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85\State", "1", "REG_DWORD"
Set WshShell = Nothing
and
CODE
Set WshShell = CreateObject( "WScript.Shell" )
WshShell.RegDelete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0DC1503A46F231838AD88BCDDC8E8F7C\InstallProperties\"
WshShell.RegDelete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37\"
WshShell.RegDelete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\"
WshShell.RegDelete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0DC1503A46F231838AD88BCDDC8E8F7C\"
WshShell.RegDelete "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5\"
WshShell.RegDelete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\InstallProperties\"
WshShell.RegDelete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85\"
WshShell.RegDelete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\"
WshShell.RegDelete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\"
Set WshShell = Nothing
WshShell.RegDelete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0DC1503A46F231838AD88BCDDC8E8F7C\InstallProperties\"
WshShell.RegDelete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\E54DA494170E9184E8511E40F1FB0F37\"
WshShell.RegDelete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0DC1503A46F231838AD88BCDDC8E8F7C\Patches\"
WshShell.RegDelete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\0DC1503A46F231838AD88BCDDC8E8F7C\"
WshShell.RegDelete "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5\"
WshShell.RegDelete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\InstallProperties\"
WshShell.RegDelete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\2F2AEE7ADCFB45A45A57B7187A686E85\"
WshShell.RegDelete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\Patches\"
WshShell.RegDelete "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\26DDC2EC4210AC63483DF9D4FCC5B59D\"
Set WshShell = Nothing
So don't worry.
It's the first one only, compiled by ExeScript (from Everstrike Software) and compressed with UPX that triggers the AVG alert (even if uncompressed with UPX), the second being in readable source form.
By the way, thank you very much for this much-needed .Net packager
Probably is caused by the loop in the script. Check post #141 again, I've included definitive results.
I'm getting error uninstalling 2.0 SP2 and 3.0 SP2 and probably 3.5 SP1, versions using KB951847_FIX.mst not finding the .msi package on some scenarios, is not a problem of the .mst file.
But I fixed it yet and there's a new update!
I recomend that if you installed from installers/add-ons built with 20090313 or 20090314 of the script, you use the 20090315 new version to build new installers keeping the previous; uninstall 2.0 SP2, 3.0 SP2, 3.5 SP1 in case you can do it without errors, and reinstall.
In case uninstall process can't find .msi file, you can:
- If you kept the previous installers, unzip them and when the popup appear asking you for the .msi file, feed it with the corresponding .msi you've just unzipped.
- If yoy didn't keep the installers try the same procedure of the last point with the new installers.
- If that fail search in C:\windows\installer\ for a file to feed the popup, search 2019 KB files for .NET 2.0 SP2 and 691 KB files for .NET 3.0 SP2.
Hope you don't need that. Ask me if you have any problem.
But I fixed it yet and there's a new update!
I recomend that if you installed from installers/add-ons built with 20090313 or 20090314 of the script, you use the 20090315 new version to build new installers keeping the previous; uninstall 2.0 SP2, 3.0 SP2, 3.5 SP1 in case you can do it without errors, and reinstall.
In case uninstall process can't find .msi file, you can:
- If you kept the previous installers, unzip them and when the popup appear asking you for the .msi file, feed it with the corresponding .msi you've just unzipped.
- If yoy didn't keep the installers try the same procedure of the last point with the new installers.
- If that fail search in C:\windows\installer\ for a file to feed the popup, search 2019 KB files for .NET 2.0 SP2 and 691 KB files for .NET 3.0 SP2.
Hope you don't need that. Ask me if you have any problem.
Hi there!
For me there is still problem integrating .NET 1.1 hotfixes. They popup, like when I use hotfix.exe /? switch, but using version 20090111 everything is OK.
For me there is still problem integrating .NET 1.1 hotfixes. They popup, like when I use hotfix.exe /? switch, but using version 20090111 everything is OK.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.