timekills

A few basic suggestions: 1) Ensure you have any AV and/or anti-spy programs either disabled or preferably turned off during the slipstream. They will sometimes stob the CAB compression or replacement of files, often without even warning you. THat is a common reason for NLITE to just stop with no warnings. 2) Make sure the base image you are using is truly a clean base image. These days that can be difficult to find - many images already have been NLITE or other program modified, and that can wreak havoc with a re-slipstreaming. Having a SP slipstreamed beforehand is usually fine, as long as it was just the servicepack that was slipstreamed and nothing else altered. 3) If you list what you are trying to do with your NLITE'd image, that can help with the problem solving. (That was the politcally correct way to say read the FAQ for posting error problems..... )

I had a few problems with MLite getting part-way through its process and just quitting - no warnings - or not wanting to get past the very initial start giving me a missing security error. I tried recopying the base XP files, checked the folder settings, rebooted, you name it. Soultion: 1) Disabled the Comodo Firewall program's Defense+ program - even though it never gave me a pop-up and I had NLite listed as a "Trusted Program". 2) Still had a few times where NLite just quit - Disabled Theatfire That solved it! I have to concur with the other threads in msfn.org about the Defense+ section of the firewall. It is too invasive, worse than Vista. I have kept it disabled since and no more pop-ups and no more problems with NLite.