Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
How to troubleshoot the installation of Visual Studio 2005
Article ID: 904732 - View products that this article applies to.
For a Microsoft Visual Studio 2003 or Microsoft Visual Studio 2002 version of this article, see How to troubleshoot Visual Studio .NET installation
This article describes best practices for how to troubleshoot the installation of Microsoft Visual Studio 2005. Additionally, this article describes the general steps for how to locate log files if you experience problems during the installation. More specific errors and problems are addressed in other Microsoft Knowledge Base articles.
Most installations of Visual Studio 2005 products occur as expected. Microsoft Windows Installer is used to install these products. Windows Installer is the same installation engine that you use to deploy applications that you have developed in Visual Studio 2005. Therefore, the installation should go smoothly, create the required log files, and perform complete rollbacks if potential problems are detected. Additionally, the installation should be self healing, also known as resiliency, if the installation is damaged.
Best practice installation methods may prevent many problems. Consider using best practice installation methods for all installations. This includes installations of service packs.
Best practice installation methodsBest practice installation methods have the following criteria:
Steps to use best practice installation methods
Use the Local Administrator accountBy default, the Local Administrator account is named Administrator. However, you can rename this account for security reasons. To view the name and to change the password, follow these steps:
Stop all nonessential services and applicationsImportant 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.
To stop nonessential services and applications, use one of the following methods, depending on the operating system:
Delete the contents of the Temp folder
InstallationThe computer where you install Visual Studio 2005 should never have had any beta or release candidate Visual Studio product installed. If any one or more of these products were installed, you should rebuild the computer to verify that these products have been removed. To rebuild the computer, reformat the hard disk, and then install the operating system again.
The executable file for Visual Studio 2005 is named Setup.exe. This file is located in the root folder of Disk 1 of the CD-ROM or DVD-ROM installation media.
During Setup, a list of prerequisites appears. The Setup wizard installs the prerequisites that are required by the operating system before the Setup wizard installs the Visual Studio 2005 IDE. For more information about prerequisites, see the "References" section.
By default, verbose logging is turned on for the Visual Studio 2005 installation. The log file is named VSMsiLog*.txt. The asterisk (*) represents the four alphanumeric characters in the file name. For example, the file name may be similar to VSMSILogA1d1.txt. The file is approximately 40 megabytes (MB).
Component files and logsThe following table lists each component, the component's location on the installation media, and the log file that is generated.
Many of these log files are put in the Temp folder and then moved to the \Program Files\Microsoft Visual Studio 8\Visual Studio 2005 Edition Name\Logs folder when the installation is completed.
Collapse this tableExpand this table
You can prevent many corrupted-file issues and media-reading issues by doing a flat installation. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/322950/ )Error messages when you cancel Setup of Visual Studio .NET or the MSDN Library
For more information about how to troubleshoot installation issues in Microsoft Visual Studio .NET 2002 and Microsoft Visual Studio .NET 2003, click the following article number to view the article in the Microsoft Knowledge Base:
319714For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/319714/ )How to troubleshoot Visual Studio .NET installation
888470For more information, visit the following Microsoft Web sites:
(http://support.microsoft.com/kb/888470/ )Another installation program starts when you try to install Visual FoxPro, Visual Studio .NET, or prerequisites
Microsoft Visual Studio 2005
Visual Studio Setup and installation information
Article ID: 904732 - Last Review: September 29, 2006 - Revision: 2.0