nuhi

JoaoVr, for the text is the file C:\Windows\System32\C_936.NLS you can extract it from full Vista with 7zip (sources\install.wim) Let me know if that fixes anything.

"It is in there" doesn't tell me if you are certain it is 32bit wimgapi.dll or 64bit, this error is known when 64bit is used, it should always be 32bit (from x86 folder in WAIK). Also use AIK SP1 if you didn't.

Make sure that wimgapi.dll is from the x86 and not x64. If you install WAIK into the default location just delete the dll and allow vLite to fetch it.

That is why Server component removal isn't supported and it will remain like that until I give it another try and make Manager work even after vLite. Congrats on the cutting edge method, not even linux enthusiasts can complain

I presume .NET 3.5. Component Cache (winsxs). You can also extract the 3.5 installer, integrate MSP files then winsxs can be removed and 3.5 will install fine later on. Note that these MSPs integrate for a looong time.

Well in this specific situation you can just extract windows\system32\cleanmgr.exe with 7zip from the full Vista install.wim into the current system32. I presume that even a renamed empty txt file to cleanmgr.exe would do. Next time listen to the dependency popup warnings.

Never seen it in Vista and it is fixed in XP-nLite. Try keeping MSHTML Engine and Windows Picture and Fax Viewer (Shimgvw).

Just a guess: "Install this update to add words to the English and German standard dictionaries" And yours is neither of those, does that mean a bug in the hotfix. Problem is you are reporting the hotfix integration issue on the full Vista (because vLite integrates first then removes) which has nothing to do with me...I hope

Slipstream caused it, hm weird. Was that a full, clean DVD before the slipstream?

Vista SP1, any edition.

Goodie. To uninstall wim filter and do that automatically and cleaner you can run vlite with the unwim switch.

Try keeping Media Metadata Handler, read description.

Select Recommended compatibility option and remove all else You might also select Windows Update compatibility.

It is true that more than half can be removed but I still don't see why would anyone use a server instead of vista sp1 for a client pc. Don't give me benchmarks, first setup both the same and test for yourself. That means remove from Vista what Server doesn't have from the start and setup caching and priorities the same, whatever there is.

Terminal service is expected when Remote Desktop removed. HTTP is only visible in Virtual tests or when Vista cannot access the web (something like that, harmless). Let me know if you think otherwise. Spooler also, read it.

Hokey.

Dobby, ok added. Let me explain the lack of IR separation. Every time the sub component is separated from the bigger component we run into issues once the hotfixes are applied because they blindly update the whole component.

Do you really have a SQL Server pre-installed on that XP before you try to apply the hotfix (KB948109)? Please move WMP11 integration above the actual WMP11 hotfixes. Recheck the same for IE7 even though that part looks fine. So the way I do it is sort by build date (click column header) then move IE and WMP11 main installers on top.

Thank you nuhi. Perhaps you're right, but if it already has SP1 on it, then why would the "repair your computer" option fail and tell me that I have the wrong version of Vista? How can I confirm this? That's different issue now, I am not in charge of Vista recovery console. First make sure that the content of the DVD is actually the same version as installed. Why Vista recovery didn't detect...well did you install XP on different or on the same partition as where your Vista was? Can you run some sort of command like to initiate boot fix, like Vista WinPE or Recovery Console?

Attach your preset for starters, maybe integrated SATA driver does that. Did you search for similar VMWare reports? Tried it in the real machine?

It will warn you about the needed components if you keep Wireless service and Battery. You can also use USB flash stick for booting installation. I would recommend to select for removal only those things that you know that you don't need like for example Tour is not needed for WiFi or battery. Slowly build upon it, when issues arises that make no sense then ask us. Best wishes.

No problem, thank you for being so nice. Remove what you don't use, if you don't know what you don't use then don't remove components at all.

It usually does that when you browse to the already SP1 version, why slipstream into a SP1. Can you confirm that yours is not RTM? Btw that disappearing is ugly, that is a glitch, it should be invisible from the start on other than RTM source. Fixed in next one.

Windows Image Acquisition?

Do you have a 32bit wimgapi.dll in the vLite folder? Try deleting it and install WAIK then run vLite again. But if in vLite 1.1.6 you had the same that doesn't make any sense. Error 11 is: An attempt was made to load a program with an incorrect format. Try also uninstalling Wim filter by running vlite with the unwim switch vlite.exe /unwim reboot and run vlite normally.