What's new in Cloudhouse release 1909

Save to PDF

Applies to: AppAcceleratorV, Auto Packager, Cloudhouse Containers

21/09/2019 Cliff Hobbs   ID: 457718

Overview

Release 1909 is now available from Cloudhouse.

This topic details the new features and fixes for AppAcceleratorV, the Cloudhouse Auto Packager, Container Editor, and the Cloudhouse Compatibility Containers™ they create released throughout September 2019.

Any components that have changed this month are version 4.6.1909.nnnn

AppAcceleratorV

New Features

AppAcceleratorV 4.6.1909.23989 (released 11th September 2019)

  • Registry API parameters are now added to logs.

Fixes

AppAcceleratorV 4.6.1909.23989 (released 11th September 2019)

  • Registry hooks will now log "null" when arguments are null pointers and "" (empty string) when arguments are empty strings.
  • AAV no longer crashes when computer name redirections are called with null pointers.
  • AAV no longer crashes when the Detach feature is used with the PID.

Auto Packager

New Features

Auto Packager 4.6.1909.24800 (released 11th September 2019)

  • The timeout period of the packaging machine is now captured and added to the Services.xml
  • The C:\Recycler temporary folder is now excluded from capture.

Fixes

Auto Packager 4.6.1909.24800 (released 11th September 2019)

  • Fixed crash caused by unknown value kind for a registry value.
  • Fixed duplication of files in captured files caused by case insensitivity.
  • Fixed an issue where an incorrect exclusion led to the capture of unwanted context menu item registry keys. Previously, the uninstallation of a Container containing these would remove all context menu items.
  • Paths with "/" path separators are now recognised as valid paths.
  • Relative path "." is now recognised as a valid working directory for runtime analysis.

Cloudhouse Containers

New Features

4.6.1909.1406 (released 11th September 2019)

  • Added a configurable timeout for service for deployment.

Advisories

Advisory 1

The Container Editor should only be used to update applications, file, and registry redirections on the same architecture the original Container was created on. For example, if the Container was created on an x86 machine, then the Container Editor must be run on an x86 machine to update the Container.

Anti-Virus Advisory

Remove any Runx.exe files (where “x” is a number), from the Container before deploying it. These files are only required if you need to create Universal Windows Platform (UWP)/MSIX packages of the Container. Anti-virus and malware scanners may flag these files as malware as they are unsigned and designed to run other executables.

Features in Upcoming Releases

See Planned features for future Cloudhouse releases for details of the features we have planned for future releases of our products.

Source:
Was this article helpful?

Table of Contents

    Can't find what you're looking for?

    Contact Support