Fellas, mind giving me a brief guide on how you obtain information on hotfixes? Like what to include, exclude, and what superseeds what? Is there a legal policy that does not allow direct downloads of hotfixes off microsoft server? Thinking of an easy way to maintain a list of hotfixes.... thru an app perhaps
2719985 is not superseded in x86, only x64 2591500-v3 is superseded by Platform Update KB2670838 (if installed), and it doesn't show to me in WU can confirm that the rest are apearing to me in WU, except 2791765
Many hotfixes are request only and thus not linkable although yes it would be preferred if we could just easily link to hotfixes stored in secured and highspeed MS servers. Im sure it would be better for MS too.
Mind briefly telling me the reason why some hotfixes are request-only (is mcrip's made up of a lot of request only?)? And if it's request only, how does one obtain them?
Via request to MS. Also, requestable hotfixes are usually for machine specific fixes. IE - My machine (custom built) needs kb###### for a hardware comparability fix for Windows. Your machine may not need these fix and/or could break your installation.
Does McRip's repo utilize a lot of request-only hotfixes? Generally newer versions are created for the better good... and my purpose is to achieve a as-STABLE-as-possible, as-SECURE-as-possible, as-COMPATIBLE-as-possible system. My assumption all along is that these (request-only) hotfixes lean towards accomplishing that. BTW, are these request-only hotfixes what you normally call GDR hotfixes? A lot of us here use mcrip's repository.. which in my mind/assumption has a lot of hotfixes that's made but isn't posted in Windows Update yet... They aren't quite machine-specific are they? But are suitable for nearly any modern machine, right?
The reason McRip packs are downloadable through the apps is due to Chinese hackers. Anyway, the info is all in this thread and you've been in this thread regularly for months so it would be easy for you to know. As far as legal issues, I don't know, but I do know SoLoR's skydrive was closed by MS but I don't know if that was due to him hosting updates and/or bandwidth issues due to many people downloading them. There are actually a lot of updates that can be installed in LDR mode as you'll see from the _BF nomer behind installed updates when you install them with a LDR enabled script like Burfadel's or McRip's. Some updates will have newer file versions inside, so if you get a well sorted pack (such as McRip's) and force LDR mode where needed your OS will be as much up to date as possible, with latest file versions, etc. If you just want WU-satisfy only updates, then install a vanilla Win7, use WU a couple of time, take note of all updates installed, and make a pack with only those. If that is what you want, the McRip and other extended packs are like buying a Cadillac when all you really need is a Metro mini car to do grocery shopping with
There still seems to be some confusion regarding LDR and GDR updates, although most seem to be almost correct GDR updates are general release updates, and typically means availability through Windowsupdate or the Microsoft download site. LDR updates are available through request for specific issues. HOWEVER, this is oversimplifying it, and isn't actually correct. Most updates, regardless of whether you get it through Windowsupdate or request a specific hotfix, have both GDR and LDR versions in the same update. The GDR version of the hotfix resolves the issue relating to the associated hotfix, in addition it includes all previous GDR updates released through Windowsupdate or Microsoft download site. It does not include non-Windowsupdate/download site changes made to other KB article GDR updates. LDR updates on the other hand not only include all Windowsupdate and download site updates, but also includes all previous changes made in other KB articles, and even changes that didn't have KB articles or previous updates. Now, if you install two hotfix updates that relate to the same files by running the .MSU, the first update will install the GDR version, the second one will automatically in stall the LDR version. The LDR version is required because the GDR version of the second update doesn't include the changes made in the first update. Windowsupdate updates include LDR versions for the same reason, so LDR updates aren't specifically Hotfix request only. If you only install Windowsupdate updates, and none of these are LDR only (sometimes this can occur), then most likely if there isn't any crossover you are on the GDR path. The LDR path however, is by far the most 'updated'. Due to the nature of the hotfix repositories, you should force install the LDR version. The whole purpose of the repository is to have the 'most up to date' system. If you install the update normally, the GDR version will be installed unless there is some crossover with another update. This defeats the purpose of the repository. If you disagree with force installing the LDR update, the only other way of making sure the LDR version is installed is to install a previous update first, which means you are installing many more, deprecated, non-functioning updates, taking up space etc.
komm has posted a new KUC for Win7, sadly, when I tried to extract the archive using both 7zip and Winrar, the exe files are reported as corrupt. And with 7zip, it said unsupported compression used, so I hope Komm can fix this soon.
I tried that, and it did work. But as Tito said W8 version needs looking at by komm, might have been a bad upload to the server.
@komm: Thanks for latest Win7 KUC. KB2811483 (DHCP & TCPIP, supersedes KB2459530 and KB2524732) is not currently available from the MS hotfix servers. However, KB2824546 (DHCP 22277) supersedes 2459530 and KB2811463 (TCPIP 22296) supersedes KB2524732.