Hi, KB2553270 contains 32 language specific .msp files and they're all in the repo. Look through what you have for files named proof-xx-xx.msp. The English language ver really only needs proof-en-us.msp, proof-es-es.msp & proof-fr-fr.msp, but if you're running a different language, make sure you have all of them (or at least the .msp file specific for your language, in addition to the other three).
I have a question: how can i integrate the update/hotfix into a 32/64bit win7 Italian all versions USB that has already SP1? Is there a way? Or is tehere a way to automatic install those packs after the first installation? Thanks
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.