Microsoft KB Archive Search

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.

  1. Home
  2. A CA does not replace space characters in URL paths for CRL distribution points and authority information access extensions on a computer that is running Windows Server 2012

A CA does not replace space characters in URL paths for CRL distribution points and authority information access extensions on a computer that is running Windows Server 2012

View products that this article applies to.

Symptoms

Assume that you have a Windows Server 2012 computer that has the certification authority role (CA) installed. Additionally, assume that the CA name contains space characters. However, when a certificate is issued from this CA, the CA does not replace the space characters with "%20" in the URL paths for certificate revocation list (CRL) distribution points and authority information access extensions.

Note You can open the certificate and then click the Details tab to check the CRL Distribution Point field and Authority Information Access extensions.

You expect that the CA replaces all the space characters with "%20" in the URL paths for the CRL distribution points and authority information access extensions.

↑ Back to the top

Resolution

This hotfix is also available at Microsoft Update Catalog

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 website:
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 Windows Server 2012.

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 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 Server 2012 file information notes
Important Windows 8 and Windows Server 2012 hotfixes are included in the same packages. However, only "Windows 8" 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 8" 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, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.

    VersionProductMilestoneService branch
    6.2.920 0.16 xxxWindows Server 2012RTMGDR
    6.2.920 0.20 xxxWindows Server 2012RTMLDR
  • 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 2012" 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 x64-based versions of Windows Server 2012
File nameFile versionFile sizeDateTimePlatform
Crypt32.dll6.2.9200.166071,889,28009-May-201300:05x64
Crypt32.dll6.2.9200.207111,912,83209-May-201300:29x64
Cryptnet.dll6.2.9200.16607141,31209-May-201300:05x64
Cryptnet.dll6.2.9200.20711141,31209-May-201300:29x64
Crypt32.dll6.2.9200.166071,569,79209-May-201300:01x86
Crypt32.dll6.2.9200.207111,592,83209-May-201300:22x86
Cryptnet.dll6.2.9200.16607109,05609-May-201300:01x86
Cryptnet.dll6.2.9200.20711109,05609-May-201300:22x86

↑ 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

Request for Comments (RFC) specifications for URL paths that are published in issued certificates require URL encoding of special characters, and this includes space characters. Many clients, such as Windows clients, can correctly access URLs that are not encoded, and these clients are not affected by this problem. However, some third-party devices, such as some Cisco iOS devices, require the URLs to be encoded according to the RFC specifications for such devices to use these URLs correctly to perform certificate revocation checking.

References

See Description of the standard terminology that is used to describe Microsoft software updates for more information.

↑ Back to the top

Additional file information

Additional file information for Windows Server 2012

Additional files for all supported x64-based versions of Windows Server 2012
File nameAmd64_09b797a466549498f2ca81aa1b8dae59_31bf3856ad364e35_6.2.9200.16607_none_aff4ea3deb7bd88c.manifest
File versionNot Applicable
File size704
Date (UTC)09-May-2013
Time (UTC)15:26
PlatformNot Applicable
File nameAmd64_18699fcb77d3766f2ef635affb11c780_31bf3856ad364e35_6.2.9200.16607_none_21287934ab8c28c2.manifest
File versionNot Applicable
File size701
Date (UTC)09-May-2013
Time (UTC)15:26
PlatformNot Applicable
File nameAmd64_395e53d42096a13e3e2797f4c1de0e1f_31bf3856ad364e35_6.2.9200.20711_none_b6c6e85e24d3a5e4.manifest
File versionNot Applicable
File size703
Date (UTC)09-May-2013
Time (UTC)15:26
PlatformNot Applicable
File nameAmd64_557d68310b37e65ad55d3664d66a82c0_31bf3856ad364e35_6.2.9200.16607_none_acedf2c9b1b32c71.manifest
File versionNot Applicable
File size703
Date (UTC)09-May-2013
Time (UTC)15:26
PlatformNot Applicable
File nameAmd64_5e3105a96405949cea036b4d67271201_31bf3856ad364e35_6.2.9200.20711_none_c80898ea9a9a3547.manifest
File versionNot Applicable
File size701
Date (UTC)09-May-2013
Time (UTC)15:26
PlatformNot Applicable
File nameAmd64_6bc96f80673bd5844654301e8fc65ec5_31bf3856ad364e35_6.2.9200.20711_none_616621e8f0e9cd99.manifest
File versionNot Applicable
File size702
Date (UTC)09-May-2013
Time (UTC)15:26
PlatformNot Applicable
File nameAmd64_a77ad3a635e670f578cf1bc953a05cfc_31bf3856ad364e35_6.2.9200.20711_none_f2a00f7773473287.manifest
File versionNot Applicable
File size704
Date (UTC)09-May-2013
Time (UTC)15:26
PlatformNot Applicable
File nameAmd64_e38830fb3d4f86f04fb6757bcef7b83c_31bf3856ad364e35_6.2.9200.16607_none_9fe5ebacfef525d2.manifest
File versionNot Applicable
File size702
Date (UTC)09-May-2013
Time (UTC)15:26
PlatformNot Applicable
File nameAmd64_microsoft-windows-crypt32-dll_31bf3856ad364e35_6.2.9200.16607_none_b492ef30675460c3.manifest
File versionNot Applicable
File size2,786
Date (UTC)09-May-2013
Time (UTC)03:14
PlatformNot Applicable
File nameAmd64_microsoft-windows-crypt32-dll_31bf3856ad364e35_6.2.9200.20711_none_b50bba53807f8474.manifest
File versionNot Applicable
File size2,786
Date (UTC)09-May-2013
Time (UTC)03:37
PlatformNot Applicable
File nameAmd64_microsoft-windows-cryptnet-dll_31bf3856ad364e35_6.2.9200.16607_none_703c6e6e8556532d.manifest
File versionNot Applicable
File size2,237
Date (UTC)09-May-2013
Time (UTC)03:14
PlatformNot Applicable
File nameAmd64_microsoft-windows-cryptnet-dll_31bf3856ad364e35_6.2.9200.20711_none_70b539919e8176de.manifest
File versionNot Applicable
File size2,237
Date (UTC)09-May-2013
Time (UTC)03:37
PlatformNot Applicable
File nameUpdate-bf.mum
File versionNot Applicable
File size1,773
Date (UTC)09-May-2013
Time (UTC)15:26
PlatformNot Applicable
File nameX86_microsoft-windows-crypt32-dll_31bf3856ad364e35_6.2.9200.16607_none_587453acaef6ef8d.manifest
File versionNot Applicable
File size2,782
Date (UTC)09-May-2013
Time (UTC)00:58
PlatformNot Applicable
File nameX86_microsoft-windows-crypt32-dll_31bf3856ad364e35_6.2.9200.20711_none_58ed1ecfc822133e.manifest
File versionNot Applicable
File size2,782
Date (UTC)09-May-2013
Time (UTC)02:23
PlatformNot Applicable
File nameX86_microsoft-windows-cryptnet-dll_31bf3856ad364e35_6.2.9200.16607_none_141dd2eaccf8e1f7.manifest
File versionNot Applicable
File size2,235
Date (UTC)09-May-2013
Time (UTC)00:58
PlatformNot Applicable
File nameX86_microsoft-windows-cryptnet-dll_31bf3856ad364e35_6.2.9200.20711_none_14969e0de62405a8.manifest
File versionNot Applicable
File size2,235
Date (UTC)09-May-2013
Time (UTC)02:23
PlatformNot Applicable

↑ Back to the top

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

↑ Back to the top

Article Info
Article ID : 2827759
Revision : 1
Created on : 1/7/2017
Published on : 6/12/2013
Exists online : False
Views : 206