I do not really understand it's not good if I used Gimagex for mount boot.wim, delete bootmgfw.efi and bootmgr.efi files in Windows\boot\efi and replace them with those of the KB2561821-v2? and after I integrate the KB2561821-v2 in ISO (install.wim) thanks thanks
Just to make thinks more clear: My Excel file contains (I hope all) updates/hotfixes published for Win7 and W2008R2 For normal Win7 users there are only small differences to SoLoR’s Update-List. These differences mostly belong to some additions like RSAT or ADLDS and DVD changes normally not needed. It also includes IE8 updates that SoLoR’s list does not contain any more (since IE9 is out). The newest updates I included will probably be on SoLoR's list next week. To demonstrate the only small differences for Win7 users I added a new “latest for” selection:”Win7 NOT on SoLoR”. As I mentioned earlier, for Win7 users it’s a list to stop all the questions about old updates. You can see with update is superseded and what is needed at the moment. If you use W2008R2 servers like me, here you can find what you need to hold your system to the most up to date state. By the way, I check the updates and hotfixes my own to see what supersedes what. When I find any differences to SoLoR’s list, mostly he’s right and I’m wrong. So, if you want your Win7 system up date, download the .7z file from page 1 of this post and use burfadel’s installer. For experimental use I add 2 new files in the “updates hotfixes” folder: x86.7z and x64.7z. They contain the not superseded updates/hotfixes for 2008R2 an Win7 witch are not available at SoLoR’s update folder, except the really big ones 2483139; 968212; 968211, 963697, 958830. I don't know how quick they can be downloaded.
normaly you integrate updates to the boot.wim images (there are 2) in the same way you integrate them to the install.wim
ok thanks there is a KB2561821-v2 integrate into boot.wim, and which is the 2nd update? must be integrated into boot.wim and install.wim? for 2 updates? thank you very much
I still don't have a perfect understanding of the sequence of integration, but I'm gonna first integrate what's in the root directory, and assume that IE9 is integrated first and then updates later automatically. I will then integrate what's under LDR placeholders. If that's not the way to do things, please do mention.
Simply put integrate root of SoLoR's packs and use burfadel's script.Generally most people do not need the things in subfolders such as MSMQ,IIS etc I used modified burfadel's script to integrate LDR versions to offline image.By modified i mean the integration feature is not officially working yet but i just adjusted some paramaters within the script to make it work.Good thing about integrating LDR versions is also the "no need" for LDR placeholders. So as i said.Nothing too complex.
No ie9 will not integrate first if you use the cmdline/dism, the kb2x hotfixes will go first...but when it comes to ldr placeholders I think you can integrate them before or after it wont matter BTW you dont really need the ldr placeholders if you force integrate the ldr branch using *bf.mum files or if you dont care at all about ldr (you aldso dont need the ie9 cumulative update if you dont force ldr)
I think I've not explained myself too clearly in many posts. What my uncertainty was the order of integrating these updates to an offline image via dism, that is integrating all of these to install.wim, so that setting up new machines will have the latest hotfixes integrated. Burfadel's script wouldn't really help me there, right? Or... will I need to modify certain parameters as well.. Alright, so it would mean that by integrating LDR hotfixes, i can 'skip' LDR placeholders..
may i have a look at your customized script that integrates to offline images? i would like to study it and make it work for myself
Look at his Sites there is a new Win7 Update and a new dot NET Framework 4.0 Extended Hotfix dated 10.10.2011 ... so i think he is still working on it