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.
@akf: sorry to say but this is a hard problem to get rid of, once you have it. I had it too in the past, but when all else fails do a reinstall of the OS. For little quirks such as this (and big ones) it is a good idea to always make a system backup (with a bootdisk preferably) so that you can always load your backup and in 5 minutes you are back intact. I like using Active@ Disk Image (current version: 5.2.5) and it also comes with a bootdisk, so you can back up your OS drive from the bootdisk, and of course also restore from there (which you'd have to with a system partition always). Good luck.
akf, I Bing'ed the issue and found this below. Not sure if this will solve the problem on your system, but it appears to have for some others: 1. Open a Command Prompt. 2. Browse to the folder containing the buggy file or folder. 3. Type 'dir /x' to obtain the 8.3 formatted filename. 4. Delete or rename the file/folder using the 8.3 filename, e.g. 'del NEWDOC~1.DOC' Maybe also try temporarily renaming the desktop.ini file in your .\Desktop folder and rebooting to see if a new default desktop.ini file fixes the issue..