mooms Posted January 11, 2014 Posted January 11, 2014 Yes, see second rule. Filenames for Windows 7: IE9-Windows6.1-KB2898785-x64.msuIE9-Windows6.1-KB2898785-x86.msu IE10-Windows6.1-KB2898785-x64.msuIE10-Windows6.1-KB2898785-x86.msu IE11-Windows6.1-KB2898785-x64.msuIE11-Windows6.1-KB2898785-x86.msu If you were thinking about KB2898785 for IE10 in Windows 8 & for IE11 in Windows 8.1 there is no problem, they are regular Windows updates.IE10 is part of Windows 8, IE11 part of Windows 8.1, so their updates don't need any particular order or prerequisites as far as I know. (like IE6 for XP, IE7 for Vista, and IE8 for 7). Edit:To be more idiot proof, maybe you can also add a warning if Win Toolkit detect mixed versions of IE files, like we see here. (only a concerns for Windows 7 so far). Quote
Legolash2o Posted January 12, 2014 Posted January 12, 2014 Just a side note: On the first image, there is a messagebox about saying it needs an update. The latest test no longer shows the message and will just say MAY need the update(s) on it's tooltip. Quote
abbodi1406 Posted January 12, 2014 Posted January 12, 2014 (edited) So what are the MINIMUM required updates for IE to integrate? mooms did a great job in explaining the situation nevertheless, here is the current list:IE11:2670838, 2756651, 2786081, 2882822, 2896820, 2834140, 2888049IE10:2670838, 2756651, 2786081, 2878068, 2896820 Edited January 12, 2014 by abbodi1406 Quote
RicaNeaga Posted January 13, 2014 Posted January 13, 2014 So what are the MINIMUM required updates for IE to integrate? mooms did a great job in explaining the situation nevertheless, here is the current list:IE11:2670838, 2756651, 2786081, 2882822, 2896820, 2834140, 2888049IE10:2670838, 2756651, 2786081, 2878068, 2896820 but isn't this also true? Replace KB2896820-x64 (by KB2905569-x64) So for x64 2905569 instead of 2896820, right? This is kind of useless btw, now that finally integrates IE at the end of the queue, so prerequisites are just for theoretical purposes For Win Toolkit users, of course, that use updates from WHD Quote
abbodi1406 Posted January 13, 2014 Posted January 13, 2014 but isn't this also true?Replace KB2896820-x64 (by KB2905569-x64) So for x64 2905569 instead of 2896820, right? This is kind of useless btw, now that finally integrates IE at the end of the queue, so prerequisites are just for theoretical purposes For Win Toolkit users, of course, that use updates from WHD That's right, but only if 2905569 installed in LDR mode, so i wanted the list to be similar for x86 and x64 also true but lets say some user just want to integrate IE11, then we need the prerequisites list Quote
Thiersee Posted January 13, 2014 Posted January 13, 2014 .......nevertheless, here is the current list:IE11:2670838, 2756651, 2786081, 2882822, 2896820, 2834140, 2888049..... This are the prerequisite for IE11 WHD is offering, they are 9: What is with KB2768486, KB2779272, KB2870165 and KB2896820 (not presenr on WHD)? Thiersee Quote
abbodi1406 Posted January 13, 2014 Posted January 13, 2014 This are the prerequisite for IE11 WHD is offering, they are 9: What is with KB2768486, KB2779272, KB2870165 and KB2896820 (not presenr on WHD)? ThierseeI reviewed the list to the mentioned above, but i was waiting to include it with patch tuesday changes, sorry about thati updated the list now.KB2896820 supersede KB2768486 partially (IE prerequisite component)KB2870165 was taking the same job as KB2896820KB2779272 is just a companion update with KB2756651 to complete KB2729094 (original prerequisite) supersedence, but it's not related to IE prerequisite component.again, sorry for the mix up Quote
ianymaty Posted January 13, 2014 Posted January 13, 2014 Now with the IE integration solved I wanted to make a disc... All was running fine but at the end I saw IE was not integrated with an red X in front and a baloon explanation about requisites. My fault as I forgot to add them to the list. :doh: Along with IE not integrated neither IE-Hyphenation and IE-Spelling was integrated with an black X in front. Only the IE Languages was integrated. (CAB file integration not EXE) So to not see this only at the end of integration, it would be very helpful to check this at the beginning. If you detect the IE for integration scan for the prereqisites and if not detected hold the process and make a note for user to add them to the list. If you consider it as a request, just say and I'll make a post in that thread pointing it out there. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.