none
Microsoft.NET version 3.0 Install Error: Installation failed for Windows Communication Foundation. MSI error code 1603 RRS feed

  • Question

  • Please help! I've been trying for the last day and a half to properly install Microsoft.NET version 3.5 so that I can install TurboTax and do my taxes. I was only on version 1.1. Multiple tries to upgrade to 3.5 was giving me a code 1603 error on install on "Microsoft.NET version 2.0a". I followed advice from forums here and elsewhere to uninstall and reinstall my prior versions. I also used Windows Install Cleanup before reinstalling. I keep getting to the same result when I try to go from version 2.0 to version 3.5.

    In my last attempt, I went all the way back to version 1.0 and installed each step up to 2.0 SP1 with (allegedly) no problems. This last time I decided to upgrade to 3.0 instead of going right to 3.5. Now I get the following error message:

    [04/03/10,04:07:14] Windows Communication Foundation: [2] Error: Installation failed for component Windows Communication Foundation. MSI returned error code 1603
    [04/03/10,04:07:22] WapUI: [2] DepCheck indicates Windows Communication Foundation is not installed.
    [04/03/10,04:07:22] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0 was not attempted to be installed.
    [04/03/10,04:17:49] Windows Communication Foundation: [2] Error: Installation failed for component Windows Communication Foundation. MSI returned error code 1603
    [04/03/10,04:17:57] WapUI: [2] DepCheck indicates Windows Communication Foundation is not installed.
    [04/03/10,04:17:57] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0 was not attempted to be installed.

    I found a more verbose install log, butI don't know if I should paste it all here, attach it or send it to someone.

    Can anyone help me? I can't fiugure what's gone wrong and I'm beside myself. I'm not familiar with any of this .NET stuff and all I want is to get my taxes done.

    Thanks,

    Sean

     

     

    Saturday, April 3, 2010 8:22 PM

Answers

  • Hi Sean,

    Thank you for your post.

    Some clarification with you:
    What's your OS?

    For error 1603, it's a common message that means "fatal error during installation".

    Could you please help me to try the following steps for your issue?

    If you're running XP or Windows Server 2003:
    1. Use Cleanup tool to remove .NET Framework 3.5 >> 3.0 >> 2.0 in order
    2. Download .NET Framework 3.5 Service Pack 1 (Full Package) and install it
    3. If any problem occurs during the installation, use Collect tool to collect the log files for further troubleshooting.
    (Please follow the following steps to collect the log files)

    If you're running Vista or Windows Server 2008:
    1. Check whether you have turned on the windows feature of .NET Framework 3.0.
    Please go to Control Panel -> Programs and Features -> Turn Windows features on or off -> Check the box next to Microsoft .NET Framework 3.0.
    2. Use Verification Tool to verify .Net Framework 2.0, 3.0. If .Net Framework 2.0 and 3.0 cannot be verified on your computer, you can try to follow the steps mentioned in the following blog to repair the .NET Framework 2.0 and 3.0 on Windows Vista.
    See: http://blogs.msdn.com/astebner/archive/2007/03/26/how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx
    3. Download .NET Framework 3.5 Service Pack 1 (Full Package) and install it
    4. If .NET Framework 2.0, 3.0 are verified successfully but the reinstallation of .NET Framework 3.5 fails, please collect the log file. (Please follow the following steps to collect the log files)

    The steps to collect the log:
    - Try to clean your "%temp%" folder (Start Menu >> Run >> Type "%temp%")
    - Install .NET Framework 3.5 SP1 full package
      (The installer must be run with administrator privileges - Right-click the installer >> "Run as Administrator")
    - Collect the logs from "%temp%" folder
       Collect tool: http://blogs.msdn.com/heaths/archive/2008/05/09/visual-studio-and-net-log-collection-utility.aspx
    - Send vslogs.cab file to me (v-yicche@microsoft.com)
      Note: Please attach the link of this post in the mail.

    If you're running Windows 7:
    .NET Framework 3.5 with SP1 is shipped with it as one of OS component.
    For .NET Framework 3.5 with SP1, it includes .NET 2.0 with SP2 and .NET 3.0 with SP2 as prerequisite.
    This means, you have the .NET Framework 2.0 SP2, 3.0 SP2 and 3.5 SP1 plus a few post 3.5 SP1 bug fixes on Windows 7. They are OS components. .NET 3.0 SP2 and 3.5 SP1 can be added or removed via the Programs and Features control panel. Thus, we don't need to manually install them. You can try Verifictaion Tool to verify .NET Frameworks on your machine.
    If .Net Framework 2.0, 3.0 and 3.5 cannot be verified on your computer, you can try to follow the steps mentioned in the following blog to repair the .NET Framework 2.0, 3.0 and 3.5 on Windows 7.
    See: http://blogs.msdn.com/astebner/archive/2007/03/26/how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx (also apply for Windows 7)

    If the .NET Framework 3.5 is installed but TurboTax 2009 can fail to install because it thinks the .NET Framework is not installed, please check the following helpful blog:
    http://blogs.msdn.com/astebner/archive/2010/01/26/9953883.aspx
    (Please see the part "What to do if the above doesn’t help")

    Hope this helps! If you have any concern, please feel free to let me know.

    Best regards,
    Yichun Chen
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
    • Marked as answer by YiChun Chen Friday, April 9, 2010 2:29 AM
    Monday, April 5, 2010 9:59 AM

All replies

  • Some further information:

    I followed advice in another thread to try the 3.0 install in diagnostic mode.

    I tried this and got the following error log:

    [04/03/10,04:07:14] Windows Communication Foundation: [2] Error: Installation failed for component Windows Communication Foundation. MSI returned error code 1603
    [04/03/10,04:07:22] WapUI: [2] DepCheck indicates Windows Communication Foundation is not installed.
    [04/03/10,04:07:22] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0 was not attempted to be installed.
    [04/03/10,04:17:49] Windows Communication Foundation: [2] Error: Installation failed for component Windows Communication Foundation. MSI returned error code 1603
    [04/03/10,04:17:57] WapUI: [2] DepCheck indicates Windows Communication Foundation is not installed.
    [04/03/10,04:17:57] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0 was not attempted to be installed.
    [04/03/10,06:11:01] VS Scenario: [2] *** Blocking Components exist and must be satisified before continuing to install ***
    [04/03/10,06:11:01] VS Scenario: [2] BITS Service
    [04/03/10,06:11:01] VS Scenario: [2] *** End of Blocking Component List ***
    [04/03/10,06:11:36] VS Scenario: [2] Failed to pass the Warnings/Blocks checks in CVSScenario::Start()
    [04/03/10,06:26:48] Windows Communication Foundation: [2] Error: Installation failed for component Windows Communication Foundation. MSI returned error code 1603
    [04/03/10,06:26:53] WapUI: [2] DepCheck indicates Windows Communication Foundation is not installed.
    [04/03/10,06:26:53] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0 was not attempted to be installed.

    I had checked BITS service in the "services" tab of msconfig before rebooting in diagnostic (at least I thought I did). Is this indicative of a problem with my BITS service?

     

    Saturday, April 3, 2010 9:12 PM
  • Hi Sean,

    Thank you for your post.

    Some clarification with you:
    What's your OS?

    For error 1603, it's a common message that means "fatal error during installation".

    Could you please help me to try the following steps for your issue?

    If you're running XP or Windows Server 2003:
    1. Use Cleanup tool to remove .NET Framework 3.5 >> 3.0 >> 2.0 in order
    2. Download .NET Framework 3.5 Service Pack 1 (Full Package) and install it
    3. If any problem occurs during the installation, use Collect tool to collect the log files for further troubleshooting.
    (Please follow the following steps to collect the log files)

    If you're running Vista or Windows Server 2008:
    1. Check whether you have turned on the windows feature of .NET Framework 3.0.
    Please go to Control Panel -> Programs and Features -> Turn Windows features on or off -> Check the box next to Microsoft .NET Framework 3.0.
    2. Use Verification Tool to verify .Net Framework 2.0, 3.0. If .Net Framework 2.0 and 3.0 cannot be verified on your computer, you can try to follow the steps mentioned in the following blog to repair the .NET Framework 2.0 and 3.0 on Windows Vista.
    See: http://blogs.msdn.com/astebner/archive/2007/03/26/how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx
    3. Download .NET Framework 3.5 Service Pack 1 (Full Package) and install it
    4. If .NET Framework 2.0, 3.0 are verified successfully but the reinstallation of .NET Framework 3.5 fails, please collect the log file. (Please follow the following steps to collect the log files)

    The steps to collect the log:
    - Try to clean your "%temp%" folder (Start Menu >> Run >> Type "%temp%")
    - Install .NET Framework 3.5 SP1 full package
      (The installer must be run with administrator privileges - Right-click the installer >> "Run as Administrator")
    - Collect the logs from "%temp%" folder
       Collect tool: http://blogs.msdn.com/heaths/archive/2008/05/09/visual-studio-and-net-log-collection-utility.aspx
    - Send vslogs.cab file to me (v-yicche@microsoft.com)
      Note: Please attach the link of this post in the mail.

    If you're running Windows 7:
    .NET Framework 3.5 with SP1 is shipped with it as one of OS component.
    For .NET Framework 3.5 with SP1, it includes .NET 2.0 with SP2 and .NET 3.0 with SP2 as prerequisite.
    This means, you have the .NET Framework 2.0 SP2, 3.0 SP2 and 3.5 SP1 plus a few post 3.5 SP1 bug fixes on Windows 7. They are OS components. .NET 3.0 SP2 and 3.5 SP1 can be added or removed via the Programs and Features control panel. Thus, we don't need to manually install them. You can try Verifictaion Tool to verify .NET Frameworks on your machine.
    If .Net Framework 2.0, 3.0 and 3.5 cannot be verified on your computer, you can try to follow the steps mentioned in the following blog to repair the .NET Framework 2.0, 3.0 and 3.5 on Windows 7.
    See: http://blogs.msdn.com/astebner/archive/2007/03/26/how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx (also apply for Windows 7)

    If the .NET Framework 3.5 is installed but TurboTax 2009 can fail to install because it thinks the .NET Framework is not installed, please check the following helpful blog:
    http://blogs.msdn.com/astebner/archive/2010/01/26/9953883.aspx
    (Please see the part "What to do if the above doesn’t help")

    Hope this helps! If you have any concern, please feel free to let me know.

    Best regards,
    Yichun Chen
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
    • Marked as answer by YiChun Chen Friday, April 9, 2010 2:29 AM
    Monday, April 5, 2010 9:59 AM
  • The error your getting is related to the WCF trying to write to this registry key.

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Eventlog\Security\ServiceModel 3.0.0.0

    Delete this key and re-run the 3.5 SP .net installer and it should run without issue and complete sucessfully.

    Wednesday, August 18, 2010 4:31 PM
  • the bigger question is, WHY SHOULD WE HAVE TO DO ALL THIS ____!!?!?!?!

     

    why don't you IDIOTS at MS make GOOD SOFTWARE?

     

    .NET is the WORST system EVER.  10 different incompatable versions of .NET.  really?  REALLY?

     

    this is utterly ridiculous.  perhaps you MORONS should make .NET a SINGLE entity with *COMPATIBILITY*.

    Tuesday, September 7, 2010 2:19 AM