ricktendo

Microsoft only offers you the critical security updates that will protect you from hackers, McRip/komm/SoLoR updates are ALL updates since SP1 which are (hot)fixes that are going to be added to SP2 So if you only want to be protected use what Microsoft is offering, if dont want to wait for SP2 to have all the fixes then use the update pack

It used to be important with the old RVM integrator, only a updatepack could have a entries.ini. The others had to have entries_<something>.ini but I dont think you need to worry about it anymore

Done, tomorrow will see if I can do the LP's

Slim Microsoft .NET Framework 4.6.1 Full x86/x64 Slim Microsoft .NET Framework 4.6.1 Full x86/x64 Incl. Language Packs (ar cs da de el es fi fr he hu it ja ko nl no pl pt-BR pt-PT ru sv tr zh-Hans zh-Hant) Some tools and resources for (re)creating your own slim (intl) installer .NET4.6.1 SFX Maker (installer repacker): .NET4.6.1 Intl SFX Maker (if you want to add LP): Silent "No GUI" SFX alternative: Slim down your dotNET4(.6.x) & LP installers: If you cant find a hotfix try using the KB(1234567) number w/ this URL: Slim Language Packs: Arabic: N/A Chinese (Simplified): Chinese (Traditional): Czech: Danish: Dutch: Finnish: French: German: Greek: Hebrew: Hungarian: Italian: Japanese: Korean: Norwegian (Bokmal): Polish: Portuguese (Brazil): Portuguese (Portugal): Russian: Spanish: Swedish: Turkish: http://support2.microsoft.com/hotfix/KBHotfix.aspx?kbnum=1234567

Depends when its executed, if you use OnePiece tool (I think it executes during setup) you have to repack it like he describes. If you install it during RunOnce or after the desktop launches you can use the default package

Whose updates are you using? I recommend running KUC to scan for updates

Yep, integrate the 3 CAB's like you would a MSU hotfix

Install drivers, then go to %WinDir%\System32\DriverStore\FileRepository, sort the folders by date and your drivers should move to the top

Con tal que usen el mismo URL de adFly no, no me molesta

Updated 10-10-2012 Add: 2756195 Rem: 2545756

Correcto, sigue igual

Actualizado Por fin, puedo aceptar donaciones por paypal

Use the 3 CABs, you can also extract them from these installers

Nope they are not stripped out, they will not install on 32 bit OS (to save space) I did remove ia64 and w9x "kerneld"

dism /Unmount-Wim /MountDir:C:\mount /commit

If you made a AIO disk then I guess you used the X86 iso to create it, so integrate the x86 drivers into your boot.wim...now when it comes to install.wim integrate the x86 drivers in the x86 image and x64 into the x64 image (no need to integrate the x86 drivers into x64 image or vice versa, they will only take up space) BTW does not matter if a driver has the same filename, Windows takes care of this by adding a hash number after the INF foldername in DriverStore To integrate multiple drivers just point dism to the root folder and use /Recurse switch, example: dism /Image:X:\<MountDir> /Add-Driver /Driver:X:\<RootFolderName> /Recurse You may want to have a look at these WAIK vids I did a while back

Integrate your usb3 drivers into both boot.wim and install.wim

Updated FX v1.4.7

I dont understand what problem you are running into BTW I dont use the EXE I use the 10.1.0 MSI and in it I integrate the 10.1.4 MSP, remove old VC Runtimes, then I process it with Adobe Customization Wizard (you may have to create a dummy Setup.ini) and also manually do some cleaning with InstEd (remove Setup.ini refrences and other misc stuff)

Its enabled by default, no need to do nothing

With Win8 when you disable you can also chose to /remove the feature from the winsxs dir, it does not remove the files from withing the wim you will have to wait for install to leave the files behind

Si, completamente normal...por eso tuve que publicar a 1.7.0 (incluye KB2744842)

OK spammer you are BANNED :banned2: LOL just a reflex

Updated ccleaner and winapp2.ini

Is the contest over, is it too late? Ricardo Cooper