nuhi

Indeed. Jamieo warned me about it as well but I didn't have any issues at first. But now while testing in virtual extensively it can crackle sometimes, very annoying. Red warning is due.

Ok now wait until I test the Win2k tomorrow, thx for the help.

Well that way of doing things, update then configure, is more logical because then the added/updated files and registry entries will be deleted if needed, hotfix won't be firing on an empty place and maybe even leaving the new file which should have been removed. Obviously vLite is breaking those pending integrated hotfix packages since they are working if integrated later (meaning it's not the missing files)...can't wait to find out why.

Wrong compared to what? If you wanted it to be entered automatically you can fill it up in the Unattended page, or skip it by checking skip the product key (select appropriate version on the right once that option is enabled).

Hold on, I removed all and no error message. Can you please attach a preset which produces that error message when used on a clean Vista please.

Under Tweaks - System, but: http://www.msfn.org/board/index.php?showtopic=100509

hehe, nice to meet you.

rickytheanuj, it's not recommended to install that, you may get missing driver files popups. And you didn't tell us what did Winrar reported. botz, appreciated and welcome to the forum.

Works here as well. Kalabaza, check your services and if maybe there is partition issues. Try chkdsk /f on all partitions.

How about you try it first then tell us what isn't clear. Basically you browse to your DVD with vLite, configure it the way you want it, press apply, select second method, after it's done on the Make ISO page you have the Split button.

Meaning that vLite normally doesn't remove what you didn't tell it to unless you thought that Select means keep the component. Select is remove the component. Also be sure to select the exact image which you edited or rebuild it by selecting second option on apply.

Ok the Jamieo user found out that Task Scheduler is needed for this.

Depends. If you mean just to put in ISO by copying into that folder then yes, just do it before you press Make ISO. If you mean to replace the file inside the WIM image then no.

How do you know if it's supposed to work without IE...that's my point. Anyway I tried it and it is same with or without IE, it runs, I press I agree...next...it says it's installed, finish. Do I need internet connection for a full test, what do you get?

Ok try to integrate after vLite. Other user says it helped. I will be checking if that is possible to change.

Because of the enabled Unattended Installation page. Do you want it to be kept? What would be the reason to have winnt.sif and unattended.txt?

If you know why then you can keep IE and problem solved. I can't promise that it can be bypassed as a dependency.

It's not the component, it's the unattended. Try deleting Autounattend.xml from the root and just remake the ISO. I'll see about adding this option so that you don't need to press anything...because sometimes I like non-ACPI for audio as well.

Ever heard of PM? I'll probably do you this favor and adapt to the way you do it, thanks for reporting.

Thilo, that's kinda weird. Don't worry about the hardware detection hanging, that can't be nLite's fault, happens with Windows sometimes, or with some drivers. About the saving settings, there is no log that I know of, it's a part of setup when Windows checks WFP/SFC, probably filling the dllcache. Try disabling the SFC, this could be a mistake in the new SFC cleanup.

slippykillsticks, I have tried your XP preset but without the addons and it was fine. Can you please do the same and confirm that it's addons before I download and try them. If you have time, and doing the checks virtually, maybe you could neutralize some. Thx.

Seppo, are you one of the "select means keep" group?

Jeronimo, those don't show much. Why bother, just install the DX redistributable, if you didn't already and doing that to run a game. Trial and error unless the log shows more.

Aha I see. I believe you're right. That's why we had issues when Winsxs folder was cleaned. This is the same issue only selective in nature. Let me know what you find out, I'll see about cleaning the integrated hotfixes from the removed files...but I doubt that. Maybe the solution is in leaving the components in the cache but I would hate that, it could exist only as optional.

barney34, yes fixed in the next one. rickytheanuj, try to open the i386\driver.cab with the Winrar and press Test in the toolbar.