@ Ms. Crybaby RicaNeaga I see you love bolt letters and jokes, so never mind this: Of course you may call me "Mr. Professor Komm". But you should not be sad, if I call you "Ms. Crybaby RicaNega". You made some statements like: "2798787 - present in RSAT sub-folder - it's actually a Group Policy update, needs to be moved to that sub-folder" That’s not a question! If you want to ask something you have to use this “?” symbol. That meant for me, there is someone -like "abbodi1406"- who looked inside the updates and found I made a mistake. No problem. So I use some of my precious time, I normally need to teach people who are not as educated as I am, to inspect the problem. For that, I have to go in my dark cellar room, nobody is there, just me and my computer. And what must I find out? My lovely sunshine, "Ms. Crybaby RicaNega", did nothing else as posting an un-checked statement. Ok, is said to myself - You know, in the dark cellar I'm alone, so I have to talk to memyselfi. - "Ms. Crybaby" was a little bit un-concentrated. She has got a lot, to learn. Let's have a look at an other statement, maybe she does things better this time. "2719985 - not superseded for x86, moved back to main folder from OLD FOR BAD". I run KUC and the info says is superseded by 2836405 and 2799406. So let's have a look inside these three updates. "Three", I again said to myself, "isn't this number to high for a student in the first class." Let’s have a deeper look: 2719985 contains "windows-msxml30" and "windows-msxml60" both version 6.1.7601.22012. OMG indeed this numbers must be too high. But let us not loose hope. Next I look in 2836405, this updates contains "windows-msxml30" version 6.1.7601.22329. Now we count: 22329 - 22012, that is even to heavy for me, just compare the digits, and we get a result > 0 (O, sorry, just for explanation ">" is the character for bigger, greater, higher), So, 2836405 supersedes the msxml30 part of 2719985. I hope you can still follow and I'm not to quick. OK let's take a résumé: -that's French and means "summery", if you did not know that before- Update 2719985 contains two components. one is superseded. But we are not finish, we have to go the rocky road up to the end. We must also look inside update 2799406. And again we have luck. This update only contains one package for --- you may guess --- come on guess --- --- Yes, it’s for "windows-msxml60" with version number 6.1.7601.22208. OMG another really big number. That must have given her deathblow. But we will go slowly this time. Code: 22208 for 2799406 - 22012 for 2719985 ------------------------- = 19 for 79421 Both number > 0 (are greater zero) so we are at the end. Conclusion: 2719985 x86 is superseded by 2836405 and 2799406. But not to quick. There could be another update that has a higher version number. But I will talk about that at the next lesson. See you tomorrow. Your sincerely and faithfully Professor Dr. Komm
Buy the way, new KUC for Win7 is out. And leisure time is over. Sorry had no time to remove the IE issue. Had to check a lot of updates somebody posts in the forum, that should be superseded or missing, supposedly. And yes I checked all updates that KUC marked to add, and did not find a mistake on my side. Some updates could be superseded. But if one component of an update has no follower, I need at least one proof it's not needed. And yes it also takes a lot of time to do all this. 2574819-v2 is not really clear. I do not have installed the GDR part and it does not come up in WU for me. maybe the windows-t..-always-installable means, it can be uninstalled if RDP-WinIP8 is installed. On the other hand, I had a lot of problems to remove 2574819-v1 form the DVD images and integrate 2574819-v2. Last I give up. My x64 DVDs now contain GDR version of 2574819-v1 and LDR version of 2574819-v2. After OS installation the GDR part can safely be removed. Or 2492386x64-component "windows-a..ence-mitigations-c2" has no follower. Was this a one time mistake of MS? So, what to do with all those unclear updates. Declare them as superseded, by decree. What, if this part of the update would have told you, that the app you want to use is not compatible with your x64 system. And you spend hours to find that out. Questions, Questions, Questions. For me the decision is easy. Keep it, if you do not know if it is needed. We have round about 700 non superseded Updates, and round about 1200 superseded ones. But we have only a hand full doubtful updates. That's (let me calculate: a hand = 5 so 5/700*100=5/7%) round about 1% we may have too much installed. Better lose a friend than a supposedly needed update. (O, I forgot I have no)
Just try to relax man- these are hotfixes you're talking about; not atomic bombs or kitten's lives.. It's not the end of the world if somebody doesn't agree with you.
I tend to concur with the idea of being open-minded to viable suggestions. For example, - suggested improvements to offline integration of IE10 (KUC) to no avail - suggested mirrors for McRip's servers ... [My region was off limit to McRip's servers for DDOS attacks ???] ["co-payment" of file hoster can be considered] Sigh
KUC can download all updates for you and they don't come from McRip's server- they're downloaded from a server that komm pays for. So he is offering an alternative download source to you, if McRip's server is not available. But KUC doesn't require you to use his server as a download source. If you've already downloaded updates from McRip's server or another source, just put the updates in KUC's \repo folder. I'm not sure what you suggested to him for improvements, but if he felt they were worthwhile ideas and he had available time, I'm sure he would consider implementing them. People don't realize how much time and effort komm has put into KUC. He has tracked every update/hotfix released for multiple versions of Windows (beyond just Win7, Win8 & Win8.1). Not only has he tracked every update, he's had to keep track of every component that is affected within these updates to ensure that the latest is used. And KUC has to deal with update conflicts/verify prerequisites are installed, etc. It really is an amazing feat that he's accomplished in KUC. komm normally has very little free time available for KUC. Recently, he's had a window of free time to work on KUC and post here at MDL, but that free time will be coming to an end soon and KUC updates will probably only be coming on a monthly basis. Instead of people moaning about what KUC doesn't do, they should be more appreciative of what KUC does.
I certainly do NOT want to get involved in any drama here but I do want to say that I have never seen a tool like KUC in all my years of being in IT... it is beyond my comprehension how Komm does what he does. With that said, despite any personalities, quirks, idiosyncrasies, etc I think this forum is hands down AMAZING and I am thankful to ALL for what they contribute and I am extremely thankful for what I have been able to obtain from here. I sincerely hope everyone will continue to contribute in the spirit in which this entire thread was founded and based. Thanks
Mind telling me the general difference between komm's updates and mcrip's? (I've been using McRip's all these while after Solor)
The goal of both repositories is the same- to contain the latest batch of non-superseded updates/hotfixes available, and they're both great sources. There is some variation in contents though since Win7 has such a massive number of updates now, and that was being discussed a few pages back. A restart of the analysis of variation would be beneficial (if it can be done dispassionately).
With the fantastic help from abbodi1406, I have the full list (with new / superseded / relocated hotfixes) almost ready for McRip - I'll send it to him as soon as I have two thing clear: 1. Is 2690750 really not superseded? 2. 2798787 is superseded by which update (partially)?
But 2866693 only has Microsoft.grouppolicy.reporting.dll, right? What about Gppref.dll, Gpprefbr.dll, Gpprefcn.dll and Propshts.dll from 2798787? Are they not superseded by any other updates? btw, just verified, none of these dlls are present on my system, so it's very likely they're RSAT only as said on the previous pages... Thanks again
2878378 and 2872862 were pulled by Microsoft Fortunately, those hotfixes weren't involved in the superseeded discussion. So I'm going to do an ultimate build (instead of my usual HP one) without 2798787, to see if it's fully superseded (HP doesn't have Group Policy, only Pro / Ultimate), and also to see if there is a variation in the needed WU Satisfy Updates.
Hi Komm, Try [KUC W7 UpdateChecker-Beta-v.1.5.009.2765.zip] It reported the following 8 files are missing: 1. Windows6.1-KB2853952-x64.msu 2. Windows6.1-KB2574819-v2-x64.msu 3. Windows6.1-KB2831154-v2-x64.msu 4. Windows6.1-KB2871085-x64.msu 5. Windows6.1-KB2868116-x64.msu 6. Windows6.1-KB2801244-v2-x64.msu 7. Windows6.1-KB2870699-x64.msu 8. Windows6.1-KB2870705-x64.msu Any advice ? Thanks.
Latest KUC v.1.5.009.2765 says ADD IE9-Windows6.1-KB2839111-x86.msu, but it doesn't get downloaded from Komm's Repo if it's missing on the local Repo. I had to request the hotfix from Microsoft. Al
Made also a comparison between McRip and komm's servers for x64. Some questions - again, for windows 7 x64 ONLY qustions: 2645640 (x64) superseded by ??? 2757638 (x64) superseded by 2799406 and 2836405 ??? 2872339 (x64) superseded by ??? 2483564 (x64) not superseded?
2645640 (x64) superseded by 2775511-v2 2757638 (x64) superseded by 2799406 and 2836405 - Yes 2872339 (x64) superseded by 2875501 2483564 (x64) not superseded - No