Article ID: 306905 - View products that this article applies to.
This article was previously published under Q306905
Important This article contains information that shows you how to help lower security settings or how to turn off security features on a computer. You can make these changes to work around a specific problem. Before you make these changes, we recommend that you evaluate the risks that are associated with implementing this workaround in your particular environment. If you implement this workaround, take any appropriate additional steps to help protect your system.
You install any of the products listed at the beginning of the article without errors, but the integrated development environment (IDE) does not appear when you first start Microsoft Visual Studio .NET. Instead, the following error message appears:
The application cannot start.
-or-The IDE may flash briefly and disappear without any error message.
The IDE startup error has occurred in the following situations:
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:
(http://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
IDE unable to load Msxml3.dllThe July 2001 Beta release of the MSXML 4.0 Technology Preview has left the computer in a state that causes this behavior. To repair the Msxml3.dll registration, follow these steps:
Note If you have not already applied the latest security updates for MSXML, download the file from the following Microsoft Web site:
IDE unable to load Mso.dllUse any or all of the following to fix the Mso.dll problem:
IDE unable to load Dte.olbRegister dte.olb with the command below:
regsvr32 "C:\Program Files\Common Files\Microsoft Shared\MSEnv\DTE.OLB"
License key for Visual Studio .NET not created during setupThe Visual Studio .NET splash screen does not contain information on what products where installed and the splash screen does not contain the end user who installed the product. Also, Visual Studio .NET in Add/Remove programs for the current user is not present. The suggested solution is to completely remove Visual Studio .NET and reinstall.
Script blocking is turned on and not allowing scripting code to executeWarning This workaround may make your computer or your network more vulnerable to attack by malicious users or by malicious software such as viruses. We do not recommend this workaround but are providing this information so that you can implement this workaround at your own discretion. Use this workaround at your own risk.
The Visual Studio .NET IDE flash is not displayed and disappears if third-party script blocking is turned on. This has been seen with Norton Antivirus 2002. For additional information, visit the following Symantec Web site:
http://service4.symantec.com/SUPPORT/nav.nsf/b69c799adfa31ecc85256aa30052f4d0/049f1b2057b8d88085256a3900652a0e?OpenDocumentMicrosoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
.NET Framework setup portion of Visual Studio .NET failed to generate a valid native image for Mscorlib.dllThe Visual Studio .NET splash screen is displayed briefly and then disappears if the .NET Framework portion of Visual Studio .NET setup failed to generate a valid native image for Mscorlib.dll in the \%windir%\assembly\NativeImages1_v1.0.3705\mscorlib directory. The suggested solution is to uninstall the .NET Framework and reinstall the .NET Framework to regenerate a new Mscorlib.dll in the \%windir%\assembly\NativeImages1_v1.0.3705\mscorlib directory.
Klez virusImportant These steps may increase your security risk. These steps may also make your computer or your network more vulnerable to attack by malicious users or by malicious software such as viruses. We recommend the process that this article describes to enable programs to operate as they are designed to, or to implement specific program capabilities. Before you make these changes, we recommend that you evaluate the risks that are associated with implementing this process in your particular environment. If you choose to implement this process, take any appropriate additional steps to help protect your system. We recommend that you use this process only if you really require this process.
You may also receive this error message if your system is infected by the Klez virus. We recommend that you obtain the most recent update to your antivirus software, and then do a system scan.
If the fixes described in this article do not resolve the problem or it arises in a different scenario, please post a message including the title of this article to the newsgroup microsoft.public.vsnet.setup. To access Microsoft public newsgroups, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn.microsoft.com/newsgroups/The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
Article ID: 306905 - Last Review: August 15, 2007 - Revision: 11.10