FIX: You receive an error message when you start the Visual Studio .NET IDE after you have upgraded from Visual Studio .NET Beta 1 to Visual Studio .NET Beta 2 (302586)

Beta Information

This article discusses a Beta release of a Microsoft product. The information in this article is provided as-is and is subject to change without notice.

No formal product support is available from Microsoft for this Beta product. For information about how to obtain support for a Beta release, see the documentation that is included with the Beta product files, or check the Web location where you downloaded the release.

Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry

SYMPTOMS

After you upgrade Visual Studio .NET from Beta 1 to Beta 2 version and you then start the Visual Studio .NET integrated development environment, the following error message appears:

Microsoft Development Environment has not been installed for the current user. Please run setup to install the application.

CAUSE

The change in the Visual Studio stock keeping unit (SKU) value between the beta versions revealed a bug in the authenticity mechanism of Visual Studio .NET.

RESOLUTION

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
Run Regedit, and then browse to the following key (if it exists):

[HKEY_CLASSES_ROOT\Licenses\C4B8C1BC-A36C-4723-AF48-F362BFAB9DF5]

If this key exists, delete it.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This bug was corrected in Visual Studio .NET (2003).