To summarize 2728738 is superseded by 2719375 2731847 is superseded by 2724781-v2 2727118 is OK 2691442 is superseded by 2722727 2696718 is superseded by 2703811-v2 McRip Added: 2724781-v2, 2727118 Removed: (2633127?), 2691442, 2696718, 2724781 komm Added: Removed: KB2714030-v2, 2728738 It's good?
With so many hotfixes and updates, it can get confusing, which is why i believe it's time for MS to release SP2 soon! It would certainly make all our lives easier for awhile.
thanks... I looked at 2647753v3 and compared it to v2... the patch contents are the same as MS have said.... I went ahead and installed the v3 and no issues so far interestingly, v3 is still on the microsoft update catalog site!
@McRip I see you have updated today your repo with the following... I have one observation and three questions: 1. You've forgot to remove KB2731847 from the x64 folder; 2. What's the status on KB2633127-v2, KB2691442 and KB2696718 ? Since you didn't remove them, they aren't superseeded? 3. komm specifically stated that KB2647753-v3 causes problems, the latest official version from Microsoft is still v2, but you've still updated it from v2 to v3. Why? 4. You haven't added KB2727118 to the 18.08.2012 changelog, but it's not in the .7z! Why? It's confusing... please move it to the 18.08.2012 changelog.
I believe so. Looks like 2714030 is only partially superseded. The main bulk of its size covers shell32, which is superseded. The part that isn't has got to do with offline files api.
KB2647753-v3 does not cause issues. It's all about WindowsUpdate. That means if you use Windows Update, it installs version 2 and not v3. Version 2 has some faulty programming issues which installs components for kernel 7.1 but 7.1 is not available. v3 is the corrected version which only has components for 6.1. I have seen several updates in the last two weeks which do have this issue. WU also searches in the Servicing Stack. And if it find the 7.1 component WU will offer the update again and again. However, this does not affect all machines. Only a few machines had been affected.
@McRip Two questions still unanswered: 1. What's the status on KB2633127-v2? Since you didn't remove it, it's not superseeded? 2. KB2727118 is in the 17.08.2012 changelog, but it's not in the .7z archive from 17.08.2012!!! Why? It's VERY confusing... please move it to the 18.08.2012 changelog. Right now I'm making a Rain Man check - downloaded both komm and McRip folders, and see what are the differences. BRB with results - first with the x86 ones
I knew that. However, people who download the archive may think that ALL the changes from the 17.08.2012 changelog is contained by the .7zip archive from the same date. So once again, you should move it to the 18.08.2012 so people won't skip that update. Thanks for the answers btw