Reezo

Hi,
 
Adobe Reader XI 11.0.07 full,Switchless install
- completely silent!!
- no desktop icon
- checked on win 7 (x64x86)
The silent installer can be used in any Windows version that is compatible with the originals setup.
 
 
MD5: 6BFBAB9D914FA4FADD58787F640581DA
Size: 72.0MB
AdbeRdr11007_en_US.sfx.zip

With this maker you can create switchless installers (and RVMi/nLite AddOn), with your own license file, in the language of your choice, and with themes &  others customization.
 
Tutorial:
 
- Download and extract this archive:
 
WinRAR_SFX_Maker_3.4.7z
SHA-1: 1EDCDD7AF14DBC8E034B10B9F68BEF2E94B09B60
Size: 181 KB
Password: mooms


- Download a copy of the WinRAR installer(s) in your language: https://www.rarlab.com/download.htm
You can grab both x86 & x64 versions to make an universal installer, the sfx will take care to install the correct version.
 
- Place the installer(s) in the setup folder. (keep the original names)
 
- Optional: put a valid WinRAR license file (rarreg.key) in the setup folder
 
- Optional: put the theme(s) you want to add in the themes folder, then copy the themes folder in the setup folder.
                     Do not extract or rename the themes.
                     Themes can be downloaded here: https://www.rarlab.com/themes.htm
 
- Optional: If you want to add custom prefs to your WinRAR install (like enabling a theme you have added),
                  you can edit the file rar.reg accordingly and place it in the setup folder.
 
- Optional: If you want to create an AddOn for RVMi/nLite, edit the script and change the value to "set addon=1"
                   Note that starting with version 6.10, WinRAR is not compatible anymore with Windows XP.


- Run WinRAR_SFX_Maker.cmd

The  switchless installer and AddOn are created in the output folder.
 
7-zip must be installed.
 
As long as the WinRAR installer routine is not modified this maker will work, so keep it, it will be useful again when WinRAR will be updated.
(Read this thread for an in depth explanation of the capability of this maker)

.: Installation Notes:.
# Old Versions Are Cleaned Before Installation.
# Initial Auto Starts and Services Removed.
Storage of Setup Files has been removed. Agreements Come Accepted.
# Product Improvement, Digital Edition Help, Acrobat.Com Access Closed.
# All Updates Closed. Update Service is Disabled.
# Wait Until Information About the Installation Is Given…
Download: 
Password: damas
 
Silent installation   x64           x86  
 

All versions in one installer.
Integrated: .NET Framework Setup Verification Tool | .NET Framework Cleanup Tool | .NET Framework Repair Tool
 
.NET Framework is a software framework developed by Microsoft that runs primarily on Microsoft Windows. It includes a large class library called Framework Class Library and provides language interoperability across several programming languages. Programs written for.NET Framework execute in a software environment named the Common Language Runtime. The CLR is an application virtual machine that provides services such as security, memory management, and exception handling. As such, computer code written using.NET Framework is called "managed code". FCL and CLR together constitute the.NET Framework.
 
Version 1.0 is now practically not used, so it is recommended to install it only when necessary, when working with programs that require it (Visual Studio 2002, Sound Forge of some versions, etc.). Version 1.1 does not include version 1.0, nor does it require or replace it during installation. It is used more often, but it is also recommended to install it as needed, only for those programs that are rigidly tied to it. This is due to the fact that the .NET Framework 2.0 package provides backward compatibility with previous versions, and most programs written for 1.0 and 1.1 work without problems in the 2.0 environment (just as programs written under 1.0 can run under version 1.1). In order to avoid conflicts, it is not recommended to install versions 1.0 and 1.1 at the same time (they have some common registry entries). Versions 1.1 and 1.1 SP1 are included with Windows Server 2003 and Windows Server 2003 SP1 / R2SP1 / SP2 / R2SP2, respectively. Version 1.1 SP1 is also distributed on disks with operating systems Windows XP SP2 and SP3 (as a separate distribution kit).
Supported operating systems: Windows 2000, Windows Server 2003 Service Pack 1 for Itanium-based Systems, Windows Server 2003 x64 editions, Windows Server 2008 Datacenter, Windows Server 2008 Enterprise, Windows Server 2008 for Itanium-based Systems, Windows Server 2008 Standard, Windows Vista Business, Windows Vista Enterprise, Windows Vista Home Basic, Windows Vista Home Premium, Windows Vista Starter, Windows Vista Ultimate, Windows XP, Windows XP Professional x64 Edition  
Version 2.0 SP2 includes versions 2.0 and 2.0 SP1 and replaces them during installation. The latest version that supports Windows 2000. To install this and previous versions under this operating system, you may need to install the KB835732 update. This version is included in Windows Vista SP2, Windows Server 2008 SP2 / R2, and Windows 7.
Supported Operating Systems: Windows 2000 Service Pack 4, Windows Server 2003, Windows XP Service Pack 2  
Version 3.0 SP2 does not include version 2.0 SP2, but requires it to install. The unofficial distribution kit downloaded from the link includes both of these versions for x86 and x64 systems. The Russian language pack for version 3.0 SP2 is not included in the distribution kit and is not separately distributed. Installing on a clean system may require Microsoft Core XML Services 6.0 aka MSXML 6.0 Parser (included in the distribution). This version is included in Windows Vista SP2, Windows Server 2008 SP2 / R2, and Windows 7.
Supported operating systems: Windows Server 2003; Windows XP  
Version 3.5 SP1 includes versions 2.0 SP2 and 3.0 SP2. At the beginning of the installation, it tries to connect to the Internet to download the language pack. If you already have this package, the installation should be done while disconnected from the network. After several unsuccessful connection attempts, the installation will continue as usual. This version is included in the Windows 7 and Windows Server 2008 R2 operating systems.
Supported operating systems: Windows Server 2003; Windows Server 2008 Windows Vista; Windows XP  
Version 4 does not include previous versions (1.0, 1.1, 2.0, 3.0, 3.5), does not require them during installation, and does not replace them. The Client Profile is intended for users and provides the launch of applications using the functions of the NET Framework 4. Full contains additional functions not included in the Client Profile, intended for application developers.
Supported operating systems: Windows 7; Windows 7 Service Pack 1; Windows Server 2003 Service Pack 2 Windows Server 2008 Windows Server 2008 R2 Windows Server 2008 R2 SP1 Windows Vista Service Pack 1; Windows XP Service Pack 3  
Version 4.5 is an in-place upgrade to the .NET Framework 4 with a high degree of compatibility. Version 4.5 replaces version 4.0 and does not include previous versions (1.0, 1.1, 2.0, 3.0, 3.5), is included with OS Windows 8. Removing version 4.5 also removes earlier versions 4.0. If you want to go back to version 4.0, you need to reinstall version 4.0 with all updates.
Supported operating systems: Windows 7 Service Pack 1; Windows Server 2008 R2 SP1 Windows Server 2008 Service Pack 2 Windows Vista Service Pack 2  
Microsoft .NET Framework 4.5.2 is an in-place, highly compatible upgrade to Microsoft .NET Framework 4 and Microsoft .NET Framework 4.5. This package can be used for Windows Vista with Service Pack 2 (SP2), Windows 7 with Service Pack 1 (SP1), Windows 8, Windows Server 2008 with Service Pack 2 (SP2), and Windows Server 2008 R2 with Service Pack 1 (SP1)
 
Microsoft .NET Framework 4.6 is a highly compatible, in-place replacement for Microsoft .NET Framework 4, Microsoft .NET Framework 4.5, Microsoft .NET Framework 4.5.1, and Microsoft .NET Framework 4.5.2. This package can be used for Windows 7 Service Pack 1; Windows 8; Windows 8.1; Windows Server 2008 R2 SP1 Windows Server 2008 Service Pack 2 Windows Server 2012 Windows Server 2012 R2 Windows Vista Service Pack 2
.NET Framework 5 is the next iteration of .NET Framework. Apps developed in .NET Framework requires a runtime to run on any compatible computer. The development can be done in Visual Studio. Version 5 specifically requires Visual Studio 2019.
 
 
      Download Microsoft .NET Framework 1.1 - 6.0.7 Final (633.82 MB):
 

All In One Runtimes 12.02.25 Silent 

RuntimePack is a free runtime component assembly installer. The software was created and developed by the Russian developer JamesZero. RuntimePack can be downloaded from any other trusted website. RuntimePack adds runtime libraries to Windows and includes the libraries and components recommended for Windows installation. RuntimePack has most of the runtime libraries needed, making it simpler and easier to install. Unlike its alternatives, Delphi Runtime and Visual C++, with this app, you don't have to install many individual components. 
All in one runtime pack
RuntimePack takes away the hassle of having to figure out which Microsoft Visual C++ Redistributable packages are needed. RuntimePack includes most of the DLL and OCX files required that might be missing or unregistered which causes system errors. It also consists of both x64 and x86 versions, so it works on all Windows PCs. 
Why would one need RuntimePack?
When installing Windows, the runtime library is the library file needed by a program when it runs, provided by the Dynamic-link library. These libraries have various functions in programming and are a practical way to install the sharing function libraries in Windows. The file extensions for these libraries are *.dll, *.drv, and *.ocx. RuntimePack has all these functions in one place, saving you the time of having to install each one of them. 
  When you install an application or a portable version of the software, and if it doesn’t start up or receive an error message, you can use RuntimePack. An example of an error message is 'xxx.dll file is missing; xxx has stopped working'. This error indicates that a dynamic-link library file is missing or cannot be found. 
When this error occurs, you can install RuntimePack. It may not solve all the problems, but it will fix most of them. Apps like RuntimePack are now a necessary tool needed to perform maintenance on your PC.
Detect system architects
When you have RuntimePack running on your PC, it has DLL and VC++ runtime libraries that detect system architects (32-bit or 64-bit). This way, you can install the installation according to the corresponding runtime package. 
RuntimePack is produced and packaged based on the RTM version of VC++ runtime libraries released by Microsoft. Among all the runtime library installation packages (that’s considered all-in-one packages), RuntimePack is one of the best.

    Included Programs and Versions:
Included Programs and Versions:
[Updated] NET Desktop Runtime (8.0.13)
Java SE Runtime Environment (JRE) (8.0 Update 441) [Updated] 
Microsoft Edge WebView2 Runtime 133.0.3065.59 [Updated]
DirectX End-User Runtimes (9.29.1974)
Microsoft Visual Basic/C++ Runtime x86 (1.1.0)
Microsoft Visual C++ 2002-2003 Runtime 1.2.0 [Updated!] 
Microsoft Visual C++ 2005 Redistributable x86 – x64- 8.0.61187 
Microsoft Visual C++ 2008 Redistributable x86 – x64- 9.0.30729.7523 
Microsoft Visual C++ 2010 Redistributable x86 – x64- 10.0.40219 
Microsoft Visual C++ 2012 x86 – x64- Additional Runtime - 11.0.61135
Microsoft Visual C++ 2012 x86 – x64- Minimum Runtime - 11.0.61135 
Microsoft Visual C++ 2013 x86 – x64- Additional Runtime - 12.0.40664
Microsoft Visual C++ 2013 x86 – x64- Minimum Runtime - 12.0.40664 
Microsoft Visual C++ 2022 x86 – x64- Additional Runtime - 14.44.34823  [Updated!]
Microsoft Visual C++ 2022 x86 – x64- Minimum Runtime - 14.44.34823  [Updated!] 
Microsoft XNA Framework Redistributable 4.0 Refresh
MSXML 4.0
OpenAL 1.1
Visual F# 4.1 SDK 
7z SFX Builder v2.1
7Zip 23.09 
NVIDIA PhysX 9.23.1019  
Resource Hacker 5.2.7

  Windows 2000, XP, Vista, 7, 8, 8.1, 10  Silent installation  
 
 

 

This pack update Windows XP / 2003 TimeZones to latest ones that can be found in Windows 10 21H2 v10.0.19041.906 (WinBuild.160101.0800).
This package is MultiLanguage and support all 24 languages. If you need you can install it on live system by extracting TimeZone.inf and install it using right click.
 
Windows 10 TimeZones settings for Windows XP / 2003 - MultiLanguage
Update (11 April 2023)
SHA-1: 10FBB91C683C9E09C16A478F066DE9D787FB0A34
Filesize: 86016 bytes (84 KB)
 
TIP: Use this pack after [REPACK] OnePiece XP Post-SP3 AIO International Update Packs FINAL v1.1.0 and [REPACK] OnePiece XP Embedded Post-SP3 International True AddOn v1.0.2 to fix TimeZones strings.
 

Updated December 14, 2014
(Just after the Patch Tuesday 12/9/2014)
A small as I can complete step-by-step guide to:
WinToolkit
As I did not found a truly comprehensive guide to this fantastic tool, I took the time to write a brand new one.
First, as I’m not that deep in all the staff and as I’m not an English mother language I would accept any kindly correction you would provide to me. I’m considering this a work in progress.
Second, I’m aware that I made some choices here that are personal ones, please don’t hung me on those ones.
What was the goal of the job
Create AIO ISOs customized with multiple languages integrated and with all updates integrated.
What I used to get the job done
Windows 7 SP1 and Windows 8.1 update 1 original ISOs.
As I’m Italian and I have MSDN subscription I used those ones:
For Windows 7 SP1:



x86it_windows_7_professional_with_sp1_x86_dvd_u_677088it_windows_7_enterprise_with_sp1_x86_dvd_u_677749x64it_windows_7_professional_with_sp1_x64_dvd_u_676945it_windows_7_enterprise_with_sp1_x64_dvd_u_677660

and the Language packs and Local Packs


x86mu_windows_7_sp1_language_pack_x86_dvd_6197167601.17514.101119-1850_x86fre_client_localpacks-GRMCLPCKFRE_DVDX64mu_windows_7_sp1_language_pack_x64_dvd_6197147601.17514.101119-1850_x64fre_client_localpacks-GRMCLPCKXFRE_DVD


For Windows 8.1 update 1:



x86it_windows_8.1_with_update_x86_dvd_4048174it_windows_8.1_enterprise_with_update_x86_dvd_4050454x64it_windows_8.1_with_update_x64_dvd_4048528it_windows_8.1_enterprise_with_update_x64_dvd_4048657

and the Language packs


x86mu_windows_8_1_language_pack_x86_dvd_2706085X64mu_windows_8_1_language_pack_x64_dvd_2706084

Windows Assessment and Deployment Kit
http://www.microsoft.com/it-it/download/details.aspx?id=39982
with two option Distribution Tools and Windows PE environment.

WinToolkit

Windows Updates Downloader
http://www.windowsupdatesdownloader.com/ProgramFiles.aspx

as preferred tools to download the updates because it downloads them and preserve their creation timestamp and organize them in a more suitable fashion.
For Windows 8.1 update 1 I also downloaded and used
Script tool from abbodi1406
http://forums.mydigitallife.info/threads/48600-Add-Multilingual-Support-to-Windows-8-1-Setup-DVD-automated-batch-script


Abbodi1406 script works only with Windows 8.1 update 1 images.
Organization
I made a structured folders system: one for Windows 7 SP1 and another for Windows 8.1 update 1

Windows 7 SP1


Windows 8.1 update 1


I will go deep into them, as I will describe the process but take this as fundamental: organization is most the important thing.
Create AIO x86 and x64
I unzipped ISO files with 7-zip and created two set of AIO one for x86 and one for x64 systems.
Here you have sample snapshots of the process:




Then I named the folders this way:


For now on I did a parallel two processes of integration for x86 AIOs and x64 AIOs.
Integrate Languages
Windows 7 SP1
I extracted the Language Pack and the Local Pack from the ISOs and started the integration of them with WinToolkit All-In-One Integrator.



I did it for AIO x86 and the AIO x64.
Windows 8.1 update 1
I used abbodi1406 script to integrate languages and Microsoft .Net 3.5 into Windows 8.1 update 1 images.
Here is the sample of the organization of the folders and the script:


For sure I did one folder and one script for each set: x86 and x64
Integrate IE11 (only Windows 7 SP1)
I used WinToolkit All-In-One Integrator.

Prerequisites files
http://forums.mydigitallife.info/threads/46644-IE11-on-Windows-7
http://www.wincert.net/forum/topic/11582-internet-explorer-11-for-windows-7-is-out/

This is the full list and the exact order in which you should integrate the updates for x64 images:
x64 system updates are the same of the x86 system updates, you can therefore get the x86 list on your own.


------------------------------------------Prerequisites------------------------------------------Windows6.1-KB2786081-x64.msuWindows6.1-KB2670838-x64.msuWindows6.1-KB2834140-v2-x64.msuWindows6.1-KB2882822-x64.msuWindows6.1-KB2888049-x64.msuWindows6.1-KB2871997-v2-x64.msuWindows6.1-KB2970228-x64.msu------------------------------------------IE11 (All languages)------------------------------------------IE11-Windows6.1-KB2841134-x64.cabIE11-Windows6.1-KB2849696-x64.msuIE11-Windows6.1-KB2849697-x64.msu------------------------------------------IE11 Italian------------------------------------------IE11-Windows6.1-LanguagePack-x64-it-it.msuIE-Hyphenation-it.msuIE-Spelling-it.msu------------------------------------------
Integrate the updates
I downloaded the updates using Windows Updates Downloader and getting the last definition ULs here:
http://forums.mydigitallife.info/threads/10872-Windows-Updates-Downloader-Project/page11?p=224955&viewfull=1#post224955
I’ve got some updates directly using Microsoft Update Catalog:
https://catalog.update.microsoft.com/v7/site/Home.aspx
Windows 7 SP1
I organized the updates in 8 subdirectories.



I used WinToolkit All-In-One Integrator.

It’s important to import the updates within each folder in chronological order.
You can do this in one step only.
This is the full list and the exact order in which you should integrate the updates for x64 images.
As x64 system updates are the same of the x86 system updates with the only exception of the KB2506014 update that applies only to x64 systems, you can therefore get the x86 list on your own.


------------------------------------------0-IE11------------------------------------------IE11-Windows6.1-KB2976627-x64.msuIE11-Windows6.1-KB3008923-x64.msu------------------------------------------1-CHOISE------------------------------------------Windows6.1-KB976002-x64.msu------------------------------------------2-ACTIVEX_KILLBITS------------------------------------------Windows6.1-KB2900986-x64.msu------------------------------------------3-DOTNET------------------------------------------Windows6.1-KB2656356-x64.msuWindows6.1-KB2604115-x64.msuWindows6.1-KB2736422-x64.msuWindows6.1-KB2729452-x64.msuWindows6.1-KB2742599-x64.msuWindows6.1-KB2685811-x64.msuWindows6.1-KB2685813-x64.msuWindows6.1-KB2789645-x64.msuWindows6.1-KB2836942-x64.msuWindows6.1-KB2832414-x64.msuWindows6.1-KB2840631-x64.msuWindows6.1-KB2836943-v2-x64.msuWindows6.1-KB2861698-x64.msuWindows6.1-KB2861191-x64.msuWindows6.1-KB2894844-x64.msuWindows6.1-KB2911501-x64.msuWindows6.1-KB2931356-x64.msuWindows6.1-KB2968294-x64.msuWindows6.1-KB2943357-x64.msuWindows6.1-KB2937610-x64.msuWindows6.1-KB2972100-x64.msuWindows6.1-KB2972211-x64.msuWindows6.1-KB2973112-x64.msuWindows6.1-KB2979570-x64.msuWindows6.1-KB2978120-x64.msu------------------------------------------4-SECURITY------------------------------------------Windows6.1-KB2479943-x64.msuWindows6.1-KB2491683-x64.msuWindows6.1-KB2511455-x64.msuWindows6.1-KB2509553-x64.msuWindows6.1-KB2506212-x64.msuWindows6.1-KB2536275-x64.msuWindows6.1-KB2544893-x64.msuWindows6.1-KB2560656-x64.msuWindows6.1-KB2532531-x64.msuWindows6.1-KB2536276-v2-x64.msuWindows6.1-KB2570947-x64.msuWindows6.1-KB2579686-x64.msuWindows6.1-KB2564958-x64.msuWindows6.1-KB2620704-x64.msuWindows6.1-KB2619339-x64.msuWindows6.1-KB2631813-x64.msuWindows6.1-KB2585542-x64.msuWindows6.1-KB2654428-x64.msuWindows6.1-KB2644615-x64.msuWindows6.1-KB2621440-x64.msuWindows6.1-KB2653956-x64.msuWindows6.1-KB2690533-x64.msuWindows6.1-KB2676562-x64.msuWindows6.1-KB2667402-v2-x64.msuWindows6.1-KB2685939-x64.msuWindows6.1-KB2712808-x64.msuWindows6.1-KB2698365-x64.msuWindows6.1-KB2705219-v2-x64.msuWindows6.1-KB2727528-x64.msuWindows6.1-KB2758857-x64.msuWindows6.1-KB2770660-x64.msuWindows6.1-KB2807986-x64.msuWindows6.1-KB2813347-x64.msuWindows6.1-KB2835361-x64.msuWindows6.1-KB2840149-x64.msuWindows6.1-KB2839894-x64.msuWindows6.1-KB2813430-x64.msuWindows6.1-KB2847927-x64.msuWindows6.1-KB2847311-x64.msuWindows6.1-KB2864202-x64.msuWindows6.1-KB2864058-x64.msuWindows6.1-KB2862973-x64.msuWindows6.1-KB2862966-x64.msuWindows6.1-KB2868038-x64.msuWindows6.1-KB2859537-x64.msuWindows6.1-KB2803821-v2-x64.msuWindows6.1-KB2872339-x64.msuWindows6.1-KB2862335-x64.msuWindows6.1-KB2884256-x64.msuWindows6.1-KB2887069-x64.msuWindows6.1-KB2868626-x64.msuWindows6.1-KB2862152-x64.msuWindows6.1-KB2892074-x64.msuWindows6.1-KB2893294-x64.msuWindows6.1-KB2862330-v2-x64.msuWindows6.1-KB2912390-x64.msuWindows6.1-KB2922229-x64.msuWindows6.1-KB2926765-x64.msuWindows6.1-KB2939576-x64.msuWindows6.1-KB2957189-x64.msuWindows6.1-KB2957509-x64.msuWindows6.1-KB2957503-x64.msuWindows6.1-KB2961072-x64.msuWindows6.1-KB2918614-x64.msuWindows6.1-KB2971850-x64.msuWindows6.1-KB2973351-x64.msuWindows6.1-KB2972280-x64.msuWindows6.1-KB2976897-x64.msuWindows6.1-KB2973201-x64.msuWindows6.1-KB2978742-x64.msuWindows6.1-KB2978668-x64.msuWindows6.1-KB2993651-x64.msuWindows6.1-KB2977292-x64.msuWindows6.1-KB2984972-x64.msuWindows6.1-KB2991963-x64.msuWindows6.1-KB2993958-x64.msuWindows6.1-KB2992611-x64.msuWindows6.1-KB3003743-x64.msuWindows6.1-KB3005607-x64.msuWindows6.1-KB3006226-x64.msuWindows6.1-KB3010788-x64.msuWindows6.1-KB3002885-x64.msuWindows6.1-KB3011780-x64.msuWindows6.1-KB3013126-x64.msu------------------------------------------5-NON_SECURITY------------------------------------------Windows6.1-KB971033-x64.MSUWindows6.1-KB2506014-x64.msuWindows6.1-KB2506928-v2-x64.msuWindows6.1-KB982018-v3-x64.msuWindows6.1-KB2515325-x64.msuWindows6.1-KB2547666-x64.msuWindows6.1-KB2545698-x64.msuWindows6.1-KB2563227-x64.msuWindows6.1-KB2552343-x64.msuWindows6.1-KB2660075-x64.msuWindows6.1-KB2640148-v2-x64.msuWindows6.1-KB2709630--x64.msuWindows6.1-KB2718704-x64.msuWindows6.1-KB2732059-v5-x64.msuWindows6.1-KB2719857-x64.msuWindows6.1-KB2732500-v2-x64.msuWindows6.1-KB2729094-v2-x64.msuWindows6.1-KB2732487-v2-x64.msuWindows6.1-KB2761217-x64.msuWindows6.1-KB2750841-x64.msuWindows6.1-KB2763523-x64.msuWindows6.1-KB2726535-x64.msuWindows6.1-KB2773072-x64.msuWindows6.1-KB2799926-x64.msuWindows6.1-KB2791765-x64.msuWindows6.1-KB2798162-x64.msuWindows6.1-KB2820331-x64.msuWindows6.1-KB2808679-x64.msuWindows6.1-KB2847077-x64.msuWindows6.1-KB2846960-x64.msuWindows6.1-KB2868116-x64.msuWindows6.1-KB2853952-x64.msuWindows6.1-KB2852386-x64.msuWindows6.1-KB2893519-x64.msuWindows6.1-KB2891804-x64.msuWindows6.1-KB2913152-v2-x64.msuWindows6.1-KB2919469-x64.msuWindows6.1-KB2928562-x64.msuWindows6.1-KB2918077-x64.msuWindows6.1-KB2929733-x64.msuWindows6.1-KB2843630-v3-x64.msuWindows6.1-KB2908783-x64.msuWindows6.1-KB2800095-v2-x64.msuWindows6.1-KB2966583-x64.msuWindows6.1-KB2978092-x64.msuWindows6.1-KB2980245-x64.msuWindows6.1-KB2977728-x64.msuWindows6.1-KB2985461-x64.msuWindows6.1-KB3001554-x64.msuWindows6.1-KB3008627-x64.msuWindows6.1-KB3006121-x64.msuWindows6.1-KB3006625-x64.msuWindows6.1-KB3009736-x64.msuWindows6.1-KB3013410-x64.msuWindows6.1-KB3014406-x64.msuWindows6.1-KB2952664-v7-x64.msu------------------------------------------6-PRE_RDP8------------------------------------------Windows6.1-KB2574819-v2-x64.msuWindows6.1-KB2857650-x64.msu------------------------------------------7-CAB------------------------------------------Windows6.1-KB2592687-x64.cab Windows6.1-KB2647753-v4-x64.cabWindows6.1-KB2830477-x64.cab Windows6.1-KB2923545-x64.cab Windows6.1-KB2965788-x64.cab Windows6.1-KB2984981-x64.cab Windows6.1-KB2984976-x64.cab Windows6.1-KB2994023-x64.cab ------------------------------------------
Let me say something about the cab files.
I discovered that some updates won’t integrate if you do not postpone their integration and you do not unzip them and integrate only the .cab file within the .msu file.
That's the magic trick to get the job done.
Windows 8.1 update 1
I organized the updates in 8 subdirectories.




I used WinToolkit All-In-One Integrator.

It’s important to import the updates within each folder in chronological order.
This is the full list and the exact order in which you should integrate the updates for x64 images:
x64 system updates are the same of the x86 system updates with the only exception of the KB2973448 update that applies only to x64 systems, you can therefore get the x86 list on your own.


------------------------------------------1-UPD1------------------------------------------Windows8.1-KB2934018-x64.msu Windows8.1-KB2959977-x64.msu ------------------------------------------2-IE------------------------------------------Windows8.1-KB2976627-x64.msu Windows8.1-KB3008923-x64.msu ------------------------------------------3-CHOISE------------------------------------------Windows8.1-KB976002-x64.msu------------------------------------------4-FLASH------------------------------------------Windows8.1-KB3018943-x64.msu Windows8.1-KB3008925-x64.msu ------------------------------------------5-CODEC------------------------------------------Windows8.1-KB2899189-x64.msu ------------------------------------------6-DOTNET------------------------------------------3.5------------------------------------------Windows8.1-KB2968296-x64.msu Windows8.1-KB2966826-x64.msu Windows8.1-KB2966828-x64.msu Windows8.1-KB2972213-x64.msu Windows8.1-KB2973114-x64.msu Windows8.1-KB2972103-v2-x64.msuWindows8.1-KB2894852-v2-x64.msuWindows8.1-KB2979573-x64.msu Windows8.1-KB2978122-x64.msu ------------------------------------------4.5.x------------------------------------------Windows8.1-KB2894856-v2-x64.msuWindows8.1-KB2977765-x64.msu Windows8.1-KB2978041-x64.msu Windows8.1-KB2979576-x64.msu Windows8.1-KB2978126-x64.msu ------------------------------------------Windows8.1-KB2954879-x64.msu ------------------------------------------7-SECURITY------------------------------------------Windows8.1-KB2926765-x64.msu Windows8.1-KB2957189-x64.msu Windows8.1-KB2920189-x64.msu Windows8.1-KB2962140-x64.msu Windows8.1-KB2964718-x64.msu Windows8.1-KB2961072-x64.msu Windows8.1-KB2973351-x64.msu Windows8.1-KB2918614-x64.msu Windows8.1-KB2971850-x64.msu Windows8.1-KB2972280-x64.msu Windows8.1-KB2976897-x64.msu Windows8.1-KB2973201-x64.msu Windows8.1-KB2978668-x64.msu Windows8.1-KB2988948-x64.msu Windows8.1-KB2993651-x64.msu Windows8.1-KB2977292-x64.msu Windows8.1-KB2993958-x64.msu Windows8.1-KB2992611-x64.msu Windows8.1-KB3002885-x64.msu Windows8.1-KB3003743-x64.msu Windows8.1-KB3005607-x64.msu Windows8.1-KB3006226-x64.msu Windows8.1-KB3010788-x64.msu Windows8.1-KB3011780-x64.msu Windows8.1-KB3013126-x64.msu ------------------------------------------8-NON_SECURITY------------------------------------------Windows8.1-KB2950153-x64.msu Windows8.1-KB2956575-x64.msu Windows8.1-KB2959626-v2-x64.msuWindows8.1-KB2958262-x64.msu Windows8.1-KB2965142-x64.msu Windows8.1-KB2955164-x64.msu Windows8.1-KB2965500-x64.msu Windows8.1-KB2969817-x64.msu Windows8.1-KB2962409-x64.msu Windows8.1-KB2971203-x64.msu Windows8.1-KB2973448-x64.msu Windows8.1-KB2967917-x64.msu Windows8.1-KB2971239-x64.msu Windows8.1-KB2980654-x64.msu Windows8.1-KB2981655-x64.msu Windows8.1-KB2975719-x64.msu Windows8.1-KB2990532-x64.msu Windows8.1-KB2993100-x64.msu Windows8.1-KB2979582-x64.msu Windows8.1-KB2993651-x64.msu Windows8.1-KB2990967-x64.msu Windows8.1-KB2977174-x64.msu Windows8.1-KB2995004-x64.msu Windows8.1-KB2994897-x64.msu Windows8.1-KB2984006-x64.msu Windows8.1-KB2998174-x64.msu Windows8.1-KB2995388-x64.msu Windows8.1-KB3003057-x64.msu Windows8.1-KB2976536-x64.msu Windows8.1-KB3003667-x64.msu Windows8.1-KB3008242-x64.msu Windows8.1-KB3008627-x64.msu Windows8.1-KB3000850-x64.msu Windows8.1-KB3014442-x64.msu Windows8.1-KB3004394-x64.msu Windows8.1-KB3013410-x64.msu Windows8.1-KB3013769-x64.msu Windows8.1-KB3013816-x64.msu Windows8.1-KB2989930-x64.msu Windows8.1-KB2994290-x64.msu Windows8.1-KB2976978-v5-x64.msuWindows8.1-KB3012199-x64.msu ------------------------------------------
Some updates come as multiple updates so I downloaded them directly from Microsoft Update Catalog.


---------------------KB2955164 includes:KB2955164KB2965500---------------------KB2962409 includes:KB2962409KB2980654KB2973448 (only x64)---------------------KB2975719 includes:KB2975719KB2995004KB2993651KB2979582KB2993100KB2990532---------------------KB2984006 includes:KB2984006KB2977174KB2995004KB2994897--------------------- KB3000850 includes:KB3000850KB3003057KB3014442---------------------
Integrate the Complements and the Tweaks (optional)
Even if WinToolkit has an embedded RunOnce tool I still like much more the SetupComplete.cmd way to get the job finished.
This step is optional but I recommend it.
Windows 7 SP1
As Windows 7 SP1 needs some components to be installed at the end of the installation and because Microsoft .Net Framework 4.5.2 is not included, actually, you should go through this step.
I will give you a sample of how you can setup this stage but, for sure, you can customize it as you want.
This is how I setup the Complements and Tweaks folders.



This is the SetupComplete.cmd script I'm suggesting:


@echo offdel /q "%USERPROFILE%\DESKTOP\*.lnk"del /q "%PUBLIC%\DESKTOP\*.lnk"start /wait %SystemDrive%\x64\DOTNET\BASE\NDP452-KB2901907-x86-x64-AllOS-ENU.exe /qstart /wait %SystemDrive%\x64\DOTNET\BASE\NDP452-KB2901907-x86-x64-AllOS-ITA.exe /qstart /wait %SystemDrive%\x64\DOTNET\UPDATES\NDP45-KB2972216-x64.exe /qstart /wait %SystemDrive%\x64\DOTNET\UPDATES\NDP45-KB2972107-x64.exe /qstart /wait %SystemDrive%\x64\DOTNET\UPDATES\NDP45-KB2979578-v2-x64.exe /qstart /wait %SystemDrive%\x64\DOTNET\UPDATES\NDP45-KB2978128-x64.exe /qstart /wait %SystemDrive%\x64\EXE\Silverlight-x64.exe /qstart /wait %SystemDrive%\x64\MSU\Windows6.1-KB2533552-x64.msu /quiet /norestartstart /wait %SystemDrive%\x64\MSU\Windows6.1-KB2603229-x64.msu /quiet /norestartstart /wait %SystemDrive%\x64\EXE\WindowsUpdateAgent30-x64.exe /quiet /norestartren %SystemDrive%\x64\INSTALL-COMPLETE.ln_ INSTALL-COMPLETE.lnkcopy %SystemDrive%\x64\INSTALL-COMPLETE.lnk %PUBLIC%\DESKTOP\INSTALL-COMPLETE.lnkshutdown -r -f -t 10
This script must be imported in: %SystemDrive%\Windows\Setup\Scripts
To implement this script I used WinToolkit All-In-One Integrator.

and exacly this one:

This will import x64 folder inside the complements one in the root of the system drive.
For sure you need to organize a x64 and x86 folders with all needed.
To get the job done smoothly I did a trick.
I created a link on the desktop to point the SetupComplete01.cmd file into the CMD folder named INSTALL-COMPLETE.lnk and renamed it INSTALL-COMPLETE.ln_ to have the file imported.
As you can see in the SetupComplete.cmd the last two commands rename back the file and put it on the desktop to have a simple link to the SetupComplete01.cmd that provides this final commands:


@echo offreg delete HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run /v BrowserChoice /fdel /q %PUBLIC%\DESKTOP\*.lnkdel /q %USERPROFILE%\DESKTOP\*.lnkrd /s /q %SystemDrive%\Windows\Setup\Scripts\shutdown -r -f -t 10rd /s /q %SystemDrive%\x64\
This will clean up everything you have to clean up and ends smoothly the installation.
I also did this tweaks configuration too:




#ServicesIP Helper::DisabledOffline Files::Disabled#TweaksAdd 'Copy To Folder' to context-menuAdd 'Move To Folder' to context-menuAdd 'Open CMD here' to Folder Context-menuAdd 'Open Elevated CMD here' to Folder context-menuAdd 'Unpack' to *.msi context menuAdd 'Register' and 'Unregister' to *.dll, *.ocx and *.ax Context MenuAllow 3rd Party ThemesAlways Show Menu BarsDisable 8.3 Name CreationIncrease Icon CacheLaunch Folder Windows in a Separate ProcessRemove Shortcut SuffixShow Explorer StatusbarSpeed Up DesktopSpeed-up Access to AVI Media FilesChange CMD Text Color::Bright GreenEnable DVD in Media PlayerEnable SSL and TLSOpen NFO files with notepadShow Notepad StatusbarAlways Show Menu BarFaster Browsing in IE Launch Internet Explorer in Separate ProcessShow IE Statusbar::Show Status BarTurn On Clear TypeUnlimited Simultaneous DownloadsShutdown Quicker
Windows 8.1 update 1
You can go alongside with Windows 7 sample.
From now on the schema of the steps it’s the same for Windows 7 and Windows 8 so I will give only one sample of it.
Clean up the images (optional)
If you want, you can go one step forward and clean up all the images one by one. It’s a boring job but at the end you can have AIO ISOs files lighter of about 1 GB at least.
These snapshots will give you how to do this job.
You will start with WIM Manager

You will mount the image you want to shrink

You will launch the Cleanup Manager

You will flag all

You will go with Clean

You will have all cleaned

Then you will unmount the image.

Then if you are going to do the same cleaning for other images you will simple save changes

If it’s the latest image you have cleaned up you will save and rebuild.

Create WINAIO x86 and x64
Now you’re done the full job and ready to create your ISO.
If you want a full x86 and x64 AIO you will first go with:

And you will create you WINAIO x86 and x64 folder

Finally, you can create your ISO

The job is done!


P.S.You can accomplish the same kind of job using the same pattern for Windows Server 2008 R2 alongside with Windows 7 and for Windows Server 2012 R2 alongside with Windows 8.1 as they have each other most of the updates in common.

Here, the whole pack: https://onedrive.live.com/redir?resid=E5ED5473010BDF2D!34741&authkey=!AKbMXE0EFOvaBrw&ithint=file%2czip

You can download both packages here:
Download (x86): https://onedrive.live.com/redir?resid=E5ED5473010BDF2D!34627&authkey=!AHvGpjvYJmD-OCs&ithint=file%2czip
Size: 164MB
MD5: 99e7af9079b5100a018a01cc3cabf5ba
SHA-1: 55c414e758443591329f5b2cf1c72498b5e65510
Download (x64): https://onedrive.live.com/redir?resid=E5ED5473010BDF2D!34628&authkey=!AF5ndFxSZWImdAk&ithint=file%2czip
Size: 164 MB
MD5: d3ad145462c791a4176fd5891e145565
SHA-1: 4f9ffebdfdf401f8605df8eb5f864ec957e1d422
To NIM. Sorry, MS grumbles. I changed the links...

Hi. Could anyone reupload this packages?

Hey nice theme on the screenshot
Where did you get it ?
thnks

Is it not possible to go ahead and include VAIO and the WLAN update, or is that against some sort of policy that the authors have set?

Thanks, but $FONT might be better, thats for NSIS varaible ^^.

%WinDir% sKz

Yep peraps you r right, I'll look into that and will release the new version soon. THank you very much.

Hi guys, hi Ricks! ^SoKoOLz^ i noticed that your installer (i've tried only the 2k3 version) installs vista fonts only in "c:\windows\fonts". Obviously this is not a bug and your work is great but maybe people with a different configuration of their hard drives (like "f:\windows" or else) could encounter some problems.
Except this your installer works like a charm! Byezzzz :welcome:

The delay load error is caused by WLan API Hotfix not being installed

Mine is an NSIS Installer, it is much much faster than Ricks method when use it as an Addon. And it also contains the gadget installer already.

Links dont work. And, what is the difference between urs and Ricks?
Edit: Links working now, sorry for that.

Okay, it's been a while since I update this installer.




This installer also comes with /S , Silent Switch command.

Windows Sidebar Installer for Windows XP/2003
Credit:
Ricktendo64
[AddOn] Windows Vista RTM Sidebar (XP Only)*