spelling is not one of my strengths, touche' all of these were from patch tuesday MS updates that come up n/a after I uninstalled then then tried to reinstall sorry for my stupid question..
Hmm, strange, when I looked up some of the KB's in that list they were actually released in February and April, etc... But OK. I wonder if anything new did come out, it being Tuesday and all
I was just messing around In terms of the security updates, I'd say the program is just checking what is installed against a list of what it expects to be installed, and doesn't actually check the actuall state of the files on the system. Newer updates may install newer versions of the same files as the security updates, making the security update effectively redundant. Some security updates may be listed and install regardless of whether they have been superseded or not, but when installed they serve no function other than taking up space. There are a couple of updates that do that currently, they're not meant to but its an anomaly of the Windows update system.
Yes this is common problem.I had some torrents that were superseded by new versions i made, so included the word superseded in the title.Some ppl who downloaded it asked why was the speed so slow - we thought it was supposed to be superseeded (the not a word).
SoLoR I think you removed KB2478063 .net4 update but these files have not been superseded (I could be wrong) Code: System.Activities.DurableInstancing.dll 4.0.30319.447 System.ServiceModel.Activities.dll 4.0.30319.447 SqlWorkflowInstanceStoreLogic.sql SqlWorkflowInstanceStoreSchema.sql
reason i removed this hotfix is because it stoped showing up on windows update on "clean" .net 4.0 install... and i thought it might be a reason for it... i didnt check files for this one, but i will...
@burfadel you should see about adding an exclusion/alternate install method for KB958559 (vpc) because it still does not like install via MUM Code: Package Microsoft-Windows-VirtualPC-Package-TopLevel-MergedCab may have failed due pending updates to servicing components in the image. Try the command again.The command completed with errors. For more information, refer to the log file. Since there are no LDR files, pointing /Package-Path to the MSU/CAB should do the trick
Easy done thanks for letting me know! I'll post what will hopefully be a final test version in the next day or so which will include that change, plus a few others, and the integration feature etc. If anyone has noticed any other issues (keeping in mind at the moment from the tools menu the integration and reg tweaks feature won't work) let me know!
Hello I am trying to install the updates, I have downloaded the x64 pack (x64-14.8.2011.7z). I execute update.cmd as admin but it only do the updates in sub folders (IIS to SNMP), it don't apply the other 228 updates in the root folder : I have Windows 7 Ultimate x64 French SP1. What am I doing wrong ? Also, can I slipstream them all in the installation disc ? Thanks. Edit : I have done it by doing the update.cmd commands manually and with a bat file for multiple commands string. I am not sure what wasn't working, that have worked perfectly like this. Thanks a lot for this pack.
@burfadel This is the first time I am using Installer For Windows Updates V21 test4.7z, so please bear with my lack of knowledge here. I want to ensure that the script has successfully integrated the updates to an offline (mounted) image. 1. In the list of installed updates, the updates with GDR and LDR branches are shown as KBxxxxxxx and KBxxxxxxx_BF. Is this correct? 2. If one of these updates has been superseded, I have to uninstall both KBxxxxxxx and KBxxxxxxx_BF, right? Thanks for the advice.
Thats correct, force installation of LDR updates are with '_BF'. If the update were installed normally or via the cab, and an LDR version is used due to it being an LDR only update or its using the LDR version due to a previous update updating the same files, then it will only show without the '_BF'. On a clean system with just relevant, non-superseded updates, its more likely the GDR branch is used (when installing normally) over the LDR branch, necessitating the need for forced LDR installation. The GDR branch is more the KB article specific fixes, whereas the LDR branch is all changes to the files, meaning that it effectively has a higher updatedness. If you uninstall via the control panel, I believe you need to uninstall the '_BF' and non '_BF' entries separately, but by using dism uninstalling the update will automatically uninstall both entries like the superseded uninstaller I provided does.
I for example had the following values: 054C00C1 05AC12xx 05AC13xx 05DCA431 Pic: View attachment 10959
Hi, It's been a while since I last updated my W7X64Pro OEM (with SP1 Integrated in the .iso file before installing windows). The last time I updated my W7 was 6/09/2011 and the updates were KB2545756, KB25441014, KB2528357, KB2526870 and KB2531385. Normally I take a look at changelog to see what updates have been removed then I remove them from my own PC, then I download and install whatever that has been added to changelog. However today I came here to download the new updates and find out changelog has been relocated and renewed, thus I have no idea what happened between the time I updated and the time changelog was relocated. so I don't know what updates I should remove (If any). Q1: Should I uninstall all my updates (except SP1,KB958488 and IE9) and then install all the update from Repository (all 319MB of it) OR Is it safe to just Install all of new updates over the Old ones? Q2: Does installing these new updates over the old ones increase my system partition's size by more than ~100MB? (The increase should be just because I haven't removed the superseded updates) Q3: If there is anything about these new updates that you think I should know (like the one above for KB2581464) feel free to tell me.