"ERROR_IPSEC_IKE_CERT_CHAIN_POLICY_MISMATCH" error when you try to start an IPsec connection between two computers that are running Windows 7 or Windows Server 2008 R2

Article translations Article translations
Article ID: 2615847 - View products that this article applies to.
Expand all | Collapse all

On This Page

Symptoms

Consider the following scenario:
  • You set up a certification authority (CA) which is compliant with ISIS-MTT version 1.1.
  • You install a CA certificate in the client trusted root store.
  • You deploy computer certificates to some computers that are running Windows 7 or Windows Server 2008 R2.
  • You configure these computers to use the computer certificates as an authentication method.
  • You try to start an Internet Protocol security (IPsec) connection between two computers.
In this scenario, the IPsec connection cannot be created. The IPsec main mode security association (SA) establishment fails. Additionally, you receive the following error message:
ERROR_IPSEC_IKE_CERT_CHAIN_POLICY_MISMATCH

Cause

This issue occurs because of a mismatch in certificate encoding. This mismatch happens because ISIS-MTT enforces UTF-8 encoding for certificates. However, the root certificate stored in the registry uses different encoding.

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 Web site:
http://support.microsoft.com/contactus/?ws=support
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 7 Service Pack 1 (SP1)
  • Windows Server 2008 R2 Service Pack 1 (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:
976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

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 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.
    Collapse this tableExpand this table
    VersionProductSR_LevelService branch
    6.1.760 1 . 17xxxWindows 7 and Windows Server 2008 R2SP1GDR
    6.1.760 1 . 21xxxWindows 7 and Windows Server 2008 R2SP1LDR
  • 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
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Bfe.dll6.1.7601.21818496,12814-Sep-201106:19x86
Fwpuclnt.dll6.1.7601.17514216,57620-Nov-201012:19x86
Ikeext.dll6.1.7601.21818675,32814-Sep-201106:22x86
Networksecurity-ppdlic.xrm-msNot applicable3,02814-Sep-201106:45Not applicable
Nshwfp.dll6.1.7601.21818657,92014-Sep-201106:25x86
Wfp.mofNot applicable82210-Jun-200921:32Not applicable
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Bfe.dll6.1.7601.21818706,56014-Sep-201106:30x64
Fwpuclnt.dll6.1.7601.21818324,09614-Sep-201106:32x64
Ikeext.dll6.1.7601.21818854,52814-Sep-201106:33x64
Networksecurity-ppdlic.xrm-msNot applicable3,02814-Sep-201106:55Not applicable
Nshwfp.dll6.1.7601.21818832,00014-Sep-201106:36x64
Wfp.mofNot applicable82210-Jun-200920:51Not applicable
Fwpuclnt.dll6.1.7601.21818216,57614-Sep-201106:21x86
Nshwfp.dll6.1.7601.21818657,92014-Sep-201106:25x86
Wfp.mofNot applicable82212-Nov-201023:57Not applicable
For all supported IA-64–based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Bfe.dll6.1.7601.218181,074,17614-Sep-201104:08IA-64
Fwpuclnt.dll6.1.7601.21818566,27214-Sep-201104:09IA-64
Ikeext.dll6.1.7601.218181,486,84814-Sep-201104:10IA-64
Networksecurity-ppdlic.xrm-msNot applicable3,02814-Sep-201104:32Not applicable
Nshwfp.dll6.1.7601.218181,114,11214-Sep-201104:13IA-64
Wfp.mofNot applicable82210-Jun-200920:57Not applicable
Fwpuclnt.dll6.1.7601.21818216,57614-Sep-201106:21x86
Nshwfp.dll6.1.7601.21818657,92014-Sep-201106:25x86
Wfp.mofNot applicable82212-Nov-201023:57Not applicable

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:
824684 Description of the standard terminology that is used to describe Microsoft software updates
For more information about how to make an Enterprise certification authority in Windows Server 2003, click the following article number to view the article in the Microsoft Knowledge Base:
890772 How to make an Enterprise certification authority that is running Windows Server 2003 with Service Pack 1 or an x64-based version of Windows Server 2003 compliant with ISIS-MTT version 1.1
For more information about how to make a stand-alone certification authority in Windows Server 2003, click the following article number to view the article in the Microsoft Knowledge Base:
888180 How to make a stand-alone certification authority that is running Windows Server 2003 with Service Pack 1 or an x64-based version of Windows Server 2003 compliant with ISIS-MTT version 1.1

Additional file information

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

Additional files for all supported x86-based versions of Windows 7
Collapse this tableExpand this table
File nameUpdate.mum
File versionNot applicable
File size2,136
Date (UTC)14-Sep-2011
Time (UTC)09:37
PlatformNot applicable
File nameX86_5abe103e8dcb5d3c952e7f405f425ada_31bf3856ad364e35_6.1.7601.21818_none_7e8d899fccaaced6.manifest
File versionNot applicable
File size704
Date (UTC)14-Sep-2011
Time (UTC)09:37
PlatformNot applicable
File nameX86_microsoft-windows-network-security_31bf3856ad364e35_6.1.7601.21818_none_cfb97b93a1e6f088.manifest
File versionNot applicable
File size158,590
Date (UTC)14-Sep-2011
Time (UTC)09:42
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
Collapse this tableExpand this table
File nameAmd64_14eb56bc4301223812ad8ef5a4c262be_31bf3856ad364e35_6.1.7601.21818_none_a37cb8b8644e497c.manifest
File versionNot applicable
File size1,058
Date (UTC)14-Sep-2011
Time (UTC)09:37
PlatformNot applicable
File nameAmd64_80f2fcb37e2a881f05bc59bdba5d224d_31bf3856ad364e35_6.1.7601.21818_none_9bb58a25b646e1d4.manifest
File versionNot applicable
File size708
Date (UTC)14-Sep-2011
Time (UTC)09:37
PlatformNot applicable
File nameAmd64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7601.21818_none_2bd817175a4461be.manifest
File versionNot applicable
File size154,588
Date (UTC)14-Sep-2011
Time (UTC)07:33
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size2,350
Date (UTC)14-Sep-2011
Time (UTC)09:37
PlatformNot applicable
File nameWow64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7601.21818_none_362cc1698ea523b9.manifest
File versionNot applicable
File size94,348
Date (UTC)14-Sep-2011
Time (UTC)06:47
PlatformNot applicable
Additional files for all supported IA-64–based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameIa64_8ae5c7268e924e449cda82a19ca5c2c1_31bf3856ad364e35_6.1.7601.21818_none_99146b9d273d55ea.manifest
File versionNot applicable
File size1,056
Date (UTC)14-Sep-2011
Time (UTC)09:37
PlatformNot applicable
File nameIa64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7601.21818_none_cfbb1f89a1e4f984.manifest
File versionNot applicable
File size154,585
Date (UTC)14-Sep-2011
Time (UTC)07:34
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size1,447
Date (UTC)14-Sep-2011
Time (UTC)09:37
PlatformNot applicable
File nameWow64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7601.21818_none_362cc1698ea523b9.manifest
File versionNot applicable
File size94,348
Date (UTC)14-Sep-2011
Time (UTC)06:47
PlatformNot applicable

Properties

Article ID: 2615847 - Last Review: December 28, 2012 - Revision: 2.0
Applies to
  • Windows 7 Enterprise
  • Windows 7 Professional
  • Windows 7 Ultimate
  • Windows Server 2008 R2 Datacenter
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Standard
  • Windows Server 2008 R2 Foundation
  • Windows Server 2008 R2 for Itanium-Based Systems
Keywords: 
kbautohotfix kbqfe kbhotfixserver kbfix kbsurveynew kbexpertiseinter KB2615847

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com