bphlpt

@Kormann,
 
IMHO, yes IT IS A MAJOR PROBLEM to do what you did.  Reaper has provided this Addon for over five years and last updated this Addon only a month ago, and he is still active on this site.  Just because there have recently been a couple of minor updates to the app does not mean he has to update the Addon for each one, no matter how many posts have been made notifying him of available updates.  In the past, when others have updated Reaper's Addons without his prior permission, Reaper has taken the approach "Fine, if the other guy wants to make the Addon then that's one less Addon I have to make."  and he then pulled his own version and never updated it again, even after the other guy later removed his version.  So unless you are prepared to maintain your update for the next five years or more, then just be patient and wait for Reaper.  And to post your version in his thread is the absolute height of rudeness.

I have moved your post to the trash.

If you want to send any of your work to Reaper via PM as a favor to him to hopefully make it easier for him to keep up the many Addons he maintains for the benefit of all of us, then please do so. If he decides to use your work in any way, then it is up to him to decide that.  If he decides to incorporate any of your suggestions, I'm sure he will give you proper credit.

I realize you had good intentions, and it looked like you did a good job and maybe even made some improvements to the Addon, but please be more respectful of all the hardworking Addon developers on this board.  If you end up making any unique Addons that you are willing to share here, and I hope you do, I will zealously defend your work just as vigorously as I am defending Reaper's.  I hope you understand.  I also encourage you to provide suggestions in the threads of how any of the existing Addons can be improved, but don't post a completed Addon unless it is requested by the original Addon maker.
 
Cheers and Regards

@chytrusek,
 
The issue is not whether SP1 is installed or not.  The reason there is a big difference in the number of updates available from Windows Update vs Alphawaves Downloader is that Alphawaves includes all the updates from Windows Update, the ones dareckibmw refers to as "official updates", PLUS updates that are normally "request only hotfixes", usually meant to solve specific problems and not usually offered to the general public.
 
In the old days, back when MS continued to offer Service packs for their OS, those request only updates would eventually be incorporated into a SP or roll-up along with the standard updates from Windows Update after MS had performed additional testing to ensure compatibility with existing systems generally available. Since MS no longer does that, it is up to you to decide whether you "want" those extra updates to get the latest versions of all the software components involved vs "risk" using updates that your particular system might not "need" based on your actual system use and hardware and other software you have installed. I, and many others, prefer the "be prepared" approach figuring that if MS has determined that an update solves a particular problem, then I want that update too so that just in case I am ever in that same situation then that potential problem will already be addressed.  I have never had a problem created by taking this approach.   dareckibmw, and many others, take the more "minimalist" approach figuring that MS has not determined that everyone needs those extra updates, so why increase the size of their installed OS and add more code complexity that is meant to address situations that they will probably never be in.  Of course you could also take a modified approach of downloading the complete list, but not using the updates that definitely don't apply to your needs such as extra languages or whatever, but since many system components interact in not so obvious ways, that takes more knowledge and research on your part to do that successfully.  That is also why I choose to not remove any system components, as some other folks do, but rather just disable the services and components that I don't need.  You just have to choose which approach fits your needs best.
 
As I said above, in all cases I am aware of, the update lists are meant for systems that already have SP1 installed or included in your install source.
 
Cheers and Regards
 

@chytrusek,
 
The issue is not whether SP1 is installed or not.  The reason there is a big difference in the number of updates available from Windows Update vs Alphawaves Downloader is that Alphawaves includes all the updates from Windows Update, the ones dareckibmw refers to as "official updates", PLUS updates that are normally "request only hotfixes", usually meant to solve specific problems and not usually offered to the general public.
 
In the old days, back when MS continued to offer Service packs for their OS, those request only updates would eventually be incorporated into a SP or roll-up along with the standard updates from Windows Update after MS had performed additional testing to ensure compatibility with existing systems generally available. Since MS no longer does that, it is up to you to decide whether you "want" those extra updates to get the latest versions of all the software components involved vs "risk" using updates that your particular system might not "need" based on your actual system use and hardware and other software you have installed. I, and many others, prefer the "be prepared" approach figuring that if MS has determined that an update solves a particular problem, then I want that update too so that just in case I am ever in that same situation then that potential problem will already be addressed.  I have never had a problem created by taking this approach.   dareckibmw, and many others, take the more "minimalist" approach figuring that MS has not determined that everyone needs those extra updates, so why increase the size of their installed OS and add more code complexity that is meant to address situations that they will probably never be in.  Of course you could also take a modified approach of downloading the complete list, but not using the updates that definitely don't apply to your needs such as extra languages or whatever, but since many system components interact in not so obvious ways, that takes more knowledge and research on your part to do that successfully.  That is also why I choose to not remove any system components, as some other folks do, but rather just disable the services and components that I don't need.  You just have to choose which approach fits your needs best.
 
As I said above, in all cases I am aware of, the update lists are meant for systems that already have SP1 installed or included in your install source.
 
Cheers and Regards
 

@chytrusek,
 
The issue is not whether SP1 is installed or not.  The reason there is a big difference in the number of updates available from Windows Update vs Alphawaves Downloader is that Alphawaves includes all the updates from Windows Update, the ones dareckibmw refers to as "official updates", PLUS updates that are normally "request only hotfixes", usually meant to solve specific problems and not usually offered to the general public.
 
In the old days, back when MS continued to offer Service packs for their OS, those request only updates would eventually be incorporated into a SP or roll-up along with the standard updates from Windows Update after MS had performed additional testing to ensure compatibility with existing systems generally available. Since MS no longer does that, it is up to you to decide whether you "want" those extra updates to get the latest versions of all the software components involved vs "risk" using updates that your particular system might not "need" based on your actual system use and hardware and other software you have installed. I, and many others, prefer the "be prepared" approach figuring that if MS has determined that an update solves a particular problem, then I want that update too so that just in case I am ever in that same situation then that potential problem will already be addressed.  I have never had a problem created by taking this approach.   dareckibmw, and many others, take the more "minimalist" approach figuring that MS has not determined that everyone needs those extra updates, so why increase the size of their installed OS and add more code complexity that is meant to address situations that they will probably never be in.  Of course you could also take a modified approach of downloading the complete list, but not using the updates that definitely don't apply to your needs such as extra languages or whatever, but since many system components interact in not so obvious ways, that takes more knowledge and research on your part to do that successfully.  That is also why I choose to not remove any system components, as some other folks do, but rather just disable the services and components that I don't need.  You just have to choose which approach fits your needs best.
 
As I said above, in all cases I am aware of, the update lists are meant for systems that already have SP1 installed or included in your install source.
 
Cheers and Regards
 

it is infact me in the avatar my friend thinks im silly to dress this way with my disability but im actually trying to be serious belive it or not.  Thank you so much for your kind words it means alot to me to get a compliment for once even more so with it being about my one leg :throb:

Hi Ruby!  Welcome to WinCert!  I think you are neighbors with at least a few of our members.  I hope they will introduce themselves to you as such.  Please participate as much as you like and have a great time!
 
Cheers and Regards
 
[ I hope you don't mind my saying that if your avatar is anywhere near accurate, that your remaining leg looks more than good enough to replace most folks two legs.  Congrats on your successful recovery.  Stay happy and healthy. ]

Hello everyone im Ruby Smith, Age 30, female,Sheffield U.K, Looking forward to being part of this community and maybe even making a new friend or two if im lucky I have a broard range of interests i basically love to tinker around with stuff abit too much but mainly pc or console related.
To save you the bother asking me Yes i do only have one leg, 4 years ago i was in a car crash and my hip and leg were smashed to bits and after battling with the pain and making very little progress to recover from this after almost 3 years i gave up and and had my right leg amputated for a better quality of life. It was hard adjusting at first but now with my prosthetic leg iv finally achieved what i wanted and can now walk again  YAYY
 
 

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.

The best alternative I can come up with is to remove the checkbox and add a 'Save and Rebuild' option.
 
Save and Rebuild Save Discard Keep

I have un-hidden all of the older versions that were uploaded to the download page since the start of 2013.  For those that haven't found which page they are listed on, it is this one, which is the main Win Toolkit download page.  The one on the top is they latest version, and the older versions are available on the right.
 
[ NOTE: Liam, the writeup on that page says that .NET 3.5 is required for XP and Vista users, but isn't .NET 4.0 required now?  If so, that note should be changed and an appropriate link should be provided.]
 
Cheers and Regards

1 ) Take the DateToIntegr8.vbs script above, (just delete the .txt part of the name) and save it wherever you want, say C:\time.
2 ) Then open a command prompt in that directory.
3 ) Enter the following command: cscript DateToInteger8.vbs "06/09/2014 10:30:00 PM", where the date and time are that of your local time zone
4 ) Use calc.exe (programmer mode) to convert to hex (QWORD) - Enter the output from DateToInteger8, which will be a decimal value, in the calculator in decimal mode, then switch modes to hex to see the hex value you need.
5 ) @KEiGHT, in his local time zone got: 1CF842195DB5400
6 ) You can validate that the value you have is correct by entering in the command prompt: w32tm /ntte 0x1CF842195DB5400
7 ) @KEiGHT, in his local time zone got: 151004 20:30:00.0000000 - 6/9/2014 10:30:00 PM
8 ) Zero pad the value from the calculator to get 16 digits: 01CF842195DB5400
9 ) The leftmost 8 digits will be the highpart (01CF8421) and the rightmost 8 digits will be the lowpart (95DB5400).

I'm not sure if the date displayed in the OS version selection window is that of your local time zone or GMT, so you might have to adjust the values you enter above slightly, but since the output from w32tm includes GMT you should be able to figure out what you need to change.
 
So you found the .xml file where you need to enter this revised value?  Where is it?
 
Cheers and Regards

Windows XP itself no longer has any official updates.  Some of the various security addons such as the Malicious Software Removal Tool still seem to get updates.  But POSReady 2009, which is based on XP SP3, is still scheduled to receive updates until 2019, and there has been a trick discovered that allows your XP installation to appear to be POSReady 2009 to Windows Update, so the POSReady 2009 updates can be downloaded and installed to your XP installation.  Does that answer your question?
 
Cheers and Regards

Liam knows this, and he has said he will work on providing the ability to allow Win Toolkit to be translated in other languages in the next generation version of Win Toolkit:
 

Cheers and Regards

request filled

Liam knows this, and he has said he will work on providing the ability to allow Win Toolkit to be translated in other languages in the next generation version of Win Toolkit:
 

Cheers and Regards

Thanks Rick.  I'll go ahead and ask since I know there are others that would like it, but is there a chance you could make a similar pack for XP x64 and 2003?  ( I assume the same pack could be installed on both? )  I think that type of pack has always been missing from the various .NET offerings.  Just a thought.
 
Cheers and Regards

Read the entire thread.  Yes he was trying to use all possible updates, but he did quite a bit of analysis to determine which lists are the most complete and up to date and without duplicates.
 
What is your intention?  Just to satisfy Windows Update or get all available updates?  And are you building an install source just for your personal home use or are you making an install source for business use or what?
 
 
1. Yes there are that many updates available if you include the request only updates.
1a.  I haven't checked all of the various lists, but reasons can include:
 
* some lists might, or might not, include updates that are obsolete
* some lists might not be up to date
* some lists might, or might not, include request only updates
* some lists might, or might not, include updates that cannot be applied on an offline image
* some lists might, or might not, include updates that only apply to optional features

2&3. Windows Update does not, and cannot, download request only updates, even though the request only updates ARE "real" updates, they just might, or might not, officially apply to you at this time.
 
Request only updates are updates, or hotfixes, that have been developed by MS to deal with specific problems and generally they have not been tested quite as extensively on as wide a variety of systems as the "regular" updates that are pushed out by Windows Update, so there is a very small possibility that they might cause an issue on your system.  But that risk is extremely small and I know of no one personally that has ever had an issue if they installed those request only updates.  But even regular updates have caused issues in the past so it is possible.  Back when MS used to put out Service Packs, such as SP1, ALL updates issued prior to that time would be included in the SP, both regular and request only, so many folks, including me, just figured they might as well go ahead and install the request only updates when they became available, even if they did not apply to them at that time, "just in case".  Others just wanted Windows Update to say they were up to date, and they thought "unnecessary" updates just added bloat and applied to issues that they were unlikely to have, so decided not to install them.  It's up to you to decide what you want.  If you decide that you do not want any of the request only updates, then you might find this thread useful - http://www.wincert.net/forum/topic/10811-15-mars-2014-updates-packs-gdr-windows-7-sp1/ - but I have not checked lately to see if all links are still valid or if it is up to date.  You'll probably need to at least read the first page and the last couple of pages in the thread using a translation program such as Google Translate to know for sure what is going on.
 
As a general rule, you will be better off if you decide whether you want Request only updates or not, pick ONE list that seems to be kept up the best and meets your needs, and just use that one list.  Then pick up the few, if any missing updates after you have installed your system using Windows Update.
 
Good luck!
 
Cheers and Regards

Yes - .NET Framework 4.0
No - .NET Framework 4.5
No - .NET Framework 4.5.1
No - .NET Framework 4.5.2

This is mainly intended for use with XP. In XP, AFAIK NET 4.5.x will not function, even if you can seem to get it installed.

If you need .NET 4.5.x for use with Win7, then you should probably use this one - http://www.wincert.net/forum/topic/10715-rebuilt-net-framework-452-full-x86x64-5-06-2014/.  .NET 4.5.2 completely replaces 4.5 and 4.5.1.
 
Cheers and Regards

NP, I know you're just trying to help.  If kanyos wants to take advice from you and Rick to improve his release then all is fine and all benefit from the interaction.  But if he wants to leave it the way it is, then your posts and especially those of chymax3m should be split out into their own thread, at least IMHO. But this is kanyos' thread so I'll let him decide what he would like to do.

Cheers and Regards

Guys, please stop hijacking kanyos' thread!
 
@kanyos, if you will PM me, or one of the other mods, a list of the posts in this thread that you would like removed, they can be split out into their own thread if you think that would be appropriate.
 
Cheers and Regards

Actually, no.  .NET 3.5 is included in Win7, but not 4.0 or 4.5.  (You can add either one you want, if either, but not both, since 4.5 completely replaces 4.0.)
 
The easiest way to add whichever one you want is to use an installer or addon that is already updated with all the available updates, such as this one, or this one, or this one.  They are made to install on an already installed OS, or at least after first log on.  As a newbie, you might be more comfortable with this one, which is made specifically to be used with Win Toolkit, but Win Toolkit can be made to use any of the others as well, if you prefer.  I know Rick's are all up to date, but I'm not positive about the other one.  Good luck!
 
Cheers and Regards

Remember, removing components with Win Toolkit does NOT typically remove much if anything from the ISO, but rather those components will not be installed so your installed size will be smaller.  If the smallest Win7 ISO is your overriding desire, then you will probably be happier using a different tool.
 
Cheers and Regards

I believe that the DISM available through the latest version of 8.1, update, is capable of handling .ESD files.  I think it would only be applicable to Win 8.1 (?), but then those are the only versions of Windows I've seen .ESD files used for.  So this should be able to to added to Win Toolkit when Liam has the time.
 
Cheers and Regards

I believe that the DISM available through the latest version of 8.1, update, is capable of handling .ESD files.  I think it would only be applicable to Win 8.1 (?), but then those are the only versions of Windows I've seen .ESD files used for.  So this should be able to to added to Win Toolkit when Liam has the time.
 
Cheers and Regards

Thanks for the info!
 
Cheers and Regards