By using that method, will it mark those servicing stacks correctly? I mean will it mark those: kb2919442 kb2969339 kb2975061 (too) as supeceded in favor of: kb2989647 but in reality I need one of those above too install the -647. Or it will mark as superceded only 1st two? BTW: What does it mean "Deeply superceded"? I am just asking to know, if I can calmly delete all marked superseded updates.
Hi all, i've just tried to apply the november 2014 rollup to windows 8.1 update 1 original iso (without any other rollup) using the following steps: 1) Offline integration with dism of kb3000850 packages 2) save wim image 3) create new iso with the new image 4) installed in a Virtual Machine to test. I tried to check in windows update what packages will show up, and it is showing 33 packages, including all the rollups may-june-july-august-september and october! what's wrong? it was supposed to not show at least a lot of these rollup packages....any suggestion? thanks!
No, servicing stacks are permanent updates, and this kind of updates can't be marked as superseded (skipped) Code: Skipping package [Package_for_KB2975061~31bf3856ad364e35~x86~~6.3.1.0] since it is permanent it's just a term the system use to identify packages that are completely superseded
Thanks, I have meant something else: What is update is superseded now, but on Windows clean installation it is still needed to install another 2nd update. (Yep, in the end it is superseded by some 3rd update, but still...) Just "like" those servicing stacks, but for regular updates not for permanent ones. I am afraid, that by deleting all updates marked as superseded by this method, maybe I could also delete something, what is superseded, but still required during the installation process.
I'm trying to establish the minimum set of updates for Windows 8.1 32-bit; by minimum I mean just those updates which will cause WU to report that no further updates are available. As is the case with most rollups, I have to install KB2955164 twice; after the second time, Windows reports that KB2965500 has been installed. I cannot find KB2965500 anywhere on the M$ website - does anyone know where I might find a copy ? Many thanks in advance for any help.
Refer to Post #2235 in this thread for information related to KB2965500 and other updates. The Microsoft Update Catalog is at URL: catalog.update.microsoft.com/v7/site/Home.aspx Code: {m} Bundled with the May 2014 update rollup (KB2955164) when downloaded from the Microsoft Update Catalog. KB2965500 cannot be downloaded from the Microsoft Download Center.
There is an interesting manner of W8-1-1: When i do "/cleanup-image /startcomponentcleanup /resetbase", in the next WU-check WU re-offers some small update like KB2959977 (part of U1's KB2919355), marks it as already downloaded (after storage is cleaned ) and installs it again. Is there anybody with same experience?
Yes, using cleanmgr with or without /resetbase one must reinstall KB2959977 to satisfy M$ update. I also have to reinstall KB2980654. Isn't that special...2959977 is completely superseeded, M$'s own cleanmgr deletes it, but, M$ update wants to waste your time.
for me it was the same when i used just "/startcomponentcleanup /resetbase" command but if i used first "/startcomponentcleanup" command and then "/startcomponentcleanup /resetbase", it won't delete 2959977 and this way WU doesn't complain about it (this is happening after install an image with all updates from WHD integrated offline, including the ones to satisfy WU)
If you want to avoid uninstalling KB2959977, you need to make it permanent that's done by installing/integrating KB2959977 (to April-based image), run the ResetBase command afterwards you proceed to other updates
Thanks for info, guys... ...I see now, that (my) ARM Windows behaves completely same as x64/x32 ones.
Sorry to be a pain - do you have a link for the 64-bit version ? MTIA. Please ignore the request above - I've discovered that it is included with the download from Windows Catalog.
I am familiar with using dism to integrate updates into my Windows install image, but not familiar with using the /cleanup-image option. Microsoft documentation is, as usual, hopelessly inadequate. Microsoft says that the November rollup replaces all previous updates, but when I install it, Windows Update gives me a list of ~30 further updates. Reading this thread suggests that most of these updates are not actually necessary. Is there any way I can use dism so that a) I don't have to integrate unnecessary updates AND b) WU doesn't list unnecessary updates ? I'd be very grateful for any assistance anyone can offer.
When checking back the thread a bit you will notice that WU is still slighly confused by itself it seems, it offers even clearly superseded updates . According to abbodi the rollup so far is listed as additional update, but will change the status to Important after next Patch Day (or the one after), then we will be all smarter . And dism isn't able to make any differences between updates which are needed or not .
Thanks for the reply. I am new to this topic, so am only slowly understanding what certain things mean. Do /cleanup-image servicing options like /startcomponentcleanup and /resetbase offer me any hope ? FWIW, I don't need dism to tell me which updates are unnecessary, I can use the lists provided by the good people on this thread. Do you think if we all clubbed together, we could afford a decent data analyst, whom we could hire to M$ to help train their twelve-year old programmers ?