You are prompted for user credentials when you try to access a business application that is configured to use the Single Sign-On (SSO) feature on a Windows Vista-based client computer

This article has been archived. It is offered "as is" and will no longer be updated.
Consider the following scenario:
  • You log on to an Active Directory directory service domain from a Windows Vista-based client computer.
  • You try to access a business application that is configured to use the Single Sign-On (SSO) feature.

    Note If the application is configured to use the SSO feature, you can typically access the application without typing your user credentials.
In this scenario, the Kerberos Authentication that is used by the application fails.

This problem occurs if the following conditions are true:
  • The user account that you use is a member of the local Administrators group.
  • On the Windows Vista-based computer, the User Account Control (UAC) feature is turned on.

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:
935791 How to obtain the latest Windows Vista service pack

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.


There are no prerequisites for installing this hotfix.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

Registry information

To use one of the hotfixes in this package, 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, 32-bit version
File nameFile versionFile sizeDateTimePlatform
Update.mumNot applicable2,01224-Sep-200704:56Not applicable
X86_f8ae11ed69625d011e3a1f19e8123d05_31bf3856ad364e35_6.0.6000.20685_none_fa74ae756aa93517.manifestNot applicable70524-Sep-200704:56Not applicable
X86_microsoft-windows-security-kerberos_31bf3856ad364e35_6.0.6000.20685_none_e528bb7ccd00ffe5.manifestNot applicable40,54024-Sep-200704:56Not applicable
Windows Vista, 64-bit version
File nameFile versionFile sizeDateTimePlatform
Amd64_69bafa603ac8cd47d49dd4b5abfaffb8_31bf3856ad364e35_6.0.6000.20685_none_9f1e979756d94a3c.manifestNot applicable70924-Sep-200704:56Not applicable
Amd64_dc613021f144dae831446d68fcc8e885_31bf3856ad364e35_6.0.6000.20685_none_f9df90e110eb16fd.manifestNot applicable70924-Sep-200704:56Not applicable
Amd64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.0.6000.20685_none_41475700855e711b.manifestNot applicable40,57624-Sep-200705:03Not applicable
Package_1_for_kb942219~31bf3856ad364e35~amd64~~ applicable1,80624-Sep-200704:56Not applicable
Package_2_for_kb942219~31bf3856ad364e35~amd64~~ applicable2,02324-Sep-200704:56Not applicable
Update.mumNot applicable1,92524-Sep-200704:56Not applicable
Wow64_microsoft-windows-security-kerberos_31bf3856ad364e35_6.0.6000.20685_none_4b9c0152b9bf3316.manifestNot applicable41,16024-Sep-200705:03Not applicable
To work around this problem, turn off UAC, or log on by using an account that is not an Administrator account.
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.

This option is not available Windows 2008 R2 and Windows 7 anymore. In this operating system release, restricted tokens are not given the TGT Session keys.
More information
This problem occurs when you try to log on to a business application that uses the Kerberos protocol to authenticate the user.

When the SSO feature in the application is implemented, the client computer uses a service ticket for authentication. To obtain this service ticket, the client computer sends a request to Key Distribution Center (KDC). After KDC provides the service ticket to the client computer, the Kerberos service on the client computer stores the service ticket in the credentials cache.

When an application that does not integrate with SSPI uses the Kerberos protocol to authenticate the user, the application needs the TGT session key to build subsequent Kerberos Ticket requests. However, if the UAC feature is turned on, and if the user account is a member of the local Administrators group, the session key in the service ticket is not given to the application.

This is not allowed anymore in Windows 7 since the session keys allows the application to gain a service ticket that would be the input for a full user token on the machine. That would circumvent the goal of using restricted tokens for the user and there is always an elevation prompt when the full token is used.

Microsoft has originally introduced this option documented in this KB article using the registry entry allowtgtsessionkey:

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
vista UAC "Kerberos cache" "service ticket session key cache"

Article ID: 942219 - Last Review: 01/16/2015 09:49:09 - Revision: 10.0

Windows Vista Enterprise 64-bit Edition, Windows Vista Ultimate 64-bit Edition, Windows Vista Business, Windows Vista Business 64-bit Edition, Windows Vista Enterprise, Windows Vista Ultimate

  • kbnosurvey kbarchive kbautohotfix kbvistasp1fix kbexpertiseadvanced kbfix kbqfe kbhotfixserver KB942219