Aaron Ruckman's Web Log

Visual Studio 2010 installation support with Bit Locker

2010-04-19T16:14:00Z

I've seen a number of Tweets with regards to not being able to install Visual Studio 2010 on OS with Bit Locker enabled. This issue was discussed in the Visual Studio 2010 Readme: http://bit.ly/aVMRde section: "2.1.9 Visual Studio 2010 fails to install on a BitLocker-enabled hard disk when Protection is On"

The known issue is when the install is installing to a custom path and then reboots during setup, if the drive is not unlocked when the OS logs in then the auto relaunch will fail. It is not a big deal, all you need to do is to restart your setup, which will ask you for your setup settings again. This might repeat once, but then you will be fine.

Alternatively, avoid this issue entirely by preinstalling the .NET Framework 4 and Windows Installer 4.5 by following the Avoiding Restart during Setup steps.

Aaron Ruckman - How do you like my brand?

2010-02-13T06:18:00Z

When you think about Aaron Ruckman, what does that make you think, feel, do?

Do you like Aaron's Brand? please leave me some comments to tell me how you feel about my brand.

I am doing this to prepare for a Marketing MBA Midterm. Any feedback you provide will be appreciated. :-)

Upgrade instructions for moving from Visual Studio 2010 RC to RTM

2010-02-10T05:26:00Z

If you evaluated Visual Studio 2010 RC, you will be happy to hear that no reformatting is required simply open the “uninstall Programs” (or previously “Add/Remove Programs”) and uninstall all Microsoft Visual Studio 2010 RC programs Then you are free to install one of the Visual Studio 2010 RTM offerings.

However if you wish to complete clean your machine of Visual Studio and do not intend to use Microsoft Visual Studio 2010 RTM then we’ve published helpful instructions on how to uninstall Visual Studio 2010 RC, in the RC Readme under the Uninstall section.

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

2009-11-25T20:42:00Z

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.

2009-10-27T22:01:00Z

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 sending Aaron Ruckman Setup logs

2009-10-20T03:29:00Z

Run the collect tool to collect and gather logs.

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/

Then send me a link to the logs. aaronru(a)microsoft_dot_com

Interesting Links VS 2010 B2

2009-10-20T03:24:00Z

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.

2009-10-19T22:57:00Z

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

2009-08-06T18:04:00Z

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.

2009-06-09T20:30:00Z

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.