Since I now no longer need Windows as much as I used to and it was "about time" to do what amounts to a "wipe and reload" of XP, I deleted the existing VM and built a new one. I didn't realize that Parallels now incorporates a true 'unattended' installation feature; I stepped away as the OS started loading, expecting to see the first of several setup screens when I returned. It was at the administrator desktop when I got back. After loading the few remaining Windows programs and restarting, I noticed it now immediately logs in. I have tried the tricks mentioned on a few other threads, but it still automatically logs me into Windows (albeit now to the additional account I will be using when using Windows) when I have the Welcome screen enabled. How do I get it back so that when the VM starts, it will come to the Welcome screen and wait for me to click on my icon on the Welcome screen?
This actually does not seem to be a Parallels part here. If you have only one user account in Windows (except administrator and guest), then Windows XP would most probably log you in automatically. There are several conditions though: - No password is configured for the user account. - No other users are registered on the computer. So, the easiest way to see a Welcome screen would be to either create one more Windows user or to set up a password for your Windows account. You can check more on this from the following link: http://www.kellys-korner-xp.com/xp_wel_screen.htm
The thing is, I only ever had the two accounts on my previous VM. Administrator and my normal account. I did NOT have a password set on the normal account then. It would boot to the Welcome screen and wait for me to click on the account's icon. I got it. I applied a password to the account then removed it. Fixed! Coulda been avoided if I was given the option of a regular setup - the one where you need to be at the computer to answer the dialogs as they appear. Anyway, I should be fine from here on out
Nope, the automatic logons came back. I had to add the string ForceAutoLogon=0 in the portion of the registry dealing with logins and it's finally resolved for good. (can't recall the exact chain but it started under HKLM \ ... Windows NT \ ...) Again, I repeat my suggestion to the developers to provide an advanced-level option to review / configure the options within the unattended install script.
