Microsoft small business knowledge base

Article ID: 936707 - Last Review: April 5, 2012 - Revision: 2.0

Hotfix Download Available
View and request hotfix downloads

On This Page


When you start a Microsoft .NET Framework 2.0 managed application that has a Microsoft Authenticode signature, the .NET Framework 2.0 managed application takes longer than usual to start.


This problem occurs because a .NET Framework 2.0 managed assembly that has an Authenticode signature takes longer than usual to load. The signature is always verified when the .NET Framework 2.0 managed assembly that has an Authenticode signature is loaded.

Additionally, the .NET Framework 2.0 managed assembly may take longer than usual to load because of various other settings. For example, the .NET Framework 2.0 managed assembly may take longer than usual to load because of the network configuration.


Hotfix information

A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next .NET Framework 2.0 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: (
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.


You must have the .NET Framework 2.0 installed before you apply this hotfix.

Restart requirement

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

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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.
Collapse this tableExpand this table
File nameFile versionFile sizeDateTime
Normidna.nlpNot Applicable59,34228-Apr-200709:22
Normnfc.nlpNot Applicable45,79428-Apr-200709:22
Normnfd.nlpNot Applicable39,28428-Apr-200709:22
Normnfkc.nlpNot Applicable66,38428-Apr-200709:22
Normnfkd.nlpNot Applicable60,29428-Apr-200709:22


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


This hotfix adds the generatePublisherEvidence configuration setting to the .NET Framework 2.0. After you apply this hotfix, you can use this configuration setting to disable signature verification in a .NET Framework 2.0 managed application. You can use this configuration setting in an application configuration file. To do this, add the following code to the <ApplicationName>.exe.config file for the .NET Framework 2.0 managed application:
		<generatePublisherEvidence enabled="false"/>
If your application is hosted in IIS, change one of the following:
  • C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet.config
  • C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config
Note On x64 machines, you must also change one of the following:
  • C:\Windows\Microsoft.NET\Framework64\v2.0.50727\aspnet.config
  • C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG\machine.config
Note Because of how no-touch deployment assemblies are loaded, this configuration setting does not work in no-touch deployment scenarios.

When you disable signature verification, the .NET Framework 2.0 managed application starts faster.

Note When you disable signature verification, the .NET Framework 2.0 managed application no longer receives publisher evidence. This behavior affects the .NET Framework 2.0 managed application only when you use publisher evidence or when you use the PublisherIdentityPermission class.

The generatePublisherEvidence configuration setting will be available in the version of the .NET Framework that follows the Microsoft .NET Framework 3.0.

To create an application configuration file that contains this configuration setting, follow these steps:
  1. Create a file, and then name the file the <ApplicationName>.exe.config file.
  2. In a text editor, open the file that you created in step 1.
  3. Add the following code to the file.
    <?xml version="1.0" encoding="utf-8"?>
    		<generatePublisherEvidence enabled="false"/>
  4. Save the changes to the file.


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

  • Microsoft .NET Framework 2.0
kbvistasp1fix kbcode kbfix kbqfe kbhotfixserver KB936707
Additional support options
Ask The Microsoft Small Business Support Community
Contact Microsoft Small Business Support
Find Microsoft Small Business Support Certified Partner
Find a Microsoft Store For In-Person Small Business Support