Error 1935. An error occurred during the installation of assembly 'Microsoft VC90.OpenMP, processorArchitecture="x86", publicKeyToken="1fc8b9a1e18e3b"

Error Message

Note:
This article applies to retired ArcGIS versions 10.2.x and prior. Later versions of ArcGIS may contain different functionality, as well as different names and locations for menus, commands and geoprocessing tools. Moreover, the Windows 7 operating system is no longer distributed or supported by Microsoft Corporation.

As such, we recommend upgrading your operating system and ArcGIS products to current versions.

When installing ArcGIS products on Windows 7, the following error message is returned:

Error:   
Error 1935. An error occurred during the installation of assembly 'Microsoft VC90.OpenMP,processorArchitecture="x86",publicKeyToken="1fc8b9a1e18e3b",version='9.0.21022.8,"type="win32". Please refer to Help and Support for note information.

This error message can also be related to the following error message:

Error:   
ArcGIS Desktop has encountered a serious application error and is unable to continue

or it can be an error similar to:

Error:   
hresult 0x800736fd

after the install of Microsoft SQL Server 2008 Native Client.

Cause

The error is returned when an incorrect registry setting prevents the Windows Modules Installer from running. The issue may be associated with Microsoft .NET Framework 3.5., but may also occur when installing other Microsoft products, such as MS Office.

This issue may be related to one or more of the following symptoms:

• When installing applications, error messages involving OpenMP are displayed, and the installation fails with a rollback:
   

  Product: Microsoft Visual C++ 2005 Redistributable -- Error 1935. An
  error occurred during the installation of assembly 
  'Microsoft.VC80.OpenMP,type="win32",version="8.0.50727.762",publicKeyTok
  en="1fc8b3b9a1e18e3b",processorArchitecture="x86"'. Please refer to Help
  and Support for more information. HRESULT: 0x800736FD. assembly
  interface: IAssemblyCacheItem, function: Commit, component:
  {1E507087-0819-45E0-A01F-C8B3B9A1E18E}

• Installing applications or trying to run Windows Update causes the following entries to be added to the System log in Event Viewer:
   

  The server {752073A1-23F2-4396-85F0-8FDB879ED0ED} did not register with DCOM within the required timeout.
  
  The Windows Modules Installer service terminated with the following error: Insufficient system resources exist to complete the requested service.
  
  Application popup: Windows - Low On Registry Space: The system has reached the maximum size allowed for the system part of the registry. Additional storage requests will be ignored.​

• When trying to make changes to the Windows configuration the 'Turn Windows Features On and Off' dialog box is empty.
• Open the %windir%\logs\cbs directory and the cbs.log file. Look for failures concerning the TrustedInstaller initialization. The error might look something like this:

  2009-08-27 00:05:20, Info CBS Starting TrustedInstaller initialization.
  2009-08-27 00:05:20, Info CBS Loaded Servicing Stack v6.1.7600.16385
  with Core: C:\Windows\winsxs\x86_microsoft-windows-
  servicingstack_31bf3856ad364e35_6.1.7600.16385_none_0935b76c289e0fd5\cbs
  core.dll
  2009-08-27 00:05:20, Info CBS Failed to load the COMPONENTS hive from
  'C:\Windows\System32\config\COMPONENTS' into registry key
  'HKLM\COMPONENTS'.
  
  [HRESULT = 0x800705aa - ERROR_NO_SYSTEM_RESOURCES]
  2009-08-27 00:05:20, Info CBS Failed to load WCP DLL. [HRESULT =
  0x800705aa - ERROR_NO_SYSTEM_RESOURCES]
  2009-08-27 00:05:20, Info CBS Failed to initialize the Core DLL:
  C:\Windows\winsxs\x86_microsoft-windows-
  servicingstack_31bf3856ad364e35_6.1.7600.16385_none_0935b76c289e0fd5\cbs
  core.dll [HRESULT = 0x800705aa -

This issue may be confirmed if any of the above symptoms are encountered, and one or more of the following tests fails:

• Test 1: Run the .NET Framework Setup Verification Tool. For more information or to download the .NET Framework Setup Verification Tool, click on the following link: .NET Framework Setup Verification Tool User's Guide.
  
  After running the .NET Framework Setup Verification Tool, there should be three Frameworks listed: 2.0 SP2, 3.0 SP2, and 3.5 SP1.
  
  Validate each Framework starting with 2.0 SP2, then 3.0 SP2, and lastly 3.5 SP1. The only one that should fail is 3.5 SP1.
   
• Test 2: As an Administrator, open a Command Prompt and run 'SFC /SCANNOW'. A failure regarding the Windows Resource Monitor should be returned.

Solution or Workaround

After confirming the issue, if the 'Low Registry Space' error is returned, reset the Registry Size Limit using the following procedure.

Warning:
The instructions below include making changes to essential parts of the operating system. It is recommended to backup the operating system and files, including the registry, before proceeding. Consult with a qualified computer systems professional, if necessary. 

Esri cannot guarantee results from incorrect modifications while following these instructions; therefore, use caution and proceed at your own risk.

1. In Windows, click Start > Run.
2. In the Run window, type regedit.
3. In the Registry Editor window, navigate to the following location:

   HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control

4. In the Registry Editor dialog box, double-click RegistrySizeLimit. This opens the Edit DWORD Value dialog box.

   Note:
   If unable to find the RegistrySizeLimit key in the above path, click Edit > Find and search for RegistrySizeLimit.
    
   
   
   If still unable to find the RegistrySizeLimit key, then create the key using the following steps:
   
   a. Create the key by right-click > New > DWORD (32 or 64 –bit) Value.  
   b. Enter ffffffff as the Hexadecimal value. Click the Decimal radio button.
   c. Enter 4294967295 as the Decimal value.
   d. Select OK and proceed to Step 6 below.

5. In the Edit DWORD Value dialog box, enter ffffffff as the Hexadecimal value. Click the Decimal radio button, and enter 4294967295 as the Decimal value. Click OK.
6. Reboot the machine.
7. Log in as an Administrator and open Command Prompt. Run SFC /SCANNOW.