SoLoR what about these? KB2603469-x64 KB2657025 KB2661663-v2 KB2663352 KB2669522 komm when will the latest kuc list be available?
Was the assumption about the bulk updates being uploaded after your Sunday scan correct, or you just super busy (just curious!) I guess those missed updates would be added at such time
Those are extra components, most of which aren't installable on most systems, or are for integration to an installer disk only. LDR placeholders - Only needed if you don't use an installer like SoLoR packages or mine MSMQ - That one update is installable NFS - All are installable Not Integratable to Offline image - These can only be applied to an active operating system, not an installation disk. KB2533552 MUST be installed with no other pending updates before you restart. My installer checks and allows for this. SNMP - Won't install on a typical image unless certain components are explicitly installed IIS - Won't install on a typical image unless certain components are explicitly installed Subsystem-for-UNIX-based-applications - Exactly what it says! Typically installable In other words, freshly boot Windows, install KB2533552 first, restart, then install the rest of the updates, including those in the MSMQ, NFS, the other update in the not integratable folder, and the update in the subsystem for Unix folder. Ideally if you can wait, don't make a fresh install until after the bulk updates are sorted and added to the repository, since there will probably be about 50 (or more!) by the time the batch updates are added, and the missing patch Tuesday updates added also.
Is it ok if I integrate all updates to image first and then the KB2533552 is installed silently at first boot?
Try copying the following into notepad, saving as a .reg file, and running it: Code: Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{BDEADE7F-C265-11D0-BCED-00A0C90AB50F}\Instance] "CLSID"="{4D5C8C2A-D075-11D0-B416-00C04FB90376}" "DontRefresh"=dword:00000000 By default, the folder view isn't updated. Whether this caused your issue or not I'm not sure, but its worth a try. By default the dontrefresh setting is 1 (dword:00000001). This setting is the cause behind the explorer refresh 'bug' which people complained about, in actual fact it isn't a bug at all! It is a potentially useful setting in folders where the view constantly changes (like deleting large amounts of tv recordings), since Explorer wants to refresh the info on every file with each deletion, which for large media files with the .mpg extension its a real pain. Of course the sensible thing would be just to apply the changes to the view, but no, explorer wants to refresh the whole thing, which leads to the setting, and the 'bug' thats not a bug! ... although I think it might actually be defaulted to 0 now? due to complaints and the annoyance behind it. Even if the media file thing isn't related to this setting, its something Microsoft should look into for Windows 8 if they haven't already. In the situation of constantly changing folder contents (such as extracting a large amount of files into the current folder) instead of trying to keep up, maybe Microsoft should consider a 'Folder contents currently changing, waiting for completion to show contents' or something when the threshold has passed between updating the Window content and the folder changing.
Yes, but Windows will need to be restarted straight away without making other changes. For integration its okay, for an online image it would be best to install KB2533552 first. Its a servicing stack update. The reason why you can't do other update/change (including Windows features) operations in the same Windows session as installing this update is because the servicing stack is used to apply the other updates as well. Basically if you install other updates alongside KB2533552 it can cause errors which are fiddly to fix. Definitely install it though, just do it by itself.
And what if I have those 2 nonintegrable updates added as a silent installations during the first boot? KB2533552 first, then the second one. Is it ok or should I not add them as silent installs and just after the first boot install the first, restart and then install the second one and restart?
I'm just working on it. Just making the new references. by the way KB2661663-v2 is superseded by 2664408
Thanks burf , just 1 more quick question what do you mean if you don't use an installer? I use a batch script similar to what SoLoR has packaged, which uses wusa.exe and dism.exe to query and install the .MSUs directly. is that what you mean? so I can ignore all of those LDR hotfixes? are you sure?
because i know there will be sihitloads of updates to remove on monday and i CBA doing them manually today, when ill just reupload everything on monday. yes i am kinda busy lately but ill fix everything on monday.... dunno... ill check them during weekend, but probably they will be caught by weekly scan.
Using a method like that you definitely need to use the LDR placeholders. Also thats the slowest way of installing 300+ updates (if from a fresh installation)! SoLoR's script and mine extract the cab's from the .msu's, then extract the cab files and install the update.mum or update_bf.mum directly. DISM still does the checking process to determine whether its applicable, its just quicker. This way you can also force install LDR updates and save space by installing just the LDR components. Using wusa or pkgmgr is more of a deprecated and slower manor of installing. Using an automated installer isn't what negates the need for the LDR placeholders, its the method used to install and the install logic the installer uses which determines whether you need them or not. Basically the intention with my installer and old update remover is to provide the simplest, quickest way of installing updates (especially a large amount of updates), ease of use, and provide some logic behind the way it does things.
SoLoR, thanks for the repo update. A minor thing (for next update)- 2635217 can be moved to LDR placeholders due to 2654428. Also, shouldn't 2635500 remain in main folder (not LDR placeholders)?
Thank you for your help, burfadel. Unfortunately, it does not work. So, I presume that no one else has this problem? For both my desktop and laptop, they will exhibit the same symptom, once any Windows-shell32 update is installed.