If I am not mistaken rt7lite installs both gdr and ldr versions. If you do not want this then you must use Burfadel's Installer for Windows Updates as it have a mode called Smart Update which only installs LDR versions and in a smart way installs both GDR and LDR versions for security update to satisfy WU however as I mentioned earlier it is meant for online installations so you need to edit it to allow integration. The modifications are very easy I can show you how to do that however I am not allowed to post a modified version.
thank you for your help I"ld like a script to integrate updates, but I do not want "LDR" and "GDR" are installed for the same updates, is this possible? for example KBxxxxxx LDR/GDR: LDR only installed KBxxxxxx LDR: LDR only installed KBxxxxxx GDR: GDR only installed I never use WU, I did not need to "Satisfy WU", I use the repo, so no interest if not possible, I keep the "superseded update" detect by KUC, to have the updates LDR (and not GDR) thanks a lot
did you know, that all the functions you are talking about can be done with KUC without and modifications?
If you dont want to Satisfy WU then you are better off with the modified version of SOLOR's update.cmd which I have attached. Simply unzip it to the folder containing your hotfixes. Before running it you need to edit it in notepad and change the second line to match the folder you have mounted your wim to (the line with SET MOUNT_DIR) 1) Mount you wim 2) open an elevated command prompt (Run as administrator) 3) navigate to the folder containing your hotfixes and the script using CD command (for example CD C:\updates) 4) run the script like this : update.cmd > update.log 5) wait for the script to finish then check update.log for any possible errors 5b) While you are here you can also copy latest mrt.exe to windows\system32 folder inside mount directory as well. 6) if everything is ok unmount your wim committing the changes That's it NOTE TO SOLOR : If you have any objections against my modifications of your script please let me know and I will remove the attachment.
Really? I didnt know that. While KUC is a great tool and I really like it but still I prefer to use a script for integration so I can have full control over what is happening behind the scenes.
the script is create automatically - differs if online or offline. the updates are installed with command files extern of kuc. so you have full control over the updates you want to install. look at KUC' faq for detail
Thank you very much I see in the scrip "update-bf.mum" I do not want "bf" appear since I have only 1 version of the update (and no, KB123456 and KB123456-BF) Is it possible? And how KUC integrates the updates? Is both LDR/GDR or not?
The script I posted will integrate only LDR if both GDR/LDR are present. Not sure about KUC havent tried the integration function.
No that's the way it is designed by microsoft. when a hotfix contains both GDR and LDR the LDR version will be indicated by _BF.
@McRip maybe you could create a WU satisfy folder for superseded .net4 updates that WU still asks for, right now those are: 2656351, 2656368 and, 2656405 I use a MST to hide them in my updated installer, but for people who do vanilla installs cant use the MST they can install them instead
KUC allows online / offline / vhd integration Also it allows to install LDR or just GDR. remove old updates or let them installed It has hundred of switches that gives you the control over nearly everything you want.
1. You have bad update so you must remove them. 2496290v2 (follow kucs faq) 2. you have old versions of updates installed 2519922v1 2496290v1 i think you use LDR placeholders. 3. LDR placeholders are superseded by default (2444677, 2459268...) if they were not placeholders, they were not superseded. with the placeholders you get a problem in the future, since nobody maintains them. 4. Since you only use LDR placeholders, most of you installed updates are installed in the lower GDR version with less features. 5. a lot of new updates you did not install on your system if you use only Solors repo So a lot to do. If you run KUC with "force LDR install" and "check for updates that are present as gdl/ldr" as i do, i think, you have over 100 updates to remove and over 100 updates to add.
Running the latest KUC against my new image shows 2632149 missing but the change log shows that it was removed & superseded Am I mistaken that 2547666, 2644615, & 2679255 are needed to satisfy MSU?
good find it's a database error; nevertheless 2632149 and 2708549 contain the same LDR version. no you are not
Ok, if I want to remove superseded updates, I have to force the installation LDR Is what KUC installs two versions (LDR and GDR) or just the LDR? And I have a windows lite (rt7lite) KUC sees updates missing, but I have no need, some components are removed
you can decide. It makes what you want. Select Code: use 'forced LDR install' packages to install LDR packages select Code: check for updates that are present as GDR and LDR to get only the LDR version Komm should really change that text it's misunderstanding. if you don't check this you get GDR and LDR. deselect Code: use "GDR/LDR to keep" if you don't care for WU what updates you do not need? I think the best way is to remove that updates from the c:\wu\repo folder before you start the command files. Or ask komm if he can add a exception.
Thanks joflomo I do not care, but KUC can integrate updates? The superseded updates that I have with KUC, are those in the folder "placeholder LDR" of Solor, but I will check So if I understand correctly, these updates are required if we are not forced installation (LDR)? All updates that will not install And with updates indicated "_BF", if in the script I deleted "_BF" is not good?