Note: If these troubleshooting instructions do not help, search or post on MSDN Forums in .NET Framework Setup or Visual Studio Setup and Installation. This is a community-driven web site on which Microsoft employees also participate.

How to locate the latest installation log file and installation error code:

1. Navigate into the temp directory (Click Windows button, type %temp% in search bar and click temp folder in search results)
2. Search for filename that starts with “Microsoft .NET Framework 4 Setup” (It is an HTML document)
3. Navigate to the end of the html file.

You would see last line in the file starting with “Final Result: Installation failed with error code:” It will be followed by error code, e.g. (0x80070642)

Refer to following table for each error code:

1. Error Code: 0x80070002 (MSI fails to start installation)

 Steps to identify the issue:

               1. Open the latest installation log file

2. Use Ctrl+F to search for the text "PerformOperation returned 2 (translates to HRESULT = 0x80070002)".

3. Look at the pervious line with the text pattern as MSI(<<Drivename:\<<GUID>>\netfx_core_x86.msi)

4. For e.g. "MSI (E:\073b39cc3bdd7647a3baf06ef854a959\netfx_Core_x86.msi) Installation failed"

5. It means that Drivename ( as above example, E: drive ) does not have administrator  appropriate permission

 Steps to resolve the issue:

1. Go to Start-> Computer

2. Right click on the Drive name identified in the log file ( drive name identified in step 4 above)

3. Go to Security tab,Click on Edit button to update the permissions

4. Select Administrators under Groups or user names list

5. Select  Full control,Modify,Read & execute,Read, Write by clicking on Allow check boxes.

6. Click on Apply, this will start updating all the files permission existing in the drive.

7. Click OK.

Steps to Verify the issue resolution:

1. Restart the .NET4 framework setup again

.NET4 Framework 4 setup -> https://www.microsoft.com/downloads/details.aspx?FamilyID=9cfb2d51-5ff4-4491-b0e5-b386f32c0992&displaylang=en

2. Error Code:  0x00000BC9

Steps to identify the issue:

1. Open the latest Microsoft .NET Framework setup log file in the temp directory

2. Search for "exit code 3017 (translates to HRESULT = 0xbc9)"   in the log file.

Steps to resolve the issue:

1. Restart the machine.

3. Error Code: 0x80070643

1. [This is applicable if you are running Windows x64 operating system]

Check if it's 1719 MSI internal error:

Steps to Identify the issue:

1. Open the latest installation log file in the temporary directory

2. Use  Ctrl + F to search for the text "Returning IDOK. INSTALLMESSAGE_ERROR [The Windows Installer Service could not be accessed. This can occur if the Windows Installer is not correctly installed. Contact your support personnel for assistance.]

3. This may indicate that Windows Installer registry keys may not be correct

Steps to resolve the issue:

1. Click Windows button and type 'regedit' in search bar.

2. Click 'regedit' in search results

3. Navigate to following registry hive:

HKLM\Software\Microsoft\Windows\CurrentVersion\Installer

 Check if following registry keys have correct values:

•  MsiExecCA32 should end with \Windows\syswow64\msiexec.exe

• MsiExecCA64 should end with  \Windows\system32\msiexec.exe

Re-run setup program after trying troubleshooting steps. 

4.  Error: 1060 (424)

Steps to identify the issue:

1. Open the latest Microsoft.NET framework setup log file in temp directory

2. Search for " exit code 1060 (translates to HRESULT = 0x424)"
3. Also, confirm that message prior to the error line shows the below message:

"The specified service does not exist as an installed service. ."

Steps to resolve the issue:

1. Install windows update service

Refer

https://windows.microsoft.com/en-ID/windows7/Windows-Update-error-80070424

https://www.techiecorner.com/112/error-number-0x80070424-in-windows-update-solution/

For Windows 2000, for Windows XP, or for Windows Server 2003

To make sure that the required services are available and are running, follow these steps:

1. Click Start, click Run, type services.msc, and then click OK.

2. Double-click Background Intelligent Transfer Service.

3. If the Startup status shows "Stopped," click Start, and then click OK.
4. Double-click Automatic Updates.

5. If the Startup status shows "Stopped," click Start, and then click OK.

6. Double-click Workstation.
7. If the Startup status shows "Stopped," click Start, and then click OK.

8. Close the Services dialog box and then try to install updates again.

Notes

• If the Background Intelligent Transfer Service does not appear in the list of services, click the following link to view the KB article on the Microsoft Web site and download the update:
  923845  An update package for Background Intelligent Transfer Service (BITS) is now available for Windows Server 2003 and for Windows XP

• If the Automatic Update Service does not appear in the list of services, follow the steps that are listed in Method 3.

For Windows Vista, for Windows Server 2008, and for Windows 7

To make sure that the required services are available and are running, follow these steps:

1. Click Start, type services.msc in the Start Search box, and then click services.msc in the programs list. If you are prompted for an administrator password or for confirmation, type the password or provide confirmation.
2. Double-click Background Intelligent Transfer Service.
3. If the Startup status shows "Stopped," click Start, and then click OK.

4. Double-click Automatic Updates.

5. If the Startup status shows "Stopped," click Start, and then click OK.

6. Double-click Workstation.
7. If the Startup status shows "Stopped," click Start, and then click OK.
8. Close the Services dialog box and then try to install updates again.

                   <https://support.microsoft.com/kb/968002 has more details>

5.  Error: 0x80004002

Steps to identify the issue:

1. Open the latest Microsoft.NET framework setup log file in temp directory

2. Search for "exit code 0x80004002"

 Steps to resolve the issue:

        1.       Click Start and type notepad in the Start Search box, and then click notepad in the Programs list.

2.       Copy the following commands, and then paste them into the Notepad window.

REGSVR32 WUPS2.DLL /SREGSVR32 WUPS.DLL /SREGSVR32 WUAUENG.DLL /SREGSVR32 WUAPI.DLL /SREGSVR32 WUCLTUX.DLL /SREGSVR32 WUWEBV.DLL /SREGSVR32 JSCRIPT.DLL /S   REGSVR32 MSXML3.DLL /S1

3.       On the Notepad File menu, click Save As .

4.       .In the File name box, type register.bat , and then click All Files (*.*) in the Save as type box.

5.       Save the register.bat file to the desktop.

6.       Right-click the register.bat file, and then click Run as administrator.

If you are prompted for an administrator password or for confirmation, type the password, or click Continue.

7.       Try to install .NET Framework 4 setup again

If installation still fails with same error code, please follow the steps below:

1.       Download and install the Windows Update Agent

For more information about how to download the latest version of Windows Update Agent, click the following article number to view the article in the Microsoft Knowledge Base: 949104   (https://support.microsoft.com/kb/949104/)

Blocking Error messages:

 1. If you see following message in .NET4 Setup message box - " You must install the 32-bit Windows Imaging Component (WIC) before you run Setup. Please visit the Microsoft Download Center to install WIC, and then rerun Setup."

Resolution: Please visit https://go.microsoft.com/fwlink/?LinkId=162643 and install "wic_x86_enu.exe" file. After installing "wic_x86_enu.exe", rerun .NET Framework 4 setup

Incase you still see setup failure, please post your question with your setup log on the forum -> https://social.msdn.microsoft.com/Forums/en-US/netfxsetup/threads

Regards,

Varun Gupta

Using Clickonce/setup projects, there is easy built in support to chain install .NET Framework 4 and .NET Framework 4 Client Profile with your application. Refer to https://msdn.microsoft.com/en-us/library/7tx0bw8y.aspx for more information on using 'prerequisites dialog box' to choose appropriate options to chain install .NET Framework.

Note that with Visual Studio 2010 RC, .NET Framework 4 redistributable packages are released. The web bootstrapper packages for .NET Framework 4 will be released with the final release. Due to this, when you select .NET Framework 4 prerequisite in Setup Projects/Clickonce, "Download prerequisites from the component vendor's web site" option is not available for RC release. This option will be available in final release of Visual Studio 2010.

Note that if you choose this option, Visual Studio will fall back to "Download prerequisites from the same location as my application" option. You would also see a build warning - " The value of the 'Public Key' attribute....". The workaround is to select "Download prerequisites from the same location as my application" radio button from the prerequisites dialog box. This would mean that you would need to include .NET Framework 4 redistributable package along with the setup.exe or clickonce package.

Let me know if you have any questions.

I hope you are enjoying Visual Studio 2010 Release Candidate!

-Varun

In case you encounter .NET Framework 4 or Visual Studio 2010 setup failure, we would need setup logs to investigate the failure.

To make this task easier, we have created a tool (collect.exe) that helps finds and creates a zip file of all relevant logs on your computer.

Here are the steps:

1. Download collect.exe from https://go.microsoft.com/?LinkId=8967043
2. You may choose to save the tool for later use, or to run directly.
3. The utility creates a compressed cabinet of all the VS and .NET logs to %TEMP%\vslogs.cab.

For more details on the usage of the tool, you can refer to https://blogs.msdn.com/heaths/pages/collect.aspx

Reporting setup errors?

If you would like to report an error, please collect logs as described above and choose from the options below.

1. Search or post on MSDN Forums in .NET Framework Setup or Visual Studio Setup and Installation. This is a community-driven web site on which Microsoft employees also participate.
2. Report installation issues or provide feedback for Visual Studio on Microsoft Connect. You may upload logs using Connect. This allows us to view and manage bugs, and customers to vote or provide additional details in a consistent manner.

 My collegue has written an interesting blog post that provides into the Client profile. Interesting read -> .NET Framework 4 Client Profile - Introduction

 Have fun!

.NET Framework 4 Beta1 release has two SKUs.

1. .NET Framework 4 Client Beta1 -> .NET Framework 4 Client is targeted at applications that run on  Windows Client operating systems. This is smaller in size than the Full .NET Framework 4 Beta1

 2. .NET Framework 4 Beta1 -> This contains the full feature set of .NET Framework 4 Beta1

You can checkout the walkthroughts, downloads @ https://msdn.microsoft.com/en-us/netframework/dd819232.aspx 

If you have any questions, you can use .NET Framework 4 Beta1 forums @ https://social.msdn.microsoft.com/Forums/en-US/netfxsetupprerelease/threads

Feel free to send your comments and feedback! 

I would be blogging more details about these SKUs and .NET Framework 4 deployment experiences in later posts.

Varun

- Just go to Add/Remove programs and uninstall 'Visual Studio 2008 Beta2\code name Orcas products'

- Install Visual Studio 2008 official final release version!

So you just need to uninstall one application in Beta2 and install final release version!

If you face uninstall issues, just go to following page: https://blogs.msdn.com/varungupta/archive/2007/12/04/visual-studio-2008-setup-troubleshooting-guide.aspx

Thanks,

Varun

State of Visual Studio 2008 Setup	Windows Vista	Windows XP & Windows 2003 Server
Setup pops up error message box in the middle of installation or setup returns failure screen	Look in this document	Look in this document
Visual Studio 2008 doesn’t start properly after installation

1.     Visual Studio 2008 Setup displays a dialog box during the middle of setup indicating failure

A)   Relevant only if you are running setup on Windows Vista:  Visual Studio Setup shows a dialog box with following message: Error 1935: An error occurred during installation of assembly ‘XYZ’

Next steps

Workaround 1:

Reboot your machine and restart Visual Studio 2008 setup.

 
Workaround 2:

 If Workaround 1 doesn’t work,

1. Reboot the machine

2. Disable windows update (start menu -> windows update)

3. Restart VS setup

4. When VS Setup is done, enable windows update (don't forget this step!)

B)   Dialog box indicating that pre-release components are present on the computer

Symptom

Setup would pop up following message box: “Thank you for participating in the Beta program. You must uninstall all the pre-release products in a specific order before you can continue with setup. For detailed information, see the uninstall support page and the readme - XYZ component name “for example component name could be MSDN Library for Visual Studio Orcas - ENU”

Next steps:

The dialog box message specifies the components that need to be uninstalled from the machine.

1.      Go to Add/remove programs and remove the prerelease components in the correct order specified at https://msdn2.microsoft.com/en-us/vs2008/bb964521.aspx. Uninstalling in correct order is important to ensure that all dependencies are met.

2.      Try running Visual Studio 2008 setup again.

3.      If it fails again with same message box, then identify the components reported by the message box.

a.      If those components can be found in Add/Remove programs (in control panel).

                                                                                                  i.      Go to Add/Remove programs and remove those components. Restart setup.

b.      If those components cannot be found in Add/Remove programs (in control panel).

                                                                                                  i.      Are these components Microsoft Windows Vista Client Headers and Libraries (6001.16533.121)" and/or “Microsoft Windows Vista Client Utilities for Win32 Development (6001.16533.121)”?

Yes? – Go to this blog post to remove these components <TODO: Insert link>

                                                                                                ii.      No?

1.      Use this post to get list of all components installed on your machine.

2.      Search for the component that is listed in the message box in %temp%\log.txt. If you can find the component in the list you would see something like this.

MSDN Library for Visual Studio Orcas - ENU

Product code:        {90120000-0021-0000-0000-0000545446}

Product state:        (5) Installed.

Package code:       {182AE326-20FA-438A-ABA8-C29E58CF320A}

3.      Use product code for that component (as highlighted in the list above) to uninstall it.

a.      In the above example you would use following command on command line.

Msiexec /x {90120000-0021-0000-0000-0000545446}

4.      Repeat steps 2 and 3 for all components that you see in the message box.

C) Visual Studio setup shows a dialog box with following message “Error 1330. A file that is required cannot be installed because the cabinet file d:\cab2.cab has an invalid digital signature. This may indicate that the cabinet file is corrupt.”

            Next steps:

1.      If you are downloading & running setup from internet, try to download again.

2.      If you are running setup from DVD or network share, copy complete Visual Studio DVD on your local computer and re-run setup.

D) VS 2008 Professional Edition Trial version setup gives following error message – “Setup has encountered a problem while trying to copy: F:\setup\VSSetupWatson\DW20.exe”

Next steps:

1.      Check the file size of the file that you downloaded. It should be 3.3 GB for VS 2008 Professional Edition Trial Version, if it’s less than that it means download didn’t happen properly.

2.     Because this file is large, we recommend that you use a download manager to download it.

2. Visual Studio 2008 Setup displays a setup failure page indicating end of setup

A)  Is beta version of Office Compatibility Pack for the 2007 Office system installed on your computer?

Next steps:

1. Go to Add/Remove programs and uninstall beta version of Office Compatibility Pack for the 2007 Office system installed on your computer?

2. If you don’t find it in Add/Remove programs run msiexec /x {30120000-0020-0409-0000-0000000FF1CE}

B) Did you install pre-release versions of Visual Studio 2008 on your computer? Sometimes, few components are left behind on the computer and could cause VS 2008 Setup to fail.

Next steps:

1.      Go to %temp% folder

2.      Open log file whose filename starts with “dd_install_vs_”. For example, If you are installing VSTS, filename would be “dd_install_vs_vstscore_90”

3.      Go to the end of file.

4.      In the log file, search for “Not attempting to call MsiInstallProduct()!!!! Baseline not met!” (Search up as you are at the end of the log file J)

If you find this text, then you could have pre-release components on your computer. Otherwise, your setup failed because of different reason.

5.      Just above the line where you found text above, look for

=================

DepCheck: gencomp97 [Note: may or not be present]

DepCheck: gencomp320 [Note: may or not be present]

DepCheck_Result: 1

Microsoft Visual Studio 2008 Professional Edition - ENU: Install(): bAttemptInstall: 0 [should be present]

================

6.      Components in front of “Depcheck:” are the ones that you need to uninstall before continuing with the install. A) Gencomp97 corresponds to Microsoft Web Designer Tools B) Gencomp320 corresponds to Microsoft Document Explorer 2007 (not 2005). Please note that there could be other components too.

You would need to remove whichever components are listed. For example, if you see DepCheck: gencomp97, you would need to remove Microsoft Document Explorer 2007.

                            Steps:

1.      Use this post to get list of all components installed on your machine.

2.      Search for the component in %temp%\log.txt. If you can find the component in the list you would see something like this.

Microsoft Document Explorer 2007

Product code:        {90120000-0021-0000-0000-0000545446}

Product state:        (5) Installed.

Package code:       {182AE326-20FA-438A-ABA8-C29E58CF320A}

3.      Use product code for that component to uninstall it.

a.      In the above example you would use following command on command line.

Msiexec /x {90120000-0021-0000-0000-0000545446}

4.      Repeat steps 2 and 3 for all components that you see in the logs above.

Note: If Visual Studio setup fails while installing any component after .NET Framework 3.5, Microsoft Web Designer Tools and Microsoft Document Explorer component, please follow following steps.

After fixing setup failure issue, if you run the setup again, setup would launch in maintenance mode. To install other components, go to add/remove features and install features that you want to install.

Note: If these issues persists, you can collect setup logs using utility mentioned at https://blogs.msdn.com/astebner/archive/2007/08/01/4172276.aspx and send them on : vs2008deployment at hotmail dot com

You could follow following steps to generate list of components that are installed on your computer.

1. Download msiinv.zip
2. Extract the contents of msiinv.zip to the folder c:\msiinv on your system
3. Click on the Start menu, choose Run, type cmd and click OK
4. Run c:\msiinv\msiinv.exe -p > c:\msiinv_output.txt