Windows 7 Home Premium Welcome Screen Differences
Hi All,
We have two laptops at home, one is a Dell Inspiron 1720 and an ASUS G73J series, both running Windows 7 Home Premium 64bit. The Dell originally came with Vista and I recently upgraded it to W7 and the ASUS came with W7. Both installation have an account
created with admin previleges with password protection.
When booting up the Dell, it boots to the screen which contains the account picture, username and the password entry field. After entering the correct password, it logs into Windows.
When booting up the ASUS, it boots to the screen which just contains the (smaller) account picture and username. I have to click on the account picture to get to the screen like that in the Dell. I can then enter my password and login.
Question: How do I make the ASUS behave like the Dell?
I've compared the following registry keys and there are no differences:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon
There were also no differences in the settings in netplwiz and msconfig (in particular, the boot tab).
Thanks in advance,
Vlad
July 11th, 2012 10:07pm
How many accounts in your Asus laptop? To hide the other accounts.
Here is one discussion can be referred to.
Hide User Accounts on Windows 7 Logon
http://social.technet.microsoft.com/Forums/en/w7itproui/thread/16378967-8a39-4aef-85e4-d859a71648d3Ivan-Liu
TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
July 13th, 2012 3:25am
Hi Ivan,
When I run netplwiz, there are a total of three accounts listed as follows:
__vmware_user__ - needed for VMware Player
HomeGroupUser$ - needed for home group access
myself
When I run control panel > user accounts > manage another account, the account Guest appears and is disabled.
I have created the Special Accounts\UserList and added the following:
__vmware_user__
HomeGroupUser$
Guest
I then rebooted and there is no difference.
I have stumbed upon something last night though:
1. Run msconfig to set to boot to safe mode with networking to run some checks for unrelated issue.
2. Windows boots up into safe mode with the two-stage logon. I then did an update which required rebooting into safe mode.
3. Windows boots up into safe mode again, but this time, with the single-stage logon (like the Dell).
4. I then run msconfig to set it to boot normally and reboot.
5. Windows boots up into normal mode, with the single-stage logon (like the Dell). I got excited too early.
6. I rebooted it and it has gone back to the normal two-stage logon.
The above process is repeatable as I did it again just to make sure I wasn't dreaming and exported the registry. However, there were too many differences to find out what is causing the two-stage logon.
July 13th, 2012 9:09am
Hi All,
Sort of got there. But does not survive a reboot.
I noticed a difference between the normal boot and safe mode boot in the
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\LogonUI]
and
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\LogonUI\SessionData\1]
keys.
Normal one had the lastloggedonprovider in both keys set to
AdsmCredentialProvider where as the safe boot one was set to
passowordprovider.
I modified both to passwordprovider ({6F45DC1E-5384-457A-BC13-2CD81B0D28ED})
and rebooted and it booted to the single-stage logon. However, after login in
and rebooting, it reverted to the two-stage login and the lastologgedonprovider
value in both keys reverted back to AdsmCredentialProvider
({455BD3EC-20A5-44C3-8D77-396909825B5E}).
Anyone know how to make this permenant?
Cheers,
Vlad
Free Windows Admin Tool Kit Click here and download it now
July 14th, 2012 4:41am
Hi All,
Problem solved for now. Noticed the Dell does not have the {455BD3EC-20A5-44C3-8D77-396909825B5E} AdsmCredentialProvider at all in [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\Credential Providers].
I also found a post where someone showed how to use the fingerprint scanner as the default login provider, which basically used a scheduled task to modify the registry.
I thus created a vbscript to import the registry settings and added as a logged on scheduled task.
It all works fine now. I wonder what will happend if I remove the AdsmCredentialProvider from Credential Providers and then disable the scheduled task.
July 15th, 2012 10:01am