Aaron Stebner's WebLog

Thoughts about setup and deployment issues, WiX, XNA, the .NET Framework and Visual Studio

Visual Studio 2005 and .NET Framework 2.0 Setup Troubleshooting Guide

Visual Studio 2005 and .NET Framework 2.0 Setup Troubleshooting Guide

  • Comments 56

Where to get Visual Studio 2005 and the .NET Framework 2.0

Uninstalling previous beta versions of Visual Studio 2005, the .NET Framework 2.0 and SQL Express

Resolving problems encountered while uninstalling previous betas

Resolving problems that can be encountered while installing the final release of Visual Studio 2005 or the .NET Framework 2.0

Resolving package load failures after installing the final release of Visual Studio 2005

Resolving other problems that can be encountered after installing the final release of Visual Studio 2005 or the .NET Framework 2.0

Resolving problems encountered while installing Visual Studio 2005 SP1

How to get help if none of the above help


  • Aaron,

    I am having trouble installing the .NET Framework 2.0 with the Error: Microsoft .NET Framework 2.0 has encountered a problem during setup.  Setup did not complete correctly.

    Error Signature: EventType : visualstudio8setup     P1 : 183     P2 : 8.0.50727.42_rtm_x86ret
    P3 : msi     P4 : inst     P5 : f    
    P6 : ca_installassemblydef.3643236f_fc70_11d3_a536     P7 : -     P8 : 1603
    P9 : -     P10 : -    

    Error Report Contents:


    Once I get this error, the components of Visual Web Developer 2005 Express Edition does not try to install.  I have tried manually installing the package (downloading .ISO file, extracting the files and installing), I have updated my systems with all available updates.  I'm using Windows XP Professional Service Pack 2 with Windows Installer 3.1.  

    I have tried installing .NET separately and still get that same error.  Any ideas?
  • I just found this error in my dd_vsinstall80.txt:
    Microsoft .NET Framework 2.0: ***ERRORLOG EVENT*** : Error code 1603 for this component means "Fatal error during installation.

  • Hi Melissa - Error code 1603 is a generic failure error code that could be caused by a lot of possible issues.  Can you please search for %temp%\dd_netfx20msi*.txt and zip and send it to me at Aaron.Stebner (at) microsoft (dot) com so I can take a look and see if I can figure out the root cause?
  • Can anyone tell me , is this release version of products or beta??? I have a few big bugs with lost bindingsource, lost DataSource in bindingsource and so on.
    Microsoft Visual Studio 2005
    Version 8.0.50727.42  (RTM.050727-4200)
    All included languages has this number
  • Hi Ray - Version 50727.42 is the final released version number for Visual Studio 2005.  I encourage you to search for and report bugs that you find at http://lab.msdn.microsoft.com/productfeedback.
  • Thanks. But I asked one of my friend to check his version of product and found that mine versions are
    but his versions are:
    even if we both have same version of VS
    Version 8.0.50727.42 (RTM.050727-4200)
    I can not go to him and look because hi is not in my country :)
    And about report bugs. I sow one bug with lost DataSource property in BindingSource , but Microsoft says its already fixed in Final Release. Thats why I'm thinking that I have beta version :(
  • I found another very strange thing. Can anyone please check it ?
    Open installation DVD (or CD1) go to VS folder, find setup.ini. Open it (in notepad or in other text editors) and look at the begining of text for BannerName variable. In my installation there are
    Visual Studio&reg; 2005 Beta 2 Setup !!!
  • Hi Ray - It sounds to me like you have the beta 2 DVD and not the final release.  Where exactly did you see the version 8.0.50727.42 version information that you mentioned in your previous comment?  If the setup files that you looked at refer to beta 2, then that is the beta 2 DVD....
  • hi guys,
    im using VS 2005, and having serious problems creating the msi to install my windowsService.....
    Even in simple drivers i create the msi is "supposedly" installes the service, but the service does not appear in he services list.
    in VS 2003 we had no problem... what's going on? how do we get over this?
  • Hi Eitan - I do not have any experience installing services using a Visual Studio setup/deployment project, so I'm afraid I won't be very helpful here.  I would suggest taking a look at the documentation, starting at http://msdn2.microsoft.com/en-us/library/ybshs20f.aspx.  If there isn't anything useful there, I would suggest looking on the MSDN Forums (http://forums.microsoft.com) or logging a bug on the Product Feedback Site (http://lab.msdn.microsoft.com/productfeedback) to see if you can find any additional help there...
  • 2 astebner
    Hi. I've posted info from About box of VS. Also I've asked my frieds to check that file and hi found same text
    Visual Studio&reg; 2005 Beta 2 Setup !!!
    Thats strange! At this moment I have only two big problems with C# designer.
    1. I have big dialog windows without about 100 of editors, all binded to datasourse. If I open DataSet designer and change something, even just moving datatableadapter, by bindingsource on dialog box just disaapeared!
    2. In another project same situation but bindingsource lost DataSource property!
  • Hi Ray - The C# designer issues that you describe are outside of my areas of expertise.  I suggest taking a look at the product feedback site (http://lab.msdn.microsoft.com/productfeedback) or the MSDN Forums (http://forums.microsoft.com) to see if there are any similar issues that might help you resolve these issues.
  • I've tried the process of running the preinstalls, and using an .mst file (created w/ setup.exe /createtransform).  It eliminates reboots, and allows me to pre-install all the prereqs.  But it will not install the x64 compilers/tools on x64 OS.  Is there something special that is needed for these tools??

  • Hi Perry - Are you referring to the x64 compilers/tools that appears as a checkable option in the VS installation tree?  If so, I believe that those tools are unchecked by default, so you need to make sure that you check them on in setup UI when you create your MST or INI file for unattended install.  Hopefully this helps...
  • RE (thanks in large part to beta testers who were willing to try out the early versions),

    What you mean is Crash dummys who mistakenly assumed that MSFT development is on a par w/ Oracle etal,  and were istead enlisted to test the stuff because Microsoft is unwilling or unable to. (to busy think up ways to complicate getting a connection string from a config file, i guess).
Page 2 of 4 (56 items) 1234
Leave a Comment
  • Please add 6 and 5 and type the answer here:
  • Post