Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Pictures on a webpage are only partly displayed in Internet Explorer 8 when both IPv4 native sites and IPv4/IPv6 dual-stack sites exist in the network


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You are in a network environment that contains both IPv4 native sites and IPv4/IPv6 dual stack sites.
  • You use Windows Internet Explorer 8 to browse some webpages on a computer that is running one of the following operating systems:
    • Windows Vista
    • Windows Server 2008
    • Windows 7
    • Windows Server 2008 R2
In this scenario, some pictures on the webpages may be only partly displayed.

For example, you may experience this issue in the following network environment:
  • The network contains the following three sites:
    • Site A, an IPv4/IPv6 dual-stack site, contains a client computer that is used to surf the Internet.
    • Site B, an IPv4 native site, contains a web server that hosts a main webpage that is accessed by the client computer.
    • Site C, an IPv4/IPv6 dual-stack site, contains a server that hosts the picture resources for the webpage on site B. 
  • IPv6 is disabled on the server on site C.
  • The HTML source code on the webpage points to the picture resources on site C.
  • The server on site B has the DNS server role installed. Additionally, the following records are configured on the DNS server:
    • A record and a CNAME record for the web server on site B.
    • A record and an AAAA record for the server on site C.
In this example, you experience the issue on the client computer in site A.

Note In dual-stack sites, both IPv4 and IPv6 addresses can be configured. In IPv4 native sites, only an IPv4 address can be configured.

↑ Back to the top


Resolution

To resolve this issue, install the hotfix, and then add the registry entry that is described in the "Registry information" section.

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 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 one of the following operating systems:
  • Windows Vista Service Pack 1 (SP1)
  • Windows Vista Service Pack 2 (SP2)
  • Windows Server 2008
  • Windows Server 2008 Service Pack 2 (SP2)
  • Windows 7
  • Windows 7 Service Pack 1 (SP1)
  • Windows Server 2008 R2
  • Windows Server 2008 R2 Service Pack 1 (SP1)
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:

935791 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:

968849 How to obtain the latest service pack for Windows Server 2008

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:

976932 Information 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 Windows
After you install the hotfix, follow these steps to add the registry entry:

For 32-bit operating systems:
  1. Click Start, click Run, type regedit, and then press Enter.
  2. Locate and then right-click the following registry subkey:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_FIX_BAD_ADDRESS_COUNT_KB2529406
  3. Point to New, and then click DWORD Value.
  4. Type Iexplore.exe, and then press Enter.
  5. Double-click Iexplore.exe, type 1 in the Value data box, and then click OK.
  6. Exit Registry Editor.
For 64-bit operating systems:
  1. Click Start, click Run, type regedit, and then press Enter.
  2. Locate and then right-click the following registry subkey:
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_FIX_BAD_ADDRESS_COUNT_KB2529406
  3. Point to New, and then click DWORD Value.
  4. Type Iexplore.exe, and then press Enter.
  5. Double-click Iexplore.exe, type 1 in the Value data box, and then click OK.
  6. Exit Registry Editor.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

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 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.
  • 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 Server 2008 and for Windows Vista" section. MUM files and 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 Server 2008 and of Windows Vista
File nameFile versionFile sizeDateTimePlatform
Jsproxy.dll8.0.6001.2316825,60028-Apr-201107:03x86
Wininet.dll8.0.6001.23168919,55228-Apr-201107:09x86
Wininetplugin.dll1.0.0.164,51228-Apr-201107:09x86
For all supported x64-based versions of Windows Server 2008 and of Windows Vista
File nameFile versionFile sizeDateTimePlatform
Jsproxy.dll8.0.6001.2316831,74428-Apr-201107:35x64
Wininet.dll8.0.6001.231681,150,97628-Apr-201107:40x64
Wininetplugin.dll1.0.0.193,18428-Apr-201107:40x64
Jsproxy.dll8.0.6001.2316825,60028-Apr-201107:03x86
Wininet.dll8.0.6001.23168919,55228-Apr-201107:09x86
Wininetplugin.dll1.0.0.164,51228-Apr-201107:09x86
Windows 7 and Windows Server 2008 R2 file information notes
  • 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 Server 2008 R2 and for Windows 7" section. MUM and 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
File nameFile versionFile sizeDateTimePlatform
Jsproxy.dll8.0.7600.1638548,12814-Jul-200901:15x86
Wininet.dll8.0.7600.20955982,01628-Apr-201105:03x86
Wininetplugin.dll1.0.0.168,60814-Jul-200901:16x86
Jsproxy.dll8.0.7600.1638548,12814-Jul-200901:15x86
Wininet.dll8.0.7601.21716981,50428-Apr-201104:42x86
Wininetplugin.dll1.0.0.168,60814-Jul-200901:16x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Jsproxy.dll8.0.7600.1638564,51214-Jul-200901:41x64
Wininet.dll8.0.7600.209551,198,08028-Apr-201105:38x64
Wininetplugin.dll1.0.0.195,23214-Jul-200901:41x64
Jsproxy.dll8.0.7600.1638564,51214-Jul-200901:41x64
Wininet.dll8.0.7601.217161,189,37628-Apr-201105:33x64
Wininetplugin.dll1.0.0.195,23214-Jul-200901:41x64
Jsproxy.dll8.0.7600.1638548,12814-Jul-200901:15x86
Wininet.dll8.0.7600.20955982,01628-Apr-201105:03x86
Wininetplugin.dll1.0.0.168,60814-Jul-200901:16x86
Jsproxy.dll8.0.7600.1638548,12814-Jul-200901:15x86
Wininet.dll8.0.7601.21716981,50428-Apr-201104:42x86
Wininetplugin.dll1.0.0.168,60814-Jul-200901:16x86
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Jsproxy.dll8.0.7600.16385114,17614-Jul-200901:46IA-64
Wininet.dll8.0.7600.209552,200,06428-Apr-201104:40IA-64
Wininetplugin.dll1.0.0.1189,95214-Jul-200901:50IA-64
Jsproxy.dll8.0.7600.16385114,17614-Jul-200901:46IA-64
Wininet.dll8.0.7601.217162,201,08828-Apr-201104:27IA-64
Wininetplugin.dll1.0.0.1189,95214-Jul-200901:50IA-64
Jsproxy.dll8.0.7600.1638548,12814-Jul-200901:15x86
Wininet.dll8.0.7600.20955982,01628-Apr-201105:03x86
Wininetplugin.dll1.0.0.168,60814-Jul-200901:16x86
Jsproxy.dll8.0.7600.1638548,12814-Jul-200901:15x86
Wininet.dll8.0.7601.21716981,50428-Apr-201104:42x86
Wininetplugin.dll1.0.0.168,60814-Jul-200901:16x86

↑ Back to the top


Status

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

↑ Back to the top


More Information

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

Additional file information

Additional file information for Windows Vista and for Windows Server 2008

Additional files for all supported x86-based versions of Windows Vista and of Windows Server 2008
File nameUpdate.mum
File versionNot applicable
File size1,435
Date (UTC)29-Apr-2011
Time (UTC)20:16
PlatformNot applicable
File nameX86_3256428b93f9bb25b6a6ea7d331897b4_31bf3856ad364e35_8.0.6001.23168_none_de80e55f65239f91.manifest
File versionNot applicable
File size726
Date (UTC)29-Apr-2011
Time (UTC)20:16
PlatformNot applicable
File nameX86_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_8.0.6001.23168_none_e522b0c4d0e78f4d.manifest
File versionNot applicable
File size52,672
Date (UTC)28-Apr-2011
Time (UTC)08:04
PlatformNot applicable
Additional files for all supported x64-based versions of Windows Vista and of Windows Server 2008
File nameAmd64_a1e96ae04f9a3cb3407703c4a70711a6_31bf3856ad364e35_8.0.6001.23168_none_fb02b26ff49294f1.manifest
File versionNot applicable
File size1,100
Date (UTC)29-Apr-2011
Time (UTC)20:16
PlatformNot applicable
File nameAmd64_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_8.0.6001.23168_none_41414c4889450083.manifest
File versionNot applicable
File size52,746
Date (UTC)28-Apr-2011
Time (UTC)08:08
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size1,443
Date (UTC)29-Apr-2011
Time (UTC)20:16
PlatformNot applicable
File nameX86_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_8.0.6001.23168_none_e522b0c4d0e78f4d.manifest
File versionNot applicable
File size52,672
Date (UTC)28-Apr-2011
Time (UTC)08:04
PlatformNot applicable

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

Additional files for all supported x86-based versions of Windows 7
File nameUpdate.mum
File versionNot applicable
File size2,773
Date (UTC)29-Apr-2011
Time (UTC)21:06
PlatformNot applicable
File nameX86_aa4d4c9e8a08b68e0729dbe9eb07865e_31bf3856ad364e35_8.0.7601.21716_none_c2ede270bf0bdc83.manifest
File versionNot applicable
File size726
Date (UTC)29-Apr-2011
Time (UTC)21:06
PlatformNot applicable
File nameX86_f784ddc614d759194118a1c727a71ea4_31bf3856ad364e35_8.0.7600.20955_none_6db791e2a5509c4b.manifest
File versionNot applicable
File size726
Date (UTC)29-Apr-2011
Time (UTC)21:06
PlatformNot applicable
File nameX86_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_8.0.7600.20955_none_1d23a6e5932ddd8e.manifest
File versionNot applicable
File size43,621
Date (UTC)29-Apr-2011
Time (UTC)21:10
PlatformNot applicable
File nameX86_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_8.0.7601.21716_none_1f3643e59032f30d.manifest
File versionNot applicable
File size43,621
Date (UTC)29-Apr-2011
Time (UTC)21:10
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_24d57d78d01bcae1fd0111a4ff5db015_31bf3856ad364e35_8.0.7601.21716_none_726b3e3b0449582f.manifest
File versionNot applicable
File size730
Date (UTC)29-Apr-2011
Time (UTC)21:06
PlatformNot applicable
File nameAmd64_57776a5a601ee5122db1cf74f4c2f693_31bf3856ad364e35_8.0.7600.20955_none_391cd888f196f80d.manifest
File versionNot applicable
File size730
Date (UTC)29-Apr-2011
Time (UTC)21:06
PlatformNot applicable
File nameAmd64_62593097f2619de453590b82eaf63ce1_31bf3856ad364e35_8.0.7600.20955_none_13b7edaded6d88f1.manifest
File versionNot applicable
File size1,100
Date (UTC)29-Apr-2011
Time (UTC)21:06
PlatformNot applicable
File nameAmd64_887e8704e8f1cae02e20d97186d7d6c4_31bf3856ad364e35_8.0.7601.21716_none_b951164e38591148.manifest
File versionNot applicable
File size1,100
Date (UTC)29-Apr-2011
Time (UTC)21:06
PlatformNot applicable
File nameAmd64_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_8.0.7600.20955_none_794242694b8b4ec4.manifest
File versionNot applicable
File size43,625
Date (UTC)29-Apr-2011
Time (UTC)21:14
PlatformNot applicable
File nameAmd64_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_8.0.7601.21716_none_7b54df6948906443.manifest
File versionNot applicable
File size43,625
Date (UTC)29-Apr-2011
Time (UTC)21:14
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size3,215
Date (UTC)29-Apr-2011
Time (UTC)21:06
PlatformNot applicable
File nameX86_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_8.0.7600.20955_none_1d23a6e5932ddd8e.manifest
File versionNot applicable
File size43,621
Date (UTC)29-Apr-2011
Time (UTC)21:14
PlatformNot applicable
File nameX86_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_8.0.7601.21716_none_1f3643e59032f30d.manifest
File versionNot applicable
File size43,621
Date (UTC)29-Apr-2011
Time (UTC)21:14
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_35ee3bbdb4d3286f46fbc95ce531b951_31bf3856ad364e35_8.0.7600.20955_none_94e40ebae3f60d2e.manifest
File versionNot applicable
File size1,098
Date (UTC)29-Apr-2011
Time (UTC)21:06
PlatformNot applicable
File nameIa64_660ae6ec502fcf8e7030cde11b8ca1bf_31bf3856ad364e35_8.0.7601.21716_none_cbd8d4e5dadf6c0c.manifest
File versionNot applicable
File size1,098
Date (UTC)29-Apr-2011
Time (UTC)21:06
PlatformNot applicable
File nameIa64_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_8.0.7600.20955_none_1d254adb932be68a.manifest
File versionNot applicable
File size43,623
Date (UTC)29-Apr-2011
Time (UTC)21:06
PlatformNot applicable
File nameIa64_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_8.0.7601.21716_none_1f37e7db9030fc09.manifest
File versionNot applicable
File size43,623
Date (UTC)29-Apr-2011
Time (UTC)21:06
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size2,168
Date (UTC)29-Apr-2011
Time (UTC)21:06
PlatformNot applicable
File nameX86_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_8.0.7600.20955_none_1d23a6e5932ddd8e.manifest
File versionNot applicable
File size43,621
Date (UTC)29-Apr-2011
Time (UTC)21:06
PlatformNot applicable
File nameX86_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_8.0.7601.21716_none_1f3643e59032f30d.manifest
File versionNot applicable
File size43,621
Date (UTC)29-Apr-2011
Time (UTC)21:06
PlatformNot applicable

↑ Back to the top


Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseinter

↑ Back to the top

Article Info
Article ID : 2529406
Revision : 2
Created on : 9/21/2018
Published on : 9/21/2018
Exists online : False
Views : 335