DVDave

Fantastic. Thanks a ton. ~Dave.

using nLite 1.0b5 Windows XP, SP2 Because of the Windows File Protection "error," I have disabled SFC during the nLite setup. Whether that and my current issue are related or not, I do not know. For some reason now, Windows does not install in a completely automated manner. I have tried Fully Automated and DefaultHide in nLite and the parallel options in Microsoft's setupmgr.exe The install seems to flow smoothly until the first reboot, at which time I am prompted with "Welcome to Microsoft Windows." The setup wants to turn on Automatic Updates, check Internet connection, and register with Microsoft. I am quite sure that I have missed a simple option, but having filled out all fields offered by nLite, I do not know what else I can do to prevent this "feature" from popping up. Thanks in advance for any suggestions, ~Dave.

I have taken over the unattended XP installataion responsibilities from someone else at our company after he left, and I started with nLite 1.00 beta 2. I had not ever heard of the Windows File Protection "error" until I started working with unattended XP installs. I have read through this thread and tried to isolate some circumstances. I re-enabled Dr. Watson and stopped integrating drivers. I still get the message. I just completed a "control" install, by using nLite 1.00 beta 5 and not integrating any drivers or even hotfixes, save for SP2. I only disabled a couple features, including that Search Agent thing, Desktop Cleanup, and a few Taskbar options. I still get the same message, although not until after the first reboot. After Windows completed the install, I removed the CD (or, more specifically, removed the .ISO mount from Virtual PC) and ran Windows Update. Everything installed fine and the computer asked to restart. Upon reboot, I was immediately prompted to insert the install CD though, for Windows File Protection. Is anyone here familiar enough with the SFC command to tell me if my next attempt will be worth trying? I was considering running SFC.EXE /SCANNOW from RunGuiOnce to see if that would work. Perhaps forcing a full scan will prevent the OS from checking file versions upon next reboot. I see a lot of references to nLite .999 Were users not seeing the WFP message using this release? Could someone URL me a link to download that version, if it will prevent this message from popping up? Any help is greatly appreciated. And, if I have to wait for the next nLite release, well, such is life. Thanks, ~Dave.

I know, regardless of logging onto a domain or the local box, we have been unable to get our unattended installs to auto-login since Windows XP Service Pack. The first unattended we created that incorporated SP2 just beeped at us about a bad username/password. Once we typed in the password, the RunOnce stuff triggered just fine. I know this isn't an answer, but at least it might help describe the issue as not specific to the fact that you're trying to log on to a domain. Perhaps another reader here has worked around the SP2 issue. ~Dave N.