Troubleshooting 1935 and 2908 errors during installation

Article
11/10/2004

Hey all, first off I want to apologize for not posting anything in a couple of weeks. I have had a couple of mini-vacations and been wrapped up with some other stuff, but I'm back now! I've been working with some Product Support folks I know to turn some documents I wrote for internal troubleshooting into knowledge base articles, and I decided that I wanted to go ahead and post some of the information here so it would be available sooner rather than later. The first installment is some detailed information about the dreaded 1935 (or 2908) error that sometimes happens when trying to install the .NET Framework or other MSI-based products that install managed assemblies to the GAC. This is a long post, but hopefully with some useful info. Let me know if you see any scenarios not covered by this information or have any questions....

1935 Errors in Setup

Abstract

The following document describes causes of 1935 errors during .NET Framework, J# redistributable package, language pack, or Visual Studio setup. It also explains how to diagnose the root cause of a 1935 error and workaround or fix the error.

Introduction

A 1935 error is one of the most common problems that can prevent a user from being able to install the .NET Framework, J# redistributable package, Visual Studio or any other application that uses the Windows Installer MSIAssembly and MSIAssemblyName tables to install assemblies.

In general, this error means that Windows Installer encountered an error while trying to install assemblies to the Global Assembly Cache (GAC) or the Win32 GAC (WinSxS). This error is considered fatal and causes setup to fail and initiate rollback.

If the setup is run in UI mode, the user will see a message box indicating that a 1935 error occurred, and it will list the HRESULT and the Windows Installer component GUID of the assembly that caused the error. If the setup is run in silent mode, the user will see no visible error. In both cases, more detailed information about the error can be found in the Windows Installer verbose log file.

Affected Products

· .NET Framework 1.0

· .NET Framework 1.1

· .NET Framework 1.1 language packs

· Visual J# .NET redistributable 1.1

· Visual J# .NET redistributable 1.1 language packs

· Visual Studio .NET 2002 (all versions)

· Visual Studio .NET 2003 (all versions)

Finding log information for 1935 errors that occur during setup

Where to find the log files

In order to diagnose the cause of a 1935 error, it is first necessary to locate information in the Windows Installer verbose log. If the error occurred during Visual Studio setup or during the .NET Framework or J# redistributable setups that are run as a part of Visual Studio Prerequisites (or Windows Component Update) setup, verbose logging is enabled by default. The log files vsmsilog*.txt, netfx.log, or jsredistmsi.log in %temp% will provide the necessary information, depending on which product’s setup failed.

If the error occurs during standalone setup for the .NET Framework, .NET Framework SDK or J# redistributable package setup, it will be necessary to rerun the failing setup with an extra command line parameter to enable Windows Installer verbose logging in order to produce a log file with the necessary information to debug the failure. To enable verbose logging, rerun the setup with the following command line syntax:

Product	Command line syntax	Log file location
.NET Framework	dotnetfx.exe /c:”install.exe /l”	%temp%\netfx.log
.NET Framework SDK	setup.exe /c:”install.exe /l”	%temp%\netfxsdk.log
.NET Framework Language Pack	langpack.exe /c:”inst.exe /l”	%temp%\langpackmsi.log
J# Redistributable Package	vjredist.exe /c:”inst.exe /l”	%temp%\jsredistmsi.log
J# Redistributable Package Language Pack	Vjredist-LP.exe /c:”inst.exe /l”	%temp%\langpackmsi.log

Note: The log file location can be controlled by passing a full path after the /l switch to install.exe or inst.exe. The locations listed in the table are the default locations if no path is provided.

Where to find error information in the log file

To pinpoint the cause of a 1935 error, search for the string return value 3 in a verbose Windows Installer log file. This will show the exact point in which setup failed and initiated a rollback. The following is an example of the information written to a Windows Installer verbose log file in the case of a 1935 error:

Error 1935.An error occured during the installation of assembly component {7D4B5591-4C80-42BB-B0E5-F2C0CEE02C1A}. HRESULT: -2146234301. assembly interface: IAssemblyCacheItem, function: Commit, assembly name: Microsoft.Vsa.Vb.CodeDOMProcessor,Version="7.0.5000.0", PublicKeyToken="b03f5f7f11d50a3a", Culture="neutral",FileVersion="7.10.3052.4", ProcessorArchitecture="neutral"

In this example, the assembly named Microsoft.Vsa.Vb.CodeDOMProcessor.dll failed to install properly due to an error with HRESULT value -2146234301.

List of causes of 1935 errors and their HRESULT values

There are many different underlying causes of a 1935 error, each represented by a different HRESULT. Once you locate the information in the Windows Installer verbose log file indicating which assembly is causing the error and what the HRESULT of the error is, you can use the table below to determine more specific information about the cause:

Return type	Return code	HRESULT	Description of error
TYPE_E_DLLFUNCTIONNOTFOUND	0x8002802F	-2147319761	Function not defined in specified DLL
ERROR_ACCESS_DENIED	0x7FF8FFFB	-2147024891	Access is denied
COR_E_MODULE_HASH_CHECK_FAILED	0x80131039	-2146234311	The check of the module's hash failed
FUSION_E_REF_DEF_MISMATCH	0x80131040	-2146234304	The located assembly's manifest definition does not match the assembly reference
FUSION_E_INVALID_PRIVATE_ASM_LOCATION	0x80131041	-2146234303	The private assembly was located outside the app-base directory
FUSION_E_ASM_MODULE_MISSING	0x80131042	-2146234302	A module specified in the manifest was not found
FUSION_E_UNEXPECTED_MODULE_FOUND	0x80131043	-2146234301	Modules which are not in the manifest were streamed in
FUSION_E_PRIVATE_ASM_DISALLOWED	0x80131044	-2146234300	A strongly-named assembly is required
FUSION_E_SIGNATURE_CHECK_FAILED	0x80131045	-2146234299	The check of the signature failed
FUSION_E_DATABASE_ERROR	0x80131046	-2146234298	An unexpected error was encountered in the Assembly Cache database
FUSION_E_INVALID_NAME	0x80131047	-2146234297	The given assembly name or code-base is invalid
FUSION_E_CODE_DOWNLOAD_DISABLED	0x80131048	-2146234296	HTTP download of assemblies has been disabled for this app-domain
FUSION_E_UNINSTALL_DISALLOWED	0x80131049	-2146234295	Uninstall of given assembly is not allowed
FUSION_E_NGEN_DEPENDENCY_NOT_FOUND	0x80131050	-2146234288	One of the native image dependencies cannot be found
FUSION_E_NGEN_INDEX_CORRUPTED	0x80131051	-2146234287	ngen index corrupted

NOTE: The Windows Installer team created separate error codes for 3 of the above return types starting with the version that shipped with Windows Server 2003. The following are the new error codes and the return types they correspond to in Windows Server 2003 and in versions of Windows Installer greater than 2.0 (all other return types from the above table continue to be represented by error code 1935):

Error code	Return Type
1936	FUSION_E_PRIVATE_ASM_DISALLOWED
1937	FUSION_E_SIGNATURE_CHECK_FAILED
1938	FUSION_E_ASM_MODULE_MISSING

Resolving 1935 errors that occur during setup

Most of the above HRESULT values in the table of 1935 errors above indicate some kind of setup authoring problem, and they require that the MSI package or some of the files in the package be patched and repackaged. All return types that begin with FUSION fit into this category.

1935 errors with HRESULT -2147319761 (function not defined in specified dll)

The most common source of a 1935 error is HRESULT -2147319761 (which means that a function is not defined in specified DLL). This error is typically caused by a mismatch or incompatibility between the version of mscoree.dll in the Windows system directory and the version needed by the product being installed. Often this can occur if a user has a previous beta version or technology preview build of the .NET Framework installed on their machine (even if they then uninstall it).

There are several possible ways to workaround this type of 1935 error. The workarounds depend on the product being installed and the OS that the product is being installed on. Refer to the sections below for more details for the individual products.

.NET Framework

This workaround applies to all versions of the .NET Framework.

The following steps will fix most cases of a 1935 error with HRESULT -2147319761 on operating systems that do not contain the .NET Framework as part of the operating system (applies to Windows 98, Windows Me, Windows NT 4, Windows 2000, and Windows XP except as noted below):

Rename the file %windir%\system32\mscoree.dll (or %windir%\system\mscoree.dll on Windows 98 and Windows Me). Also, please take note of what the version of this file is to aid in tracking down why this error is occurring.
Delete the folder %windir%\system32\urttemp (or %windir%\system\urttemp on Windows 98 and Windows Me) if it exists.
Re-run the .NET Framework setup that failed originally.

Because the .NET Framework ships as part of the OS for Windows XP Tablet PC Edition, Windows XP Media Center Edition and Windows Server 2003, it is dangerous to delete mscoree.dll from the system directory because it can affect OS functionality. In some cases, it is impossible to delete this file because it is under system file protection. The following steps will fix most cases of a 1935 error with HRESULT -2147319761 on these OS types:

Rename the file %windir%\system32\mscoree.dll. Also, please take note of what the version of this file is to aid in tracking down why this error is occurring.
Extract the file mscoree.dll from netfx.cab in the i386 directory of your original OS installation media or network path.
Copy mscoree.dll from netfx.cab to %windir%\system32.
Re-run the .NET Framework setup that failed originally.

NOTE: This error should not ever be seen for .NET Framework v1.1 on Windows Server 2003 because .NET Framework v1.1 shipped as part of the operating system, and the Windows Installer package for this version should block if a user attempts to install it on this OS. This error should also not ever be seen for .NET Framework v1.0 on Windows XP Tablet PC or Media Center editions because .NET Framework v1.0 shipped as part of the OS.

J# Redistributable Package, Language Packs, and Visual Studio

In most cases, a 1935 error with HRESULT -2147319761 during installation of the J# redistributable package, .NET Framework or J# redistributable package languages packs, or Visual Studio will require a repair of the highest version of the .NET Framework currently installed on the machine.

If you have the .NET Framework installed via a Windows Installer MSI package, you can perform the following steps to repair the .NET Framework:

Rename the file %windir%\system32\mscoree.dll (or %windir%\system\mscoree.dll on Windows 98 and Windows Me). Also, please take note of what the version of this file is to aid in tracking down why this error is occurring.
Delete the folder %windir%\system32\urttemp (or %windir%\system\urttemp on Windows 98 and Windows ME) if it exists.
If you are trying to repair the .NET Framework v1.0, locate the file repair.htm in the folder %windir%\Microsoft.NET\Framework\v1.0.3705 and follow the instructions on that page.
If you are trying to repair the .NET Framework v1.1, locate the file repairRedist.htm in the folder %windir%\Microsoft.NET\Framework\v1.1.4322\1033 and follow the instructions on that page.
Rerun the setup that failed originally.

If you have the .NET Framework installed as part of the operating system and find that it needs to be repaired, you should first try the following steps:

Rename the file %windir%\system32\mscoree.dll. Also, please take note of what the version of this file is to aid in tracking down why this error is occurring.
Extract the file mscoree.dll from netfx.cab in the i386 directory of your original OS installation media or network path.
Copy mscoree.dll from netfx.cab to %windir%\system32.
Re-run the setup that failed originally.

If these steps fail, you may need to rerun OS setup to trigger a repair of the entire .NET Framework.

What to do if the above troubleshooting steps do not work

In some cases, the 1935 error with HRESULT -2147319761 can be caused by orphaned registry keys from a different version of the .NET Framework, and replacing mscoree.dll or repairing the .NET Framework will not fix the error. In these cases, try to look in the registry key HKLM\Software\Microsoft\.NETFramework and look for any sub-keys or values containing version numbers of previous builds of the .NET Framework. If any are present, rename or delete them, then try to rerun the previously failing setup.

In addition if you are trying to install the .NET Framework v1.0, delete the following registry keys and any sub-keys and values, if present:

· HKLM\Software\Microsoft\NET Framework Setup\Full

· HKLM\Software\Microsoft\NET Framework Setup\Product

NOTE: Be very careful when directly modifying the registry in this way, particularly on operating systems where the .NET Framework ships as part of the OS. It is always recommended to backup your registry prior to making direct modifications to it so that you can roll back to a known state.

If there are no orphaned registry keys or deleting orphaned keys did not fix the problem, it may be necessary to completely uninstall and reinstall the highest version of the .NET Framework on the machine. This can be done by locating the entry in the Add/Remove Programs control panel applet and choosing to uninstall, then reinstalling from the original source.

If uninstalling and reinstalling also does not work, it may be necessary to perform a manual removal of the highest version of the .NET Framework on the machine.

NOTE: Manual removal is not recommended and can be very dangerous if the .NET Framework shipped as part of the operating system. In these cases, it is recommended to repair the OS by rerunning OS setup.

Additional Information

· https://support.microsoft.com/default.aspx?scid=kb;en-us;308096

· https://support.microsoft.com/default.aspx?scid=kb;en-us;824643

· https://support.microsoft.com/default.aspx?scid=kb;en-us;830646

· https://support.microsoft.com/default.aspx?scid=kb;en-us;839547

· https://support.microsoft.com/default.aspx?scid=kb;en-us;872904

Comments

Anonymous
May 08, 2005
The comment has been removed
Anonymous
May 11, 2005
Thank you very much indeed! It is so nice to find a proffesional and responsible solution. I have been working for days trying to resolve this prolem. Have gone down many blind alleys and encountered many people with the same problem but nobody had any real solutions.

Thank you again. I sincerely appreciate your efforts and generosity.
Anonymous
May 16, 2005
The comment has been removed
Anonymous
May 22, 2005
Hi Matthew - Can you please try the steps listed at http://blogs.msdn.com/astebner/archive/2005/03/29/403575.aspx and send me the log file that is produced? Unfortunately, the log file snippet you posted does not contain enough information to determine the root cause, but the steps at my other blog post should create a verbose log that will help us figure this out.
Anonymous
June 16, 2005
I have heard from a few people (including this customer comment on a previous blog post and a fellow...
Anonymous
July 12, 2005
error 1935 microsoft.msxml2,publickeytoken="6bd6b9abf345378f,version="4.1.0.0",type="win32",processorArchitecture="x86"
Anonymous
July 12, 2005
Hi John - can you please try to use the steps listed at http://blogs.msdn.com/astebner/archive/2005/03/29/403575.aspx to gather a verbose log of this setup failure. The snippet of the error message that you list is not enough to allow us to figure out the root cause. If you can gather the logs go ahead and send them to me at aaronste (at) microsoft (dot) com and I can take a look.
Anonymous
July 16, 2005
'SoapSudsCode,Version="1.0.5000.0",PublicKeyToken="b03f5f7f11d50a3a",Culture="neutral",FileVersion="1.1.4322.573"' HRESULT 0x80070003. This HRESULT isnt mentioned in your post. I am currently doing another (going to fail) setup with the verbose mode as you mentioned in the other post. Meanwhile you could perhaps look into this thing and deduce what might be the problem here.

Thanks in advance
Anonymous
July 18, 2005
Hi uXuf - the HRESULT value 0x80070003 means "the system cannot find the path specified". In many cases I have seen errors with this HRESULT have the same root causes as errors with HRESULT 0x80070002 ("the system cannot find the file specified"). So can you please try to use the troubleshooting steps at http://blogs.msdn.com/astebner/archive/2005/02/01/364375.aspx and see if they help you get past this error? If not, please contact me at aaronste (at) microsoft (dot) com and send your verbose logs and we can dig into it more deeply.

Hope this helps...
Anonymous
July 18, 2005
Ever since I published my blog post describing 1935 errors in more detail, I have been contacted by customers...
Anonymous
July 19, 2005
The comment has been removed
Anonymous
August 04, 2005
The comment has been removed
Anonymous
August 04, 2005
Hi Trevor - can you please use the steps listed at http://blogs.msdn.com/astebner/archive/2005/03/29/403575.aspx to gather the verbose setup log file and then send it to me at aaronste (at) microsoft (dot) com and I will take a look and see if I can figure out how to fix this issue on your computer?
Anonymous
August 16, 2005
I was contacted by a customer this week who could not install the .NET Framework 1.1 due to a 1935 error...
Anonymous
August 16, 2005
I was contacted by a customer this week who could not install the .NET Framework 1.1 due to a 1935 error...
Anonymous
October 07, 2005
The comment has been removed
Anonymous
November 06, 2005
Hey,

I was having trouble installing a sitebuilder because of that 1935 error. I am a total novice at the computer and I probably shouldn't have been messing around with technical stuff. I have to admit though I followed what you said to the T and works like a champ. Genius you are I tell you. Thanks for that advice. Save me probably huge dollars taking it downtown.

Darrell
Anonymous
December 14, 2005
The comment has been removed
Anonymous
February 11, 2006
Thanks a lot for this perfect article - this helped me solving my installation problem with Visual Studio 2003 and .NET Framwork.

... and I will pay the second beer :-)
Anonymous
February 17, 2006
Installed .net version 2 and all worked using new mscoree.dll
Thanks
Anonymous
February 17, 2006
i need help

Fehler 1935.An error occurred during the installation of assembly
`Microsoft_VsaVb,Version="7.0.5000.0",PublicKey Token="b03f5f7f11d50a3a",Cultire="neutral",FileVersion="7.10.3052.4".
Anonymous
February 17, 2006
Thanks! Making the changes you suggested for WinXP (renaming mscoree.dll and removing urttemp directory) did the job.

Thanks thanks thanks!
Anonymous
February 18, 2006
Hi Marco - There is not enough information in the snippet of the error message that you included in your comment to figure out what the root cause is. Can you open up %temp%vsmsilog*.txt and search for "return value 3" and then find the HRESULT value for this error code? That will help us figure out the best next step to take to solve this.
Anonymous
February 19, 2006
I find this here
[02/19/06,14:34:40] Starting Install.exe
[02/19/06,14:34:40] Parsing switches from commandline: C:DOKUME~1SEEHOL~1LOKALE~1TempIXP000.TMPInstall.exe
[02/19/06,14:34:40] SourceDir: C:DOKUME~1SEEHOL~1LOKALE~1TempIXP000.TMP
[02/19/06,14:34:40] Install started
[02/19/06,14:34:40] Checking system requirements
[02/19/06,14:34:40] OS: Win 2k
[02/19/06,14:34:40] Ver:
[02/19/06,14:34:40] SP: Service Pack 4
[02/19/06,14:34:40] Checking Internet Explorer Version
[02/19/06,14:34:40] Looking for 5.0.2919.6307
[02/19/06,14:34:40] Found Internet Explorer Version: 6.0.2800.1106
[02/19/06,14:34:40] Internet Explorer Version is OK...
[02/19/06,14:34:40] System meets minimum requirements
[02/19/06,14:34:40] Checking Windows Installer version...
[02/19/06,14:34:40] Trying to load msi.dll
[02/19/06,14:34:40] Loading: C:WINNTsystem32\msi.dll
[02/19/06,14:34:40] msi.dll loaded ok
[02/19/06,14:34:40] Looking for: 2.0.2600
[02/19/06,14:34:40] Found: 3.1.4000
[02/19/06,14:34:40] Windows Installer version ok
[02/19/06,14:34:40] Finished Checking Windows Installer version.
[02/19/06,14:34:40] Trying to load msi.dll
[02/19/06,14:34:40] Loading: C:WINNTsystem32\msi.dll
[02/19/06,14:34:40] Looking for mscoree.dll from PDC
[02/19/06,14:34:40] mscoree.dll from PDC is not installed local
[02/19/06,14:34:40] Looking for mscoree.dll from Beta
[02/19/06,14:34:40] mscoree.dll is not installed local
[02/19/06,14:34:40] Trying to load msi.dll
[02/19/06,14:34:40] Loading: C:WINNTsystem32\msi.dll
[02/19/06,14:34:40] Installing: C:DOKUME~1SEEHOL~1LOKALE~1TempIXP000.TMPnetfx.msi
[02/19/06,14:34:40] Checking IIS...
[02/19/06,14:34:40] IIS not found
[02/19/06,14:34:40] Checking MDAC Version
[02/19/06,14:34:40] Looking for 2.70.7713.0
[02/19/06,14:34:40] Found MDAC Version: 2.70.9001.0
[02/19/06,14:34:40] MDAC Version OK
[02/19/06,14:34:41] StopDarwinService(): Darwin service successfully stopped
[02/19/06,14:34:41] Trying to load msi.dll
[02/19/06,14:34:41] Loading: C:WINNTsystem32\msi.dll
[02/19/06,14:34:41] Full UI
[02/19/06,14:34:41] Calling MsiInstallProduct() with commandline: REBOOT=ReallySuppress IIS_NOT_PRESENT=1
[02/19/06,14:35:20] MsiInstallProduct() returned 1603
[02/19/06,14:35:20]

[MsiInstallProduct]

ReturnCode=1603
[02/19/06,14:35:20] Preparing Dialog
[02/19/06,14:35:20] Message: Fehler beim Setup von "Microsoft .NET Framework". Wenden Sie sich an den Produktsupport, wenn das Problem weiterhin auftritt.
[02/19/06,14:35:21] Install.exe returning 1603
[02/19/06,14:35:21]

[Install.exe]

ReturnCode=1603
Anonymous
February 19, 2006
Hi Marco - that log file is not a verbose MSI log file. The problem is that error code 1603 is a generic failure code that could have many possible root causes, so we need to look at the verbose log file for more detailed information. Can you please use the steps listed at http://blogs.msdn.com/astebner/archive/2005/03/29/403575.aspx to enable verbose logging and gather a verbose log file for the .NET Framework setup and then contact me using http://blogs.msdn.com/astebner/contact.aspx so I can try to take a look and see if I can figure out what is causing this on your system?
Anonymous
March 14, 2006
The comment has been removed
Anonymous
March 21, 2006
Hello. I need help too. During installation Framework 1.1 I have:
Error 1935.An error occurred during the installation of assembly 'System.Web.Mobile,Version="1.0.5000.0",PublicKeyToken="b03f5f7f11d50a3a",Culture="neutral",FileVersion="1.1.4322.573"'. Please refer to Help and Support for more information. HRESULT: 0x80070003.
In the log I have:
MSI (s) (70:F0) [21:26:28:386]: Note: 1: 1402 2: HKEY_CLASSES_ROOT.1 Wizards 3: 2
MSI (s) (70:F0) [21:26:28:416]: Executing op: ActionStart(Name=CA_PatchInstall.3643236F_FC70_11D3_A536_0090278A1BB8,,)
Action 21:26:28: CA_PatchInstall.3643236F_FC70_11D3_A536_0090278A1BB8.
MSI (s) (70:F0) [21:26:28:487]: Executing op: CustomActionSchedule(Action=CA_PatchInstall.3643236F_FC70_11D3_A536_0090278A1BB8,ActionType=3682,Source=C:WINDOWSMicrosoft.NETFramework,Target="C:WINDOWSMicrosoft.NETFrameworknetfxsbs11.exe" /install,)
MSI (s) (70:F0) [21:26:28:517]: Executing op: End(Checksum=0,ProgressTotalHDWord=0,ProgressTotalLDWord=113278965)
MSI (s) (70:F0) [21:26:31:020]: Assembly Error
As I found 0x80070003 means COR_E_DIRECTORYNOTFOUND, but I don't what to do with this. I hope you'll help me! Thanks. Sorry for my English :)
Anonymous
March 21, 2006
Hi Oleg - Error code 0x80070002 and 0x80070003 tend to have the same set of root causes. I have written a couple of suggestions at http://blogs.msdn.com/astebner/archive/2005/02/01/364375.aspx and also several customers have added additional suggestions that worked for them. Can you please check out that blog post and see if the information there helps in your scenario?
Anonymous
March 21, 2006
Hi Mahesh - It might be useful for you to try to remove the .NET Framework 1.1, reinstall it and then try to install VS 2003 again. You can find steps for removing the .NET Framework 1.1 at http://blogs.msdn.com/astebner/archive/2005/10/11/479928.aspx. Hope this helps!
Anonymous
March 24, 2006
1935 HRESULT 2147319761 IN HP 1510V INSTALL

I just wanted to say thanks for your message board. I was having trouble installing my wife's new hp 1510 scanner printer. I got a 1935 error.
I noted from all the internet logs that this has been a fairly widespread problem. After having tried at least half of the procedures on your webpage, I noted the text that referred to broken installations.
I went into the net framework area and found another later version that did not appear in win98 ad/rem section of control panel.
I moved everything out of that folder into another folder of a different temp name.
Then I ran dotnetfx.exe and after the reinstall it came up fine on the software install.
I might note that the later version of framework was not even listed in the ad/rem sections of win98 control panel.
Hope this helps someone get up and running faster than the days it took me
sglover8@carolina.rr.com

steve
Anonymous
March 27, 2006
Thanks for this blog!!!
It was awesme. I could fix the problem I was having with the mscoree.dll, plus I could understand a lot of what was going on!!
Thanks!!!!
Anonymous
March 31, 2006
When loading .net 2:

I get - Error 25015 Failed to install C:...VisualBasic.VSA.dll 0x80131046

Can I follow the procedure you have and expect good results?

Other sites with possible fixes?
Anonymous
March 31, 2006
Hi Paul - Can you please use the steps listed at http://blogs.msdn.com/astebner/archive/2005/04/16/408856.aspx to manually remove and then try to reinstall the .NET Framework 2.0 and see if it helps resolve this issue?
Anonymous
April 03, 2006
I tried the procedure at

http://blogs.msdn.com/astebner/archive/2005/04/16/408856.aspx

several times. No luck. Same

Error 25015 Failed to install C:...VisualBasic.VSA.dll 0x80131046
Anonymous
April 05, 2006
Hi Paul - I am not sure what might be causing this issue on your system. You are entitled to a free technical support call for setup-related .NET Framework issues, so I think the best option would be for you to contact the Microsoft technical support team for additional assistance. I'm sorry I haven't been able to be more helpful.
Anonymous
April 06, 2006
Hi Everybody,

I have same problem as mahesh. I uninstalled .NET 1.1 and installed it again. But still problem remain as it is.

Any help in this case will be appreciated.

Regards.
Anonymous
April 08, 2006
Kent Damgaard you are my #$#*(NG hero!

Your post is the only one I have found with erros matching mine (from J# redistributable during VS install). Reinstalling .NET 2.0 solved my issues just like you said.

THANK YOU
Anonymous
April 09, 2006
Hi Nirav - Can you please try to use the steps listed at http://blogs.msdn.com/astebner/archive/2005/10/11/479928.aspx to try to cleanup the failed .NET Framework 1.1 install and then try to install it again?
Anonymous
April 22, 2006
After much wasted time trying to follow MS KB fixes that didn't work, stopping here solved my problem with 1935 error on a Win98 system.
I deleted urttemp folder and renamed mscoree.dll, turned off startup, antivirus. I installed 1.0 first and then rebooted and installed 1.1 next. That's what I needed to do so I could install Quickbooks. Thanks.
rob
Anonymous
May 05, 2006
Running XP SP2 - received the described error. Renamed the %SystemRoot%mscoree.dll to mscoree.old. Copied the mscoree.dll from the Service Pack 2, I386 directory to %Systemroot%, rerun setup.... No problem at all.

Thanks for your assistance - appreciated.

JB
Anonymous
May 12, 2006
I have a new machine with Windows XP 64 installed and I get a forest of 2908 and 1935 errors when I run dotnetfx.exe
Are there specific steps to avoid these errors
when XP 64 is installed?
Thanks
Anonymous
May 13, 2006
error1935.error occured during the instalation of assembly 'hpqcmctl,Version = "3.0.0.0." public key token="A53CF5803F4C3827" culture= "Neutral" please refer to help and support for information HRESULT:0X8002802F

The problem I am having is that I can no longer scan on my HP 2110 all purpose printer?
HELP
Anonymous
May 13, 2006
error1935.error occured during the instalation of assembly 'hpqcmctl,Version = "3.0.0.0." public key token="A53CF5803F4C3827" culture= "Neutral" please refer to help and support for information HRESULT:0X8002802F

The problem I am having is that I can no longer scan on my HP 2110 all purpose printer?
HELP
Anonymous
May 13, 2006
Hi Leo - This particular HRESULT value means "function not defined in specified DLL." You can normally solve this issue with these steps (also listed above in the main blog post):

1. Rename the file %windir%system32mscoree.dll (or %windir%systemmscoree.dll on Windows 98 and Windows Me).

2. Delete the folder %windir%system32urttemp (or %windir%systemurttemp on Windows 98 and Windows ME) if it exists.

3. If you are trying to repair the .NET Framework v1.0, locate the file repair.htm in the folder %windir%Microsoft.NETFrameworkv1.0.3705 and follow the instructions on that page.

4. If you are trying to repair the .NET Framework v1.1, locate the file repairRedist.htm in the folder %windir%Microsoft.NETFrameworkv1.1.43221033 and follow the instructions on that page.

5. Rerun the setup that failed originally.
Anonymous
May 15, 2006
Hi Norm - What is the exact HRESULT value that you get on your Windows XP 64-bit system? You may want to try the renaming suggestions that are listed above and see if they help.
Anonymous
May 24, 2006
I get the following error msgs and can't fix the problem. This happens when each time the install gets 99-100% complete. Would you know what I may do to fix it??

Error 1935 - An error occurred during installation assembly.
'Microsoft.MSXML2,publicKeyToken="6bd6b9abf345378f",version="4.1.0.0",type="win32",processorArchiture="x86"'. Please refer to Help and support for more information.
HRESULT: 0x80070002.
Then the install performs a rollback of install and gives another error msg - Error 1603: Fatal error during installation. Consult Windows Installer Help (Msi.chm) or MSDN for more info.

I uninstalled the .Net Framework and reinstalled it to the current version 2, but it still didn't help. Very frustrating.... your advice is appreciated.
Anonymous
May 29, 2006
Hi Greghar - Can you please try the workarounds posted by myself and other customers in my blog item at http://blogs.msdn.com/astebner/archive/2005/02/01/364375.aspx and see if any of them help solve this issue on your system?
Anonymous
June 14, 2006
thanks man , youre informations were really helpfull.

peace
Anonymous
June 19, 2006
PingBack from http://www.eddieoneverything.com/windows-xp/working-around-the-1935-error-with-hresult-0x80131532-when-installing-visual-studio.php
Anonymous
August 27, 2006
PingBack from http://blogs.msdn.com/astebner/articles/454956.aspx
Anonymous
August 27, 2006
PingBack from http://blogs.msdn.com/astebner/articles/454956.aspx
Anonymous
October 21, 2006
The comment has been removed
Anonymous
October 23, 2006
Hi! I dont know what else to do.I've tried to install my new game MS Flight Simulator X, but in the end gives me this error, and I dont know what to do.Please help.Error 1935. An error occurred during the installation of assembly 'Microsoft.FlightSimulator,SimConnect,publickeyToken="67c7c14424d61b5b", version="10.0.60905.0", type="win32", processorArchitecture="x86". Please refer to help and Support for more information. HRESULT: 0x800736E7.
Anonymous
October 23, 2006
Hi LuisP - It sounds like there might be some kind of problem with MSXML on your system. Can you please try to run the MSXML MSI on the root of your installation disc and then try to install Flight Simulator X again and see if that helps solve this problem?If that does not help, it might also help to do the following: Click on the Start menu, choose Run, type msconfig and click OK Go to the Startup tab and click the button to disable all startup programs Go to the services tab, check Hide All Microsoft Services and disable the rest of the services on the system Click OK to accept the changes Reboot and try to install again
Anonymous
October 24, 2006
Hi again. Thanks for the help, but Im afraid that didnt worked.I've run the MSXML MSI at the root, the MSXML4 SP2. And made all the steps you said. But apearsthe same 1935 error. I forgot to say, but after I press OK to the 1935 error, the game UnInstall automatic and at the end gives me a "fatal error -1603" and it says for I check for "help on the MSDN" or someting like that, sorry i dont remenber all the words. I dont know, but It may help you help me. Help me please, I would like to play this game.
Anonymous
October 28, 2006
hii got a problem with installing microsoft .NET 1.1After the installation is almost completed i get the following error:Error 1935 An error ocurred during installation of assembly "Microsoft.Vsa.Vb.CodeDOMProcessor,Version="7.0.5000.0",PublicKeyToken="b03f5f7f11d50a3a",culture="neutral",FileVersion="7.10.3052.4"
Anonymous
October 29, 2006
Hi Brute - I would suggest first trying the steps listed at http://blogs.msdn.com/astebner/archive/2005/10/11/479928.aspx. If that doesn't help, you can use the steps at http://blogs.msdn.com/astebner/archive/2005/03/29/403575.aspx to gather a verbose log file from setup, and you can send it to me at Aaron.Stebner (at) microsoft (dot) com and I'll try to take a look and see if I can figure anything out.Hope this helps!
Anonymous
November 11, 2006
I have same problem with LuisP. I have installed MSXML MSI. It did not work. Furthermore i have tried msconfig way to solve problem but it did not wor,k too. What is problematical i don't know. I have framework updates on windows update website. May it framwork problem? I am going to update it.Thanks.
Anonymous
January 13, 2007
Visual Studio 2005 SP1 Troubles: 2908 error
Anonymous
January 13, 2007
Visual Studio 2005 SP1 Troubles: 2908 error
Anonymous
March 11, 2007
PingBack from http://rohand.com/2007/03/11/enterprise-architect/
Anonymous
May 06, 2007
Question: I am attempting to create an MSI-based setup for my application. This application needs to
Anonymous
June 12, 2007
A while back, I posted an article describing causes of many types of 1935 errors that have been seen
Anonymous
June 12, 2007
PingBack from http://msdnrss.thecoderblogs.com/2007/06/13/possible-cause-of-1935-error-with-hresult-0x8002802f/
Anonymous
July 30, 2007
PingBack from http://www.freesoft-board.to/f58/office-install-problem-236421.html#post1865686
Anonymous
August 10, 2007
The comment has been removed
Anonymous
August 12, 2007
The comment has been removed
Anonymous
November 18, 2007
Hi Aaron!I have been trying desperately to install VS 2005 Pro for days now, but no success!I am getting RESULT -2147023293, during installation with the following error:during the installation of assembly 'Microsoft.VC80.ATL,type="win32",version="8.0.50727.42",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64"'I previously had VS installed, but i removed everything using tools downloaded from Microsoft!Any ideas why this is happening!?i checked c:windowswinsxs and found the following:x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.42_none_dc990e4797f81af1x86_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_11ecb0ab9b2caf3c if it makes any difference...More info about my problem can be found at http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2417626&SiteID=1&mode=1Thanks!
Anonymous
November 19, 2007
The comment has been removed
Anonymous
January 16, 2008
The comment has been removed
Anonymous
January 18, 2008
Hi JimSelf - I'm sorry for the hassle that this issue is causing for you. The error code 0x8007054F is a generic error that means "an internal error occurred." Since this is happening on a Windows Vista system, this type of error will result in a more detailed error message being logged to the file c:windowslogscbscbs.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.
Anonymous
March 19, 2008
The comment has been removed
Anonymous
March 20, 2008
Hi Petrhlavka - When an MSI installs Win32 assemblies on Windows Vista, Windows Installer uses the underlying OS servicing APIs to try to install it. That means, if there are any Win32 assembly install failures, you can find more detailed error information in the log named c:WindowsLogsCbsCbs.log. That log should include a more specific explanation for that HRESULT. Cbs.log tends to be very long, so what I typically do is find the timestamp values in the verbose MSI log and then correlate that time to the timestamps in cbs.log to narrow down the exact error.Hopefully this helps.
Anonymous
May 20, 2008
In January I install a Deployment Server BDD 2007 and everything was working perfect!Now we moved the server to another subnet and the problems came puring down on me:-)First I wasn't able to PXE boot from clients, but this was fixed with further add to DHCP scope option 67(Boot file name) pointing at wdsnbp.com in the Remoteinstallboot directory.Then I had to copy the wim file from x86 directory to x64 in the same bootimages directory, and now I can load Vista images on my clients again.But now I have problems specially with installing MS Office 2007 +SP1. It pops up with an return code 1935???. Also an error code saying"Warning - unable to set working directory????
Anonymous
May 21, 2008
Hi Speltz - There are a lot of possible root causes of 1935 errors - some are related to the .NET Framework and some are not. You will likely need to look at the verbose log files from Office setup to narrow down this error further. You can find information about the names and locations of log files created by Office setup at http://technet2.microsoft.com/Office/en-us/library/e16af71c-fed4-40da-a886-95e596c3999e1033.mspx?mfr=true and http://technet2.microsoft.com/Office/en-us/library/6e8f6aee-1a3c-4b1a-a70e-e6d0d6018b341033.mspx?mfr=true.
Anonymous
July 09, 2008
PingBack from http://www.novolocus.com/2008/07/09/setup-projects-in-visual-studio-2005-2008/
Anonymous
July 09, 2008
PingBack from http://www.vistax64.com/general-discussion/166666-error-1935-vista.html#post771274
Anonymous
August 06, 2008
The comment has been removed
Anonymous
August 08, 2008
Hi Orico - It looks like the issue here is that the Name value you're using to install the assembly to disk is GacFmDll instead of the full DLL name. Can you try changing GacFmDll to Gizmox.WebGUI.Deployment.FileManipulation.dll, rebuild your MSI and see if the install will work as expected after doing that?
Anonymous
September 04, 2008
Recently, I heard from a customer who was attempting to create an MSI-based installer using WiX v3.0
Anonymous
January 20, 2009
PingBack from http://www.hilpers.com/1040829-installation-net-framework-auf-einem
Anonymous
January 22, 2009
PingBack from http://www.hilpers.nl/46780-cd
Anonymous
April 20, 2009
The comment has been removed
Anonymous
April 22, 2009
Hi Knightonquest - Unfortunately, the HRESULT you are receiving is just a generic E_FAIL error and doesn't help much in providing a root cause. I've got a few questions to try to narrow this down further: What OS are you seeing this error on? Do you have problems installing any other .NET applications, or only this one? Do you see this error on multiple computers or only on one specific computer? Can you try to use the steps listed at http://blogs.msdn.com/astebner/archive/2008/03/07/8108332.aspx to remove all versions of the .NET Framework, then install back the .NET Framework 3.5 SP1, then the .NET Framework 1.1 and 1.1 SP1 and see if that helps resolve this issue?
Anonymous
April 24, 2009
Hi Aaron,Thanks a lot for your reply. Given below are answers to your questions -1) Windows XP Professional with SP22) I didn't try with any other application, but I believe this is one3) This error I have seen only on 3 user machines out of user base of ~3004) ok, I will try the steps given and get back to you.This application which I am using is dependent on .Net framework 1.1 only. It doesn't work with any other higher version of .Net.and in this case .Net 1.1 installation completes successfully, but the application installation fails.Regards.
Anonymous
April 24, 2009
Hi Knightonquest - Even if the application depends specifically on the .NET Framework 1.1, Windows Installer can end up using the .NET Framework 2.0 to install assemblies if it is present on the system too.Do these affected systems also have the .NET Framework 1.1 SP1?Are you the manufacturer of this application? If not, and if this is the only application you are seeing this error for, you may want to ask the manufacturer of this application if they have any known issues. It is also possible that this is a bug in the application itself as opposed to a .NET Framework bug.
Anonymous
April 28, 2009
The comment has been removed
Anonymous
April 30, 2009
Hi Knightonquest - I'm not sure if installing the .NET Framework 1.1 SP1 will help or not. It might also help to install .NET 2.0 on the affected systems, then reboot and try to install again. It would also be really good to know if this error happens for any other .NET applications or if it is specific to this one.
Anonymous
May 13, 2009
Hi Aaron,Would it make sense to get help of paid Microsoft support to resolve this issue? We need to get this one resolved asap.Please advise.Thanks
Anonymous
May 13, 2009
Hi Knightonquest - It is definitely an option for you to try contacting Microsoft technical support for more detailed troubleshooting of this issue. However, if this issue is specific to this one application, I'm not sure they will be able to fix it for you because in that case it would likely require a fix to the product itself. Microsoft technical support should be able to help you definitively narrow down whether or not this issue is specific to this one application or a symptom of a more general problem though, which would be really useful as a starting point.
Anonymous
May 28, 2009
The comment has been removed
Anonymous
May 28, 2009
Hi Rjshook - Thank you for this additional information. Do you know how those Orsus-related assemblies got into the GAC on that system in the first place? Were they different versions than the ones that were attempted to be installed when the 0x80004005 error started appearing? It seems like some other version of that Orsus package may have installed some bad assemblies that interfered with installation of future versions of their assemblies on that system.
Anonymous
June 19, 2009
PingBack from http://debtsolutionsnow.info/story.php?id=4208
Anonymous
September 10, 2009
The comment has been removed
Anonymous
September 14, 2010
I have solved one issue that had erros like this -Product: Visual Studio .NET Enterprise Architect 2003 - English -- Error 1937.An error occurred during the installation of assembly 'System.CF.Design,Version="7.0.5000.0",PublicKeyToken="b03f5f7f11d50a3a",Culture="neutral",FileVersion="7.10.3077.0"'. The signature or catalog could not be verified or is not valid. HRESULT: 0x80131045. assembly interface: IAssemblyCacheItem, function: CommitAfter going through this site and many other sites, I came up with this.Run gacutil.exe /i "System.CF.Design.dll" (Or whatever Assembly you are facing a problem with). you will find these DLL's under the Program FilesMicrosoft Visual Studio .NET 2003 , in that path, there are multiple directories below search everywhere and you will find your target.Once you run the above command, you should see a result like this -Microsoft (R) .NET Global Assembly Cache Utility. Version 1.1.4322.573Copyright (C) Microsoft Corporation 1998-2002. All rights reserved.Assembly successfully added to the cacheGo confirm if this assembly can be seen in Control Panel, Administrative Tools, Microsoft .NET Framework <1.1> Configuration and choose Assembly Cache. If you can see it there, then you can go to the next step.Run from the same location Microsoft .NET Framework 1.1 Wizards and choose "Trust an Assembly", then choose your assembly DLL and trust for the computer.Rerun your setup. It worked for me, hope it works for you.Thanks.
Anonymous
December 23, 2010
The comment has been removed
Anonymous
December 24, 2010
Hi Rifae - Which version of Windows are you running when you see this error? If it is Windows Vista or later, then I'd suggest trying out the System Update Readiness Tool because the 0x80073712 error code is listed in the knowledge base article for that tool. You can find a link to that tool and some information about how I have used that tool in the past at blogs.msdn.com/.../9303167.aspx.
Anonymous
March 03, 2011
The comment has been removed
Anonymous
March 03, 2011
Hi Meodegard - I'd suggest trying the System Update Readiness Tool and the steps listed at the end of the blog post at blogs.msdn.com/.../9303167.aspx to see if that helps in this scenario.If that doesn't help, then I'd suggest one of the following: Contact Microsoft technical support for further troubleshooting assistance. You can find contact information at http://support.microsoft.com Repair/re-install Windows on your computer
Anonymous
April 17, 2011
Great! It helped to me too!Thank you very much!
Anonymous
June 07, 2011
The comment has been removed
Anonymous
June 07, 2011
Hi Snepper - Error code 0x8007007E means "The specified module could not be found." That usually indicates some kind of problem with the installer that you're trying to run as opposed to a problem with the .NET Framework. I'd suggest trying to re-download and re-run the installer to see if that helps. If not, then I'd suggest contacting the manufacturer of this installer to see if they have any known issues and/or suggested workarounds for this error.
Anonymous
June 24, 2011
The comment has been removed
Anonymous
June 24, 2011
The comment has been removed
Anonymous
June 24, 2011
Im using windows 7. Im installing microsoft office 2010. It happens during the middle of the installation. Also, im getting the error 2908 before 1935. The 2908 has three options whether to abort, retry or ignore.
Anonymous
June 24, 2011
The comment has been removed
Anonymous
June 24, 2011
The comment has been removed
Anonymous
June 26, 2011
The comment has been removed
Anonymous
June 26, 2011
Sorry i dpn't know how to use windows live. but i've uploaded it to mediafire. is it ok?www.mediafire.comim currently downloading the System Update Readiness Tool for Windows 7. is that the one you were talking about? the 100+mb
Anonymous
June 26, 2011
The system update tool did not work:(
Anonymous
June 27, 2011
The comment has been removed
Anonymous
June 27, 2011
last questions. is reinstalling windows a guaranteed way of solving my problem? will the problem not repeat?
Anonymous
June 28, 2011
The comment has been removed
Anonymous
July 15, 2011
I have been trying to install visual c++ 2008 Distributables on my computer no and an error message pops up,Error 1935.An error occurred during the installation of assembly 'Microsoft.VC90.ATL,version="9.0.30729.4148", publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x8",type="win32" Please refer to Help and Support for more information. HRESULT:0x800736B3.Would any of you shed some light on this?Kind regardstaro
Anonymous
July 15, 2011
Hi Taromiya - I'm guessing you're using Windows Vista or Windows 7 when you see this. If so, then the HRESULT value 0x800736b3 usually means that there is something wrong with a part of Windows, and I'd suggest trying to use the System Update Readiness Tool and the steps listed at blogs.msdn.com/.../9303167.aspx to try to solve this issue.If that doesn't help, you may need to repair/re-install Windows to solve this type of problem.
Anonymous
August 12, 2011
The comment has been removed
Anonymous
August 14, 2011
The comment has been removed
Anonymous
September 26, 2011
I'll need Help i can't install the vcredist_x86 2005 and 2008 here is the log fileskydrive.live.comI've tryied all
Anonymous
September 26, 2011
Hi Ozkarleo - The log you uploaded shows the following error:Error 1935.Error al instalar el ensamblado "Microsoft.VC80.MFC,type="win32",version="8.0.50727.4053",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86"". Consulte Ayuda y soporte técnico para obtener más información. HRESULT: 0x80073712. Interfaz de ensamblado: IAssemblyCacheItem, función: Commit, componente {9BAE13A2-E7AF-D6C3-A01F-C8B3B9A1E18E}The HRESULT value 0x80073712 means ERROR_SXS_COMPONENT_STORE_CORRUPT, and it is one of the error codes listed at support.microsoft.com/.../947821. I'd suggest trying the System Update Readiness Tool described in that knowledge base article to see if it can help solve this error.If that doesn't help, I don't know of any suggestions for you to try other than to repair/re-install Windows.
Anonymous
October 11, 2011
The comment has been removed
Anonymous
October 11, 2011
Hi Janoweil - The MSXML2 assembly is a Win32 assembly, and 1935 errors for Win32 assemblies are not caused by the .NET Framework. If you're running Windows Vista or later, then I'd suggest looking at the information at blogs.msdn.com/.../9904471.aspx for troubleshooting ideas.
Anonymous
November 20, 2011
Hello,i have been looking for this. i also faced this problem many times but after reading this article i fixed it. Thanks for sharing this post. i also got some help from this article <a href="ezinearticles.com 1935 windows 7</a> , hope someone might get help from this article.
Anonymous
November 20, 2011
Hi Error 1935 Windows 7 - I took a look at the article that you posted a link to, and I'm not sure I agree with some of the suggestions listed there. In my experience, these are the most common causes of 1935 errors on Windows 7, so I'd suggest that folks who run into this problem look at these posts:blogs.msdn.com/.../10110053.aspx blogs.msdn.com/.../9904471.aspx
Anonymous
November 30, 2011
The comment has been removed
Anonymous
December 04, 2011
Hi Calvin - I deleted the cbs.log file that you posted in your follow-up comment because it was too large. In the future, please upload log files like that to a file server (such as http://skydrive.live.com) and post a link as a comment so I can download it separately.I think this is the issue in the log file that is causing the failure:2011-11-30 08:58:08, Info CSI 00000006 Pending transaction content must be resolved, cannot begin another transaction yetIf you do a web search for this error, there are several possible causes and different ideas for how to work around it. Here are a few links I found that might be helpful to you:support.microsoft.com/.../968440 social.technet.microsoft.com/.../92be1b34-23cd-46b0-bf21-106d0a5e2e38 blogs.technet.com/.../installation-failures-cbs-store-corruptions-uncommon-issues-and-troubleshooting.aspx
Anonymous
January 22, 2012
I am trying to follow up your steps but unfortunately I can not renamed mscoree.dll! It is protected. Please help.
Anonymous
January 23, 2012
Hi Sandra_CMVG - This troubleshooting guide was created before the .NET Framework 2.0 started shipping as a part of the OS on Windows Vista and Windows 7. Starting in those versions of Windows, it is not possible to rename mscoree.dll like that, and in my past experience it is also not necessary to do so.What is the exact error message that you're seeing in your scenario? I can post some links to additional troubleshooting steps for you to try, but the steps you'll need to try depend on what the exact HRESULT is on your computer.
Anonymous
March 04, 2012
Error 1935 appeared due .Net framework but i fixed it after taking help from this post. Thanks for sharing this. I also got some help from this site; http://www.error-1935.com/ Hope it helps you also.
Anonymous
March 24, 2012
im using windows 7 with 32 bit operating system....im installing SPSS 17 and then an error occurred "Error 1935.An error occured during the installation of assembly componetn {9BAE13A2-E7AF-D6C3-A01F-C8B3B9A1E18E}.HRESULT: 0x800736CC"..Dude how i be able to solve this issue...thanks to anyone who can help me..... appreciated it all
Anonymous
March 27, 2012
The comment has been removed
Anonymous
April 22, 2012
The comment has been removed
Anonymous
April 26, 2012
Hi Liviu - The HRESULT value that you're getting (0x8002802F) means that there is something wrong with the file %windir%system32mscoree.dll on your computer. Most commonly, it means that the version of mscoree.dll is older than the version of the .NET Framework that you're trying to use. On Windows 7, the most common cause I've seen for that type of error is the one I described at blogs.msdn.com/.../10110053.aspx. I'd suggest taking a look at that post to see if the information there helps at all in your scenario.It might also be possible that your installer is suppressing a reboot after .NET Framework installation when it shouldn't be. If you get exit code 3010 when installing the .NET Framework, you need to make sure that your installer reboots before you run later installers that require the .NET Framework.
Anonymous
April 29, 2012
I'm using Windows Vista and trying to install .NET V1.1.4322 and I keep getting Internal Error 2908 {7D4B5591-4C80-42BB-BOE5-F2C0CEE02C1A} and several other 2908 codes. Do you have any ideas about what I should do?
Anonymous
April 29, 2012
Hi Random Comments - Can you please use the steps listed at blogs.msdn.com/.../help-me-help-you-if-you-have-setup-bugs.aspx to get a verbose log file from the failing .NET Framework 1.1 setup on your computer, zip and upload the log file 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 file and take a closer look?
Anonymous
May 27, 2012
Hi Aaron,on Windows 2008 R2, I get this error:Fehler 1935. Während der Installation von Assemblykomponente "{4F6D20F0-CCE5-1492-A01F-C8B3B9A1E18E}" ist ein Fehler aufgetreten. HRESULT: 0x800736FD.I tried to reinstall VC 2005 runtime, also I tried MSIZAP g! but nothing helped.Any ideas how to solve this issue?Walter
Anonymous
May 27, 2012
Hi WalterHofstaedtler - On Windows Vista and later, error code 0x800736FD means that there is something wrong with the Windows OS installation engine (because it is used behind the scenes to install the VC++ runtime files and other Win32 assemblies on those versions of Windows). Here are the steps that I suggest for this type of error: Install the latest Windows service pack if you haven't yet. Try to run the System Update Readiness Tool from support.microsoft.com/.../947821. Try to repair the files that are a part of your OS by using the steps listed at blogs.msdn.com/.../how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx. If none of the above help, you might need to repair/re-install Windows to fix this type of error.
Anonymous
May 29, 2012
Hi Aaron,this sounds worse, I already run the System Update Readiness Tool without errors, also sfc /scannow did not find any errors. SP1 for Windows 2008 R2 is already installed. Also all Patches up to today are installed. Any additional ideas to solve this issue?Walter
Anonymous
May 29, 2012
Hi walter@hofstaedtler.com - I'd suggest doing a web search for the error code 0x800736FD. There are some forum posts from people who have had that type of issue that include other suggestions that you might want to try before you resort to re-installing Windows.
Anonymous
September 02, 2012
The comment has been removed
Anonymous
September 04, 2012
The comment has been removed
Anonymous
October 07, 2012
Hi.I am having problem while installing the software called COMMON VISON BLOX while installing it give me an error stating that "Error 1935 an error occured during the installation of Assembly Compenent 8731EA9c-B0D8-8F16-A0-1F-C883B9A1E18E HRresult 0x80073683.Plz help me out how to solve this problem.
Anonymous
October 09, 2012
Hi Tarun Patel - I don't recognize the HRESULT value that you listed in your comment. If this is happening on Windows Vista or later versions of Windows, then here are the steps that I usually suggest that someone try to resolve this type of error: Install the latest Windows service pack if you haven't yet. Try to run the System Update Readiness Tool from support.microsoft.com/.../947821. Try to repair the files that are a part of your OS by using the steps listed at blogs.msdn.com/.../how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx. If none of the above help, you might need to repair/re-install Windows to fix this type of error. It might also help to post a question on one of the Windows forums to see if someone there has any additional suggestions for you to try before you resort to re-installing Windows.
Anonymous
October 20, 2012
Hi, I also encounter this problem, but Regmender.com helps me fix the error too...visit for more: www.regmender.com/how-to-fix-error-1935.htmlHope this information is helpful.
Anonymous
February 14, 2013
Hi AAron,The earlier post had some mistake in HRresult.I am having problem while installing the software called COMMON VISON BLOX while installing it give me an error stating that "Error 1935 an error occured during the installation of Assembly Compenent 8731EA9c-B0D8-8F16-A0-1F-C883B9A1E18E HRresult 0x800736B3.I run full scan of .netframework to verify my installation all is working well.I also used System Update Readiness Tool and it works perfectly.I don't want to format my system because i have several server license on my system for robots and others.Plz help me out how to solve this problem.eagerly waiting for your reply.
Anonymous
February 18, 2013
Hi Tarun Patel - On Windows Vista and later, error code 0x800736B3 means that there is something wrong with the Windows OS installation engine (because it is used behind the scenes to install some types of assemblies on those versions of Windows). Here are the steps that I suggest for this type of error:1. Install the latest Windows service pack if you haven't yet.2. Try to run the System Update Readiness Tool from support.microsoft.com/.../947821.3. Try to repair the files that are a part of your OS by using the steps listed at blogs.msdn.com/.../how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx.If none of the above help, you might need to repair/re-install Windows to fix this type of error. It might also help to post a question on one of the Windows forums to see if someone there has any additional suggestions for you to try before you resort to re-installing Windows.
Anonymous
February 24, 2013
The comment has been removed
Anonymous
February 24, 2013
The comment has been removed
Anonymous
February 24, 2013
Hi Pankaj Jadhav - On Windows Vista and later, error codes that start with 0x800736 (including the 0x800736FD in your log) mean that there is something wrong with the Windows OS installation engine (because it is used behind the scenes to install the Visual C++ runtime files and some other types of assemblies on those versions of Windows). Here are the steps that I suggest for this type of error: Install the latest Windows service pack if you haven't yet. Try to run the System Update Readiness Tool from support.microsoft.com/.../947821. Try to repair the files that are a part of your OS by using the steps listed at blogs.msdn.com/.../how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx. If none of the above help, you might need to repair/re-install Windows to fix this type of error. It might also help to post a question on one of the Windows forums to see if someone there has any additional suggestions for you to try before you resort to re-installing Windows.
Anonymous
March 09, 2013
Hi Aaron, could you help me?~~pleaseerror 1935.an error occurred during the installation of assembly 'Microsoft.VC90.ALT,version="9.0.30729.6161",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32".please refer to help and support for more information.HRESULT:0x80070BC9.assembly interface:IAssemblyCacheItem,function:Commit,compoent:(03329364-ED3E-3EF1-ACB0-C1E9F5282929)
Anonymous
March 09, 2013
Hi William - What version of Windows are you running? If it is Windows Vista or later, here are the steps that I suggest for this type of error: Install the latest Windows service pack if you haven't yet. Try to run the System Update Readiness Tool from support.microsoft.com/.../947821. Try to repair the files that are a part of your OS by using the steps listed at blogs.msdn.com/.../how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx. If none of the above help, you might need to repair/re-install Windows to fix this type of error. It might also help to post a question on one of the Windows forums to see if someone there has any additional suggestions for you to try before you resort to re-installing Windows.
Anonymous
April 06, 2013
Hi Aron! I do have a brand new desktop with Windows 8 installed. Everything works as a charm... I installed various programs w/o any problem. Recently I tried to instal Adobe Lightroom 4.3 and then 4.4 version. Everytime I get the installation freezing right after I press Install button. If I use "Diagnostic startup" the installation begins but stops after about 75% of the files are copied. The error is, as you may guess: 1935. I have here a screenshot with the complete message:www.graphy.ro/.../2013-04-01_145212.pngCan you give me any suggestion please? I posted a question in the Win 8 forum from Microsoft but w/o to receive a solution that works. I tried to turn off the NET frameworks that are installed (3.5 and 4.5) but doesn't work. I tried to reinstall them but I get a message saying that are already installed. What can I do?
Anonymous
April 06, 2013
Hi Mihai C - Most 1935 errors on Windows Vista and later are not caused by the .NET Framework. In this particular case, I'd first suggest trying the steps at support.microsoft.com/.../958043 to see if they help.If those steps don't help, then I'd suggest the following: Try to run the System Update Readiness Tool from support.microsoft.com/.../947821. Try to repair the files that are a part of your OS by using the steps listed at blogs.msdn.com/.../how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx. If none of the above help, you might need to repair/re-install Windows to fix this type of error.
Anonymous
September 10, 2013
I just wanted to add that you can get this error 1935 if you having Windows updates that are pending on a restart. When I restarted and tried again, no errors. This was on Windows 7 SP1.
Anonymous
November 11, 2013
The comment has been removed
Anonymous
November 11, 2013
Hi Abhishek - I'd suggest trying the workarounds listed in the forum post at social.technet.microsoft.com/.../error-0x80071a91 and see if they help in this scenario.
Anonymous
January 17, 2014
The comment has been removed
Anonymous
January 19, 2014
Hi nythil - Here are the steps that I suggest for this type of error: Install the latest Windows service pack if you haven't yet. Try to run the System Update Readiness Tool from support.microsoft.com/.../947821. Try to repair the files that are a part of your OS by using the steps listed at blogs.msdn.com/.../how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx. If none of the above help, you might need to repair/re-install Windows to fix this type of error. It might also help to post a question on one of the Windows forums to see if someone there has any additional suggestions for you to try before you resort to re-installing Windows.
Anonymous
February 08, 2014
I need help.I have the error code 2908. HRESULT 0x8002802FI know you need to rename or delete i don't know but you need to do something with mscoree.dll.I have a little problem, i don't know why it says i don't have permissions and im the owner of the computer (IT'S MY COMPUTER) Q-QI used that program that is 'TakeOwnership' and it didn't work. I need help please help me! :(
Anonymous
February 09, 2014
Hi Max - What version of Windows are you running on your computer? If you are running one of the versions supported by the .NET Framework 4.5.1, I'd suggest trying to install that to see if it helps resolve this issue. You can download the .NET Framework 4.5.1 from www.microsoft.com/.../details.aspx.If that doesn't help, then the information at blogs.msdn.com/.../3260076.aspx might help too.
Anonymous
February 28, 2014
The comment has been removed
Anonymous
February 28, 2014
Hi Thethi - There is some information about the 0x8002802F error code in the blog post at blogs.msdn.com/.../3260076.aspx that might help you in this situation.
Anonymous
April 23, 2014
The comment has been removed
Anonymous
April 24, 2014
The comment has been removed
Anonymous
July 22, 2014
hi, can please someone help me in this? i'm trying to install visual studio 2010 express, while installation my computer gets almost hanged when the installation reaches the point of installing vc 9.0 runtime (x86).i posted that question on several blogs and got different answers, someone said me to install microsoft visual c++ 2008 redistributable package (x64) and microsoft visual c++ 2008 redistributable package (x86) alone, i did this thing and while installing i get these errors.while installing (x86) i get this error:Error 1935. An error occurred during the installation of assembly 'Microsoft.VC90.ATL, version="9.0.21022.8", publicKeyToken="1fc8b3b9a1e18e3b", processorArchitecture="x86", type="win32"'.Please refer to Help and Support for more information. HRESULT: 0x800736FD.and while installing (x64) i'm getting this error:Error 1935. An error occurred during the installation of assembly 'Microsoft.VC90.ATL, version="9.0.21022.8", publicKeyToken="1fc8b3b9a1e18e3b", processorArchitecture="amd64", type="win32"'.Please refer to Help and Support for more information. HRESULT: 0x800736FD.please someone help me :(
Anonymous
July 22, 2014
Hi haseeb qureshi - Error code 0x800736FD means that there is something wrong with the Windows OS installation engine (because it is used behind the scenes to install the VC++ runtime files and other Win32 assemblies on Windows Vista and newer versions of Windows). Here are the steps that I suggest for this type of error: Install the latest Windows service pack if you haven't yet. Try to run the System Update Readiness Tool from support.microsoft.com/.../947821. Try to repair the files that are a part of your OS by using the steps listed at blogs.msdn.com/.../how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx. If none of the above help, you might need to repair/re-install Windows to fix this type of error. It might also help to post a question on one of the Windows forums to see if someone there has any additional suggestions for you to try before you resort to re-installing Windows.
Anonymous
August 28, 2014
HI IM TRAYING TO INSTALL LIGHTROOM, VERSIONS 4, 5 AND 5.6. NONE OF THOSE THREE WOULD WORK. IT ALWAYS APPEAR THE ERRO 1935. I HAVE WINDOWS 8.1. BOUGHT A NEW ASUS X550L FROM BEST BUY. AND I CAN DOWNLOAD LIGHTROOM, BUT THE INSTALLATION WOULDNT WORK. I NEED HELP. DONT KNOW ANYTHING ABOUT COMPUTER.THNX IN ADVANCE
Anonymous
August 29, 2014
Hi Mariana - Here are the steps that I typically suggest to try to resolve 1935 errors on Windows Vista and all newer versions of Windows: Install the latest Windows service pack and updates if you haven't yet. Try to run the System Update Readiness Tool from support.microsoft.com/.../947821. Try to repair the files that are a part of your OS by using the steps listed at blogs.msdn.com/.../how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx. If none of the above help, you might need to repair/re-install Windows to fix this type of error. It might also help to post a question on one of the Windows forums to see if someone there has any additional suggestions for you to try before you resort to re-installing Windows.
Anonymous
October 12, 2014
The comment has been removed
Anonymous
October 13, 2014
Hi Vijay - On Windows Vista and later, Win32 assemblies are installed by a Windows service, and 1935 errors from Win32 assemblies are not related to the .NET Framework at all. So, you don’t need to worry about uninstalling or re-installing the .NET Framework because it won’t help solve this issue.The error code 0x80070422 that you’re seeing means “ERROR_SERVICE_DISABLED - The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.”I haven’t run into this exact error in my past experience, but I found this item on the forums that contains a suggested fix that will hopefully help in your scenario - answers.microsoft.com/.../08d8b4b0-ecb5-45f9-8028-b82f62794f7c.
- Anonymous
  May 27, 2016
  The comment has been removed
  - Anonymous
    August 09, 2017
    Thanks Tim - this worked for me!
Anonymous
January 02, 2015
Need Help ASAP! Trying to install Office 2007 on a Dell 32 bit laptop w/a new Windows 7 Ultimate SP1 install by mid-day tomorrow (1/3/15)when my soldier son flies back to base from Christmas Break. Keep getting error 1935 and install rollback. Some inet research led me to look up Net Framework on computer which I found to be 4.5.1. Do I need a different one or more Net Frameworks (whatever they are) to make this install work?Thanks, Pam
Anonymous
January 02, 2015
Hi denpam1@juno.com - On Windows Vista and all newer versions of Windows, nearly all 1935 errors are caused by a problem with Windows and not a problem with the .NET Framework. Here are the steps that I suggest for this type of error: Install the latest Windows service pack and updates if you haven't yet. Try to run the System Update Readiness Tool from support.microsoft.com/.../947821. Try to repair the files that are a part of your OS by using the steps listed at blogs.msdn.com/.../how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx. If none of the above help, you might need to repair/re-install Windows to fix this type of error. It might also help to post a question on one of the Windows forums to see if someone there has any additional suggestions for you to try before you resort to re-installing Windows.
Anonymous
February 03, 2015
The comment has been removed
Anonymous
February 04, 2015
Hi ALVARO WILCHES - Hresult 0x80070bc9 means "The requested operation failed. A system reboot is required to roll back changes made." I'd suggest trying to reboot your computer and trying to install again. If that doesn't help, then I'd suggest these troubleshooting steps: Install the latest Windows service pack and updates if you haven't yet. Try to run the System Update Readiness Tool from support.microsoft.com/.../947821. Try to repair the files that are a part of your OS by using the steps listed at blogs.msdn.com/.../how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx.
Anonymous
February 04, 2015
The comment has been removed
Anonymous
February 05, 2015
Hi pEtE - Here are the steps that I suggest for this type of error: Install the latest Windows service pack and updates if you haven't yet. Try to run the System Update Readiness Tool from support.microsoft.com/.../947821. Try to repair the files that are a part of your OS by using the steps listed at blogs.msdn.com/.../how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx. If none of the above help, you might need to repair/re-install Windows to fix this type of error. It might also help to post a question on one of the Windows forums to see if someone there has any additional suggestions for you to try before you resort to re-installing Windows.
Anonymous
March 02, 2015
hey plzzz help me , microsoft office enterprise 2007 encountered an error during setup . error 1935.An error occurred during the installation of assembly componennt (837BF1EB-D770-94EB-A01F-C8B3B9A1E18E) . HRESULT:00800736B3.
Anonymous
March 02, 2015
The comment has been removed
Anonymous
June 16, 2015
an error occurred during the installation of assembly'microsoft.vc80.ATL,processArchiture="x86",publickeytoken="1fc8b3b9a1e18e3b",version="8.0.50727.762",type="win32".Please refer to help and suport for more information..please provide solution..
Anonymous
June 17, 2015
The comment has been removed
Anonymous
June 24, 2015
The comment has been removed
Anonymous
June 25, 2015
Hi Juliocsa - You're getting a 1935 error with hresult 0x8002802F. That means "function not defined in the specified DLL." When that error happens on Windows XP, it tends to be caused by a problem with the version(s) of the .NET Framework that are installed on your PC. I'd recommend using the tools and steps listed at blogs.msdn.com/.../8108332.aspx to manually remove all versions of the .NET Framework that are installed on your PC, then re-install the .NET Framework 3.5 SP1 from www.microsoft.com/.../details.aspx, then try again to install your application.
Anonymous
June 26, 2015
Thank you very much, mr. Aaron
Anonymous
June 26, 2015
Thank you very much, Mr Stebner
Anonymous
October 01, 2015
The comment has been removed
Anonymous
October 01, 2015
The comment has been removed
Anonymous
November 23, 2015
The comment has been removed
Anonymous
November 24, 2015
Hi Phani - Error code 0x80073715 maps to ERROR_SXS_MANIFEST_IDENTITY_SAME_BUT_CONTENTS_DIFFERENT, and that means that there is something wrong with the Windows OS installation engine on your PC. Here are the steps that I suggest for this type of error:

Install the latest Windows service pack and updates if you haven't yet.
Try to run the System Update Readiness Tool from support.microsoft.com/.../947821.
Try to repair the files that are a part of your OS by using the steps listed at blogs.msdn.com/.../how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx. If none of the above help, you might need to repair/re-install Windows to fix this type of error. It might also help to post a question on one of the Windows forums at answers.microsoft.com/.../windows to see if someone there has any additional suggestions for you to try before you resort to re-installing Windows.

Anonymous
November 03, 2016
facing error 1935 with hr result: 0X80070422 while installing SAP Crystal report 2010
- Anonymous
  November 03, 2016
  Hi Fasy - Error code 0x80070422 means "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it." I did a web search for that error code and 1935 errors, and some of the solutions suggested going to services.msc and making sure that you can start the service named Windows Module Installer and that it isn't set to disabled. Can you check that on your PC and see if that helps resolve this installation error?
  - Anonymous
    February 04, 2017
    The comment has been removed
    - Anonymous
      February 04, 2017
      and finally shows "YOUR SYSTEM HAS NOT BEEN MODIFIED TO COMPLETE INSTALLATION AT ANOTHER TIME, PLEASE RUN THE SETUP AGAIN"Fatal Error during installation.Click finish to exit setup.
    - Anonymous
      February 06, 2017
      Hi MD. ASIF - Error code 0x8002802F means "function not defined in specified DLL" and that typically means that there is something wrong with the file c:\windows\system32\mscoree.dll or c:\windows\syswow64\mscoree.dll on your PC. Can you check and see if you have those files, and if so, tell me what version number they are?It might also help to install the newest version of the .NET Framework from https://www.microsoft.com/en-us/download/details.aspx?id=53344.
Anonymous
March 13, 2017
Como solucionar esse erro:An error coccurred during the installation of assembly 'Microsoft.VC80.MFC,version="8.0.50727.6195", publickeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32".Please refer to Help and Support for more information.
- Anonymous
  March 14, 2017
  The comment has been removed

Share via

Troubleshooting 1935 and 2908 errors during installation

Comments

Additional resources