I have previously posted descriptions of a couple of issues that can cause the .NET Framework 3.5 beta 1 to fail to install –
- Cannot install the .NET Framework 3.5 on a pre-release build of Windows Vista
- Cannot install the .NET Framework 3.5 if a pre-release build of the .NET Framework 3.0 is installed
Symptoms of the error
The customer who contacted me received a pop-up error message during Visual Studio setup that has a title Windows Update Standalone Installer, text that lists command line switches and an OK button. It looked like the following:
How to find information about the error in the setup log files
The .NET Framework 3.5 setup log file (located at %temp%\dd_dotnetfx35install.txt) showed the following error message:
[05/07/07,13:28:33] Microsoft .NET Framework 2.0SP1 (CBS): CBSComponent Action: CreateProcess launched with cmd line : C:\Windows\system32\WUSA.exe “C:\Windows\system32\WUSA.exe” c:\Downloaded Files\microsoft\orcas_team\setup\..\wcu\dotnetframework\dotnetmsp\x86\Windows6.0-KB110806-x86.msu /quiet /norestart
[05/07/07,13:29:08] Microsoft .NET Framework 2.0SP1 (CBS): C:\Windows\system32\WUSA.exe exited with return value 87
[05/07/07,13:29:09] Microsoft .NET Framework 2.0SP1 (CBS): ***ERRORLOG EVENT*** : Error: Installation failed for component Microsoft .NET Framework 2.0SP1 (CBS). MSI returned error code 87
When installing on Windows Vista, the .NET Framework 3.5 attempts to install service packs for the .NET Framework 2.0 and 3.0 (which are OS components on Windows Vista). Error code 87 for these service packs mean that the package could not be installed due to an error with the command line parameters. In this case, the problem is that the path to the service pack setup file contains a space in it (c:\Downloaded Files), and there is a bug in .NET Framework 3.5 beta 1 setup where it does not correctly put quotes around paths with spaces in them.
How to resolve the error
If you run into this issue while attempting to install the .NET Framework 3.5 beta 1 and Visual Studio Orcas beta 1 setup, you will need to move the setup files to a folder that does not contain spaces in the name and then re-run setup.