Aaron Stebner's WebLog

Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio

Issue installing the .NET Framework 3.5 or 3.5 SP1 on checked or pre-release builds of Windows Vista or Windows Server 2008

Issue installing the .NET Framework 3.5 or 3.5 SP1 on checked or pre-release builds of Windows Vista or Windows Server 2008

  • Comments 53

I have heard from a couple of customers who ran into issues installing the .NET Framework 3.5 and/or the .NET Framework 3.5 SP1 on one of the following OS types:

  • Checked (also known as debug) builds of Windows Vista and/or Windows Server 2008
  • Pre-release builds of Windows Vista and/or Windows Server 2008

One of these customer reports can be found in this forum post.  I wanted to describe this scenario in more detail in case anyone else runs into a similar issue in the future.

Description of the issue

The .NET Framework 3.5 and 3.5 SP1 install service packs for the .NET Framework 2.0 and the .NET Framework 3.0 behind the scenes.  On Windows Vista and Windows Server 2008, the .NET Framework 2.0 and 3.0 service packs are installed as OS updates.  These OS updates are marked to only install on the final release versions of Windows Vista and Windows Server 2008.  That means that they will not allow you to install them on checked builds of these OS's, and they will also not allow you to install them on pre-release versions of these OS's.

Here is the exact list of .NET Framework 3.5 installation scenarios that will fail on checked builds of the OS or pre-release builds of the OS:

  • Installing the .NET Framework 3.5 on the original release of Windows Vista (but not Windows Vista SP1 or later)
  • Installing the .NET Framework 3.5 SP1 on the original release of Windows Vista or Windows Vista SP1
  • Installing the .NET Framework 3.5 SP1 on Windows Server 2008

However, installing the original release of the .NET Framework 3.5 on Windows Vista SP1 or Windows Server 2008 will not fail due to this issue.  This is because Windows Vista SP1 and Windows Server 2008 already include the .NET Framework 2.0 SP1 and 3.0 SP1 as OS components, so .NET Framework 3.5 setup does not need to install any OS updates on those systems.

How to work around the issue

Unfortunately, there is not a workaround that will allow you to install on a checked build or a pre-release build of Windows Vista or Windows Server 2008.  Instead, you will need to install a final release build of Windows Vista or Windows Server 2008, then re-run .NET Framework 3.5 or 3.5 SP1 setup.

How to diagnose the issue

If you try to install in one of the above configurations, you will see the following error in the .NET Framework 3.5 or 3.5 SP1 log file named %temp%\dd_dotnetfx35install.txt:

[08/08/08,11:11:11] Microsoft .NET Framework 2.0SP1 (CBS): ***ERRORLOG EVENT*** : Error: Installation failed for component Microsoft .NET Framework 2.0SP1 (CBS). MSI returned error code 1.

Error code 1 for Windows Vista or Windows Server 2008 OS update packages means that the package is not applicable on the current OS.

Important note about error code 1 during .NET Framework 3.5 or 3.5 SP1 setup

Please note that this blog post only describes one possible cause of error code 1 during .NET Framework 3.5 or 3.5 SP1 installation.  If you are not running a checked build of Windows or a pre-release version of Windows, then the issue described here is not the cause of the installation failure on your system.

If you are running into error code 1 but are not running a checked or pre-release build of Windows, then it typically helps to review the .NET Framework 3.5 log files to try to learn more about the root cause of the issue.  You can find more information about what log files are produced by .NET Framework 3.5 setup in this blog post, and there is information in this blog post that describes options for reporting installation failures back to Microsoft for additional investigation.

The logs that are typically the most useful in diagnosing error code 1 are the following:

  • %temp%\dd_dotnetfx35install.txt
  • %windir%\logs\cbs\cbs.log
  • %windir%\WindowsUpdate.log
  • Hi Betty - Can you please use the tool described at blogs.msdn.com/.../6458047.aspx to collect all of your .NET Framework setup log files, upload the file named %temp%\vslogs.cab that this tool will create to a file server (such as http://skydrive.live.com) and then reply back here and post a link that I can use to download your log files and take a further look?

  • I'm having a problem installing .NET Framework 3.5 SP1 and .NET Framework 3.2 Family Update for .NET Versions 2.0 through 3.5 (KB951847) x86.  What can I do to resolve this issue?

  • Hi Pam - Can you please use the tool described at blogs.msdn.com/.../6458047.aspx to collect all of your .NET Framework setup log files, upload the file named %temp%\vslogs.cab that this tool will create to a file server (such as http://skydrive.live.com) and then reply back here and post a link that I can use to download your log files and take a closer look?

  • Can you help me please ? instalation error Microsoft .NET Framework 3.5 'package': [2] Error: Installation failed for component Microsoft .NET Framework 3.5 'package'. MSI returned error code 1603

  • Hi Matt - Can you please use the tool described at blogs.msdn.com/.../6458047.aspx to collect all of your .NET Framework setup log files, upload the file named %temp%\vslogs.cab that this tool will create to a file server (like http://skydrive.live.com) and then reply back here and post a link that I can use to download your log files and take a closer look?

  • skydrive.live.com/redir.aspx

  • Hi Matt - The logs you attached show that the .NET Framework 3.5 is failing with the following error:

    Error 25541.Failed to open XML file C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\web_mediumtrust.config, system error: -2147024786

    I'd suggest trying the following to see if it helps solve this issue:

    1.  Rename the file C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\web_mediumtrust.config to web_mediumtrust.config.old

    2.  Make a copy of the file named C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\web_mediumtrust.config.default

    3.  Rename the copy that you made to web_mediumtrust.config

    4.  Try again to install the .NET Framework 3.5 SP1

    Hopefully this will help.

  • Hi

    It doesnt work.

    [09/22/11,15:30:28] Microsoft .NET Framework 3.5 'package': [2] Error: Installation failed for component Microsoft .NET Framework 3.5 'package'. MSI returned error code 1603

    [09/22/11,15:39:02] Microsoft .NET Framework 3.5 'package': [2] Error: Installation failed for component Microsoft .NET Framework 3.5 'package'. MSI returned error code 1603

    [09/22/11,15:39:23] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.5 'package' is not installed.

    [09/22/11,15:43:09] Microsoft .NET Framework 3.5 'package': [2] Error: Installation failed for component Microsoft .NET Framework 3.5 'package'. MSI returned error code 1603

    [09/22/11,16:33:35] Microsoft .NET Framework 3.5 'package': [2] Error: Installation failed for component Microsoft .NET Framework 3.5 'package'. MSI returned error code 1603

    [09/22/11,17:12:22] Microsoft .NET Framework 3.5 'package': [2] Error: Installation failed for component Microsoft .NET Framework 3.5 'package'. MSI returned error code 1603

    [09/22/11,21:04:36] Microsoft .NET Framework 3.5 'package': [2] Error: Installation failed for component Microsoft .NET Framework 3.5 'package'. MSI returned error code 1603

    [09/22/11,21:04:50] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.5 'package' is not installed.

    [09/26/11,15:29:22] Microsoft .NET Framework 3.5 'package': [2] Error: Installation failed for component Microsoft .NET Framework 3.5 'package'. MSI returned error code 1603

    [09/26/11,15:29:36] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.5 'package' is not installed.

  • Hi Matt - I'm sorry to hear that those steps didn't help.  Could you please collect and upload an updated set of log files from your computer so I can see if you're getting the same error afterwards or if it is now failing due to some other cause?

  • skydrive.live.com/redir.aspx

  • Hi Matt - Your new logs show the same error when setup tries to open web_mediumtrust.config.  It it possible that the file or folder has some kind of permission problem that is preventing setup from being able to access it.  Can you please double-check that the folder and file are both marked to allow Administrators and the local system account to have full control?

    If that doesn't help, then I'd suggest trying the repair steps listed at blogs.msdn.com/.../how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx.  If those steps don't work either, then you might have to repair/re-install Windows to solve this type of error.

  • Both accounts doesnt have full control and when I wanted to change it , the windows wrote "access denied" . I was logged as Administrator.

  • Hi Matt - You might need to try to take ownership of these items.  There are some steps that explain how to do this for registry keys at www.raymond.cc/.../full-control-permission-to-delete-or-edit-restricted-windows-registry, and the steps to do this for files and folders are similar.

  • Ok , thank you for your help but Im a layman in Pcs. Can you please tell me what registry should I allow ?  Theres a lot of registry and and dont know which allow.

  • Hi Matt - Here are steps that you should be able to use to update your file and folder permissions:

    1.  Right-click on the file or folder and choose Properties.

    2.  Click on the Security tab.

    3.  Click on the Edit button to change the settings.

    4.  Add the items named SYSTEM and Administrators and check the box to allow Full Control permissions for each of them.

Page 3 of 4 (53 items) 1234
Leave a Comment
  • Please add 8 and 2 and type the answer here:
  • Post