Partilhar via

Where to find .NET Framework 2.0 SP1, 2.0 SP2, 3.0 SP1, 3.0 SP2, 3.5 and 3.5 SP1 setup log files

  • Artigo

A while back, I posted a list of possible log files for .NET Framework 3.5 and Visual Studio 2008 setup.  Since then, I've realized that there are some sets of log files missing from that list, so I decided to create a separate blog post with information about setup log files that are specific to the .NET Framework 3.5 family of products.  This family includes the following:

  • .NET Framework 2.0 SP1 and SP2
  • .NET Framework 2.0 SP1 and SP2 language packs
  • .NET Framework 3.0 SP1 and SP2
  • .NET Framework 3.0 SP1 and SP2 language packs
  • .NET Framework 3.5 and 3.5 SP1
  • .NET Framework 3.5 and 3.5 SP1 language packs

The following is a list of log files that can be produced by all of the above setup packages.  In all of the cases below, the logs are created by default, and you do not need to specify any verbose logging settings or registry values to cause the logs to be produced.  Also, you can find the %temp% directory by clicking on the Windows start menu, typing %temp% and pressing Enter.

.NET Framework 2.0 SP1 and SP2 setup log files

The following is a complete list of log files that can be produced during .NET Framework 2.0 SP1 and SP2 setup.  This list may vary depending on what OS you are installing on, what processor architecture, and what prerequisite components were already installed on the system prior to running .NET Framework 2.0 SP1 and SP2 setup.

Logs produced by the .NET Framework 2.0 SP1 and SP2 setup wrapper:

  • %temp%\dd_dotnetfx20install*.txt
  • %temp%\dd_dotnetfx20error*.txt
  • %temp%\dd_depcheck_netfx20*.txt

Logs produced by the packages chained during .NET Framework 2.0 SP1 and SP2 setup:

  • .NET Framework 2.0 SP1 and SP2 verbose MSI log - %temp%\dd_net_framework20*.txt
  • .NET Framework 2.0 SP1 and SP2 language pack verbose MSI log - %temp%\dd_NET_Framework*20*LP*.txt

.NET Framework 3.0 SP1 and SP2 setup log files

The following is a complete list of log files that can be produced during .NET Framework 3.0 SP1 and SP2 setup.  This list may vary depending on what OS you are installing on, what processor architecture, and what prerequisite components were already installed on the system prior to running .NET Framework 3.0 SP1 and SP2 setup.

Logs produced by the .NET Framework 3.0 SP1 and SP2 setup wrapper:

  • %temp%\dd_dotnetfx30install*.txt
  • %temp%\dd_dotnetfx30error*.txt
  • %temp%\dd_depcheck_netfx30*.txt

Logs produced by the packages chained during .NET Framework 3.0 SP1 and SP2 setup:

  • RGB Rasterizer - %temp%\dd_RGB9Rast_*.txt
  • MSXML 6.0 - %temp%\dd_msxml6_*.txt
  • WIC - %temp%\dd_wic*.txt
  • .NET Framework 2.0 SP1 and SP2 verbose MSI log - %temp%\dd_net_framework20*.txt
  • .NET Framework 2.0 SP1 and SP2 language pack verbose MSI log - %temp%\dd_NET_Framework*20*LP*.txt
  • .NET Framework 3.0 SP1 and SP2 verbose MSI log - %temp%\dd_net_framework30*.txt
  • .NET Framework 3.0 SP1 and SP2 ServiceModelReg.exe custom action - %temp%\dd_wcf_retCA*.txt
  • .NET Framework 3.0 SP1 and SP2 language pack verbose MSI log - %temp%\dd_NET_Framework*30*LP*.txt

.NET Framework 3.5 and 3.5 SP1 setup log files

The following is a complete list of log files that can be produced during .NET Framework 3.5 and 3.5 SP1 setup.  This list may vary depending on what OS you are installing on, what processor architecture, and what prerequisite components were already installed on the system prior to running .NET Framework 3.5 and 3.5 SP1 setup.

Logs produced by the .NET Framework 3.5 and 3.5 SP1 setup wrapper:

  • %temp%\dd_dotnetfx35install*.txt
  • %temp%\dd_dotnetfx35error*.txt
  • %temp%\dd_depcheck_netfx_*.txt

Logs produced by the packages chained during .NET Framework 3.5 and 3.5 SP1 setup:

  • RGB Rasterizer - %temp%\dd_RGB9Rast_*.txt
  • MSXML 6.0 - %temp%\dd_msxml6_*.txt
  • WIC - %temp%\dd_wic*.txt
  • .NET Framework 2.0 SP1 and SP2 verbose MSI log - %temp%\dd_net_framework20*.txt
  • .NET Framework 2.0 SP1 and SP2 language pack verbose MSI log - %temp%\dd_NET_Framework*20*LP*.txt
  • .NET Framework 3.0 SP1 and SP2 verbose MSI log - %temp%\dd_net_framework30*.txt
  • .NET Framework 3.0 SP1 and SP2 ServiceModelReg.exe custom action - %temp%\dd_wcf_retCA*.txt
  • .NET Framework 3.5 and 3.5 SP1 verbose MSI log - %temp%\dd_net_framework35*.txt
  • .NET Framework 3.5 and 3.5 SP1 language pack verbose MSI log - %temp%\dd_NET_Framework35_LangPack*.txt

Setup log files for other .NET Framework products

I have written separate blog posts about log file locations for other .NET Framework products not listed above.  Here they are for your reference in case you need them:

<update date="8/24/2008"> Updated list of .NET Framework 3.0 SP1 log files </update>

<update date="4/13/2009"> Clarified that the list of logs in this post is applicable to 2.0 SP2, 3.0 SP2 and 3.5 SP1 as well. </update>

Comments

  • Anonymous
    May 15, 2008
    The comment has been removed

  • Anonymous
    May 20, 2008
    The comment has been removed

  • Anonymous
    June 02, 2008
    The comment has been removed

  • Anonymous
    June 14, 2008
    A while back, I posted a set of instructions that can be used to try to resolve .NET Framework installation

  • Anonymous
    June 24, 2008
    A while back, I posted a list of instructions that can be used to enable Windows Installer verbose logging

  • Anonymous
    June 24, 2008
    Recently, I heard from a customer who could not get the .NET Framework 2.0 SP1 to install correctly on

  • Anonymous
    June 26, 2008
    Question: A while back, you posted a set of instructions that can be used to perform silent or unattended

  • Anonymous
    July 13, 2008
    The .NET Framework 3.5 setup package is a chainer that installs multiple packages behind the scenes.&#160;

  • Anonymous
    July 28, 2008
    I have heard from several customers in the past who have had issues installing hotfixes or updates for

  • Anonymous
    August 25, 2008
    I have heard from a couple of customers who ran into issues installing the .NET Framework 3.5 and/or

  • Anonymous
    September 10, 2008
    Recently, I was helping a colleague troubleshoot an installation error in the .NET Framework 3.5 SP1

  • Anonymous
    January 18, 2009
    PingBack from http://www.keyongtech.com/3989794-net-framework-v2-install-corrupts/2

  • Anonymous
    March 06, 2009
    I was working with our product support team on an interesting .NET Framework 3.5 SP1 installation failure

  • Anonymous
    March 12, 2009
    A while back, I wrote a blog post describing a specific error that can occur when trying to install the

  • Anonymous
    August 01, 2012
    The comment has been removed

  • Anonymous
    August 03, 2012
    Hi Acquiel - Can you please use the tool described at blogs.msdn.com/.../6458047.aspx to collect all of your 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 provide a link that I can use to download your log files and take a closer look? Also, I noticed that you posted the same comment on several different blog posts.  In the future, you only need to post a comment on one blog post, and I'll see it and respond to it.

  • Anonymous
    November 04, 2013
    The comment has been removed

  • Anonymous
    November 05, 2013
    Hi balaji,pune - Error 1603 is a generic error code that means setup failed, but it doesn't give any information about why it failed. Can you please use the tool described at blogs.msdn.com/.../6458047.aspx to collect all of your 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 provide a link that I can use to download your log files and take a closer look?