Possible cause of 1935 error with HRESULT 0x8002802F
A while back, I posted an article describing causes of many types of 1935 errors that have been seen in the past. I wanted to talk about one specific type of 1935 error in a little more detail and provide information about a possible root cause that I did not describe in that previous article.
A 1935 error in an MSI-based installations code is a catch-all for most of the possible assembly installation errors. In order to diagnose the problem in more detail, it is usually necessary to look at the verbose MSI log file. In some cases, you will see an error like the following:
Error 1935. An error occurred during the installation of assembly '<myAssembly>'. Please refer to Help and Support for more information. HRESULT: 0x8002802F. assembly interface: , function: CreateAssemblyNameObject, component: {A7A9D92E-C67F-4E96-BB90-5A4147DAEF6B}
The key information needed to diagnose the exact root cause of a 1935 error is usually the HRESULT value listed in the verbose MSI log file.
The HRESULT value listed above is 0x8002802F (-2147319761), and it means "function not defined in specified DLL." There are a few possible root causes of this issue. The most common cause is that the file %windir%\system32\mscoree.dll is missing, corrupt or an incorrect version. In most cases, repairing the highest version of the .NET Framework on the system will correct any problems related to mscoree.dll and will resolve the problem if this is the case.
In a few less common cases, the file %windir%\system32\mscoree.dll is present, but registry values used by the .NET Framework to find and load specific versions of the .NET Framework are missing. The following values are required by mscoree.dll in order to load each version of the .NET Framework:
For the .NET Framework 2.0 (on an x86 version of Windows):
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework]
InstallRoot = C:\Windows\Microsoft.NET\Framework\
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\Policy\Upgrades]
2.0.50727 = 1.0.0-2.0.50727
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\Policy\v2.0]
50727 = 50727-50727
For the .NET Framework 2.0 (on an x64 version of Windows):
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework]
InstallRoot = C:\Windows\Microsoft.NET\Framework64\
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\Policy\Upgrades]
2.0.50727 = 1.0.0-2.0.50727
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\Policy\v2.0]
50727 = 50727-50727
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework]
InstallRoot = C:\Windows\Microsoft.NET\Framework\
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432NodeMicrosoft\.NETFramework\Policy\Upgrades]
2.0.50727 = 1.0.0-2.0.50727
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\Policy\v2.0]
50727 = 50727-50727
For the .NET Framework 1.1:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework]
InstallRoot = C:\Windows\Microsoft.NET\Framework\
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\Policy\Upgrades]
1.1.4322 = 1.0.0.0 - 1.1.4322
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\Policy\v1.1]
4322 = 3706-4322
For the .NET Framework 1.0:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework]
InstallRoot = C:\Windows\Microsoft.NET\Framework\
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\Policy\v1.0]
3705 = 3321-3705
If any of the above registry values are missing on your system, you will need to manually add them in order to resolve 1935 errors with HRESULT value 0x8002802F. Note that the InstallRoot value must be set to the exact location of the %windir% folder on your system, so you may need to adjust that value from the one listed above if your %windir% is not located at c:\Windows.
<update date="2/4/2008"> One of the values for the .NET Framework 1.0 was incorrect, so I fixed it </update>
<update date="12/16/2009"> Added 64-bit registry information for the .NET Framework 2.0. </update>
Comments
Anonymous
June 13, 2007
The comment has been removedAnonymous
June 17, 2008
When I am attempting to investigate a setup-related failure, I typically end up looking at verbose logAnonymous
June 29, 2008
The comment has been removedAnonymous
July 01, 2008
The comment has been removedAnonymous
May 29, 2009
Question: I tried to install the .NET Framework 4 beta 1 and Visual Studio 2010 beta 1 on my WindowsAnonymous
July 06, 2009
The comment has been removedAnonymous
August 26, 2010
The comment has been removedAnonymous
August 26, 2010
The comment has been removedAnonymous
October 30, 2010
HELP IK OOK ZIT VAST MET ERROR 2908 EN VIND GEEN WEG ER UIT ????Anonymous
November 01, 2010
Hi Jack - What version of Windows are you seeing this error on, what is the exact HRESULT value, and what product are you trying to install when you see this error? It often helps to repair/re-install the .NET Framework to solve this type of error, but this may or may not help in your scenario depending on what version of Windows you're using and what the exact HRESULT value is for your error.Anonymous
July 16, 2012
Hi, I was also getting same error, the HRESULT :0x8002802F, I have replaced my mscoree.dll and problem get solved. Previous version of C:windowssystem32mscoree.dll file was 2.* something. I have downloaded newer version 4.* at www.dll-files.com/.../dll-files.shtml Please try it before going for any other options. Thanks.Anonymous
August 03, 2012
How to set InstallRoot values ? What do I need to do ? I'm awful with those kind of manipulationsAnonymous
August 04, 2012
The comment has been removedAnonymous
December 06, 2012
The comment has been removedAnonymous
June 30, 2013
The comment has been removedAnonymous
June 30, 2013
Hi Joao - I'd first suggest trying to repair/re-install the .NET Framework to see if that will resolve this error. If that doesn't help, then I'd suggest trying to manually set the InstallRoot registry key using regedit.exe.Anonymous
July 19, 2013
Aeron I did what you asked me, agr'm having another "little problem" when I try to open a file folder v2.0.50727 appears this error: To run this application, you must first install one of the following versions of the. Net framework: v2.0.50727 Contact the application publisher for instructions about obtaining the appropriate version of the. Net framework. Hey, I also have problem when I install the. NET Framework 1.1: Microsoft. Net Framework 1.1 setup has ended prematurely.If this presists, please contact Product Support Thank Aeron, excuse the inconvenience.Anonymous
July 19, 2013
Yes, just to point out I already delete the mscoree.dllAnonymous
July 23, 2013
Hi Joao - What version of Windows is on your computer? It might help to install the .NET Framework 4 or 4.5 before trying to install the .NET Framework 1.1, 2.0, 3.0 or 3.5. It might also help to try to use the repair/removal/re-install steps at blogs.msdn.com/.../8108332.aspx.Anonymous
February 07, 2014
The comment has been removedAnonymous
February 07, 2014
the application failed initailize properly (0xc0000135)click on ok to terminate the applicationAnonymous
February 07, 2014
Hi hardik patel - There are a lot of possible causes of 1935/2908 errors. I would need to see your full setup log files in order to narrow down the root cause further. Can you please zip up your log files, upload them to a file server (such as http://skydrive.live.com) and then reply back here and post a link I can use to download your log files and take a closer look?Anonymous
February 07, 2014
Hi khan - I will need more information about your scenario in order to try to help. What version of Windows are you running, what version(s) of the .NET Framework do you have installed, and what application are you trying to run when you see that error? Also, do you see that error only for one application, or do you see it for all .NET applications that you try to run on your computer?Anonymous
February 07, 2014
my computer all application this error my computer windows 2002 sp 2 so plz help meAnonymous
February 07, 2014
Hi khan - There isn't a version of Windows called Windows 2002. Do you mean Windows XP? If so, then I'd suggest trying the steps and tools described at blogs.msdn.com/.../8108332.aspx to full remove and then re-install all versions of the .NET Framework to see if that helps resolve this error.Anonymous
September 16, 2015
Hi there all, Microsoft Office 2010 is refusing to reinstall itself giving the message 'ERROR 1935' then lots of numbers and letters then 'HRESULT 0x8002802f, Set up failed, Rolling back Changes'. This after hours. Following MS troubleshooting tips I have reinstalled what I believe to be the latest Microsoft.Net Framework 4.5.2, but I don't see the Microsoft.Net Framework Client Profile and the message I receive when I have subsequently tried to download Client Profile is that I already have this or better. I run Windows 7 on an Acer Aspire 1 with 4 GB DDR8 memory. Help me reinstall all my paid for MS Office 2010 stuff please. I have the PKC here but every time the download fails. I already have download.microsoft.com/.../dotNetFx40_Client_x86_x64.exe downloadedAnonymous
September 20, 2015
Hi John Overton - Can you please double-check that the .NET Framework 2.0 registry values listed at the top of this blog post are present on your PC? If they're not, I'd suggest manually adding them to your registry using regedit.exe, rebooting, and trying to install Office again. If the registry keys are present and you're still seeing a 1935 error with HRESULT 0x8002802F, then you may need to repair Windows to fix this issue.Anonymous
May 10, 2016
Thanks a lot. Event Viewer, Server Manager, SharePoint workflow all stopped functioning after an upgrade to Windows 2008. A single missing .Net Framework 2.0.50727 registry key was the culprit.