A "Request For Permission to Use a Key" dialog box appears every time that you send an e-mail message in Outlook 2007

Work anywhere from any device with Microsoft 365

Upgrade to Microsoft 365 to work anywhere with the latest features and updates.

Upgrade now

Symptoms

Consider the following scenario:

  • On a computer that is running Windows 7 or Windows Server 2008 R2, you configure Microsoft Office Outlook 2007 to use a digital signature when you send e-mail.

  • You import a digital ID into Outlook 2007.



In this scenario, a Request For Permission to Use a Key dialog box appears every time that you send an e-mail message. After you grant Outlook 2007 permission to use the digital ID, Outlook 2007 successfully sends the e-mail message.

Note When you try to send the e-mail message, you may also be prompted to enter the password of the digital ID. This situation depends on the security level that you specify for the digital ID.

Resolution

After you apply this hotfix, you can set registry entries to configure the number of digital IDs that an application uses. Additionaly, you can set the length of time that the application caches the digital IDs. For more information, see 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:

http://support.microsoft.com/contactus/?ws=supportNote 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 7 or Windows Server 2008 R2.

Registry information

This section contains information about how to configure the number of digital IDs that an application uses, and the length of time that the application caches the digital IDs.

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 WindowsTo configure the number of digital IDs that Windows 7 and Windows Server 2008 R2 can cache in an application, follow these steps:

  1. Click Startstart button , type regedit in the Search programs and files box, and then press ENTER.

  2. Locate and then click the following registry subkey:

    HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Cryptography

  3. On the Edit menu, point to New, and then click DWORD Value.

  4. Type PrivKeyCacheMaxItems to name the new entry, and then press ENTER.

  5. Right-click PrivKeyCacheMaxItems, and then click Modify.

  6. Click Decimal under Base.

  7. In the Value data box, type the maximum number of digital IDs that Windows can cache in an application, and then click OK.

    Note If you do not want Windows to cache digital IDs, type 0 in the Value data box.

  8. Exit Registry Editor.

To change the length of time that Windows 7 and Windows Server 2008 R2 cache digital IDs in an application, follow these steps:

  1. Click Startstart button , type regedit in the Search programs and files box, and then press ENTER.

  2. Locate and then click the following registry subkey:

    HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Cryptography

  3. On the Edit menu, point to New, and then click DWORD Value.

  4. Type PrivateKeyLifetimeSeconds to name the new entry, and then press ENTER.

  5. Right-click PrivateKeyLifetimeSeconds, and then click Modify.

  6. Click Decimal under Base.

  7. In the Value data box, type the length of time in seconds that you want Windows to cache digital IDs in an application, and then click OK. For example, if you type 2,592,000, Windows caches digital IDs for 30 days.

  8. Exit Registry Editor.

To change the interval at which Windows removes the outdated keys, follow these steps:

  1. Click Startstart button , type regedit in the Search programs and files box, and then press ENTER.

  2. Locate and then click the following registry subkey:

    HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Cryptography

  3. On the Edit menu, point to New, and then click DWORD Value.

  4. Type PrivKeyCachePurgeIntervalSeconds to name the new entry, and then press ENTER.

  5. Right-click PrivKeyCachePurgeIntervalSeconds, and then click Modify.

  6. Click Decimal under Base.

  7. In the Value data box, type the time interval in seconds for Windows to remove the outdated keys, and then click OK. For example, if you type 2,592,000, Windows removes the outdated keys every 30 days.

    Note By default, the value is 86,400. Therefore, if you do not change this value, Windows removes the outdated keys every single day.

  8. Exit Registry Editor.

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 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 of these 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 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 maintaining the state of the updated component. 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 name

File version

File size

Date

Time

Platform

Ncryptui.dll

6.1.7600.20613

60,928

09-Jan-2010

06:49

x86

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Ncryptui.dll

6.1.7600.20613

66,048

09-Jan-2010

07:49

x64

For all supported IA-64-based versions of Windows Server 2008 R2

File name

File version

File size

Date

Time

Platform

Ncryptui.dll

6.1.7600.20613

109,056

09-Jan-2010

06:20

IA-64

Status

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

More Information

If you configure Microsoft Office Outlook 2007 to use digital signatures in Windows 7 or in Windows Server 2008 R2, you are prompted to grant Outlook 2007 permission to use a digital ID. This behavior occurs only when you send the first e-mail message after you start Outlook 2007.

To configure Outlook 2007 to use a digital signature when you send e-mail, follow these steps:

  1. Start Outlook 2007.

  2. On the Tools menu, click Trust Center.

  3. In the Categories pane, click E-mail Security.

  4. Select the Add digital signature to outgoing message check box, and then click OK.


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

Additional files for all supported x86-based versions of Windows 7

File name

Update.mum

File version

Not applicable

File size

1,674

Date (UTC)

09-Jan-2010

Time (UTC)

10:15

Platform

Not applicable

File name

X86_88da6db1e1c809790d468bedb3354d34_31bf3856ad364e35_6.1.7600.20613_none_01e2d0c93e4589aa.manifest

File version

Not applicable

File size

700

Date (UTC)

09-Jan-2010

Time (UTC)

10:15

Platform

Not applicable

File name

X86_microsoft-windows-ncryptui-dll_31bf3856ad364e35_6.1.7600.20613_none_824559dd5d3ecfdf.manifest

File version

Not applicable

File size

2,389

Date (UTC)

09-Jan-2010

Time (UTC)

07:24

Platform

Not applicable

Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2

File name

Amd64_399bbe23a4ebf41df26fc7522bf6ac5c_31bf3856ad364e35_6.1.7600.20613_none_39d51286c940f168.manifest

File version

Not applicable

File size

704

Date (UTC)

09-Jan-2010

Time (UTC)

10:15

Platform

Not applicable

File name

Amd64_88da6db1e1c809790d468bedb3354d34_31bf3856ad364e35_6.1.7600.20613_none_5e016c4cf6a2fae0.manifest

File version

Not applicable

File size

702

Date (UTC)

09-Jan-2010

Time (UTC)

10:15

Platform

Not applicable

File name

Amd64_microsoft-windows-ncryptui-dll_31bf3856ad364e35_6.1.7600.20613_none_de63f561159c4115.manifest

File version

Not applicable

File size

2,393

Date (UTC)

09-Jan-2010

Time (UTC)

08:26

Platform

Not applicable

File name

Update.mum

File version

Not applicable

File size

2,328

Date (UTC)

09-Jan-2010

Time (UTC)

10:15

Platform

Not applicable

File name

X86_microsoft-windows-ncryptui-dll_31bf3856ad364e35_6.1.7600.20613_none_824559dd5d3ecfdf.manifest

File version

Not applicable

File size

2,389

Date (UTC)

09-Jan-2010

Time (UTC)

07:24

Platform

Not applicable

Additional files for all supported IA-64-based versions of Windows Server 2008 R2

File name

Ia64_88da6db1e1c809790d468bedb3354d34_31bf3856ad364e35_6.1.7600.20613_none_01e474bf3e4392a6.manifest

File version

Not applicable

File size

701

Date (UTC)

09-Jan-2010

Time (UTC)

10:15

Platform

Not applicable

File name

Ia64_cbe2d2290cf6f7653e260d9b979cfce0_31bf3856ad364e35_6.1.7600.20613_none_cea48bfaf7d233d0.manifest

File version

Not applicable

File size

702

Date (UTC)

09-Jan-2010

Time (UTC)

10:15

Platform

Not applicable

File name

Ia64_microsoft-windows-ncryptui-dll_31bf3856ad364e35_6.1.7600.20613_none_8246fdd35d3cd8db.manifest

File version

Not applicable

File size

2,391

Date (UTC)

09-Jan-2010

Time (UTC)

07:48

Platform

Not applicable

File name

Update.mum

File version

Not applicable

File size

1,684

Date (UTC)

09-Jan-2010

Time (UTC)

10:15

Platform

Not applicable

File name

X86_microsoft-windows-ncryptui-dll_31bf3856ad364e35_6.1.7600.20613_none_824559dd5d3ecfdf.manifest

File version

Not applicable

File size

2,389

Date (UTC)

09-Jan-2010

Time (UTC)

07:24

Platform

Not applicable

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×