I did but I just pulled it, having issues integrating the new update into extended (it switches the guid of extended package to the client one) I guess this is what happens when you rush a patch Edit: I think its my fault, it appears the guid from the last msp you integrate is given to the msi...so because they shared the same msp and it was the last one I integrated into both client/extended installers they were conflicting Edit2: updated dotNET4 installer rev2 is up, all should be OK now
newer kb2615128 shell32.dll 21869 ? v2 and v3 here, get v3 support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=2615128
The 2615128 I downloaded via the link posted is v3; and the files correspond to that also posted as v3
@RickSteele, I think you misunderstand. The rev2 in "12.29.2011 + 02 meaning rev2" has nothing to do with the internal files. ricktendo64 had just made a slight mistake when he first released the latest installer. So when he fixed it and re-released it, he released it as rev2. At least I think that is correct. Cheers and Reagrds
Komm, no problem- v3 was just released a couple days ago. I haven't run the Update Checker in a while so I missed 2615128 being flagged as an old ver by v2. Regarding the Update Checker, I have a suggestion- on my system, it flags about 20 updates for optional, uninstalled components (like IIS, BPA, NFS, SUA, MSMQ, SNMP and Hyper-V) as "ADD | Update is missing!" so I end up looking up those KB #'s to see what they are. It'd be useful if they could be flagged with a description that notes they're for an optional component, so those updates could be skipped over quickly while reviewing the Checker's results. Just a suggestion- it's still a great tool as is.
@Ricktendo64, I was curious if it is okay to just run the new .NET 4 installer directly over an old version? Will that leave anything behind that should have been cleaned up? Or do we need to uninstall .NET client and uninstall .NET extended from Program and Features first? and then install the Updated .NET 4 installer? If we can just run the update without uninstalling the old .NET 4, will it always be that way or will there be some message explaining if that changes?
@PointZero Please send me your packages.txt to the support e-mail address at the end of the reference. I will look if there is a way to flag those updates. I created KUC to check my now 27 wim-files for servers and clients. In those wims, all updates should be included for all possibilities. Therefore, the main target is/was: Do not miss any and it is better to have one to much than one to less. However, I understand your wish. You want a quick overview that matches to your needs. I extended the last version of KUC (and the update list) with a lot of new information about the updates. (BPA and Hyper-V should already have that info) To flag the other optional components I need a list of all updates (superseded or not) that point to them.
Thanks komm. Just to summarize: KUC says 20 or so updates for optional Windows components (IIS, NFS, MSMQ, etc) are missing and should be installed even when those Windows components are not installed. The updates won't apply if those Windows components are not installed. You do have descriptions for many updates already. But only the KB # is listed for those 20 updates, so the user needs to look up those KB's to discover they're actually not applicable. My suggestion was to add a description to those 20 updates saying they're for optional components and might not be applicable in all cases, so users wouldn't need to look them up. This is not a big deal It's a convenience issue. But since a majority of KUC's users probably won't have those Windows components installed, the suggestion may benefit others as well. I'll send you the packages.txt and a list of the 20 updates.