With the changers/corrections made to the old update remover for the 18th, it seem now WU is showing KB2556532 and 2644615 for me... so Komms earlier post was correct about them having the GDR to keep... anyone else finding this, as the Cesidian repository has them listed to be removed...
@Burf: Should read: Updated: 18.04.2012 Added: KB972959-v2, KB2556532, KB2644615, KB2645594 Readded KB2532445-v2 (previously in LDR placerholders) Removed: KB951422-v2 The txt file is corrected on the server-updates always were present. I have deleted the LDR placeholders folder-was way too obselete-and kept the GDR/LDR hotfixes in their respective main folders; ie: IIs, MSMQ, NFS, x86/x64 etc. which means they are no longer separated out of the main pack into a separate folder. Current April 18 7-zipped x86/x64 repo' uploaded.
@McRip I never had any problem using the original VC_RedistInstaller, but, used your latest after a fresh install in a First Logon cmd with the silent switch and it, too, worked perfectly; Thanks, very nice!
@ amires: I'm not so sure about your 'satisfying Windows Updates' story, as this happens to me quite frequently, that WU is not showing any updates. Yet, when SoLoR refreshes there may be 30 new updates in there and WU hasn't even mentioned anything yet. So I don't think WU not showing any updates is any validation of your GDR vs LDR story. I installed an old Win7 x64 image I made in January as my HDD got messed up, and it only showed 14 updates on WU, ya know
Well whenever SOLOR refreshes do not expect all of the new hotfixes to appear on windows update only security updates will show on WU. A lot of the hotfixes are private hotfixes and they will never appear on WU. So out of 30 new updates mentioned in your example you will find maybe 4 or 5 of them on WU.
@komm is there anything wrong with your latest KUC??? All the following updates had been installed before. KUC said the updates are missing and downloaded all of'em and installed the updates. Windows6.1-KB2518869-x64.msu Windows6.1-KB2386667-x64.msu Windows6.1-KB2512715-x64.msu Windows6.1-KB2607047-x64.msu Windows6.1-KB943790-x64.msu Windows6.1-KB970985-x64.msu Windows6.1-KB974405-x64.msu Windows6.1-KB974674-x64.msu Windows6.1-KB975541-x64.msu Windows6.1-KB2656946-x64.msu Windows6.1-KB2647644-v2-x64.msu Windows6.1-KB2619082-x64.msu Windows6.1-KB2607496-v3-x64.msu Windows6.1-KB2589154-x64.msu Windows6.1-KB2581690-x64.msu Windows6.1-KB2577917-x64.msu Windows6.1-KB2568771-x64.msu Windows6.1-KB2545735-x64.msu Windows6.1-KB2539513-x64.msu Windows6.1-KB2531907-x64.msu Windows6.1-KB2466373-v2-x64.msu Windows6.1-KB2385838-v2-x64.msu Windows6.1-KB2462585-v2-x64.msu Windows6.1-KB2462137-v2-x64.msu
Does anyone know why KB2532445-v2 has been readded to the Cesidan repository? It is obsoleted and is not required.
Hehe, well that's what I'm saying, being up to date on WU doesn't really mean anything, and as you were mentioning it, this is why I said that
Thanks for that nice tut, RickSteele, 5 counts is even better than 4 So one could use an xml but then discard it after it served its purpose, I never thought of it that way. Quick question: what do you name that .xml you place in the sysprep folder?
Just checked M$ update after a fresh install using my unexpired image, all that is on Cesidian x64 integrated via KUC-run twice on the image; and no updates at all showing. I find KUC must be run twice online or off to integrate/install all updates.