mooms

On which OS are you integrating it ? If you've created a svcpack addon for XP (this kind of addon generally runs at T-13 stage of the install), it is because the first user was not yet created when the sfx was executed so the themes couldn't be copied. Themes are extracted in %APPDATA%\WinRAR\Themes\ variable %APPDATA% is used here because it is user specific, so the sfx must be executed after user login. Edit: I've made a new version: the maker will now also create a svcpack AddOn that is executed at RunOnceEx, thanks to these lines: AutoInstall="hidcon:reg add HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnceEx\\WinRAR /ve /d \"WinRAR\" /f"AutoInstall="hidcon:reg add HKLM\\Software\\Microsoft\\Windows\\CurrentVersion\\RunOnceEx\\WinRAR /v Install /d \"%%S\\%%M\" /f"Please try it and report if it works as intended: WinRAR_SFX_Maker-v2.3.zip edit: link removed, version is deprecated.

Update pack testé en virtuel, tout est OK. Merci!

I've just seen your post. I would have liked to see it before, it would have saved me from making the same mistake than Thiersee... I've added KB2830477 & KB2857650 in the RunOnce pack Because KB2574819-v2 is a prerequisite for these two and KB2592687, I prefer to keep it integrated. I think the issues your mentioned are caused by something else. KB2592687 is still proposed as as optional update so I let it in the RunOnce pack. Thank you for the infos.

Update Packs de Novembre en ligne. Changelog: Si personne n'y voit d'inconvénients je supprimerai les packs IE10 dès le mois prochain vu que IE11 est déjà proposé sur Windows Update.

I see, thanks.

Interesting, even on the Russian thread the latest beta is still 1.6.0.2712, where do you have found this version?

alfreire: Which version of the 7zip sfx module do you use ? I use version 1.5.0.2712 (latest 32bits stable version) This: SetEnvironment="Path=%programfiles%\\WinRAR"RunProgram="hidcon:cmd /c copy rarreg.key %Path% /y"Don't work for me. (Key is not copied, tested on Win7 x86 & x64) This SetEnvironment="Path=\"%ProgramFiles%\\WinRAR\\\""RunProgram="hidcon:cmd /c copy rarreg.key %Path% /y"Works on x86 but key is not copied on x64. But even if it had worked, I think it would have copied the rarreg.key in Program Files (x86) in 64 bits Windows, because we use 32 bits sfx module. This: RunProgram="x86:hidcon:cmd /c copy rarreg.key \"%ProgramFiles%\\WinRAR\\\" /y"RunProgram="x64:hidcon:cmd /c copy rarreg.key \"%ProgramW6432%\\WinRAR\\\" /y"Works 100% of the time. (tested on XP, win7 x86 & x64) :beerchug:

Indeed, we can use %%P to simplify the config file, good finding! About your config file: - You should add \" around appdata and ProgramFiles & ProgramW6432 because the full paths contains spaces) - No need to use xcopy to copy rarreg.key, this is what I use: RunProgram="x86:hidcon:cmd /c copy rarreg.key \"%ProgramFiles%\\WinRAR\\\" /y"RunProgram="x64:hidcon:cmd /c copy rarreg.key \"%ProgramW6432%\\WinRAR\\\" /y"- You can eliminate some switches from your xcopy command to copy themes: RunProgram="hidcon:xcopy Temas \"%APPDATA%\" /s /i /y"Should be enough. Note that %%T isn't needed

Version 2.2: Il est maintenant possible d'inclure un fichier reg pour personnaliser les préférences.

You're welcome alfreire. ____________ V2.2 of the maker: added the possibility to import a reg file with customs prefs (thanks to alfreire for the idea).

That's already done by the original installer if you don't extract it (or if you recreate it like Onepiece explained). In your install scenario the uninstall.exe /clean command should be run before copying WinRAR folder in the program files (you can run it from the temp sfx folder).

That's not true. Try my maker and you'll see.

They are listed in a text file inside the IE11 installer. See also this page from Microsoft. Be aware that some of them are already superseded. If you use my packs you should not worry about prerequisites.

Hi alfreire, that's similar to the OnePiece method he posted above, but with 7zip sfx instead of winrar sfx You can achieve the same without extracting WinRAR setups with this much simpler config file: (Install is silent, all files are in the root of the 7zip archive except themes who are in the Temas subfolder) ;!@Install@!UTF-8!GUIMode="2"MiscFlags="4"RunProgram="x86:rar32.exe /S"RunProgram="x64:rar64.exe /S"RunProgram="x86:hidcon:cmd /c copy rarreg.key \"%ProgramFiles%\\WinRAR\\\" /y"RunProgram="x64:hidcon:cmd /c copy rarreg.key \"%ProgramW6432%\\WinRAR\\\" /y"RunProgram="hidcon:cmd /c xcopy Temas\"%APPDATA%\\WinRAR\\Themes\" /s /i /y"RunProgram="\"regedit\" /S Themdef.reg";!@InstallEnd@!

C'est parce que tu utilise l'édition ultimate (ou intégrale en français). La prochaine fois installe la pro si tu peux. (Pense à supprimer ei.cfg si ce n'est pas déjà fait) http://windows.microsoft.com/fr-fr/windows7/products/compare#T1=tab01

The script was found by Etz, I only made a sfx of it. The Microsoft page about it is here. The main purpose of the vbs/sfx is to achieve MU opt-in unattended. You should try it ,it is simpler than the way you describe (and no need to reboot, it's instantaneous).

Indeed. Either run the vbs or the SFX inside MU.zip and Microsoft Update will be instantly enabled.

Version 2.1: le renommage est maintenant effectué par le maker. Important: le renommage échouera si les noms des installateurs ne sont pas sous cette forme: winrar-x64*.exe pour la version 64 bits wrar*.exe pour la version 32 bits (* peut être n'importe quel nombre de caractères) Si vous le(s) téléchargez depuis le site officiel il n’y aura aucun problème, mais certains sites, comme Clubic par exemple, renomment les installateurs donc attention à ce point. Vous pouvez vérifier que le renommage a bien fonctionné en vérifiant dans le dossier binary une fois que vous avez exécuté le maker: le setup 64 bits doit être nommé rar64.exe et le 32 bits rar32.exe

Version 2.1: now the renaming is done by the maker, you just have to put the installers in the binary folder. Important: renaming will fail if the setup names are not in this form: winrar-x64*.exe for 64 bits versions wrar*.exe for 32 bits versions (where * can be any number of characters) This is the naming convention of the official site so as long as you download them from there it will be OK, but third party download sites often renames the setups so be careful. You can verify the renaming was OK by looking in the binary folder after you ran the maker: the 64 bits setup should be named rar64.exe and the 32 bits setup rar32.exe .

RicaNeaga: Never had a problem with KB2574819 & WinToolkit so for the moment I will keep it in the main packs. Thiersee: I remember having the same problem with IE10, solved with the activation of the compatibility mode on the page: I don't know if it still exist in IE11, but there is an alternative. (put it in silent installers tab of WinToolkit or run it on live install). No doubt MS will address the problem anyway.

Actually it is not only security fixes, it is more a "WU satisfy" (GDR) solution. Also, the solution pointed by bphlpt already exist: it is Windows Updates Downloader with update lists. See also here and here. I don't know if the same can be done with all know hotfixes, and this is indeed a lot of works with 400+ updates and growing....

Nouvelles versions en ligne changelog:

Packs Internet Explorer 11, testés avec WinToolkit 1.4.1.27: Internet Explorer 11 x64 MD5: 7eadf5cb7ca6b4dec6a1eec7eabd5a65 Taille: 54,8 Mo IE11_x64_Fr_2013_11.rar Internet Explorer 11 x86 MD5: 3e39d457f98190cec709a70ebfabac55 Taille: 29,7 Mo IE11_x86_Fr_2013_11.rar Je suis en train d'uploader de nouvelles versions des packs d'Octobre sans IE10, ça permettra de choisir sa version.

Already done I will separate IE10 from the main packs starting today, uploading in progress.

The standalone cab is English IE11 only. The exe setup contains the same cab plus English spell checker and hyphenation packs, and eventually specific language, spell checker and hyphenation packs. You will also find a text file with many links to download language packs. The main advantage of the standalone cab over the one included in the setup: it is updated every patch Tuesday. (No need for additional KB for IE) apparently this is not true anymore with IE11. I have tested the cab integration, it works with WinToolkit 1.4.1.27. Just be careful with the order of the integration, to avoid problems with prerequisites, IE11 should be integrated at the end, then eventually his additional packs. The direct integration of the exe will fail however, because at this day WinToolkit do not recognize IE11 setup, (it expect IE9/10 setup so it need an update).