Aaron Ruckman's Web Log : install

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.

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?

aaronru — Wed, 21 May 2008 07:41:00 GMT

If you see an error like:

[05/20/08,14:05:17] Microsoft .NET Framework 2.0SP1 (CBS): ***ERRORLOG EVENT*** : Error: Installation failed for component Microsoft .NET Framework 2.0SP1 (CBS). MSI returned error code 1058

[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.0 or 3.5 installation will fail if the Print Spooler is not running on Windows XP or Windows Server 2003

aaronru — Thu, 20 Dec 2007 03:32:00 GMT

One of the .NET Framework 3.0 or 3.5 prerequisite packages requires that the Print Spooler service is running in the "Started" State. If the Print Spooler Service is not running, the .NET Framework 3.0 or 3.5 installation will fail.

To resolve this issue

Start the Print Spooler service before you install the .NET Framework. To do this:

1.	Click Start, point to Settings, click Control Panel, and then double-click Administrative Tools.
2.	Double-click Services, click to select Services (Local), right-click Print Spooler, and then click Properties.
3.	Click Start, and then click OK.

.NET framework 3.0 SP1 & 3.5 download managers

aaronru — Thu, 13 Dec 2007 18:03:00 GMT

.NET Framework 3.0 SP1 & 3.5 released with a small webdownload, which then manages the installation of .NET Framework across all supported OS and architectures. This Blog will explain what they are and how to use them in your role as an end-user, Administrator and ISV.

For End Users, we expect that you will get the .NET Framework 3.0 SP1 and .NET Framework 3.5 in one of the following ways:

Downloading it from the links above
via Windows Update as they become available
Preinstalled on your box by an OEM like Dell, HP, Gateway, etc.
Your network administrator might install it for you
An ISV (application like ATI Catalyst) will install it as a prerequisite for an application that you might want to install.

If you download it yourself, then just go ahead and follow the instructions at the above links.

For ISVs and administrators, you should understand the process of what happens during the download steps. This is what is happening under the covers:

It looks to see what you need to install on your machine and makes a list, which generates the total download size, this is displayed in the UI.
Then it beings the download process

It first looks for each file in the list locally in a known and predetermined location verifying that it has the right package locally, if it exists then it moves to the next one.
If it does not exist locally, or if the validation fails on the local package, then it will attempt to download one for you from the internet, securely from Microsoft.

After it has a full set of files that match what it thinks it needs then the download manager installs them.

This is very powerful in that now an ISV does not need to carry additional binaries for supported by non-mainline scenarios. For example, an ISV might want to support both x86 & x64 but they know that they will have 80% of their customers on x86. Therefore, they can optimize their redistributable experience in that they carry only the x86 packages, and let the bootstrapper download the x64 packages for the additional 20%. Also, if a package becomes corrupted, then it provides a way to self heal the installation via a download.

For Administrators & ISVs, I've been getting the question frequently lately regarding what happened to the redist packages that we are used to?

In the past we were also asked why do I have to carry everything in the Redist, when I don't need everything for my particular scenario?

We addressed both of these issues of why do I have to carry everything and what happened to the redist packages in this implementation of the download manager.

(Full Admin guides for 3.5 & 3.0 SP1 are in the publishing pipeline, the following is just to whet your appetite)

For 3.0 SP1 see the following blog: http://blogs.msdn.com/aaronru/archive/2007/12/13/creating-net-framework-3-0-sp1-redist.aspx

For 3.5, please wait for the admin guide, which will be published soon.

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.

Downloading and installing .NET Framework 2.0 results in a not a windows application error

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

Most of the time this issue points back to a corrupted download. Redowndownloading the package to a different directory will normally do the trick.

The place to download the framework from:

http://msdn2.microsoft.com/en-us/netframework/aa731542.aspx

You will need to make sure that you download the right architecture that matches your machine.

Uninstalling the Framework

aaronru — Fri, 13 Apr 2007 17:54:00 GMT

I've been noticing that quite a few of you are having issues uninstalling a framework when partially installed or when it has been corrupted.

If you can get to the framework origininal installation package then that would be very helpful. A central location to get these downloads would be: http://msdn2.microsoft.com/en-us/netframework/aa569263.aspx

Then after you've got the installation package on your machine, execute it. what happens is that the installation will go into what is known as the maintenance mode. It will give you the option to repair and uninstall the framework.

Repairing and then uninstalling the framework in this manner normally will fix most of the issues that we've seend.

For those of you who are using 3.0, we've released a 3.0 prerelease clean up tool, which should help you put your machine into a clean state.

http://www.microsoft.com/downloads/details.aspx?familyid=AAE7FC63-D405-4E13-909F-E85AA9E66146&displaylang=en