Then you are integrating by installing both GDR and LDR version. You can check this by looking out at output of dism /Image:/path/to/mount/dir /Get-Packages /Format:Table. If for a given LDR hotfix you see two entries for that hotfix one of them having _BF in the name then you are installing both GDR and LDR.
The problem is, some users install it like I do and WU shows the updates nevertheless. Systems can't be that different. The installation methods can't be that different either, because the same commands for installing are used.
Well that all depends on the tools you use to integrate. Most of these tools integrate LDR hotfixes by installing both GDR and LDR version to force LDR which in my opinion is not a good idea why install more packages than necessary. That is why I never use any tools and I prefer to use DISM directly. Anyway I use update.cmd script by SOLOR to integrate only LDR hotfixes where applicable and then manually add GDR version of the hotfixes I mentioned above. I can also recommend burfadel's Installer for Windows Updates as it correctly install only LDR version and adds GDR version for needed hotfixes. However it can only be used on a live system. For integration a couple of modifications needs to be done to the script. UPDATE : I have just tested a new image I created in VMware using method I described above and no updates are shown on windows update.
Well there is not a simple answer to that question. I personally prefer to have a clean image and not install any unnecessary packages. There is nothing wrong with installing both GDR and LDR of hotfixes like you do just more packages than necessary.
I personally prefer a clean image, too. Sometimes all is in order and sometimes WU is going to be nuts... This time I just got lucky. I don't know. But I have an open mind about everything new...
Not sure if this is any use Burf', but, I've attached the packages.txt and Features.txt in install_wim_info.7z for the system I just installed fresh now-updates integrated via KUC UpdateChecker-Beta-v.0.8.002.008. VM, NTBackup, Help are not enabled/updated; IIs, SNMP, NFS, MSMQ, AMD Core Parking, Subsystem-for-UNIX-based-applications etc. along with the PreSP1.Packages updates-except as previously noted-integrated. The only difference between your latest Superseded Uninstaller 18-Apr-2012 and komms latest KUC UpdateChecker-Beta-v.0.8.002.008 are as follows: you remove the following installers from the latest repositories (KUC_Repo on my HDD) and the Cesidian server uncompressed folders which mirrors all that has been discovered since SoLoR's last update-new added, superseeded removed etc.: KB2519922-v2 KB2556532 KB2597665-IIs KB2642947-v3 KB2644615 while komm retains them (for M$ I imagine). Oh, and no updates show at M$ update.
if have also the above hotfixes in my gdr to keep database for x64 except i don't have 2446710 and 2478662 but also 2518869, 2633873, 2656356 an 2603229
2519922-v2 is not superseded 2556532 is superseded but GDR to keep 2597665 is for IIS and not superseded 2642947-v3 is not superseded 2644615 is superseded but gdr to keep I do not deep check the files on my server, if they are superseded. For me it is not necessary. I use KUC to download only the files I need. In addition, sometimes old updates are needed to repair a "BAD" update. I somebody finds superseded updates, please let me know.
You are correct. KB2518869 and KB2633873 are replacements for KB2446710 and KB2478662. As for KB2603229 I always install both GDR and LDR versions of KB2603229 via sysprep. However I am pretty sure GDR version of KB2656356 is not necessary. I just did a test install last night with only LDR hotfixes and those I listed only appeared on windows update minus KB2603229 which I already had it integrated via sysprep. To be sure I manually installed GDR versions of the hotfixes I listed above substituting KB2518869 and KB2633873 for KB2446710 and KB2478662 on my vmware install and checked again for updates and no more updates showed on windows update.
Yes I have seen this issue before however it looks like all ntoskrnl security updates are necessary. An example of this are KB2556532 and KB2679255v2. Even thought KB2679255v2 contains updated version of files included in KB2556532 however both of them must be installed otherwise WU will complain.
Komm, Maybe its a DNS server issue? you could try changing the order of your DNS servers, it sounds like the ones lower on the list are more reliable? Of course, run the command: Code: ipconfig /flushdns from the command prompt after you do this. Two common alternative DNS providers are Google and OpenDNS: (I copied these from Wikipedia, but they are correct) Google: Code: IPv4 addresses 8.8.8.8 8.8.4.4 IPv6 addresses 2001:4860:4860::8888 2001:4860:4860::8844 OpenDNS: Code: IPv4 addresses 208.67.222.222 (resolver1.opendns.com) 208.67.220.220 (resolver2.opendns.com) 208.67.222.220 208.67.220.222 IPv6 addresses (experimental) 2620:0:ccc::2 2620:0:ccd::2