You cannot unlock a Windows Vista-based computer after you log on to an Active Directory domain

Consider the following scenario.

• On a Windows Vista-based computer, you log on to an Active Directory domain in a forest by using a user account in this domain.
• The Windows Vista-based computer belongs to another domain in this forest.
• You lock the Windows Vista-based computer.

In this scenario, you cannot unlock the computer by entering the account password.

This issue occurs if the following conditions are true.

• You configure the "Assign a default domain for logon" Group Policy setting, and then you set the domain to which you log on as the default domain.
• You log on to the domain from the Windows Vista-based computer by entering the user name without including the domain name.

This problem occurs because of a timing issue.

During the logon process, the "Assign a default domain for logon" Group Policy setting may not be applied. In this situation, when the logon process queries Group Policy, the process cannot find the "Assign a default domain for logon" Group Policy setting. Then, Windows Vista assumes that the user is logging on by using the credentials from the same domain as the domain to which the computer belongs. This combination of domain name and user name is saved. Later, when you try to unlock the computer, the saved domain name and the saved user name, together with the password that you enter, are used as the credentials to verify the unlock operation. Because the user account does not belong to the domain to which the computer belongs, verification fails. Therefore, the computer cannot be unlocked.

Service pack information

To resolve this problem, obtain the latest service pack for Windows Vista. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

No prerequisites are required.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

To use this hotfix, you do not have to make any changes to the registry.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista, x86-based versions

Windows Vista, x64-based versions

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Vista Service Pack 1.

The "Assign a default domain for logon" Group Policy setting was introduced in Windows Vista. This Group Policy setting specifies a default logon domain that may differ from the domain to which the computer belongs. If this Group Policy setting is not configured, and if a user does not specify a domain on which to log on during the logon process, the domain to which the computer belongs is presumed to be the default domain. For example, if the computer belongs to the Fabrikam domain, the default domain to which the user logs on is Fabrikam.

To configure an "Assign a default domain for logon" Group Policy object, follow these steps:

1. Open the Group Policy Object Editor.
2. In the Group Policy Object Editor console tree, expand Administrative Template, expand System, expand Logon, and then double-click Assign a default domain for logon.
3. On the Setting tab, click Enabled, and then enter the domain name in the Default Logon Domain box.

For more information, click the following article number to view the article in the Microsoft Knowledge Base: