System TipThis article applies to a different operating system than the one you are using. Article content that may not be relevant to you is disabled.
You run Windows Internet Explorer 8 on a computer that is running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 Service Pack 1 (SP1).
You implement a smart card-based single sign-on (SSO) solution by using a third-party provider.
You use a web application that requires authentication by using client certificates that are located on the smart card.
The SSO solution is configured in such a way that you are not prompted for the smart card's PIN when you log on to Windows by using the smart card.
You close an instance of Internet Explorer that requires the smart card. However, you have another instance of Internet Explorer still open, and this instance does not require the smart card.
In this scenario, when you visit a webpage that requires the smart card, you are prompted for a PIN.
This problem occurs because, when you close an instance of Internet Explorer that requires the smart card, and another instance that does not require the smart card is still open, the smart card receives a reset. Therefore, the pin type is changed to require a PIN.
Internet Explorer performs a cleanup of the security contexts when the last instance of Internet Explorer is closed. However, when the Iexplore.exe process that used the smart card is shut down, but another instance of the Iexplore.exe process is still running, the cleanup of the security context does not occur. This causes the Smart Card service to issue a reset to the smart card. The reset from the Smart Card service then causes the SSO feature to be disabled.
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that 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:
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
You must have Internet Explorer 8 installed on one of the following to apply this hotfix:
Windows 7 Service Pack 1 (SP1)
Windows Server 2008 R2 Service Pack 1 (SP1)
Registry information
To enable this hotfix, you must create a registry entry. To do this, follow these steps:
Exit all instances of Internet Explorer.
Click Start, click Run, type regedit in the Open box, and then click OK.
Locate and then click the following registry subkey:
On the Edit menu, point to New, and then click DWORD Value.
Type iexplore.exe, and then press ENTER.
Right-click iexplore.exe, and then click Modify.
In the Value data box, type 1, and then click OK.
Exit Registry Editor.
Restart information
You must restart the computer after you apply this hotfix.
Replacement information
This hotfix does not replace a previously released hotfix.
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 7 and Windows Server 2008 R2 file information notes
The MANIFEST files (.manifest) that are installed for each environment are listed separately in the "Additional file information for Windows 7 and for Windows Server 2008 R2" section. MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. 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
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Urlmon.dll
8.0.7601.21761
1,232,896
01-Jul-2011
05:44
Jsproxy.dll
8.0.7600.16385
48,128
14-Jul-2009
01:15
Wininet.dll
8.0.7601.21761
981,504
01-Jul-2011
05:44
Wininetplugin.dll
1.0.0.1
68,608
14-Jul-2009
01:16
Ieframe.dll
8.0.7601.21761
10,991,104
01-Jul-2011
05:41
Ieframe.ptxml
Not Applicable
13,270
13-Jul-2009
20:45
Ieui.dll
8.0.7600.16385
176,640
14-Jul-2009
01:15
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Urlmon.dll
8.0.7601.21761
1,494,528
01-Jul-2011
05:24
x64
Jsproxy.dll
8.0.7600.16385
64,512
14-Jul-2009
01:41
x64
Wininet.dll
8.0.7601.21761
1,189,376
01-Jul-2011
05:24
x64
Wininetplugin.dll
1.0.0.1
95,232
14-Jul-2009
01:41
x64
Ieframe.dll
8.0.7601.21761
12,262,400
01-Jul-2011
05:19
x64
Ieframe.ptxml
Not Applicable
13,270
13-Jul-2009
20:36
Not Applicable
Ieui.dll
8.0.7600.16385
247,808
14-Jul-2009
01:41
x64
Ieframe.dll
8.0.7601.21761
10,991,104
01-Jul-2011
05:41
x86
Ieui.dll
8.0.7600.16385
176,640
14-Jul-2009
01:15
x86
Wow64_ieframe.ptxml
Not Applicable
13,270
13-Jul-2009
20:45
Not Applicable
For all supported IA-64-based versions of Windows Server 2008 R2