Legolash2o

Sorry i was asleep and i uploaded it late at night, you will find it has been corrected. Note: They wasn't really a need to double post but i've merged your posts anyway.

I haven't added support for compressed drivers, probably wont anytime soon.

Which part of the integrator, or did you mean the entire thing lol

This has been fixed, sorry about that

http://www.computersnyou.com/2012/03/vmware-windows-8-key-problem.html

OK, i've testing it and it's all fixed.

I did say that IE9 integrate WILL go red all the time no matter what, even if it integrates However i've fixed that and just fixed a massive bug

Update: After installing all updates in alphabetical order, i integrated 336 and at the end 339 was integrated with nothing red I'm going to test integrating everything in descending order and see what happens

The strange thing is i'm installing my updates in alphabetical order and they all seem to be going green So ordering them by KB may be the solution

The red bar thing for IE9 is normal, i was expecting that! I haven't added the proper detection code for it, to be honest i think im gonna get rid of the red/green bar thing

An update it needed must of been installed then

ignore the red IE9, the detection doesnt fully work

I never really use additions, is there a special way you have to integrate them?

is that all of the Red errors or is there more? 3 of them are NFS (Only applicable in special cases) 1 of them is for UNIX-based applications 2 of them probably need something else installed first, ill google them KB2636613: Windows-TerminalServices-RemoteApplication (LDR only) KB2519946: synth3dvsc.inf UPDATE: http://forums.mydigi...ll=1#post379755 and http://forums.mydigitallife.info/threads/19461-Windows-Hotfix-repository?p=379763&viewfull=1#post379763

As you may have noticed they're a lot more guides in the Windows 7 Toolkit Guides sub-forum, i would appreciate it if anyone would read through them and give me some feedback here, and what sort of stuff you think i have missed or could explain more on. Feedback in here please Thanks

For some reason it was hidden before, i just made it visible

Source Basic Description General Distribution Release GDR packages contain only security and critical stability issue fixes. These are usually released via Windows Update. Limited Distribution Release LDR packages contain "other" fixes that have not undergone as extensive testing, and resolve issues that only a fraction of the millions of Windows users might ever encounter. You usually request these from the Microsoft website but they're mostly found in SoLoR Updates. Quick Fix Engineering QFE is the old name for LDR (above). How are they installed differently? At the end of the day, if you have LDR/QFE Mode enabled it will install LDR Mode if the update has that option regardless if its cab or an msu file. MSU Files *.msu files will get installed normally using the command below. pkgmgr.exe/norestart /ip /o:"C:\W7T\Mount;C:\W7T\Mount\Windows" /m:"UpdateLocation\update.msu" /quiet If you have LDR/QFE Mode enabled then the *.cab file is extracted and the below (CAB Files) method is then applied to the newly extract cab file. CAB Files Normally *.cab updates have a file called 'update.mum' but LDR updates also have a file called 'update-bf.mum', if the 'update-bf.mum' is not detected W7T will install cab files normally. Cab files are usually extract from the msu file or when a user has used 'MSU to CAB Converter' pkgmgr.exe/norestart /ip /o:"C:\W7T\Mount;C:\W7T\Mount\Windows" /m:"CABLocation" /quiet If, however the update-bf.mum has been located it will extract the cab to a temp folder and install both *.mum files like so: pkgmgr.exe/norestart /ip /o:"C:\W7T\Mount;C:\W7T\Mount\Windows" /m:"ExtractCABTemp\\Update.mum" /quiet pkgmgr.exe/norestart /ip /o:"C:\W7T\Mount;C:\W7T\Mount\Windows" /m:"ExtractCABTemp\\Update-bf.mum" /quiet That's it. Full Description Out of the box, all of the files in Windows are on what we refer to as the "General Distribution Release" (GDR) branch. If updates are only delivered from Windows (or Microsoft) Update (including via WSUS), then all the files remain on the GDR branch. Some KB articles have packages to address specific issues that are not delivered by Windows Update - "Limited Distribution Release" (LDR) branch packages. Previously we used the term "Quick Fix Engineering" (QFE), but LDR has taken over – expect to see these terms used synonymously. GDR packages contain only security and critical stability issue fixes. LDR packages contain "other" fixes that have not undergone as extensive testing, and resolve issues that only a fraction of the millions of Windows users might ever encounter. It is not the entire OS that is considered GDR or LDR - it is down to the individual file level. A package delivered by Windows Update contains both GDR and LDR versions of the files it updates, so that it is able to replace the files on the system regardless of which branch they are currently on. A package acquired outside of Windows Update contains only LDR versions of the files it updates, and this will "move" the files onto the LDR branch where they will remain until the next Service Pack. A Service Pack (SP) contains only GDR branch versions of the files which have been updated by ANY package since the previous Service Pack (or RTM). So installing the latest Service Pack at, or shortly after release will likely put all of your files (back) onto the GDR branch. One other thing that Service Packs imply is that hotfix packages need to have versions of the files to replace for the most current SP level and the previous one (dubbed "N and N-1 support"). So for every single file updated by a Windows Update hotfix package after the first SP, there are 4 versions of the file present: "N-1" GDR "N-1" LDR "N" GDR "N" LDR Taking a ficticious example, where we have the following files straight out of the box: A.EXE RTMGDR 1.0 B.DLL RTMGDR 1.0 C.SYS RTMGDR 1.0 1) Hotfix package KB000001 is installed through windows Update, and contains an update to B.DLL - this pacakge contains: B.DLL SP1GDR 1.1 B.DLL SP1LDR 1.1 > The SP1GDR version is installed by default, and there are only 2 (identical) versions of this file in the package as we're not yet at SP1. The machine now has: A.EXE RTMGDR 1.0 B.DLL SP1GDR 1.1 C.SYS RTMGDR 1.0 2) Hotfix package KB000002 is installed, NOT through Windows Update, and contains an update for A.EXE - this package contains: A.EXE SP1LDR 1.02 > No options here, the version that ends up on disk is now the LDR version The machine now has: A.EXE SP1LDR 1.02 B.DLL SP1GDR 1.1 C.SYS RTMGDR 1.0 3) Hotfix package KB000003 is installed through Windows Update and contains an update to A.EXE and C.SYS - this package contains: A.EXE SP1GDR 1.11 A.EXE SP1LDR 1.11 C.SYS SP1GDR 1.11 C.SYS SP1LDR 1.11 > A.EXE is on the LDR branch because of KB000002, while C.SYS is still on the GDR branch The machine now has: A.EXE SP1LDR 1.11 B.DLL SP1GDR 1.1 C.SYS SP1GDR 1.11 4) Hotfix package KB000100 is installed through Windows Update, and contains an update for C.SYS for the RTM and SP1 versions of the OS - this package contains: C.SYS SP1GDR 1.5 C.SYS SP1LDR 1.5 C.SYS SP2GDR 2.5 C.SYS SP2LDR 2.5 > OS level is still RTM, the current file is on the GDR branch, so we remain on the GDR branch The machine now has: A.EXE SP1LDR 1.11 B.DLL SP1GDR 1.1 C.SYS SP1GDR 1.5 5) SP1 is now installed on the system, which contains only GDR version 2.0 of every file: A.EXE SP1GDR 2.0 B.DLL SP1GDR 2.0 C.SYS SP1GDR 2.0 > OS level is now raised to SP1 and we push all files on the GDR branch... but look what happens to C.SYS... The machine now has: A.EXE SP1GDR 2.0 B.DLL SP1GDR 2.0 C.SYS SP2GDR 2.5 > The SP1 package does not contain anything other then the GDR 2.0 versions of the files… so where did the GDR 2.5 version come from? The hidden, compressed folders named $NtUninstallKBxxxxxx$ in the %systemroot% folder contain the backup of the version(s) of the replaced file(s) when the hotfix was applied, plus the executable to uninstall the package (in the spuninst sub-folder). The hidden $hf_mig$ folder in the %systemroot% folder contains all the files extracted from the hotfix packages in sub-folders KBxxxxxx- these are necessary to ‘migrate’ the hotfix in the event that a switch of branches occurs or an earlier hotfix package is later installed. In the example above at step 5, the post-SP1 hotfix package was used to migrate the updated version of C.SYS during the installation of SP1. If this was not done, or if the folder had been deleted, then the file would have been regressed from 1.5 to 2.0. What? A regression from a lower version to a higher version? Is that a typo? Think of 1.5 as "RTM with KB000100" and 2.0 as "SP1 without KB000100" and it makes a bit more sense. The migration of hotfixes to avoid regression is done from hotfix to hotfix as well as with SPs. Imagine we have module X.DLL which has a dependency on module Y.DLL, and they both start at GDR 1.0. Now a GDR hotfix KB000123 is applied which updates Y.DLL to 1.3. Now an LDR hotfix KB000075 is applied which updates X.DLL to 1.1 and Y.DLL to 1.1. The resultant files on the system would be: X.DLL SP1LDR 1.1 Y.DLL SP1LDR 1.3 If we took Y.DLL 1.1 from the second hotfix then we regress in the security fixes, and if we left Y.DLL 1.3 from the GDR branch then we might miss a dependency that X.DLL LDR 1.1 may have which could lead to instability. By switching to the LDR branch for the higher version of the file Y.DLL, we remain at the correct level in terms of security & stability fixes (changes in the GDR branch) but also add the fix for the issue mentioned in KB article KB000075. Moving to the LDR branch for a specific KB article number will not just give you the security changes up to that point plus the 1 non-security issue mentioned in the KB article - it will also contain every non-security update to the files in the hotfix package. For this reason you will see the all-too-familiar disclaimer: "A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix." If you followed the above then you will also understand why you should never manually delete the$NtUninstallKBxxxxxx$ folders – you will be unable to remove these hotfix packages yet they will be listed in Add/Remove Programs (and you will gain very little disk space by doing this as the contents are compressed on disk). If you were to delete the $hf_mig$ folder then you would break migration and may prevent the installation of future hotfixes or introduce unexpected regressions when installing service packs. As if that wasn’t enough… you then have separate packages for the same hotfixes (where appropriate) x86 (i386/IA32), x64 (amd64) and IA64. x86 is “only 32-bit” and IA64 is “only 64-bit”… but x64-based Windows has the concept of WOW (Windows-On-Windows) so these packages can have an even bigger list of files for the native 64-bit versions and the WOW6432 versions to support 32-bit apps. Now you can see the value in the file lists documented in the KB articles, showing not just the file versionnumber, but the different branches which have fixes, and this has de-mystified the versioning system a little. The above is correct for Windows versions up to and including 5.2 (Server 2003 & XP x64 Edition) – when we moved to 6.0 (Vista) we changed how it works.

The 350 is the amount of Updates + the amount of 'Options' ticked. i.e. 336 updates and 14 Options EDIT: Simply put... it's the amount of lines in the preset text file. For example if you have 100 updates, 100 drivers and 10 settings it would say x of 220

Introduction The 'All-In-One Integrator' is one of the most important tools available in Windows 7 Toolkit, this is the tool which lets you integrate everything into your image such as Updates, Drivers, Wallpapers, Tweaks, Gadgets, etc... but it also lets your remove things too, so lets get started... Selecting your image When you first load the 'AIO Integrator' you will be asked which image you wish you use, if the list it empty, click 'Browse' and select your extract ISO or select the install.wim directly. Once done you should see a list of images, you can either double click an item or press select. TIP: You can hold ctrl or shift to select more than one image, once done press 'Select'. Select your preset If you have used this tool before then you will be greeted by a list of things you have previously done, you can simply select a previous tasks and click 'Load Preset' or if you want to start fresh and do something different then press 'Skip (No Preset)'. ---Basic--- This tab has all the most important tools, to get the most basic jobs done such as integrate updates and drivers. I recommend beginners or new users to stick to this tab. Basic: Addons Addons are pre-installed programs which have been created by other users (usually *reaper*), they have the file extension *.WA, I would probably say programs such as crap cleaner and flash are the most common. If you have any addons then press 'Add Addons' at the top or the green '+' button on the left to add them to this list. Basic: Drivers Drivers are what make your devices and hardware work, sometimes its easy just to them them already installed after you have installed Windows. If you want to add some you just have to press 'Add Drivers' and browse to the folder which contains your drivers (*.inf files). You may notice that not all of them get added, this is because W7T does not include duplicate drivers with the same MD5 files and not all *.inf files are actually drivers and just normal inf files. Colours Red: If the user has selected an x86 image and then adds an x64 driver to the integration list then that driver will display red. Blue: When adding drivers to the list Win Toolkit also makes note of the *.inf MD5 hash, if there's another driver with the same MD5 hash then the items will change to a blue. Basic: Gadgets Gadgets are those little widgets things on your desktop, for example 'CPU Meter'. On Vista they had the gadget bar but on Windows 7 you can place them anywhere. If you want to have addons pre-installed then click 'Add Gadgets' and select all of your *.gadget files. Basic: Theme Packs These area of the tool lets you add your Windows themes, so when you have installed Windows you can select from your favourite theme packs. Just click 'Add Themes' and select your *.themepack files. Basic: Updates + Languages Its very handy to have all of the Windows updates installed. This makes sure your computer is up-to-date, bug free and more secure. Click 'Add Updates' and simply selected your *.MSU or *.CAB files and they will be added to the list, alternatively you can change the drop down box from MSU/CAB to EXE which will allow you to install Internet Explorer 9 and Windows XP Mode. NOTE: If you wish to install updates in LDR/QFE Mode then the option to do that is on the 'Options' tab at the top. Basic: Wallpapers As usual, this one is pretty self-explanatory, here you can add your favourite desktop wallpapers so that they are ready to be selected after Windows installation. ---Advanced--- Users who have more experience with Windows 7 Toolkit or experience with modifying images can use this tab, i wouldn't recommend new users to start using this until they gain a bit of confidence. Advaned: Component Removal Windows comes with features already installed, this features can be anything from Windows Media Player, Internet Explorer, Windows Media Center to more important features. The list you see here is not a full as the list from 'Component Remover' because the AIO contains a pre-defined set of features which i've manually added whilst 'Component remover' actively scans your image and lists everything including updates. I wouldn't recommend this to new users at all, and just to note that once something has been removed it can't be returned without using a fresh ISO. This tab doesn't do a full removal like vLite and uninstalls the features using DISM. Advanced: vLite Some users may instantly know what this does, this is similar to Component Removal but actually deletes files and therefore reduces the image size more significantly. It quite a new tool so there's not many items yet but i will hopefully add more as time progresses. Advanced: Files This replaces files within your image, so if for example you modify system32 files, you can import them into your image using this tool. This will most probably be used by users who have custom 3rd party theme files. Caution though as replacing an important file with a bad one can and most probably will make your ISO unbootable, so be very careful! Advanced: Services As you know Windows has many services running in the background. This part of the tool lets you reduce that and get the best performance from your computer. As you can see on the picture (below) you have to click the item in the column to change its value. You can also choose from 'BlackVipers' presets depending on what you use your computer for, you can also use the shortcut buttons on the left to do the same thing. NOTE: Services which are important are not available in the list, if you don't know anything about a service you can press the purple 'i' button on the left sidebar. Advanced: Silent Installs + SFX A lot of users like to have programs installed silently after Windows has completely installed, simply click 'Add Silent Installer' and select your EXE, you may have to go on google to find it's silent switch which is usually something like '/s /q /qn /quiet /silent' and so on. TIP: Some developers have already created silent installers so you can leave that box blank. If you have a folder full of silent installers then you can select them all and they will be added in bulk. Option: Always Install If you tick this option the the program(s) you add will be installed automatically, if it's unticked then it will ask the user what program(s) they wish to install straight after Windows installation. Option: Copy Folder Some programs such as Office have a setup.exe and then a bunch of other needed files in the same/sub-folder as the installer. Tick this option to include those files. This option is not usually needed. Advanced: Tweaks Most users will add tweaks to their install, there are literally hundreds to describe them all here but hopefully the descriptions are detailed enough for you. Just simply tick the ones you want. ---Options--- You don't really have to change these, most of them are used by me (Legolash2o) to debug issues. If you need to know what something is then just put your mouse over its name and a tooltip will appear. I will mention that the 'Prompts' items are they ones which tell you after AIO has finished what has been integrated successfully. Start OK now your ready, click start and you will be asked to enter a name, this is so you can use the same session next time you use AIO Integrator, similar to vLite/nLite last session presets. The image will automatically mount if not mounted: It will then integrate everything, green means the update has been integrated sucessfully, whilst yellow is the current item it's working on: Once done the image will save all the changes: Some drivers or language packs need to mount the boot.wim if, if it does then it will mount it now. Drivers are ususally ones for SCSI, HDD and SATA devices: Once everything has been completed it willre build the image to decrease it size so your ISO will be much smaller (hopefully). Now that everything is done, you can review what got integrated, now you can use the ISO Maker to create an ISO or just copy it to your USB device (assuming it's bootable).

WOW thanks again It really is much appreciated! Thanks again

EVERYTHING which would get applied to the default user will apply to admin user. EVERYTHING

Normally it writes the to "Default" (HKEY_USERS\\.Default\\) account but now if W7T detects that it will automatically write it to the "administrators" account too.

1. Well i've just fixed an issue where you could not re-order priority updates, but i think what your explaining works fine for me. You can't add KB2647516 to the priority list (thats done on purpose) because why would you want it installed before IE9??? If you really want that update it be installed first then move it to the top or the normal list. 2. I'm assuming you was using the *.cab IE9? That now gets added to the priority list. Sorry missed this earlier, im not entirely sure, im fairly confident they can be installed in any order.

Have you tried the new RunOnce?