August 21, 2008 at 18:4210 hours of installing .Net Framework 3.0 and 3.5 on Windows XP Pro
The day before yesterday there was a need to install .Net Framework 3.0 so that the System.Workflow libraries appeared. Then he wondered “why get up twice” and decided to install 3.5 as well. I was surprised a lot, because I see this installation of Framework for the first time. I will not describe the whole process in paints, I just mention once again - 10 hours of installation. I re-read most of the forums found, all English-speaking and decided to share my experience in order to save time and nerves of my colleagues - you.
How can install Framework swear for an example and ease of search:
So, to install on you should have:
The first two conditions turned out to be quite enough, but I also learned a few tricks from the forum forums:
In some cases, installing 3.5 required the already installed SP1 on the 2 and 3 framework. Also, sometimes for a version of Windows Server 2003 it was necessary to remove IIS first, and for XP, remove IIS or stop the Windows World Wide Publishing service. It didn’t help me.
I recommend reinstalling all installed Framework. For uninstall, uninstall them first through "Add or Remove Programs", and then clean them with the Automated cleanup tool .
And with unsuccessful installations, see EventLog, it will tell a lot of interesting things.
Framework Links:
Microsoft .NET Framework 2.0 Redistributable Package
Microsoft .NET Framework 2.0 Service Pack 1 (x86)
Microsoft .NET Framework 3.0 Redistributable Package
Microsoft .NET Framework 3.0 Service Pack 1
Microsoft .NET Framework 3.5
Microsoft .NET Framework 3.5 Service Pack 1
UPD: Indeed, for many this process does not take more than 20 minutes, but it happens like this. Hope it helps someone.
How can install Framework swear for an example and ease of search:
Windows Communication Foundation: [2] Error: Installation failed for component Windows Communication Foundation. MSI returned error code 1603
Microsoft .NET Framework 3.0a: [2] Error: Installation failed for component Microsoft .NET Framework 3.0a. MSI returned error code 1603
Microsoft .NET Framework 3.5 'package': [2] Error: Installation failed for component Microsoft .NET Framework 3.5 'package'. MSI returned error code 1603
Microsoft .NET Framework 2.0a: [2] Error: Installation failed for component Microsoft .NET Framework 2.0a. MSI returned error code 1603
So, to install on you should have:
- Windows Installer 3.1 Redistributable (v2)
- rights (in my case, I had to give Full rights to Everyone user) to the registry branch HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ Eventlog \ Security \ ServiceModel 3.0.0.0
- fresh Framework 2.0
The first two conditions turned out to be quite enough, but I also learned a few tricks from the forum forums:
In some cases, installing 3.5 required the already installed SP1 on the 2 and 3 framework. Also, sometimes for a version of Windows Server 2003 it was necessary to remove IIS first, and for XP, remove IIS or stop the Windows World Wide Publishing service. It didn’t help me.
I recommend reinstalling all installed Framework. For uninstall, uninstall them first through "Add or Remove Programs", and then clean them with the Automated cleanup tool .
And with unsuccessful installations, see EventLog, it will tell a lot of interesting things.
Framework Links:
Microsoft .NET Framework 2.0 Redistributable Package
Microsoft .NET Framework 2.0 Service Pack 1 (x86)
Microsoft .NET Framework 3.0 Redistributable Package
Microsoft .NET Framework 3.0 Service Pack 1
Microsoft .NET Framework 3.5
Microsoft .NET Framework 3.5 Service Pack 1
UPD: Indeed, for many this process does not take more than 20 minutes, but it happens like this. Hope it helps someone.