I could be wrong but I thought vLite wasn't compatible with anything after Vista SP1?
I had no problems with it... Granted it's no longer supported by it's programmer since MS came out with it's own configuration tools but, IMO, VLite is still far easier and quicker to use.
As someone on here that has extensively studied vLite (I have a tutorial dedicated to this), there is ABSOLUTELY no reason to recommend using this for Win7....
The reasons?
1. vLite was made by nuhi to be used for Windows Vista and Windows Vista SP1. Anything past that is unsupported and the app may remove mission critical files (which it does)
2. I agree that it is possible to use vLite for Windows 7...but the resulting "chopped build" will have underlining issues caused by like I said above....vLite was made to remove files based on Windows Vista's file architecture and no matter how much the two are alike...they are not the same.
3. Why try and strip down Windows 7 to begin with? Vista was almost a necessity cause of the lack of tweaking it for performance. Windows 7 is the almost tweak of Windows Vista...a slimmed down optimized improved version. All of my builds I made all chanted the same thing....I would be saving disk space and that is all. The supposed "RAM saving" people talk about is based on that timely myth that RAM saved is a good thing. Windows 7's Superfetch has been improved to a level where RAM saved is now something I would rather NOT SEE
In conclusion...to avoid a lot of pointless installs of "frakenbuilds" for illusory performance boosts and saved HD space...please stop using vLite on Windows 7. It was here for Windows Vista and now (as Vista has become)...it is a relic of the past