This guide shows you how to set a Windows Vista computer to automatically log a user on when the computer boots up.
Introduction
Home computers with Windows Vista usually don’t need the security of a business computer. This guide shows you how to set Windows Vista to automatically log a user in when the computer boots up.
Note: If you only have one user account and that user account doesn’t have a password assigned to it your computer will automatically logon for you.
Set Up Auto Logon for a User
- Open the Start Menu and type run in the search box.
- Type control userpasswords2 in the run box and press Enter.
- Select the user you want to auto logon when Windows Vista boots and uncheck User must enter a user name and password to use this computer.
- Click OK and type the current password for the user. Click OK when you’re done.
Set Up Auto Login for a Domain User
Download this regedit file. Edit the file by right-clicking it and selecting Edit. Change the “UserName”, “Password”, and “YourDomain.local” settings in the registry edit file. Double-click the regedit file to make the changes once you’ve edited it.
Bypass Automatic Logon
You can stop a computer that’s set to logon automatically from automatically logging on by holding down the left Shift key while the computer boots up.
Still need help? Ask Your Computer Question Now.
Explore other guides about: All • Customization • Vista • Windows.
Great website, thanks for all info and help you provide.
I’ve edited my registry in Vista Business 32 with the above. The shift override would not work (not on our Vista or XP machines).
I found I needed to add another string:
HKEY_LocalMachine\Software\Microsoft\WindowsNT\CurrentVersion\WinLogon
IgnoreShiftOverride = 1 enables or 0 disables
I set this key to “0″ and now can use the sift key upon startup to override autologon. This works on the XP machines but NOT the Vistas. Is there another registry edit required?
After searching the internet for a while I noticed many people are reporting this problem (I would call it a bug).
The only solution I can find is a tool called LogonExpert.
Let me know if this worked.