Some of those updates supersede other updates. Update kb2491890 is superseded by KB2495655. There are probably others as well, keeping in mind that earlier versions won't install if later versions (even with a different KB article number and issue) are already installed. However, later versions will install if earlier versions are installed, and the old version won't be removed (it needs to be done manually). Some updates are Windows version specific, such that the files to be updated only exist on certain versions of Windows, most commonly the different between Server 2008 R2 and Windows 7. Some updates, although they particularly target certain issues on either Server or 7 will still update the other Windows if the files to be updates are currently older on the computer. For instance, if there's an issue with networking that only affects Server, but the files affected are common to both Windows 7 and Server, the update will still be applied. These update lists are basically 'blind' lists, they contain all the updates and they need to be sorted. The same goes for Zukobonus packs (if ever there will be more). The list maintained by SoLoR already sorted, superseded updates aren't listed# and specific updates are highlighted in the update log. #Since certain issues may update the same files to different versions, there are occasions where the newer update doesn't update all the same files. In this instance, both the newer and old update can be installed so that all the latest files are utilised. The term supersede used in relation to these updates are for the files updated, not the KB articles.
KB2490728-x64 KB2485543-x64 KB2495655-x64 KB2491890-x64 These 4 install/slipstream for me withiout issue, Ultimate 64-bit SP1 slipstreamed. The other 5 are versioned as listed and neither install or slipstream for me. I only install the extracted cab files using DISM, never the msu's: Code: DISM /Online /Add-Package /PackagePath:<your path to cab> They are all listed in Programs and Features>Installed Updates.
Thanks for the info. I still don't understand why some of those before mentioned updates don't install on my system but do on others' (assuming they actually do). I tried both with SoLoR's list (so far) installed, and also no updates at all installed, and still those won't install at all. I'm just going to leave them aside for now, but I was trying to make sure it was not due to some system/install specific thing that these wouldn't install. I just tried everything I knew how, but still the following won't install so I'm going to leave those alone for now: Windows6.1-KB2462585-v2-x64 Windows6.1-KB2462137-v2-x64 Windows6.1-KB2413670-v3-x64 Windows6.1-KB2462576-v2-x64 Windows6.1-KB2468316-v2-x64 Windows6.1-KB2466373-v2-x64 Windows6.1-KB2490728-x64 Windows6.1-KB2495655-x64 Windows6.1-KB2485543-x64 Windows6.1-KB2491890-x64 With the rest I'm going to do an integrated build so we'll see how that goes... EDIT: OK, you just posted Rick. So, what you're saying is that you don't integrate .msu's at all but use only the cab files, I wonder if that makes the difference. I would think that whatever does not install manually, it won't integrate with the .msu integration method either, but as for the cab integration that may explain something then. Thank for the info, I'll report back with my findings on the integrated build.
ok, don't install if I understood ^^ (the Update will be OK, Solor would have in its repo I think) for these Updates, the articles indicate that it is only for Server 2008 R2 or Windows Vista or Windows Server 2008 if I understood what was said bufardel, do not install them, if it is not indicated for Windows 7
The above is an excerpt from that post; I understand it to mean those updates flagged only for Server 2008 R2 or Windows Vista or Windows Server 2008 may still be relevant to Windows 7 so I would leave them in.
I also only install updates/hotfixes on a live system using the cabs; I never use the msu's for anything except to extract the cab, then, I delete the msu. Further, I only remove features, components etc. using imagex in my answer file. If you remove anything via DISM to an offline image, even though it shows as "pending", my experience is anything associated with the files contained within those removed items-hotfixes/updates for instance-will spit out "not applicable" even when slipstreaming offline if the operation is performed after component removal using DISM. Referring to burfadel's post, I may have older versions of some files in my DVD than you in your's, or I may have those files because I still have the components associated as still present and, therefore, the updates install-hard to say, but, I would look at some of the files and compare between the fixes and what you have. If you do not even have the files in your image..........just food for thought.
...I'm no expert at this, but, after going through each extracted update listed by you I would say it is good because the files you list as superceeded are the only ones contained in each update. Yes, it's good. I searched about how to weed out superceeded updates and the only thing to come up is via WSUS which is a server only tool-updated from SUS-and even using this is no longer automated; one must manually delete any outdated fixes. (apparently a degression from SUS). Perhaps someone can point me in an alternate direction; I will continue searching anywho. Thanks bapt. I'm sure I'm not alone in appreciating your effort here.
I did not upload hotfixes for Windows Server 2009 R2 only. So you can install all hotfixes I uploaded. However, if you cannot install some hotfixes, those hotfixes are updates for specific feature which you do not turn on, such as IIS or NFS or other features. Also those hotfixes may be updates for Remote Server Administration Tools for Windows 7.
Updates the specified "for Windows Server 2008 R2" are not applicable on my Windows 7 when I install the KB2444677-v2 (Microsodt-Explorer), it installs without problem, but on reboot I get an failure message and the explorer.exe file is not changed (and updates is not installed) and also with one of the Update (which I do not know yet) I had a message with the explorer (before installing the KB) when I double click a file and I have solved the problem with a command
Installing (manually) KB2444677-v2 (x64) works fine for me, no error messages and explorer.exe got updated and it shows to be installed. Maybe try to make sure your file is not corrupted.
Thats essentially correct although a hotfix may specifically target an issue that is only relevant to Server 2008 R2, and hence the update is 'flagged' under Server 2008 R2 and not also Windows 7, if the files to be updated are newer versions, the update will still apply. This is by design and isn't a bad thing. Installing these updates is no less safe or an issue than installing any other hotfix. The purpose of installing all the latest updates and hotfixes is the equivalent of personalising and modding a car, its an enthusiast thing (there are many types of enthusiasts). If you don't feel comfortable 'modding' the OS, then stick with the normal 'regular servicing' of downloading the updates through Windowsupdate. If you do have enthusiasm towards updating to the latest, then thats fine to do so! Its no different than installing a sports muffler, high flow catalytic converter and resonator (front muffler), better rims, leather steering wheel, race pedals, polyurethane bushes (especially for the sway bars) etc etc. That analogy probably doesn't make sense to some, but basically what I was referring to is if you feel comfortable with what you are doing, and you like the feeling of fully hotfixing the system like someone that is comfortable and likes the feeling of modding their car, then install them. If not, then it may be better to just use the Windows Update updates, or at least read through the update descriptions and use only those that you feel comfortable installing.
to be sure that each updates are installed correctly there in order to install the Updates? some must be installed separately? it's better to reboot whenever asked? or no importance and can install all Updates at the same time
is not the same? KB2480118: windows-printing-spooler-core 6.1.7601.17543//6.1.7601.21642 (GDR) KB2466040: windows-print - Spooler-core 6.1.7601.21642 (LDR) there is one that should not be installed? if yes, which one?
Install just the bottom one (KB2466040). Ideally, since the principle reason for installing these updates is to be fully up to date... (like I posted earlier), the LDR version is preferable to install over GDR versions. LDR contains all changes, whereas GDR releases contain specific changes. For SP1, the GDR releases are 7601.17xxx, and LDR 7601.21xxx. If the top update had a newer LDR than the bottom update, you install the bottom update first and the top one will install the LDR version. If you installed the bottom update after, Windows will look to the WinSxS repository and utilise the newer version. In this case since the bottom version has the same LDR, and no GDR, then you need to only install the bottom one. If both updates had LDR and GDR versions (the bottom one doesn't have a GDR version), to utilise the newer LDR you need to install both updates, or have previously installed a LDR version! I hope that came out correctly, its a bit of a BS system. For XP, you could force LDR versions, but unfortunately with Windows Vista and 7 MSU/CAB install methods, you have to let the installer decide.
ok thank you for the info, I'll just install the KB2466040 and remove the KB2480118 but the KB2480118 is more recent than the KB2466040, is the KB2466040 that must be installed, if I understood
Thats correct. Its the contained file versions that are important, not the date of the update. In general, the later update dates usually means later contained file versions, but there are exceptions such as this one.
@ burfadel So, in a nutshell: LDR over, and discard, GDR both KB's have LDR versions of the same file-install both both KB's contain LDR and GDR versions-install both Correct?