Cached credentials are always used when you run an elevated task in Windows 7 or in Windows Server 2008 R2

Symptoms

Consider the following scenario:

  • You log on to a computer that is running Windows 7 or Windows Server 2008 R2 by using a non-administrator account.

  • You run an elevated task by selecting the Run as Administrator option. Then, you are prompted for an administrator credential.

  • You enter domain administrator account credentials to continue the operation.
    Note When you use an administrator account for the first time on the computer, the administrator group membership is cached locally on the computer.

  • Later, you run an elevated task by selecting the Run as Administrator option.

  • You are prompted for an administrator credential.

In this scenario, the cached credentials are always used when you run elevated tasks by selecting the Run as Administrator option. The cached credentials cannot be updated on the computer even when the group membership for the administrator account is changed in the domain environment. Therefore, the cached group membership is used on the computer. 

Note You can only update the cached credentials by using the administrator account to log on to the computer interactively.

Resolution

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 the problem described in this article. 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 website:

http://support.microsoft.com/contactus/?ws=supportNote 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

To apply this hotfix, you must be running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1.

For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

322756 How to back up and restore the registry in WindowsAfter apply this hotfix, you must create a registry key before you restart the computer. To do this, follow these steps:

  1. Click Start start button , type regedit in the Search programs and files box, and then press ENTER.

    UAC If you are prompted for an administrator password, type the password. If you are prompted for confirmation, provide confirmation.

  2. Locate and then click the following registry subkey:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System

  3. On the Edit menu, point to New, and then click REG_DWORD Value.

  4. Type InteractiveLogonFirst, and then press ENTER.

  5. Right-click InteractiveLogonFirst, and then click Modify.

  6. In the Value data box, type 1, and then click OK.

  7. Exit Registry Editor.

Note When the value of the InteractiveLogonFirst registry entry is set to 1, an interactive logon is required when you run an elevated task. If the domain controller is not available, the system uses the cached credentials internally.






Restart requirement

You must restart the computer after you apply this hotfix.




Hotfix replacement information

This hotfix does not replace a previously released hotfix.

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    Version

    Product

    Milestone

    Service branch

    6.1.760
    1.22xxx

    Windows 7 and Windows Server 2008 R2

    SP1

    LDR

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows 7 and for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x86-based versions of Windows 7

File name

File version

File size

Date

Time

Platform

Authui.dll

6.1.7601.22296

1,796,096

10-Apr-2013

05:14

x86

Authui.ptxml

Not applicable

2,721

09-Apr-2013

23:40

Not applicable

Appinfo.dll

6.1.7601.22296

47,104

10-Apr-2013

05:14

x86

Consent.exe

6.1.7601.22296

102,248

10-Apr-2013

05:18

x86

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Authui.dll

6.1.7601.22296

1,931,776

10-Apr-2013

05:21

x64

Authui.ptxml

Not applicable

2,721

09-Apr-2013

23:38

Not applicable

Appinfo.dll

6.1.7601.22296

70,656

10-Apr-2013

05:21

x64

Consent.exe

6.1.7601.22296

112,488

10-Apr-2013

05:24

x64

For all supported IA-64-based versions of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Authui.dll

6.1.7601.22296

2,303,488

10-Apr-2013

04:27

IA-64

Authui.ptxml

Not applicable

2,721

09-Apr-2013

23:31

Not applicable

Appinfo.dll

6.1.7601.22296

128,000

10-Apr-2013

04:27

IA-64

Consent.exe

6.1.7601.22296

181,096

10-Apr-2013

04:30

IA-64


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information

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

824684Description of the standard terminology that is used to describe Microsoft software updates

Additional file information for Windows 7 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7

File name

X86_microsoft-windows-authentication-authui_31bf3856ad364e35_6.1.7601.22296_none_0e2fe6a16d06d207.manifest

File version

Not applicable

File size

70,946

Date (UTC)

10-Apr-2013

Time (UTC)

05:49

Platform

Not applicable

File name

X86_microsoft-windows-lua_31bf3856ad364e35_6.1.7601.22296_none_a886c6bcd46a5b88.manifest

File version

Not applicable

File size

6,108

Date (UTC)

10-Apr-2013

Time (UTC)

05:44

Platform

Not applicable

Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name

Amd64_microsoft-windows-authentication-authui_31bf3856ad364e35_6.1.7601.22296_none_6a4e82252564433d.manifest

File version

Not applicable

File size

70,952

Date (UTC)

10-Apr-2013

Time (UTC)

05:53

Platform

Not applicable

File name

Amd64_microsoft-windows-lua_31bf3856ad364e35_6.1.7601.22296_none_04a562408cc7ccbe.manifest

File version

Not applicable

File size

6,112

Date (UTC)

10-Apr-2013

Time (UTC)

05:51

Platform

Not applicable

Additional files for all supported IA-64-based versions of Windows Server 2008 R2

File name

Ia64_microsoft-windows-authentication-authui_31bf3856ad364e35_6.1.7601.22296_none_0e318a976d04db03.manifest

File version

Not applicable

File size

70,949

Date (UTC)

10-Apr-2013

Time (UTC)

05:34

Platform

Not applicable

File name

Ia64_microsoft-windows-lua_31bf3856ad364e35_6.1.7601.22296_none_a8886ab2d4686484.manifest

File version

Not applicable

File size

6,110

Date (UTC)

10-Apr-2013

Time (UTC)

05:33

Platform

Not applicable


Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

×