FME Installer fails with Microsoft MFC or CRT error

Symptoms

FME Installation Error

When installing FME on Windows 7 or Windows 10, one of the following error messages (or similar) is returned:

 "An error occurred during the installation of assembly 'Microsoft VC90.MFC, version ="9.0.21022.8",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86",type="win32". Please refer to Help and Support for more information."

"An error occurred during the installation of assembly 'Microsoft.VC80.CRT,version="8.0.50727.6195",publicKeyToken="1fc9b3b9a1e18e3b",processorArchitecture="amd64",type="win32". Please refer to Help and Support for more information."

If this only occurs with a 64-bit FME installation (i.e. 32-bit FME installs successfully), then see Resolution #2 below.

Note: This issue may be related to one or more of the symptoms listed below.

OpenMP Errors

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}

Event Viewer Errors

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 allowedfor the system part of the registry. Additional storage requests will be ignored.

Can't turn Windows Features on/off

When you click Turn Windows features on or off in the Programs and Features Control Panel item, the Windows Features dialog box is empty. No features are shown. http://support.microsoft.com/kb/931712

TrustedInstaller Initialization Failures

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 -

Confirm the Issue

To confirm that this is the issue, run the following tests. One or more of them should fail.

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.

Run the System File Checker

Run SFC /SCANNOW. As an Administrator, open a Command Prompt and run 'SFC /SCANNOW'. A failure regarding the Windows Resource Monitor should be returned.

Cause

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

Resolution

1) 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 your operating system. It is recommended that you backup your operating system and files, including the registry, before proceeding. Consult with a qualified computer systems professional, if necessary.

Safe Software 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'. In the Registry Editor window, navigate to HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Control.
3. In the 'Registry Editor' dialog box, double-click on 'RegistrySizeLimit'. This opens the 'Edit DWORD Value' dialog box.
4. In the 'Edit DWORD Value' dialog box, enter ffffffff as the 'Hexadecimal' value. Click on the 'Decimal' radio button, and enter 4294967295 as the 'Decimal' value. Click OK.
5. Reboot the machine.
6. Log in as an Administrator and open a Command Prompt and run 'SFC /SCANNOW'.
7. Install FME

2) There have been reports that 32-bit FME will install, but not 64-bit FME. If this is applicable to your situation, try manually installing the Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package MFC Security Update (x84 and x64) .

Note: Resolution 2, above, has been confirmed to resolve an installation issue for 32-bit FME 2017 (Build 17291) for at least one of our customers.

If none of the above resolves the issue, please contact FME Technical Support , or if you come across a different solution, then please share your experience with the FME Community by leaving a comment.