mooms

No actual need to repack, installer can be used as-is with the switch /y to make it passive or /ai to make it completely silent (not recommended as the install is relatively long). You have to repack only if you want to change something in the default installer. Personally, instead of using Intl installer, I repack the US one to add French langpack , this save space & time on unpacking (just before installing), but that's completely optional and don't change anything the the actual install.

As a silent installer, in the silent instal+SFX tab of Win Toolkit. 4.0 was updated recently, that's all, there is no mixup.

What are you talking about ? This thread is only for 4.5.1 and there is no mention to XP. To be clear: 4.5.1 is only for Win7. 4.0 can be installed on XP and 7. 4.5.1 replace 4.0, no need for both in Win7. You can pack the 4.0 into and addon for XP. For win7, no need for an addon, can be added 'as is' in Win Toolkit. And yes, you can use the tools provided to remake your own installer.

Win Toolkit 1.4.29 est dispo et il gère correctement l'ordre de priorité de IE, ses addons et ses maj, qui se retrouvent intégrés à la fin. ça signifie que le renommage (z-) deviens inutile. Il accepte aussi directement le setup (exe) de IE11, mais il n'est pas rajouté avec les autres maj, il faut le sélectionner à part. Les packs IE11 s'en trouveront simplifiés. Petite mise en garde si vous utilisez la v1.4.29 avec le pack IE11 de Décembre, supprimez z7- devant KB2898785, sinon la KB sera installée avant IE11 et donc échouera.

Nouvelle version: ajoute la possibilité d'importer des tweaks depuis un fichier reg.

New version: added the possibility to import reg tweaks and added a readme file.

Just tested integration and silent installers on Win7 x86: all is OK. Will test with Win7 x64 and report here. edit:ok with x64.

Allright it is major1.major2.minor.build (with build number hidden except for test builds) And what's the "1" before the change ?

But don't use the test build for anything else than downloading updates, currently test17 is bugged, see this. There is other ways to obtain latest updates: If you don't want LDR hotfixes, there is many updates list/packs that are up-to-date: http://www.wincert.net/forum/topic/10811-11-d%C3%A9cembre-2013-packs-de-maj-gdr-pour-windows-7-sp1/ http://www.wincert.net/forum/topic/11319-update-list-gdr-pour-windows-7-sp1-x64-d%C3%A9cembre-2013/ http://www.msfn.org/board/topic/139877-post-sp1-updates-for-windows-7-updated-20122013/ http://www.windowsupdatesdownloader.com/UpdateLists.aspx If you want QFE/LDR hotfixes: http://forums.mydigitallife.info/threads/44645-Windows-Hotfix-Downloader-5-1 http://forums.mydigitallife.info/threads/19461-Windows-7-Hotfix-repository/page894

Result of the test with test17: All updates showed as integrated: 1 2 Once on the desktop, only 109 updates installed. It should be 145 I used the exact same configuration than test16 (copied ini and settings). edit: didn't see your post dareckibmw, so the bug is confirmed. In a sense, I'm glad I'm not the only one, that means the bug is not on my end.

One question: can you explain your numbering scheme ? I agree with the change anyway, this numbering scheme is more easy to understand.

It shows 109 updates installed. (should be 145) 135 updates are integrated and the rest is installed at RunOnce so it seems consistent with Windows Update. Yes I'm sure. In this case it should be way more than 41 updates found on WU anyway. Not sure about this particular sentence, but I didn't see any error message and all updates were reported as integrated in the Update+Language tab. (all were in green, then showed install pending once finished) Will test again with test17 and report here.

Result of the test: IE11 is successfully integrated and in French, all silent installers are successfully installed, but: - Windows Update founds 41 updates (not counting Windows Defender Update). All of them have been reported successfully integrated by Win Toolkit. see image: Logs are here: WinToolkit141-29Test_16.zip

Seems more future proof

Indeed. I think you should move main cab/exe to the top of IE group before clicking start, seeing the actual integration order before pressing start seems more intuitive and should avoid confusion. I have launched the integration process in Win7 HP x86 French and IE Fr x86 + KB2898785, I will let Win Toolkit upload the log to you and reports here how integration & installation behave.

Tested the integration order of IE11 French with test 16: All files have their original name. IE11 cab: Order is not good, hyphenation and spelling libraries are added before IE11 cab. See picture: IE11 exe: First, the IE exe is not added if I use add updates+subfolders, I had to use add updates and change the target from msu/cab to exe, I think this can be merged into one ? After succesfully added the exe, I can see the order is again not good, see the picture: Third test, just for completeness: If I rename IE files with "Z-number" in front (that the trick I use in 1.4.1.27), order in IE group is good, but KB2898785 is not added in IE group. (it is in the last entries of main group but this seems logical, it is not really a bug). See image:

That's perfect. That's not "idiot" proof, many unaware users will have issues with this setup. You should move them automatically at the bottom of the IE group. See this for more details and suggestions. An option to move any updates from their group is a good idea, it is more future proof.

Please, fix the issue with IE integration order before releasing 1.4.1.29, so we can test it before the incoming patch Tuesday.

Yes, see second rule. Filenames for Windows 7: IE9-Windows6.1-KB2898785-x64.msu IE9-Windows6.1-KB2898785-x86.msu IE10-Windows6.1-KB2898785-x64.msu IE10-Windows6.1-KB2898785-x86.msu IE11-Windows6.1-KB2898785-x64.msu IE11-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).

Yes. Its is much simpler for everyone. If I remember Ricaneaga have made a similar request recently. Edit: yes, see here.

I suspect the only mandatory thing is IE main cab first then all the others cab/msu related after it, with no particular order. You should code something base on these three rules: First rule: - If filename [*.exe] starts with the string ie (case insensitive) then it is IE Setup: + Extract it to a temp folder and delete the file named [*support*.cab]. + Add all others msu/cab in temp folder to integration list with respect to the second rule. Second rule: - If filename [*.cab][*.msu] starts with the string ie (case insensitive) then it is IE main cab or language pack or hyphenation or spelling pack or IE update. + Move the main IE cab after all other updates. + Move all others after the main IE cab. These two rules should do the trick for IE9/10/11(12?) and it will be much simpler to maintain. You could visually representing that in Win Toolkit GUI by creating an IE group at the bottom of integration list.

That's showed in my image. My way (I use cab versions of IE11): - IE main cab, then MSU/cab addons, then IE update(s). I rename the files with Z+number in front to achieve this in 1.4.1.27. (see image). The same with IEsetup.exe: - The cabs/MSU of the extracted IEsetup.exe (IE-Win7.CAB first then others msu/cab*), then IE update(s). * Minus IE_SUPPORT_*.CAB that is not needed in integration.

@Lego: If you move IE and all the related updates/addons to the end of the integration process, you should not worry about prerequisites. That's the smartest and simplest way , because months after months, more and more updates will be superseded and because of this the list of prerequisites will be constantly changing. Win Toolkit 1.4.1.27 does not recognize IE11 cabs and let me integrate them at the end: that works beautifully ! Because an image worth thousand words:

You have to understand that QFE/LDR hotfixes are not meant to be used in general usage (that's the purpose of GDR). Their purpose are to fix particular bug(s), and they are only distributed by MS by express demand of a customer (generally a sys admin, not the average Joe). They are not meant to be blindly installed/integrated as you are doing ! QFE/LDR hotfixes are not as much tested as GDR, and they can do more harm than good (new bugs, regressions, etc...) if not carefully and wisely used. Even GDR updates are sometimes buggy and must be removed for Windows Update.... Also, as Lego as stated, they are many in your list that are superseded, and it is very time consuming to maintain an up-to-date list of all KB. The names are pretty self explanatory: GDR means General Distribution Release LDR means Limited Distribution Release. QFE, the ancient name of LDR, means Quick Fix Engineering. If you really want as much update as possible, use this (and only this): http://forums.mydigitallife.info/threads/44645-Windows-Hotfix-Downloader-5-1

I don't see any advantages to integrate as much as possible, only inconveniences