Aaron Ruckman's Web Log : Visual Studio

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.

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

aaronru — Thu, 06 Aug 2009 18:04:00 GMT

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.

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!

What to do when you go to post a setup and deployment issue on the MSDN forums?

aaronru — Tue, 11 Dec 2007 08:33:00 GMT

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

Version of .NET Framework you are trying to install.
Where did you get it (web page, path, application that redistributed the framework)
Is this a pre-release, CTP or beta version? Which? (Beta#, CTP (Month Year), RC, etc)
What .NET Framework Patches do you currently have installed?

Step 1. Follow Aaron Stebner's blog: http://blogs.msdn.com/astebner/archive/2007/08/01/4172276.aspx

I use http://home.services.spaces.live.com/ to post my logs, applications, etc. It is free and easy to use.
I've seen others use: http://www.file-upload.net/

Step 2. If this is a .NET Framework 3.5 install on Vista then you should run the following tool and post the output of the command: http://blogs.msdn.com/aaronru/archive/2007/11/29/net-framework-3-5-installation-validation-tool.aspx

Step 3. If this is a .NET Framework 3.5 isntall on Vista RTM then you should additionally try the following:

Run the following from an elevated command prompt

1. Winmgmt /verifyrepository

2. If the repository is reported as INCONSISTENT, run “Winmgmt /resetrepository” (if it fails because of service dependency, run “net stop winmgmt” and try again). If the repository is consistent, skip this step.

3. Do “mofcomp C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet.mof” to compile the failed mof.

If you feel the need to completely remove the .NET Framework and Visual Studio from your machines then you should follow the blog: http://blogs.msdn.com/aaronru/archive/2007/12/10/uninstalling-the-visual-studio-2008-rtm-or-rc.aspx

Thanks for taking the time to enhance our product.

Shaping the next generation deployment experience

aaronru — Sat, 01 Dec 2007 01:34:00 GMT

We are thinking about the next version of Visual Studio's deployment experience. I need your help to make the next version of Visual Studio's installation and deployment as valuable as possible.

Please send me your feedback. For example, I am looking for feedback in the following areas:

Do people like a lot of install options or just as few as possible.
Installation type:

Do people install through the UI or silently?
Do you launch and forget about the installation or watch it go?
Is there a silent installation method that you would like to see supported in the future?

What is a reasonable time to install the product?
Do people like the companion products that we install?
Do people ever look at the installation logs? If so, what for?
How do you deploy your applications to your customers?
How often and under what circumstances do you uninstall Visual Studio?
How often and under what circumstances do you add/remove features to/from Visual Studio?

Additionally, Have you installed any applications recently, which had a cool install experience? Tell us about it.

Send feedback and comments to aaronru@nospam_microsoft.com (prior to sending please remove "nospam_")

Thanks for improving Visual Studio.

How do I get that annoying Visual Studio compatiblity dialog to go away when running on Vista

aaronru — Tue, 17 Apr 2007 08:33:00 GMT

When using whidbey you might see a compatibility dialog. This dialog can be remedied by installing the Visual Studio's Vista Patch:

http://go.microsoft.com/?linkid=6366078

For more information:

http://msdn2.microsoft.com/en-us/vstudio/aa948853.aspx

After installing the patch, you will then be able check the box in the right way to not see that compatibility dialog again. :-)