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. Strong key protection cannot be enforced in Windows 8.1 and Windows Server 2012 R2

Strong key protection cannot be enforced in Windows 8.1 and Windows Server 2012 R2

View products that this article applies to.

Summary

In Windows 8.1 and Windows Server 2012 R2, strong key protection for software-based keys cannot be enforced. If strong key protection is set and password caching is turned off, the password is required only for first-time access. Later access of the certificate does not prompt you for the password until the password is aged from the cache. 

Note Password aging typically occurs after one day.

Additionally, key descriptions appear to be missing in these systems. The description of keys in the Crypto Next Generation (CNG) user interface always displays a "There is no key description provided with this key" message even if a description of the key is provided.

Note In the CNG user interface, the key description is displayed in several dialog boxes. The key description is useful if you manage multiple keys. For example, when you have to sign an email message by using one of several available keys, the key description can help you determine which key to use.

↑ Back to the top

Hotfix information

A supported hotfix is available from Microsoft Support. 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, go to 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 update in Windows 8.1 or Windows Server 2012 R2, you must first have update 2919355 installed.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

↑ Back to the top

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 8.1 and Windows Server 2012 R2 file information and notes

Important Windows 8.1 and Windows Server 2012 R2 hotfixes are included in the same packages. However, only "Windows 8.1" 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.1" 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.3.960 0.17xxxWindows 8.1 and Windows Server 2012 R2RTMGDR
  • 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 8.1 and Windows Server 2012 R2" 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 8.1
File nameFile versionFile sizeDateTimePlatform
Ncryptprov.dll6.3.9600.17887303,10426-May-201519:34x86
For all supported x64-based versions of Windows 8.1 and Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Ncryptprov.dll6.3.9600.17887303,10426-May-201519:34x86

Additional file information for Windows 8.1 and Windows Server 2012 R2

Additional files for all supported x86-based versions of Windows 8.1
File nameX86_71f115eb857dc08d7667ffd1ee473888_31bf3856ad364e35_6.3.9600.17887_none_e4bfc929b538cc5c.manifest
File versionNot applicable
File size702
Date (UTC)27-May-2015
Time (UTC)06:37
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameX86_microsoft-windows-ncryptprov-dll_31bf3856ad364e35_6.3.9600.17887_none_b3188914afab54a7.manifest
File versionNot applicable
File size2,586
Date (UTC)26-May-2015
Time (UTC)21:40
SHA-1 hashNot applicable
MD5 hashNot applicable
Additional files for all supported x64-based versions of Windows 8.1 and Windows Server 2012 R2
File nameAmd64_3737db8c40cb456114288e9021ff454f_31bf3856ad364e35_6.3.9600.17887_none_ce1c977d6fa2fb21.manifest
File versionNot applicable
File size706
Date (UTC)27-May-2015
Time (UTC)06:37
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameAmd64_71f115eb857dc08d7667ffd1ee473888_31bf3856ad364e35_6.3.9600.17887_none_40de64ad6d963d92.manifest
File versionNot applicable
File size704
Date (UTC)27-May-2015
Time (UTC)06:37
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameAmd64_microsoft-windows-ncryptprov-dll_31bf3856ad364e35_6.3.9600.17887_none_0f3724986808c5dd.manifest
File versionNot applicable
File size2,590
Date (UTC)26-May-2015
Time (UTC)22:31
SHA-1 hashNot applicable
MD5 hashNot applicable
File nameX86_microsoft-windows-ncryptprov-dll_31bf3856ad364e35_6.3.9600.17887_none_b3188914afab54a7.manifest
File versionNot applicable
File size2,586
Date (UTC)26-May-2015
Time (UTC)21:40
SHA-1 hashNot applicable
MD5 hashNot applicable

↑ 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

References

Learn about the terminology that Microsoft uses to describe software updates.

↑ Back to the top

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

↑ Back to the top

Article Info
Article ID : 3066685
Revision : 1
Created on : 1/7/2017
Published on : 7/14/2015
Exists online : False
Views : 236