Wednesday, September 17, 2008

Installation failed for component Microsoft .NET Framework 2.0SP1

I'm trying to install .NET 3.5 SP1 onto Server 2008 Enterprise and I'm getting this error:

Microsoft .NET Framework 2.0SP1 (x64) (CBS): [2] Error: Installation failed for component Microsoft .NET Framework 2.0SP1 (x64) (CBS). MSI returned error code 1

On inspection of the folders it appears that .NET 3.0 is already installed C:/Windows/Microsoft.NET/Framework/ here. Mystery still not solved...


  1. This blog has a fair amount of info about this error:

  2. Relevant part from the previously linked blog:
    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

  3. I tried this update: recommended on a forum which is the System Update Readiness Tool for Windows Server 2008 x64 Edition (KB947821) [August 2008] but when I ran it I got a message that said "The update does not apply to your system"

  4. I think that I've finally found the solution to my problem in this posting and I'm guessing that I have a checked build of Windows Server 2008 instead of a release build. I didn't even know that. Search and install again...

  5. SOLUTION: My last comment was indeed the answer to the problem. At the start of this exercise I didn't even know what a checked build was let alone that I had installed a checked build. (A checked build is a debug build of (in this case) the operating system.)
    My mistake was that I had installed the wrong version of Windows Server 2008 and when I reinstalled the correct version everything else worked very smoothly and all the other updates and installs went without a hitch.

  6. Just wanted to thank you for this. I've been banging my head against the wall for a couple weeks on this with no luck. Even wasted a support call with Microsoft. Your solution is accurate, I installed and was running a checked build of Server 2008. Thanks again.

  7. Great to hear that this helped someone!

  8. Thanks soo much for that hint !!!