Jeronimo

@awalraja: thanks for the heads-up, I updated the removal.bat accordingly.

@dcatcher: Win Integrator reports several packages dependant on another main package. the "parent" package is x.0 and its "children" are x.1, x.2, ...

@aviv00: I have tried to add support for 32-bit Windows, but I have not tested it. If you test it and encounter issues, I could try help and these resolve issues. However I do not have Windows 7 32-bit and I have no intention on using it, let alone test it. @trickstar: I think imagex has to be from Vista SP1 WAIK, the one from Windows 7 RC works rather slow in every way (mount, unmount, compress, vLite). For the intlcfg I do have the 1 from the Windows 7 RC WAIK. Not sure weither the 1 from Windows 7 RC WAIK works, but you could try. I have not tested any other .NET applications, because I do not have (want) any. I want to completely remove it, but I just need it for vLite. If not, then I would remove it completely.

@trickstar: no printer drivers, no printer support and no networking (only internet/WLAN) Trying to get Windows as much down in size as possible. Only keeping essential components.

The following has already extensively been discussed under Windows 7 & vLite and I would appreciate continuing the discussion there when it is related Windows 7 component removal in combination with vLite. Any bugs, questions, remarks and/or issues related to my work described below can be discussed here. The following is not for the average user! You have to know a bit about the commandline in Windows as well as how batch-files work. It does not work out of the box and requires modifications to fit your needs, if you do not comprehend this, then be satisfied with the removal vLite can do for you (just stay clear of removing Game Explorer, IE8, Windows Firewall and Internet Connection Sharing). I went a bit further on what I had achieved previously and I managed to remove most of Microsoft.NET up to the point that vLite still works (so no complete removal of .NET). After this the install.wim is 822MB, the installation is about 2.4GB without compression and pagefile-/hibernate-file, even a bit less (2.39GB) after you have performed the final step and for those interested it is 1.54GB with compression (though I would not choose to do this). packages_xls.txt (rename to packages.xls) Contains information about all Windows packages, vLite component, the relation between them, removal issues and specified removal (dism or vLite) removal_bat.txt (rename to removal.bat) Contains removal of packages, cleanup and language pack integration (not fully automated). Works by specifying a parameter (eg "removal.bat packages") Please make sure you edit it to fit your needs (everything up to the choice between using imagex or dism for mounting, use imagex for proper functionality) The removal.bat can perform the following actions : parameter - action (see contents for possibilities) <none> - initialize environment variables (a new prompt called "WIM-prompt" will be started) updates - integrate updates with dism (not functional yet, might only work when executed under the same Windows 7 build) packages - remove packages with dism (see packages.xls for details) cleanup - remove files and folders drivers - driver integration (recurses the specified folder) pre - actions updates + packages post - actions cleanup + drivers full - actions packages + cleanup + drivers (not recommended) langpack - integrate language pack in Windows 7 langpack2 - integrate language pack in Setup final - register file for safe removal and extra removal of Microsoft.NET files (post-installation) init2 - performs intialisation without setting parameters desribed below (used from removal_custom.bat) The removal.bat contains the following parameters: cb - empty (determine from %DVD%\setup.exe; can also be x86, amd64 for respectively Windows 7 32-bit, 64-bit) build - 7600 (build number of your Windows version, default RTM-build) svn - 16385 ("sub-version" of Windows build number) pre - 31bf3856ad364e35 (do not change; string part used in the name of Windows Packages) edition - HomePremium (Windows edition you will be modifying (case sensitive!): Starter, HomeBasic, HomePremium, Professional or Ultimate) II - 2 (obsolete! - the image if that you will be modifying: 1 HomeBasic/Starter?, 2 Home Premium, 3 Professional, 4 Ultimate) remove.NET - V (removal of Microsoft.NET: C for complete removal, V to keep vLite working or K to keep) updateloc - C:\vLite\Updates (folder of updates to be integrated) update.ext - * (extension of the updates to be integrated: msu, cab or * for all/both) driverloc - C:\vLite\Drivers (folder of drivers to be integrated) lang - nl-NL (your language code; see this page) langid - 1043 (your language setting: see this page) intlcfg - C:\vLite\intlcfg.exe (location of intlcfg.exe from WAIK) langloc - C:\vLite\Langpack (location of your Language Pack) DVD - C:\Windows 7 DVD (DVD & sources-folder containing install.wim and dism.exe) mount - C:\Wim (folder for mount Dism/Imagex or Root Imagex only) imagex - "C:\vLite\imagex.exe" (location of imagex.exe from WAIK) Pre-requirements/notes - in case of Windows 7 x64, make sure you are running a x64 version of Windows as well (only tested for x64); - (have vLite) install the wim-filter, otherwise mounting the image will fail; - Windows 7 DVD-contents (or ISO) copied to a local drive; - dism.exe present in the sources-folder (for those of you that remove all files from the sources-folder); - remove ei.cfg from sources-folder to be able to install all editions (not required for RTM/final); - removal of Game Explorer component (by vLite) requires removal of Snipping Tool package (by dism); - after the cleanup phase with nullify of winsxs-Backup, do not select any Component removal in vLite this will no longer work; - final step is essential to keep vLite functioning (folder needs to be removed from Windows\assembly). The following files need to be placed in the same folder as removal.bat (it alters the path, so it does not need to be root): install_wim_tweak (direct link: win6x_registry_tweak_bin_v1.1.rar) imagex.exe and intlcfg.exe from the Windows Vista SP1 AIK (take the proper version of these files amd64 for x64 or x86; Windows 7 AIK gives issues) Recommended use 1. Modify the removal.bat to fit your needs (just in case you forgot) 2. Integrate Language pack (removal.bat langpack) 3. Integrate Updates (removal.bat updates) 4. Packages removal (removal.bat packages; 3/4: removal.bat pre) 5. vLite (Component removal only) 6. Cleanup of files and folders (removal.bat cleanup) 7. Integrate Drivers (removal.bat drivers; 6/7: (removal.bat post) 8. vLite (Tweaks only: reduce image size after cleanup) 9. Test on a secondary partition or to a virtual environment (such as VMware) 10. After installation final steps can be performed (removal.bat final) edit: resolved a few issues with the removal.bat file. edit 10-08-2009: corrected final & update (mount first; fix DirectX Web Setup -keep fusion.dll and mscorie.dll) action in removal.bat. edit 11-08-2009: restored edition parameter (II - image index is obsolete now), take into account lang "en-US", renamed langcode to langid in removal.bat. edit 15-08-2009: removed redundant removals (avm/Fritz, Printing, fonts) in removal.bat, added Ultimate-N details in packages.xls edit 23-08-2009: cb parameter changed, restructured to allow usage with custom actions in removal_custom.bat (such as for SausageHack's guide; my example) edit 30-08-2009: corrected use of Windows 7 AIK to Windows Vista SP1 AIK edit 31-08-2009: corrected some issue for cleanup action (see this post and the reply to it) edit 06-09-2009: corrected IEtail parameter for IE Optional package removal edit 19-09-2009: corrected dism functionality, changed used location of language package (as seen in this post by franner) edit 19-10-2009: corrected integration of updates (thanks again franner) edit 23-10-2009: corrected check on codebase parameter cb. edit 24-10-2009: repositioned codebase determination to correct functionality of package removals. Windows_7.ini packages_xls.txt removal_bat.txt

There are a few bugs I found in my Batch-file. Maybe that is the reason. I am however still testing .NET removal before I can make it available.

I got wim-file below 900MB and installation below 2.5GB when removing .NET related stuff. However I do want vLite to keep working, so I need to look this through a bit more.

@Something Corporate: I only had this once when I used my external HD and it got disconnected along the proces, not sure what else can cause it. You are running it on a clean image, no vLite used on it yet to remove components?

I suggest checking the dependecies of mediaCenter in vLlite keeping those as well as all packages that might be related (removing them from removal.bat).

I made some improvements to my preset and batch-file that I will be posting shortly. Also trying to remove Windows Codecs, because I am trying VideoLAN VLC Palyer or whatever it is called (name is as confusing as the documentation/Wiki). Media Player Classic that I was using before, required for instance ffdshow, but then it still was not capable of playing WMV-fileswhen Windows codecs were removed.

Read the full topic and you will have some hints or you can clarify what you have already tried. For starters: keep Game Explorer, IE, Firewall, ICS and MDAC.

Please make sure, that you edit the removal.bat for your purpose: not only set II to 2, but also set the edition to H! It might be better for me to join the 2 settings, but considering there will be different versions (where one has 1 Starter, 2 HomePremium,... and another 1 Starter, 2 HomeBasic, 3 HomePremium,...) I will need to check how this can be done easiest. I will check within the next day or 2. Then I will then have the full Dutch RTM and be able to check HomePremium. For now I only have RTM Ultimate (with Dutch integrated), which works perfectly now (I did need to make some modifications though).

I updated my post post here with slightly different preset (Task scheduler poses no issues and now is removed) and some additional remarks. One remark is that on the dummy run of vLite, that you should not remove any components or it will provide an error and exit.

That is because I remove packages before running vLite, see my guide (link a few posts up). I think liquid0624 pointed out it is because of Snipping Tool. @Zumoc: if you have build 7600 and it says 7264 in your preset (ini-file), then isn't that in the part where it states on which Windows version you ran vLite? For me this was build 7132 and that what it states in my preset. This is no problem.

I am just trying my presets with the RTM build with Dutch integrated and it works great. I also nullified the Backup-directory (recreating all files there with size 0). An article on My Digital Life said the files should only be present in order for WIndows Update to work and far as I can see it works. I updated the removal.bat accordingly, see my post here for all details and downloads. I am at 1.02GB install.wim size, 3.37GB installed size and 4.37GB after installing all my stuff. Most of the extra space is Nvidia PhysX (118MB) and OpenOffice.org (337MB). Also something I have not read yet here, which liquid0624 found out: when you do not remove Application Expereince with vLite, but disable the service, then it causes issues with removal of executables (exe-files). The files can be removed, but then reappear as some kind of ghost files (removed, but still vissible) and eventually they vanish all on their own.

I think manual capture is not worth it: on an image of around 1GB, vLite trails behind only 1.5MB on capturing with maximum compression.

Yes I had something similar, but I think it was only after 1st boot when clicking on the "My Computer" icon: every drive/folder would open in a seperate window, but since they are all grouped in the taksbar, it seemed like back/forward is not working. Similar things happen when QoS is removed and after entering your details (ending with timnezone) Windows does not restart for 1st use, but directly ggoes to desktop. Then I can not add a WLAN manually. After reboot everything works fine. Also opon investigating this, I noticed that it would be handy to keep Personalization package. Without the option you lack proper control over your Dekstop (Aero-interface). Will update the details within the next few days after I have tested it.

Yeah I know, but select the icon and it shows only "...", run the command, select the icon again and voi la it does work.

Lol, just search for the string and you will find it. You do need to keep Windows Connect as well, have not found the file(s) that break safe removal in that component and I doubt I will. ... REM Internet Explorer copy "%mount%\Program Files\Internet Explorer\ieproxy.dll" "%mount%\Windows\system32" REM regsvr32 /s "%SystemRoot%\system32\ieproxy.dll" ... I could have made a more explicite remark, but I have it put in another "script" that I run after installing Windows (to bloat it up again with all the stuff you need to install).

Updated my post and removal.bat. Now supports driver integration, maybe I should rename the file. I saw a question on how it works (script? If scripting where a car, then this would not even be a bicycle), but I added the post for quick detail and some insight. I assume that the people here know a bit what they are doing (read the cmd-file) and, with all due respect, have a basic understanding of the English language. I am happy to answer any question, clear up confusion and correct irregularities, but I am not going to make a step by step manual. [edit]Re-download removal_bat.txt : I ran into some issues during my final tests (probably was a bit too eager to post it[/edit]

Do you have the install_wim_tweak along with the dll in the same folder? I never had any issues with ownership with files in the install.wim so I am not sure why you get them. I tried removing all files related o the packages that i removed with dism/vLite from the image(servicing, catroot, winsxs, manifests), but then the installation fails. I am fine with the image as I have it now. Might juggle a bit wit Win Integrator now.

Well after running vLite it is no longer present as a package, what makes you think it is still present?

Ok here is my information on creating a slimmed down version of Windows 7... packages_xls.txt (rename to packages.xls) Contains information about all Windows packages, vLite component, the relation between them, removal issues and specified removal (dism or vLite) removal_bat.txt (rename to removal.bat) Contains removal of packages, cleanup and language pack integration (not fully automated). Works by specifying a parameter (eg "removal.bat packages") Please make sure you edit it to fit your needs (everything up to the choice between using imagex or dism for mounting, use imagex for proper functionality) The updated removal.bat, "does" the following action for you: Remember to set the image id to 1 after you have run vLite (in case you rebuild to 1 image). parameter - action (see contents for possibilities) <none> - initialise environment variables (a new prompt called "WIM-prompt" will be started) packages - remove packages with dism (see packages.xls for details) cleanup - remove files and folders drivers - driver integration (recurses the specified folder) post - actions cleanup + drivers full - actions packages + cleanup + drivers (not recommended) langpack - integrate language pack in Windows 7 langpack2 - integrate language pack in Setup Pre-requirements/notes In case of Windows 7 x64, make sure you are running a x64 version of Windows as well Windows 7 iso-contents (or DVD) copied to a local drive dism.exe present in the sources-folder (for those of you that remove all files from the sources-folder) remove ei.cfg from sources-folder to be able to install all editions removal of Game Explorer component (by vLite) requires removal of Snipping Tool package (by idsm) after the cleanup phase with nullify of winsxs-Backup, do not select any components in vLite or it will not be able to complete. The following files need to be placed in the same folder as removal.bat: install_wim_tweak (direct link: win6x_registry_tweak_bin_v1.1.rar) imagex.exe and intlcfg.exe from the WAIK for Vista SP1 (take the proper version of these files amd64 for x64 or x86) Recomended use Modify the removal.bat to fit your needs (just in case you forgot) Integrate Language pack Packages removal vLite (normal run) Cleanup of files and folders vLite (dummy run: reduce image size after cleanup) Test on a secondary partition or to a virtual environment (such as VMware) Afterwards use the regsvr32-command to make safe-removal of external drives work (see removal.bat).

I guess something like that, trying to find a best of both worlds. It seems dism does not remove everything (winsxs) )and therefore I prefer vLite. I checked after removing all components with vLite, which packages remain present and those are the ones I try to remove with dism. Sometimes removing a package also removes a component in vLite and then I do not remove the package. I know that drivers are not fully removed with vLite, but that is why I have my own clean-up afterwards. I need to check 2 driver-packages that failed in the past, after that the dism/vlite part is done and I can move on to testing the clean-up process.

I am nearly finished with the dism removal-part. Just need to test 1 or 2 installations (1 without IE removed and if all goes well 1 with IE removed). After that I am going to check the cleanup-part. Probably somewhere tomorrow I will know more. On a side note: still working on x64 7600.16384, but I saw 7600.16385 also is available.