<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Blue Sphere Knowledge Base</title><description>Blue Sphere Knowledge Base RSS 2.0 Feed</description><link>http://kb.bluesphereqa.com/</link><webMaster>support@bluesphereinc.com</webMaster><lastBuildDate>Thu, 09 Sep 2010 01:24:36 GMT</lastBuildDate><ttl>20</ttl><generator>Blue Sphere Knowledge Base</generator><item><title>.Net Framework 3.0/3.5 Installation Failure</title><link>http://kb.bluesphereqa.com/article.aspx?id=10044</link><description>&lt;B&gt;Abstract:&lt;/B&gt; &lt;P&gt;I came across a very tricky to find installation problem on my laptop when attempting to install the .Net Framework 3.5.  In the end, after going down many wrong roads that looked very right, it turned out to be a Registry Key deep in the registry that had permissions incorrectly assigned to the ASP.NET user and only the ASP.NET user.&lt;/P&gt;&lt;P&gt;The .Net Framework 3.5 installation would crash, resulting in an error log file containing the following:&lt;/P&gt;&lt;P&gt;------------------------------------------&lt;BR&gt;[02/17/08,09:06:00] Microsoft .NET Framework 3.0a: [2] Error: Installation failed for component Microsoft .NET Framework 3.0a. MSI returned error code 1603&lt;BR&gt;[02/17/08,09:07:07] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0a is not installed.&lt;BR&gt;------------------------------------------&lt;/P&gt;&lt;P&gt;Running the .Net Framework 3.0 installation would also crash, resulting in the following error:&lt;/P&gt;&lt;P&gt;------------------------------------------&lt;BR&gt;[02/17/08,09:58:38] Windows Communication Foundation: [2] Error: Installation failed for component Windows Communication Foundation. MSI returned error code 1603&lt;BR&gt;[02/17/08,09:59:06] WapUI: [2] DepCheck indicates Windows Communication Foundation is not installed.&lt;BR&gt;[02/17/08,09:59:06] WapUI: [2] DepCheck indicates Microsoft .NET Framework 3.0 was not attempted to be installed.&lt;BR&gt;------------------------------------------&lt;/P&gt;&lt;P&gt;&lt;BR&gt;To find the problem, after many failled attempts and uninstalling/reinstalling many different things, I found instructions on how to create a Windows Installer verbose logfile, then traced through it to find the exact place the installation was failing.&lt;/P&gt;&lt;P&gt;First thing need was to set the Windows Installer into verbose mode, by executing the following two commands from the command prompt to get the proper registry entries in place:&lt;/P&gt;&lt;P&gt;------------------------------------------&lt;BR&gt;reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer" /v Debug /t REG_DWORD /d 7 /f&lt;</description><pubDate>Mon, 18 Feb 2008 08:48:00 GMT</pubDate><dc:creator>Clayton Osborn</dc:creator></item></channel></rss>