Windows Setup Hanging at Last Step (Scripted Installation)
I have one system image that hangs at the very last bit of Windows Setup. This is the "Windows is finalizing your settings." bit immediately before you are taken to the desktop (i have autologon in the unattend).
I let the thing sit there for many hours. I found that I could complete the setup by killing a cmd.exe process. Once I did this setup would complete and the image would be fine.
I have a different image that doesn't have this issue. I use the same unattend for each image. I have nearly identical post-installation tasks, although I suppose this is the next place to look. (EDIT: Checked really quick, I am able to use the same post-installation with other SIs)
However, my question is on trying to figure out the nature of the cmd.exe process that seems to be holding up the party here. What could be spawning this process? Is it possible to figure out what exactly it is doing?
EDIT: Tried again without any post-installation tasks at all. Would could be generating this cmd.exe process? I will be seeing what sysinternals tools can help with.
Answers (2)
I was able to use procmon and its process tree to identify the issue. msobe.exe spawned a script from C:\windows\setup\scripts called SetupComplete.cmd that had a bogus postinstallation task stuck in it. Will have to clear that out on next iteration of image. Thanks!
You may be able to get a better look at what's going on with some of the Sysinternals products. http://technet.microsoft.com/en-us/sysinternals/bb842062
Comments:
-
I was able to use procmon and its process tree to identify the issue. msobe.exe spawned a script from C:\windows\setup\scripts called SetupComplete.cmd that had a bogus postinstallation task stuck in it. Will have to clear that out on next iteration of image. Thanks! - muebel 12 years ago
You shouldn't use setupcomplete.cmd at all, as the K2000 uses this to add its post installation tasks.
Now one thing you can do is use a midlevel task to append that file.
