Unsolved
This post is more than 5 years old
6 Posts
0
18428
XPS drivers for BRCM2070 BT 2.1 ( R280283 ) do not install!!
On my computer (XP
S L501X Win
dows 7 Ultimate x64, 4 Gb RAM, Intel Core i7 740 1.73 GHz Q) appears a "peripheral Bluetooht" not installed.
I'am
BRCM2070 BT 2.1 + HS USB Module
I'am downloaded the appropriate driver (R280283), but does not install ...
Error:
policy.8.0.Microsoft.VC80.ATL,
type = "win32-policy",
type = "win32-policy",
version = "8.0.50727.42",
publicKeyToken = "1fc8b3b9a1e18e3b"
processorArchitecture = "amd64"
publicKeyToken = "1fc8b3b9a1e18e3b"
processorArchitecture = "amd64"
What can I do?
Thanks!!
speedstep
8 Wizard
8 Wizard
•
47K Posts
1
June 24th, 2011 12:00
There are many different underlying causes of 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):
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:
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:
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:
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:
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
aleixaXPS
6 Posts
1
June 27th, 2011 09:00
Sorry, but I did all the corrections indicated, and the tests and nothing was ressolvido ... R280283 The driver can not be installed ...