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


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 (18)

  1. nwourms says:

    On a (somewhat) related note, I have been bashing my head trying to pass msi cmd line properties to the Visual Studio 2003 EA setup. I am using a MSDN DVD from a few years back to install it. I followed the directions you had in your related post, where you suggested using <code>D:setupsetup.exe /msipassthru=BEGIN"TRANSFORMS=C:foo.mst"END</code>, but the verbose msi log reported that setup.exe did not pass any parameters to msiexec.exe. I then tried to pre-emptively force the transform by adding the Transforms entry to the GUID in HKCRInstallerProducts{…} and that only made setup.exe angry and crap out. I suppose it was confused because I think it checks that key to see if VS2003 is installed. So, I’ve just broken down and hacked the msi, but I would *prefer* to do it the right way. Can you verify that the msipassthru switch exists in the VS2003 setup source code? I’ve been examining the strings in the dlls and setup.exe to see if I could find something, but that was fruitless. So I guess I want to know, is there a "section" or "parameter" in either the setup.sdb or unattended ini file which will allow me to pass command line parameters for msiexec.exe. If not, is there a "section" or"parameter" which will allow me to specify a tranform file for it to use? If I had the source, I’m sure I could figure it out myself. However, since the Suite Installer Toolkit source is not available or documented, I am reduced to asking here. Thanks in advance!

  2. astebner says:

    Hi Nwourms – Yes, the msipassthru switch should work for VS 2003 setup.  One thing to make sure is that you put a space after BEGIN" and another one before "END in your command line.  It would need to look something like this:

    <VS install path>setupsetup.exe /msipassthru=BEGIN" TRANSFORMS=c:foo.mst "END

    Do those extra spaces help allow this scenario to work on your system?

  3. Details about the .NET Framework 2.0 setup packaging Available command line switches for .NET Framework

  4. A while back, I posted a set of instructions that can be used to try to resolve .NET Framework installation

  5. A while back, I posted a list of instructions that can be used to enable Windows Installer verbose logging

  6. Recently, I heard from a customer who could not get the .NET Framework 2.0 SP1 to install correctly on

  7. Question: A while back, you posted a set of instructions that can be used to perform silent or unattended

  8. The .NET Framework 3.5 setup package is a chainer that installs multiple packages behind the scenes.&#160;

  9. I have heard from several customers in the past who have had issues installing hotfixes or updates for

  10. I have heard from a couple of customers who ran into issues installing the .NET Framework 3.5 and/or

  11. Recently, I was helping a colleague troubleshoot an installation error in the .NET Framework 3.5 SP1

  12. I was working with our product support team on an interesting .NET Framework 3.5 SP1 installation failure

  13. A while back, I wrote a blog post describing a specific error that can occur when trying to install the

  14. Acquiel says:

    Hi Aaron Stebner,

    Yesterday I installed .net framework 3.5 sp1 in my computer after i look at my computer that i have no net framework installed . in the end it fails . when i look at my control panel , add/remove programs i have net framework 2.0 installed . i dont know why . i read some articles on how to fix net frame work 3.5 sp1 . none of them works . i have this problem

    [08/02/12,21:58:38] XPSEPSC Installer: [2] Component XPSEPSC Installer returned an unexpected value.

    [08/02/12,21:58:39] WapUI: [2] DepCheck indicates XPSEPSC Installer is not installed.

    [08/02/12,22:01:43] XPSEPSC Installer: [2] Component XPSEPSC Installer returned an unexpected value.

    [08/02/12,22:01:44] WapUI: [2] DepCheck indicates XPSEPSC Installer is not installed.

    i already have XPSEPSC INSTALLER and i install it . and it didnt work . i download log collection tools . please help me on this one .

    I just dont want to uninstall net framework 2.0 yet without me letting you know my real problem .

    where can i post my vslogs.cab ?

  15. astebner says:

    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.

  16. balaji,pune says:

    in xp sp2 the Error: Installation failed for component Microsoft .NET Framework 2.0

    a. MSI returned error code 1603 occured.

    please give me solution

    i want  to install sql server 2005 my pc o.s. isxp sp2.

    immeditely,

    thank you.

    mob . 9766649577

  17. astebner says:

    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?