DEPRECATED: How to resolve problems with out-of-process COM

Save to PDF

Applies to: Cloudhouse Containers

12/08/2019 Cliff Hobbs   ID: 267087


The content is this article has now been deprecated so should no longer be used.


Applications with components that are running out-of-process can cause issues. Procmon can be used to detect these components by monitoring SVCHOST.exe or APIMON filtering by CoCreateInstance,  the failure will result in either CLSID not found, or Component not registered, this is due to the COM subsystem not running within the  Container's virtual environment. To resolve this issue, find the CLSID  keys for this component and import them into the local HKCU registry.


Upgrade your Container, and use the new <Feature>COMVirtualization</Feature> compatibility Feature which provides automatic support for Out of Process COM refer to How to enable support for out of process COM (COMVirtualization)‍ 

Step-by-step guide

  1. Identify the CLSID keys and add them into AppRegistry.xml.
      <Value ValueType="String">C:\ProgramData\Cloudhouse\DemoApplications\ProgData\Program Files (x86)\AAVOriginalExecutable.exe</Value>
  2. Change the LocalServer32 value to point to AppAcceleratorV.exe which has been renamed to AAVOriginalExecutable.exe.
  3. Create a copy of AppAcceleratorV.exe and AppAccelerator32.dll, place these files in the same directory as the original executable.
  4. Rename AppAcceleratorV.exe to AAVOriginalExecutable.exe.
  5. Create a configuration file named AAVOriginalExecutable.clc.
  6. In the configuration file (AAVOriginalExecutable.clc), create an EXE tag to refer the virtualization engine to the original executable.
  7. Specify an INCLUDEtag to refer the virtualization engine to the main redirection file.
      <Exe>C:\ProgramData\Cloudhouse\DemoApplication\ProgData\Program Files (x86)\Original.exe</Exe>
Was this article helpful?

Table of Contents

    Can't find what you're looking for?

    Contact Support