The Windows Server 2008 Online Certificate Status Protocol (OCSP) responder does not work with signing certificates that do not use the SHA1 algorithm

Applies to: Windows Server 2008 Datacenter without Hyper-VWindows Server 2008 Enterprise without Hyper-VWindows Server 2008 Standard without Hyper-V


Consider the following scenario:
  • On a Windows Server 2008-based computer, the Online Certificate Status Protocol (OCSP) responder is enabled.

    Note To enable the OCSP responder, you must add the Active Directory Certificate Services role on the computer.
  • The OCSP responder uses a manually assigned OCSP signing certificate.
In this scenario, the OCSP revocation does not work. Additionally, you receive the following error message:
Signing Certificate: Error HRESULT E_FAIL has been returned from a call to a COM component.
When this issue occurs, an event that resembles the following is logged in the Application log:


OCSP is hardcoded to use the Secure Hash Algorithm 1 (SHA1) algorithm for signature verification. This issue occurs if the manually assigned certificate does not use the SHA1 algorithm.


A hotfix is available to resolve this issue. This hotfix resolves this limitation so that OCSP is not bound to SHA1 signing certificates.

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 this specific problem. 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.

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.


To apply this hotfix, you must have Windows Server 2008 installed.

Restart requirement

After you apply this hotfix, you must restart the Online responder service (Ocspsvc.exe).

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

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

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 Server 2008 note

The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are
listed separately
. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatformService branch
Ocspsvcctrs.hNot Applicable1,56918-Dec-200721:29Not ApplicableX86_MICROSOFT-WINDOWS-OCSP
Ocspsvcctrs.iniNot Applicable2,91818-Dec-200721:29Not ApplicableX86_MICROSOFT-WINDOWS-OCSP
For all supported x64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatformService branch
Ocspsvcctrs.hNot Applicable1,56918-Dec-200721:29Not ApplicableAMD64_MICROSOFT-WINDOWS-OCSP
Ocspsvcctrs.iniNot Applicable2,91818-Dec-200721:29Not ApplicableAMD64_MICROSOFT-WINDOWS-OCSP


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, 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 for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Package_for_kb960809_server_0~31bf3856ad364e35~x86~~ Applicable1,40909-Dec-200823:11Not Applicable
Package_for_kb960809_server~31bf3856ad364e35~x86~~ Applicable1,43009-Dec-200823:11Not Applicable
X86_microsoft-windows-ocspsvc_31bf3856ad364e35_6.0.6001.22325_none_ddba509b7c8010ea.manifestNot Applicable51,64409-Dec-200804:57Not Applicable
Additional files for all supported x64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Amd64_microsoft-windows-ocspsvc_31bf3856ad364e35_6.0.6001.22325_none_39d8ec1f34dd8220.manifestNot Applicable51,68209-Dec-200805:46Not Applicable
Package_for_kb960809_server_0~31bf3856ad364e35~amd64~~ Applicable1,41709-Dec-200823:11Not Applicable
Package_for_kb960809_server~31bf3856ad364e35~amd64~~ Applicable1,43809-Dec-200823:11Not Applicable