A webpage is not displayed correctly when you browse the webpage by using Internet Explorer 8 Standards mode or Compatibility View in Internet Explorer 7
A webpage is not displayed correctly in Internet Explorer when any of the following is true:
You use Windows Internet Explorer 8 Standards mode to browse the webpage.
You enable Compatibility View in Internet Explorer 7 to browse the webpage.
Additionally, if you do not have the permissions to implement the Meta tag or the HTTP header for browser emulation, you cannot force the browser to work in QUIRKS mode from the client-side.
Notes:
When you browse a webpage by using Internet Explorer 6 or by using Windows 7 without using the compatibility mode, the webpage is displayed correctly.
The webpage is displayed correctly if you run the Developers toolbar in Internet Explorer and then you switch the document mode to Quirks mode.
This issue occurs because of the standard compliance in Internet Explorer 7 and Internet Explorer 8. Features in the earlier versions of Internet Explorer become obsolete to allow for compliancy with the current standards.
Note There are many reasons for a webpage that is written for Internet Explorer 6 to be displayed incorrectly in Internet Explorer 8 or in Internet Explorer 7 Compatibility View mode. Some of these reasons are the implementation of a feature or a bug in the product.
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.
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, submit a request to 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
To apply this hotfix, you must be running Windows Internet Explorer 8 together with one of the following operating systems:
Windows XP Service Pack 3 (SP3)
Windows Server 2003 Service Pack 2 (SP2)
Windows Vista Service Pack 1 (SP1)
Windows Vista SP2
Windows Server 2008
Windows Server 2008 SP2
Windows 7
Windows Server 2008 R2
For more information about how to obtain a Windows XP service pack, click the following article number to view the article in the Microsoft Knowledge Base:
For more information about how to obtain a Windows Server 2003 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
How to obtain the latest service pack for Windows Server 2003
For more information about how to obtain a Windows Vista service pack, click the following article number to view the article in the Microsoft Knowledge Base:
How to obtain the latest Windows Vista service pack
For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
How to obtain the latest service pack for Windows Server 2008
Installation instructions
To add an .adm file, follow these steps:
Click Start, click Run, type gpedit.msc, and then click OK.
In the Local Group Policy Editor, right-click Administrative Templates, and then click Add/Remove Templates.
NoteAdministrative Templates are available under either Computer Configuration or User Configuration. Select the configuration that is suitable to your custom template.
Click Add to add the .adm file, and then click Close.
The custom .adm file policy settings are now available in the Local Group Policy Editor.
Note The Local Group Policy Editor does not show preferences. If you add an .adm file that contains preferences instead of policy settings, you have to make the settings visible in the Group Policy object editor. To do this, click the Administrative Templates, click View, then click Filtering, and then clear the Only show policy settings that can be fully managed check box.
Restart requirement
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
File information
The English (United States) version or 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 XP and Windows Server 2003 file information notes
In addition to the files that are listed in these tables, this hotfix also installs an associated security catalog file (KBnumber.cat) that is signed with a Microsoft digital signature.
For all supported x86-based versions of Windows XP
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
SP requirement
Iertutil.dll
8.0.6001.23022
1,986,048
13-May-2010
05:17
x86
SP3
Mshtml.dll
8.0.6001.23022
5,952,512
13-May-2010
05:17
x86
SP3
Urlmon.dll
8.0.6001.23022
1,210,880
13-May-2010
05:17
x86
SP3
Inetres.adm
Not applicable
2,774,372
12-May-2010
10:41
Not applicable
SP3
For all supported x86-based versions of Windows Server 2003
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
SP requirement
Iertutil.dll
8.0.6001.23022
1,986,048
13-May-2010
05:25
x86
SP2
Inetres.adm
Not applicable
2,774,372
12-May-2010
10:54
Not applicable
SP2
Mshtml.dll
8.0.6001.23022
5,952,512
13-May-2010
05:25
x86
SP2
Urlmon.dll
8.0.6001.23022
1,210,880
13-May-2010
05:25
x86
SP2
For all supported x64-based versions of Windows Server 2003
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
SP requirement
Service branch
Iertutil.dll
8.0.6001.23022
2,334,720
13-May-2010
05:58
x64
SP2
Not applicable
Inetres.adm
Not applicable
2,774,372
13-May-2010
05:58
Not applicable
SP2
Not applicable
Mshtml.dll
8.0.6001.23022
9,255,936
13-May-2010
05:58
x64
SP2
Not applicable
Urlmon.dll
8.0.6001.23022
1,488,384
13-May-2010
05:58
x64
SP2
Not applicable
Wiertutil.dll
8.0.6001.23022
1,986,048
13-May-2010
05:58
x86
SP2
WOW
Wmshtml.dll
8.0.6001.23022
5,952,512
13-May-2010
05:58
x86
SP2
WOW
Wurlmon.dll
8.0.6001.23022
1,210,880
13-May-2010
05:58
x86
SP2
WOW
Windows Vista and Windows Server 2008 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
Service Pack 1 is integrated into the release version of Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxxx version number.
The MANIFEST files (.manifest) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are very 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 Server 2008 and of Windows Vista
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Urlmon.dll
8.0.6001.23023
1,210,880
13-May-2010
06:48
x86
Mshtml.dll
8.0.6001.23023
5,952,512
13-May-2010
06:45
x86
Mshtml.tlb
8.0.6001.23023
1,638,912
13-May-2010
05:08
Not applicable
Iertutil.dll
8.0.6001.23023
1,986,048
13-May-2010
06:44
x86
Sqmapi.dll
6.0.6001.23023
129,536
13-May-2010
06:47
x86
Inetres.adml
Not applicable
542,465
13-May-2010
06:55
Not applicable
Inetres.admx
Not applicable
3,068,121
11-May-2010
02:15
Not applicable
For all supported x64-based versions of Windows Server 2008 and of Windows Vista
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Urlmon.dll
8.0.6001.23023
1,488,384
13-May-2010
07:04
x64
Mshtml.dll
8.0.6001.23023
9,255,936
13-May-2010
07:03
x64
Mshtml.tlb
8.0.6001.23023
1,638,912
13-May-2010
05:35
Not applicable
Iertutil.dll
8.0.6001.23023
2,334,720
13-May-2010
07:02
x64
Sqmapi.dll
6.0.6001.23023
165,888
13-May-2010
07:04
x64
Inetres.adml
Not applicable
542,465
13-May-2010
07:13
Not applicable
Inetres.admx
Not applicable
3,068,121
11-May-2010
02:15
Not applicable
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 MANIFEST files (.manifest) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are very 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
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Urlmon.dll
8.0.7600.20713
1,226,240
14-May-2010
02:24
x86
Microsoft-windows-ie-htmlrendering.ptxml
Not applicable
1,141
13-May-2010
17:12
Not applicable
Mshtml.dll
8.0.7600.20713
5,972,992
14-May-2010
02:24
x86
Mshtml.tlb
8.0.7600.20713
1,638,912
13-May-2010
21:02
Not applicable
Iertutil.dll
8.0.7600.20713
2,056,192
14-May-2010
02:24
x86
Sqmapi.dll
6.1.7600.20713
189,440
14-May-2010
02:24
x86
Inetres.admx
Not applicable
3,077,269
11-May-2010
00:17
Not applicable
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.7600.20713
1,495,040
14-May-2010
01:57
x64
Microsoft-windows-ie-htmlrendering.ptxml
Not applicable
1,141
13-May-2010
17:09
Not applicable
Mshtml.dll
8.0.7600.20713
9,295,360
14-May-2010
01:54
x64
Mshtml.tlb
8.0.7600.20713
1,638,912
13-May-2010
21:21
Not applicable
Iertutil.dll
8.0.7600.20713
2,439,168
14-May-2010
01:53
x64
Sqmapi.dll
6.1.7600.20713
235,008
14-May-2010
01:56
x64
Inetres.admx
Not applicable
3,077,269
11-May-2010
17:29
Not applicable
Mshtml.dll
8.0.7600.20713
5,972,992
14-May-2010
02:24
x86
Mshtml.tlb
8.0.7600.20713
1,638,912
13-May-2010
21:02
Not applicable
Wow64_microsoft-windows-ie-htmlrendering.ptxml
Not applicable
1,141
13-May-2010
17:12
Not applicable
For all supported IA-64-based versions of Windows Server 2008 R2
The following is a list of what the Quirks mode policy list can and cannot do:
You add a hostname.tld or hostname to the Quirks policy list. For example, you add Microsoft.com or MyWebServer (netbios name). In this case, all webpages that are displayed in Quirk mode reference primary hostname.tld or hostname.
You have to send the Meta tag or the HTTP header to override Quirks mode policy list for a hostname or a hostname.tld for particular websites or webpages that should not be displayed in Quirks mode.
Note There is an order of precedence that has to be observed when you use the Quirks mode policy list:
The presence of the X-UA-Compatible item in the Meta tag or the HTTP header overrides Internet Explorer 7 Compatibility View and Quirks Compatibility View.
Internet Explorer 7 Compatibility View overrides Quirks Compatibility View.
Quirks Compatibility View overrides the Intranet zone. By default, the Intranet zone displays all websites in Internet Explorer 7 Compatibility View.
If the website uses the Intranet Zone and none of the above is true, the webpage will be displayed in Internet Explorer 7 Compatibility View.
Sub-domains are not supported with the Quirks mode policy list. The same is true for the Internet Explorer 7 Compatibility View mode.
The following is a sample of Group Policy object that is used to implement a Quirks Policy list:
; Start Copy
; CompatView Use Quirks Policy List Custom ADM
CLASS USER
CATEGORY !!WindowsComponents
CATEGORY !!InternetExplorer
POLICY "CompatView_UseQuirksPolicyList"
#if version >= 4
SUPPORTED !!SUPPORTED_IE8
#endif
EXPLAIN !!IE_ExplainCompatView_UseQuirksPolicyList
KEYNAME "Software\Policies\Microsoft\Internet Explorer\BrowserEmulation\QuirksPolicyList"
PART !!QuirksMode_SiteList LISTBOX ADDITIVE
END PART
END POLICY
END CATEGORY
END CATEGORY
CLASS MACHINE
CATEGORY !!WindowsComponents
CATEGORY !!InternetExplorer
POLICY "CompatView_UseQuirksPolicyList"
#if version >= 4
SUPPORTED !!SUPPORTED_IE8
#endif
EXPLAIN !!IE_ExplainCompatView_UseQuirksPolicyList
KEYNAME "Software\Policies\Microsoft\Internet Explorer\BrowserEmulation\QuirksPolicyList"
PART !!QuirksMode_SiteList LISTBOX ADDITIVE
END PART
END POLICY
END CATEGORY
END CATEGORY
[strings]
SUPPORTED_IE8="At least Internet Explorer 8.0"
WindowsComponents="Windows Components"
InternetExplorer="Custom ADM - Use Quirks Policy List"
CompatView_UseQuirksPolicyList="Use Policy List of Quirks Mode sites"
QuirksMode_SiteList="List of Quirks Mode sites"
IE_ExplainCompatView_UseQuirksPolicyList="Compatibility View determines how Internet Explorer identifies itself to a Web server and determines whether content is rendered in Quirks Mode or the Standards Mode available in the latest version of Internet Explorer. \n\nIf you enable this policy setting, Internet Explorer will use an Internet Explorer 7 user agent string (with an additional string appended). Additionally, Web pages included in this list will appear in Quirks Mode."
; End Copy
For more information about how to add an .adm file that is described in the sample, click here.
If you want to see the Compact View User Quirks policy list setting, you have to edit the policy filter. To do this, right-click the Custom ADM-Use Quirks Policy List folder, click View, then click Filtering, then clear Only show policy settings that can be fully managed check box, and then click OK.
In Windows XP and Windows Server 2003, the policy is displayed in the following path:
Administrative Templates/Windows Components/Custom ADM/Use Quirks Policy List
In Windows Vista, Windows Server 2008, Windows 7 and Windows Server 2008 R2, the policy is displayed in the following path:
Administrative Template/Classic Administrative Templates (ADM)/Customer ADM-User Quirks Policy List
For more information about website troubleshooting guidance, visit the following Microsoft Developer Network (MSDN) website:
For more information about how to implement different compatibility modes that are supported by Internet Explorer 8 on a per-page basis, visit the following MSDN website: