iainb

DEP is on the default setting of essential windows programs/services only. I don't think there is anything special about the setup... (Do you know why an antivirus affects cabinet creation? Does nLite do anything unusual?) I'll try and get a FileMon trace in the next couple of days (not much time during the week) and see if it breaks on a particular file. Thanks for the note about the IE packages - I'll switch the order around.

No, it froze again at the same spot. It appears to be sitting in the cabinet.dll when it freezes, in various functions that look like they're compression related. The nLite binary seems to be obfuscated too, so looks like a lot of work to find out what is going on. Is there a way to get a trace/log that might shed more light on this? I don't think it is just me being impatient... 40 minutes of compression seems excessive.

Ok - the only thing I have running is Diskeeper, but I'll give it another go with that disabled.

I'm using nLite 1.4.1 running under Windows XP 64 trying to create an updated install CD for XP64. Everything seems to go well until it reaches the "Finalizing" stage. At this point it hangs at about 1/4 of the progress bar (been going now for about 50 minutes on a dual 2.4GHz system w/2GB of RAM). CPU usage has hit 50% for the nLite.exe process, but I can see no disk writes occuring for it under ProcMon. I've attached the "Last Session.ini" file - I've just added a few drivers and hotfixes. Has anyone else had this problem, or have any suggestions? Last_Session.ini