Aaron Stebner's WebLog

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

VS 2005 setup fails with 1935 or 2908 error

VS 2005 setup fails with 1935 or 2908 error

  • Comments 32
I have heard from a couple of customers who have tried to install the final release of Visual Studio 2005 or one of the Express Editions and have gotten 1935 (or 2908) errors with HRESULT values of 0x8002802F, and then setup failed and rolled back.  The cases I have seen so far have had the same root cause as the problem I described in this previous blog post.

In the cases I have seen for this problem in the final release of VS 2005, the machines had the .NET Framework 1.1 installed, and the version of %windir%\system32\mscoree.dll was 1.1.4322.573 or 1.1.4322.2032.  When VS setup tried to install assemblies to the GAC, it failed because Windows Installer tried to call into a 2.0-specific API from mscoree.dll (needed because there are new processor architecture attributes on VS 2005 assemblies that only 2.0 knows about).  Since the version of mscoree.dll on the system was 1.1, these API calls failed.  This issue is described in more detail in my 1935 troubleshooting guide if you are interested.

The underlying problem was that VS setup detected that the .NET Framework 2.0 was already installed and skipped that prerequisite step.  However, the machine did not actually have the .NET Framework 2.0 installed, but instead only had the registry key that VS setup uses to detect whether or not the .NET Framework 2.0 is installed.  I found that the machines had the following orphaned registry key/value that VS setup uses to determine that .NET Framework 2.0 was already installed:

  • Key name: HKLM\Software\Microsoft\NET Framework Setup\NDP\v2.0.50727
  • Value name: MSI
  • Data type: REG_DWORD
  • Value data: 1

Once the customers deleted this key/value and re-ran VS 2005 setup, it detected that it needed to install the .NET Framework 2.0, and after installing that, VS setup worked perfectly.

As a side note if you're really interested, you could use some of the setup reverse engineering tricks that I describe here to determine the exact location of this registry key.  In this case, the key/value are listed in the [gencomp18] section of the file named baseline.dat in the setup subdirectory of the VS 2005 DVD or in the self-extracting setup package for the Express Editions.


  • Well..thanks anyway I tried hard for about 6-7 hours to install Visual Studio. İ sepped towards many but at last I opened regedit and teleted the key of HKLM\Software\Microsoft\NET Framework Setup\NDP\ v2.0XXXXX and it assumed that there hasnt been a net framework package at teh system and started to install that first and now it is just about to finish.
    the error was about the procedurecallentrypoint at mscoree.dll
  • ...and what if .net framework 2.0 is successfully installed and you still get the 2908 error (installing Document Explorer 2005)?
  • Hi Ilya - can you please locate any files named %temp%\dd_dexplore80msi*.txt on your system and zip and send them to me so I can take a look and see if I can figure out why you are hitting this error? You can send it to aaronste@microsoft.com.
  • I've been trying to install Visual Basic 2005 Express Edition on my machine, but i got the followin error 0xc000000d when it is starting the installation
  • Hi Sarah - Do you see any log files being created in %temp% when this happens on your system?  You can find a list of the possible log files at http://blogs.msdn.com/astebner/articles/447012.aspx.
  • A while ago, I posted an item regarding a possible cause and resolution for 1935 or 2908 errors during...
  • I have a problem, I launched Visual Studio 2005 one day with one big problem: it gave me a message box saying "Unknown Error" - How bad is that? So i uninstalled everything, and Document Explorer 2005 and VS.NET 2005 have been giving me those errors during install and uninstall and they simply do not work.
  • Hi Tom - I have heard of this "unknown error" message before but I'm not sure I know of a single root cause that you could check for on your system.  You may want to search for suggestions on the MSDN Forums (http://forums.microsoft.com).  In the worst case, you could try to use the steps listed at http://blogs.msdn.com/astebner/archive/2005/12/16/504906.aspx to manually clean off all of VS 2005 and attempt to reinstall it and see if that helps.

  • Okay ill admit it doesnt take much but im confused again. okay si im installing VB express and the .net framwork comes with the package, well it doesnt install with the errors 2908 several of them. Im a n00beeeeee in all thing registry so really i sont want to go pocking round i know enough not to do that he he. Okay so could you email me like the possible problems Hughesaar@gmail.com. please help its driving me mad............
  • Hi AaronHughes - Can you please try to use the .NET Framework 2.0 cleanup tool described at http://blogs.msdn.com/astebner/archive/2006/05/30/611355.aspx and then try to install VB 2005 Express again and see if that helps solve this issue on your system?
  • PingBack from http://www.johannes-rest.de/modules/wordpress/?p=17

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

  • hi.. i tryied to inst. VS2005/2008 .net2.0/3.5

    but everytime i get the 1935 because of .net2.0

    tryied the most of tips of troubleshouting..

    nothing works.. please help.. thx

    Produkt: Microsoft Visual C++ 2005 Redistributable -- Error 1935.Während der Installation der Assembly "Microsoft.VC80.ATL,type="win32",version="8.0.50727.762",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86"" ist ein Fehler aufgetreten. Weitere Informationen finden Sie unter Hilfe und Support. HRESULT: 0x8007054F, Assemblyschnittstelle: IAssemblyCacheItem, Funktion: Commit, Komponente: {97F81AF1-0E47-DC99-A01F-C8B3B9A1E18E}

  • Hi JimSelf - I'm sorry for the hassle that this issue is causing for you.  This error is coming from a Win32 assembly, not a .NET assembly, so I'm not sure this is related to the .NET Framework 2.0.  Unfortunately, the error code 0x8007054F is a generic error that means "an internal error occurred."

    If this is a Windows Vista system, this type of error will result in a more detailed error message being logged to the file c:\windows\logs\cbs\cbs.log.  It might help to search for this error code in this cbs.log file and see if it helps narrow down the root cause further.

  • <code>MSI (s) (2C:D0) [16:50:38:558]: Executing op: AssemblyCopy(SourceName=z9qi6zyr.zqi|x86_Microsoft.VC80.OpenMP_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_6c18549a.manifest,SourceCabKey=ul_manifest.1E507087_0819_45E0_FF1F_C8B3B9A1E18E,DestName=x86_Microsoft.VC80.OpenMP_1fc8b3b9a1e18e3b_8.0.50727.762_x-ww_6c18549a.manifest,Attributes=16384,FileSize=468,PerTick=32768,,VerifyMedia=1,ElevateFlags=4,,,,ComponentId={1E507087-0819-45E0-A01F-C8B3B9A1E18E},IsManifest=1,,,AssemblyMode=0,)

    MSI (s) (2C:D0) [16:50:38:558]: Assembly Error:The system cannot find the path specified.</code>

    This happens on vista sp1 machine with all relevant updates and office 2007, and i really hate the idea of reinstalling. Any advice, 10x?

Page 1 of 3 (32 items) 123
Leave a Comment
  • Please add 8 and 5 and type the answer here:
  • Post