What's new in Cloudhouse release 1801

16/01/2019 Cliff Hobbs


Release 1801 is now available from Cloudhouse.

New features and fixes for the Auto Packager, and the Containers created by the Auto  Packager. All changes detailed have been released January 2018.

New Features In Containers

  • Deployment scripts perform the Container copy action first, so that deployment scripts XML can reference content included in the Container during deployment e.g. MSIs, driver files.

Fixes in Containers

  • Hooked CryptVerify signature check performed by AAV no longer defaults to TRUE, the signature is always checked for an application's files.
  • Registry getSid function could fail to return the correct Sid.
  • Registry Redirection no longer assumes the registry path has a virtual root; the path is always checked to see if it contains a virtual root.
  • "ERROR, AAV INTERNAL, Stack overflow in (pid_number)Application.exe; are your static buffers too big?" appears in the logs, after the following message is repeated because AAV fails to recognize an opcode.
    • INFO, AAV INTERNAL, Loaded dll at 00007FFCA7DC0000. Name "binding.node"; 0 functions of interest. In process (5296)Teams.exe
      INFO, AAV INTERNAL, Hooking ole32.dll!CoRegisterClassObject purple to 00007FFC95347BF0
      INFO, AAV INTERNAL, Opcode 0x61 not implemented yet at 00007FFCB85DEC75
      INFO, AAV INTERNAL, Cannot hook ole32.dll!CoRegisterClassObject, only 0 bytes available to be overwritten

New Features In Auto Packager

  • Container Editor - Able to encode and decode Registry data when creating snapshots.
  • Container Editor - Supports exclusion rules for the Registry.
  • Container Editor - Reports usage and support Telemetry, the default is True.
  • Container Editor - Provides a context menu to delete registry items from the Container. 
  • Container Editor - Provides tooltips, legends and workflow optimizations to remove unnecessary clicks during the update process.
  • Container Editor - Speed up registry delete operations.
  • Container Editor - Do not display semaphores for empty Registry keys that have no child keys.
  • Container Editor - Undo / redo operations for the Registry.

Fixes in Auto Packager

  • Container Editor - Including an inaccessible folder will no longer crash the Editor.
  • Container Editor - Consistent use of "Container" throughout UI, improved instructional text and UI controls; buttons changed from "Build the Container" to "Save", "Update with snapshot" to "Update".
  • Container Editor - When the Container is merged with an empty snapshot, the user was unable to save the Container, or undo their changes.
  • Container Editor - Deleting a key, and then re-adding it, will show two different entries merged with a new key.
  • Container Editor - Unable to build the Container, error message  "System.InvalidOperationException: Sequence contains no matching element", after all registry entries under HKCU and HKLM in the Container snapshot have been deleted.
  • Container Editor - Encode special characters in Registry value names.
  • Container Editor - Registry key serializing to invalid XML, and caused the Editor and Container to crash in two places when reading the keys with special characters.
  • Container Editor - Editor gives an 'Invalid cast exception' when capturing a binary value in the Registry, logs ERROR Cloudhouse.Packager.Editor.Core.Containers.Registry.OperationBuilder - Could not serialize value: "" for key 
  • Auto Packager - No longer fails to perform a runtime capture because the default log location was changed.
  • Auto Packager - If the application requires a restart during the capture process, restarting the Auto Packager via the shortcut will not cause the shortcut to be included in the Container.
  • Auto Packager - Failed to handle short paths 8.3 correctly in AppRegistry.xml and FileAssociations.xml, causing the application to fail to run - short paths are now converted to full paths during Container creation.


Cloudhouse recommends using the Auto Packager on x86 operating systems only, re-directions will not be created correctly for applications that contain a mix of x64 and x86 components. Containers will be created successfully for applications that contain only x64 components, but successful packaging on this platform requires detailed knowledge of the application prior to packaging.

Features in Upcoming Releases

See the Features in Upcoming Releases page for details of the features we have planned for feature releases of our products.

Was this article helpful?

Table of Contents

    Can't find what you're looking for?

    Contact Support