0nline

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)...

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.

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...

Please, install on your current machine all (supported) Framework versions you want to deploy. Create a working folder ("Framework", for example) in the root of your system drive. Copy all full executables you've used in your previous installation in your working folder and also extract "SNMsynth.zip" and "7za464.zip" into it. Run "SNMsynth.cmd": the default settings will merge your Framework versions in a single executable (really in a RAR archive that you can use in nLite-d installs as Add-on or, extracting the executable, within Windows or in nLite-d installs running it At First Log-on). If nLite-d as Add-on then a couple of errors appear (3.5 related) in Event Viewer (it seems they imply no issues), if running at first log-on instead (or wiyhin Windows) then the two errors will disappear. If you need 1.1 version and related updates too then in order to avoid a (double) restart the script will automatically install it at the process ending. I've successfully merged "Microsoft .NET Framework 3.5 SP1" ("dotnetfx35.exe" - 231 MB - including 2.0 SP1, 3.0 SP1 and 3.5 SP1) plus its "Family Update" ("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) in a single executable (50,8 MB) that perfectly and silently work in a nLite-d install at first log-on (I do not need Language Pack then I do not know about it but I'm sure that somebody knows how to). Please note that if you install also the latest "DirectX End-User Runtime" in a your possibly nLite-d install then DirectX would be installed after .NET Framework in order to correctly install "DirectX for Managed Code" components. BTW1: really in the first post you can read also about the stated support for 2.0 SP1 ("NetFx20SP1_x86.exe"), but IMO I think that it probably is useless [and then also (my previously suggested) 2.0 SP2 ("NetFx20SP2_x86.exe") support would be so] considering that the support for .NET Framework 2.0 is not (yet?) available... BTW2: I was trying an app (NovaShield - "NovaShield_xp_release_2_5_8.exe") that at any case requests Framework 2.0 SP1 although the SP1 would must be already correctly installed, but probably that is an isolated issue that specific program-related.

Hi, everyone! Just for better clarity, my previous whistle emoticon [] meant: << please, strel, existing already the support for "NetFx20SP1_x86.exe", could you now add also the support for "NetFx20SP2_x86.exe" just released (1/16/2009) from Microsoft? >> Thank you, at any case! online

Great stuff: all works so fine for me at the first shot, many thanks! (My first post here: hi, everyone!) Microsoft .NET Framework 2.0 Service Pack 2 is out... Cheers