Unable to install Visual Studio 2010 Beta 2 due to VC 9.0 runtime.

Problem:

Installing Visual Studio 2010 Beta2 (Express, Professional, Premium or Ultimate SKUs) results in a failed setup.

If the dd_error_*100.txt contains the following:

[11/25/09,09:24:37] VC 9.0 Runtime (x86): [2] Setup detection logic indicates that this component is NOT installed, but MSI indicates that it IS already installed.  This is usually caused by an incompatible previous version being installed on the system.  Check in Add Remove Programs and uninstall any previous versions of VC 9.0 Runtime (x86).
[11/25/09,09:24:37] VC 9.0 Runtime (x86): [2] Error: Installation failed for component VC 9.0 Runtime (x86). MSI returned error code 1603

Work around:

• Uninstall all VC 9.0 Runtime versions on your box.
• Then Retry to install Visual Studio 2010.
  

Visual Studio and .NET Framework do not support installing via app compat modes.

Symptoms

Visual Studio 2010 and/or .NET Framework 4.0 setup fails with 1603 error code or blocks running in Program Compatibility Mode.

Windows Program Compatibility Assistant indicates that Visual Studio setup might not have installed correctly and prompts to reinstall using recommended setting (program compatibility mode).

Workaround

Visual Studio setup cannot run in program compatibility mode. Please ensure compatibility mode setting is not enabled system wide or for the Visual Studio setup application.

Check manual setting

Compatibility mode could have been set manually through the Compatibility tab on the executable file properties.

1.       Browse to Visual Studio setup media, where you intend to run setup.exe.

2.       Right-click setup.exe and select Properties.

3.       On the Compatibility tab, clear the "Run this program in compatibility mode for" check box and then click OK.

Check Program Compatibility Assistant registry settings

Compatibility mode could have been set by Program Compatibility Assistant on previous failed or canceled attempts to run Visual Studio setup.exe.

1.       Select Run from the Windows Start menu.

2.       Type regedit, and then click OK button.

3.       Browse to HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Compatibility Assistant\Persisted registry key.

4.       Delete any value that refers to setup.exe in the location you are installing Visual Studio.

Re-launch Visual Setup

1.       Open Windows Explorer.

2.       Browse to Visual Studio setup.exe.

3.       Double-click setup.exe to run Visual Studio setup.

Guidance on posting on the Forums or sending Aaron Ruckman feedback.

Step 1. It would be super helpful if you could provide the following information at the beginning of your post:

1. Include the Product name (aka Visual Studio Ultimate 2010 Beta 2)
2. Where did you get it? (web site path)
3. What other Visual Studio or expression products do you have installed?
4. If you are using OS virtualization, please tell us which product? (aka Hyper-V, Virtual PC, etc.)
5. Which OS and language are you using?

Step 2: Run the collect tool to collect and gather logs. Then post these logs on the internet. Reference the link in your forum post.

• I use Windows Live^TM SkyDrive to post my logs, applications, etc. It is free and easy to use.
• I've seen others use: http://www.file-upload.net/

Interesting Links VS 2010 B2

Visual Studio 2010 Beta2 Forum: http://social.msdn.microsoft.com/Forums/en-US/setupprerelease/threads

Visual Studio 2010 Beta 2 Readme: http://go.microsoft.com/fwlink/?LinkID=166199

Visual Studio 2010 Beta 2 Installing and maintaining Visual Studio documents: http://msdn.microsoft.com/en-us/library/e2h7fzkw(VS.100).aspx

Connect Bugs: https://connect.microsoft.com/visualstudio?wa=wsignin1.0

Microsoft VS/.NET Log Collection Tool: http://go.microsoft.com/?LinkId=8967044

Installing Visual Studio 2010 Beta 2 if you’ve already installed Visual Studio 2010 Beta 1 and you don’t want to flatten your box.

If you evaluated Visual Studio 2010 Beta 1, you will be happy to hear that no reformatting is required. Additionally, a simple path exists to upgrade Beta2 on the same machine. It involves uninstalling your Visual Studio 2010 Beta1 product and then installing one of the Visual Studio 2010 Beta2 offerings.

Given the nature of pre-release software, there may be a few pre-steps needed to ensure success, depending on what operating system you are using or what you have installed on your machine. 

Here is a quick guide to upgrading to Beta 2.  (These steps need to be performed in this order).

1.     If you have Visual Studio Team System 2010 Beta 1 installed: go to Add/Remove Programs and uninstall Microsoft Team Foundation Server 2010 Beta 1 Object Model.

2.     If you have Silverlight SDK 3 installed:, go to Add/Remove Programs and uninstall it. (It's often installed with Expression Suite 3 or as an add-on to Visual Studio 2008).    

3.     Everyone: Go to Add/Remove Programs, Uninstall Microsoft Visual Studio 2010 Beta 1,

4.     If you are using Vista RTM or SP1, or Windows Server 2008 RTM: then go to Add/Remove Programs and uninstall .NET Framework 4. That would include any associated langpacks, Extended, and Client, in that order.

       Everyone: Now Install Visual Studio Beta 2!

For full details about these issues, you can read the official Visual Studio 2010 Beta 2 ReadMe here.

See the following help documentation link for more information on how to install and maintain Visual Studio Beta 2.

Guidance to upgrade from Windows Vista and to Windows 7 with Visual Studio 2010 Beta 1 Installed

Hi everyone,

The following will implement preventative measures and will avoid an unusable Visual Studio 2010 on your brand new Windows 7 OS if upgrading from Windows Vista.  Please note that .NET Framework 4 Beta 2 has resolved this issue.

If you upgrade to Windows 7 from Windows Vista with the .NET Framework 4 Beta 1 installed, your machine will be in an unreliable state. In this state, Visual Studio 2010, and some managed programs depending on .NET Framework 3.5 or earlier will not work.  There is no way to repair a machine that gets into this state. You will need to reinstall Windows 7. 

However, uninstalling .NET Framework 4 Beta 1 before upgrading to Windows 7 alleviates this issue and upgrading should work fine.  Below are detailed steps to completely remove .NET Framework 4 Beta 1 as well as Visual Studio 2010 Beta 1.

Uninstalling Visual Studio 2010 Beta 1 and .NET Framework 4 Beta 1

Perform the following steps to completely remove Visual Studio 2010 Beta 1 and the .NET Framework 4 Beta 1 from your machine.

1.      Uninstall TFS Object Model (Visual Studio Team System 2010 Team Suite Beta 1 customers only)

a.       Click Run from the Start Menu (or press Win+R)

b.      In the Run Dialog box, type control appwiz.cpl and then click OK.

c.       In the list of installed applications, select Microsoft Team Foundation Server 2010 Beta 1 Object Model and then choose Uninstall

2.      Uninstall Visual Studio 2010 Beta 1

a.       Click Run from the Start Menu (or press Win+R)

b.      In the Run Dialog box, type control appwiz.cpl and then click OK.

c.       In the list of installed applications, select an instance of Visual Studio 2010 Beta 1 (e.g. Microsoft Visual Studio Team System 2010 Team Suite Beta 1) and then choose Uninstall

d.      The Wizard will load then on the Welcome screen click Next to proceed.

e.     On the Maintenance page click Uninstall and choose OK to completely uninstall.

f.     The Uninstall progress dialog will show the progress and then you should see the finish dialog indicating whether the uninstall was successful.

g.     Reboot if prompted.

h.     Repeat this step 2 for each installed version of Visual Studio 2010 Beta 1.

3.      Uninstall .NET Framework 4 Beta 1

a.       Click Run from the Start Menu (or press Win+R)

b.      In the Run Dialog box, type control appwiz.cpl and then click OK.

c.       In the list of installed applications, locate the following applications and choose Uninstall for each in this order:

                                i.            Microsoft .NET Framework 4 Extended Beta 1 - Language Pack

                              ii.            Microsoft .NET Framework 4 Client Profile Beta 1 - Language Pack

                            iii.            Microsoft .NET Framework 4 Extended Beta 1

                             iv.            Microsoft .NET Framework 4 Client Profile Beta 1

d.      Reboot

4.      Uninstall C++ 2010 Redistributable

a.       Click Run from the Start Menu (or press Win+R)

b.      In the Run Dialog box, type control appwiz.cpl and then click OK.

c.       In the list of installed applications, select Microsoft Visual C++ 2010 Beta 1 Redistributable (x86 and/or x64) and then choose Uninstall

5.      Reboot

6.   It is now safe to start upgrading to Windows 7

Please do not install Visual Studio 2010 in compatibility mode.

Issue

We've seen a number of people attempt to install Visual Studio 2010 in compatibility mode on Vista and Windows 7. This results in strange behavior, like setup not installing on Vista/Windows 7 and resulting in messages like: Windows XP SP2 is not installed.

How do I run in compatibility mode?

There are 3 ways to enter compatibility mode:

1.      Find the Exe, right click on it and choose the properties.  Then go to the compatibility tab. You can specify older Operating systems there.

2.      On Windows 7, find the Exe, right click on it and choose “Troubleshoot compatibility”.

3.      After executing an application, which returns non-0, then you are prompted to re-run in compatibility mode.

Running in compatibility mode for many applications solves the issue of allowing your favorite application to continue running even when your application stops working natively.

Why is running in compatibility mode inappropriate when installing Visual Studio 2010 Beta1?

Visual Studio installs many prerequisites and companion products so you don’t have to search for them and hope that they will work together. One of things we do for our customers is detect the operating system and architecture you have installed and then install different sets of packages based on what the OS is.

When running in compatibility mode, one of the things that happens is that the version of the Operating system is returned masking the real operating system version, so the program believes that it is using a different Operating system than it actually is using.

What results is that our code path might go down a XP SP2 when installing on Vista, which results in package installation failure or blocks, because some packages target a very narrow band of operating systems.

Will start blogging about Visual Studio 2010 Beta1

So, first I want to thank all of you who have been coming to my blog for .NET Framework related solutions. I've been sort of quiet on blogging for the past several months, because I transitioned over to Visual Studio 2010 Deployment and have been gaining knowledge and expertise on that product.

 Well to be clear, it is about the same only magnitudes more information in size.

With that I will try to post something new to try and want you to help us make Visual Studio 2010 awesome.

Thanks!

Aaron Ruckman

When installing .NET Framework 3.5 on Vista what does the .NET Framework 2.0 SP1 on Vista error code 1058 mean and how do I work around it?

If you see an error like:

[05/20/08,14:05:17] Setup.exe: GetGlobalCustomProperty - Property: {BBE1827C-F2FD-4FDA-A6D6-C83B62FFFDCA} - PropertyName: compfailed - Value: 0

Then that is a known issue with your machine having the IIS server turned off and it needs to be turned on.  The reason is that some of the ASP.NET updates require the Server to be running during install.

 After installing .NET Framework 3.5 (which applies the .NET Framework 2.0 SP1 and 3.0 SP1 Updates) then you can turn the IIS server service back off.

For a more detailed description of how to find this type of error see the following:

When analyzing .NET FX 1603 errors, start with the dd_dotnetfx35install.txt log file.

Search for “1603” in the log.

In your case:

[07/17/07,13:44:29] Microsoft .NET Framework 3.5 'package': ***ERRORLOG EVENT*** : Error: Installation failed for component Microsoft .NET Framework 3.5 'package'. MSI returned error code 1603

Scroll up a few lines and note the name of the MSI log:

[07/17/07,13:44:09] Microsoft .NET Framework 3.5 'package': Enabling MSI log file: C:\DOCUME~1\username\LOCALS~1\Temp\dd_NET_Framework35_MSI69C8.txt

Open that log file.

Search for “return value 3”. This is what typically results in a 1603 error.

Action ended 13:44:25: InstallExecute. Return value 3.

Scroll up a few lines to see the actual error:

07/17/07 13:44:24 DDSet_Error: The Commandline '"C:\WINDOWS\Microsoft.NET\Framework\v3.5\WFServicesReg.exe" /c /v /m /i' returned non-zero value: -2147023838.

In this case, there is more:

DDSet_Warning: CScriptMapsComponent::Initialize m_spAdminBase.CoCreateInstance failed. Error code: 0x80070422

DDSet_Warning: CFxInstaller::SetupScriptMapsIIS6 Failed to initialize IIS6 APIs. Error code: 0x80070422

DDSet_Status: CScriptMapsComponent::Close

DDSet_Error: CFxInstaller::SetupComponents SetupScriptMaps failed. Error code: 0x80070422

Find out what the error code means:

# as an HRESULT: Severity: FAILURE (1), FACILITY_WIN32 (0x7), Code 0x422

# for decimal 1058 / hex 0x422

  ERROR_SERVICE_DISABLED                                         winerror.h

# The service cannot be started, either because it is

# disabled or because it has no enabled devices associated

# with it.

# 1 matches found for "-2147023838"

The installation needs the IIS Service running on your machine.

.NET Framework 3.5, 3.0 SP1 & 2.0 SP1 Language packages

Recently the .NET Framework 3.5 Language packages were released.

 You can get them by going to the following Microsoft Download center details page.

2.0 x86 -- http://www.microsoft.com/downloads/details.aspx?FamilyId=5F7F4632-C9C0-4E79-B269-C2AEE9D1962E&displaylang=en

2.0 x64 – http://www.microsoft.com/downloads/details.aspx?FamilyId=1CC39FFE-A2AA-4548-91B3-855A2DE99304&displaylang=en

2.0 ia64 – http://www.microsoft.com/downloads/details.aspx?FamilyId=DE4DFCCD-E75F-4C2F-9991-565A69AF9015&displaylang=en

3.0 -- http://www.microsoft.com/downloads/details.aspx?FamilyId=B3E05715-4D28-4C18-9A60-E26C0E3FFE1E&displaylang=en

3.5 -- http://www.microsoft.com/downloads/details.aspx?FamilyID=c78987b9-97f4-455f-bee7-f6bfa4ad774e&DisplayLang=en

After you browse to the page then you will need to choose a language.  When you choose that language click download to attempt to download and install that language package. 

Do you want a job?

We're looking for smart people for various jobs on the Deployment Technology Team! 

You can either submit your resume online, or send it to me directly at aaronru@microsoft<remove>.com and I'll forward it to the right people. 

Thanks!

.NET Framework 3.5 Deployment and administrator guides are published

.NET Framework 3.5 Deployment Guide

http://msdn2.microsoft.com/en-us/library/cc160716.aspx

.NET Framework 3.5 Administrator Guide:

http://msdn2.microsoft.com/en-us/library/cc160717.aspx

.NET Framework 3.0 SP1 & 2.0 SP1 on Vista RTM?

I've received the following type of question a few times and would like to give the answer with some background:

Q. Where is the .NET Framework 3.0 SP1 & 2.0 SP1 for Vista RTM?

A. .NET Framework 3.0 & 2.0 released with Vista as OS Windows Components, which means that they are serviced as any other windows Component.  Therefore, the .NET Framework 3.0 & 2.0 Service packages will be officially released as part of the Vista Service packages. When Vista SPX is shipped then .NET Framework 2.0 & 3.0 might also include updates in that service package. 

In this case the .NET Framework 3.0 & 2.0 have a service package that will be shipped with Vista SP1.  Vista SP1 RC is available now (http://technet.microsoft.com/en-us/windowsvista/bb738089.aspx)

NOTE: The same logic stated for Vista and .NET Framework will also be true for Windows2008 & .NET Framework 2.0 & 3.0, only Windows Server2008 will release with .NET Framework 2.0 SP1 & 3.0 SP1 in the OS.

Installing .NET Framework 3.5 language packages with the core

Installing ENU/Core .NET Framework 3.5 on non-ENU Operating System: 

You can install .NET Framework 3.5 on a non-English machine by providing the following command line:

dotnetfx35.exe /LANG:ENU

Installing .NET Framework 3.5 with a single Language package matching the OS:

To install .NET Framework 3.5 with a corresponding Language package, then you will need ot do the following:

1)      Download 3.5 web or full redist

a.       If full redist then you will need to extract it using the following command

                                                               i.      “dotnetfx35.exe /x:<path>”

b.      If web bootstrapper then you will need to create the following directory, at the same directory level as where you downloaded the web bootstrapper

                                                               i.      X86

1.       wcu\dotNetFramework\dotNetFX35\x86

                                                             ii.      x64

1.       wcu\dotNetFramework\dotNetFX35\x64

                                                            iii.      ia64

1.       wcu\dotNetFramework\dotNetFX35\ia64

2)      Download and copy the language package into the appropriate dotnetFX35 directory

a.       i.e. if x86 then you would copy the language package into:

                                                               i.      wcu\dotNetFramework\dotNetFX35\x86

3)      Execute the Web or full redist package.  The download manager will automatically determine which OS language that you have and install the matching language package with the OS language.

Installing .NET Framework 3.5 with a single language package,which does not match the OS language:

        Follow the steps above only for step 3, use the /LANG:<lang> switch from the command line.

Installing .NET Framework 3.5 with multiple Language packages

The general guidance is to install the core .NET Framework with the /LANG:ENU switch and then install the desired language packages.

Recent .NET Framework KBs enumerated

With .NET Framework 3.5 on Vista or LHS you might get one of the following KBs installed.  The following table helps to identify which KB matches what Framework version and which language.

LCID = Language Code ID.

NetFx2.0 SP1 & NetFx3.0 SP1 = These KBs are the representation for the Language enabling packages. 

• The English + CORE packages must be present prior to installing an additional language package.
• The non-English KBs are included in the appropriate 3.5 language package.

2.0 & 3.0 RTM Stand Alone Language Pack = These KBs enable Users to install a .NET Framework Language on Vista or LHS when the OS Language package, which contains the 2.0 & 3.0 RTM, is not installed. 

• These are included in the 3.5 Language packages and installed as appropriate.
• Note that the 936704 & 936705 are not necessary, as 110806 and 929300 contain all of the relevant files anyway.