Aaron Ruckman's Web Log : Deployment

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

aaronru — Wed, 25 Nov 2009 20:42:00 GMT

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.

aaronru — Tue, 27 Oct 2009 22:01:00 GMT

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.

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.

aaronru — Mon, 19 Oct 2009 22:57:00 GMT

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.

Please do not install Visual Studio 2010 in compatibility mode.

aaronru — Tue, 09 Jun 2009 20:30:00 GMT

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

aaronru — Tue, 09 Jun 2009 20:26:00 GMT

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

Do you want a job?

aaronru — Mon, 25 Feb 2008 19:22:00 GMT

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

Job Code	Position
218272	Software Development Engineer in Test
217222	Software Development Engineer
222180	Software Development Engineer
220716	Program Manager Lead
221339	Program Manager
222179	Software Architect
224188	Test Manager

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!

More download manager under the covers

aaronru — Fri, 21 Dec 2007 19:18:00 GMT

I've received the following question enought that I decided it would make a good blog post.

Q. Why does the installation process say that it needs to download XX MB when I've either got the packages locally or if I am using the full redist package?

A. This is really a formality of how we chose to design our process. The download size is really just the amount of package size that will be included total and not what might necessarily be downloaded from the internet. The following are the steps that the process goes through:

User chooses to install the .NET Framework
The package determines what is required to install based on a number of factors including OS, Architecture, if the product is already installed.
Every sub package has an associated size, which it adds up and then displays as the downloadable size.
Next it looks locally for the packages, if it finds them then it uses them. Otherwise it downloads them from the web.
Next it installs the queued sub packages in the right order.

The bottom line is that the download size might not have to download anything if it can find the package locally.

When I try to download .NET Framework 3.0 GOLD my computer says that this isn't a Windows 32 application.

aaronru — Tue, 17 Apr 2007 16:37:00 GMT

Commonly this is caused by the installation program you've downloaded to become corrupted in the download. By redownloading to either a different location you should be able to fix this issue.

Another common remedy for this issue is to download the redistributable package corresponding to your architecture:

To download the full redistributable package, rather than the bootstrapper, click the architecture you need below to start the download:

X86 Redist Package

X64 Redist Package

The redistributable might download more than you need, but is a single download. This is a preferred method if you do not worry about bandwidth, or if you want to put it on a secure location.

Be sure to Check Windows Update for any updates after you've installed the .NET Framework.

.NET Framework 3.0 available for download

aaronru — Tue, 07 Nov 2006 22:04:00 GMT

Last night .NET Framework 3.0 was made available for download. See the following links:

.NET Framework Setup forum Announcement

.NET Framework 3.0 Deployment Guide

.NET Framework MSDN Announcement

These announcements declare the really cool event that .NET Framework 3.0 is finally Released! YAY!!!!

New .NET Framework Setup Forum

aaronru — Sat, 21 Oct 2006 00:38:00 GMT

I would like to announce the new .NET Framework Setup Forum. This forum is the place to discuss .NET Framework Setup and Deployment issues and questions.

I hope you enjoy the new forum and look forward to your comments.

Best Regards,

Aaronru