mooms

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

Lol, more than 700 updates, that's insane ! also, your'e integrating IE9, IE10, and IE11, no wonder it doesn't works ! dareckibmw is right, follow his instructions and you will have a perfectly up-to-date (with the least bloat possible) Windows 7 image.

Seems a faulty USB pen drive.

Hi Lego, Tested beta 5 with Home Premium X86 French: Integration was OK, but I had two errors with RunOnce installer: error1: It is the Root Update installer by Microsoft that can be downloaded here: http://www.download.windowsupdate.com/msdownload/update/v3/static/trustedr/en/rootsupd.exe Works fine with Win Toolkit 1.4.1.27 or if launched manually (without any switches). Command line options ( "/Q" is not needed to launch it silently) Error 2 (it seems the switch "/S" was not passed to the setup) This is an AIO switchless installer made with my maker. Again, works fine in Win Toolkit 1.4.1.27 or if launching "manually" (tested the installer in the same virtual machine). Also, I have found that the silent installer of Flash Player (made with my maker) only installed the plugin version, not ActiveX one. This one is weird because the Active X version is supposed to be installed before the Plugin version. Again, works fine in Win Toolkit 1.4.1.27 or if manually launched. . There is a problem with the new Runonce installer, in particular with switches not passed to the setups. The last two problems have in common to be 7-zip SFX installer, but nearly all installers you can see in the last image are similar and as you can see they have been installed. Others programs and updates installed fine. New function with "Drivers" folder seems to work, but as it is a virtual machine I can't really say. Log have been uploaded to you after the completion. Logs and last session on my disk: WinToolkit141-29Beta_5.zip

Voici un script batch qui va télécharger Thunderbird dans la langue et la version de votre choix, puis modifier l'installateur pour le rendre silencieux. Il peut aussi créer un AddOn RVMi/nLite. Mode d'emploi: Extraire le contenu de l'archive dans un dossier Lancer Thunderbird_SFX_Maker.cmd ou downloader.cmd Vous pouvez aussi ouvrir Thunderbird_SFX_Maker.cmd avec notepad et modifier certaines variables pour éviter une ou plusieurs questions (voir fichier readme). Les fichiers sfx sont créés dans le dossier output Les fichiers d'installation originaux sont téléchargés dans le dossier download Thunderbird_SFX_Maker_5.5.zip SHA1: D6D00BDE18357D992BFA8E8C0182D0A80093AC17 Taille: 2,93 Mo

Here is a script that will download Thunderbird in the language/version of your choice and create a switchless installer (and nLite/RVMi AddOn if you still use it). How-to use: Extract the content of the archive in a work folder. Simply run Thunderbid_SFX_Maker.cmd You can also edit the file to skip one or more question. See the included Readme file Thunderbird_SFX_Maker_5.4.zip SHA1: 3af6498fc4505e75b409eb9b6cf4cbb3209532fb Size: 1.69 MB

This tutorial is more than 6 years old, no wonder some links are dead ! @ricktendo: If you don't want/don't have time to update it, I can if you wish. The 7zsd linked is the first post is a very old version, get latest stable version here: 7zSD A cmd file is a text file with the extension changed, so you just have to create a new text file and paste the content, save it then change the file extension (*.txt to *.cmd) About the content of the cmd file: this cd Bin..\7za a -mx=9 "..\Program.7z" *cd ..can be simplified to this: 7za a "Program.7z" ".\Bin\*" -mx=9So your cmd file look like this: upx --ultra-brute 7zsd.sfx 7za a "Program.7z" ".\Bin\*" -mx=9copy /b 7zsd.sfx + Config.txt + Program.7z Program_Name.exedel Program.7zThe first line upx --ultra-brute 7zsd.sfx is optional, (UPX is an executable compressor, this commands is used to compress 7zsd.sfx) so your cmd file should only have these 3 lines for beginning: 7za a "Program.7z" ".\Bin\*" -mx=9copy /b 7zsd.sfx + Config.txt + Program.7z Program_Name.exedel Program.7zAlso, all the steps that involve Resource Hacker are optionals, you should first familiarize yourself with these things, then you can change the icon, etc.... Two SFX maker (if you prefer using a GUI): http://sourceforge.net/projects/sfx-maker/ http://www.isoft-online.com/