What's new in Cloudhouse release 1904

Save to PDF

Applies to: AppAcceleratorV, Auto Packager, Cloudhouse Containers, and Container Editor

21/06/2019 Cliff Hobbs   ID: 390918

Overview

Release 1904 is now available from Cloudhouse.

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

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

AppAcceleratorV

New Features

AppAcceleratorV 4.6.1904.23336  (released 24th April)

Fixes

AppAcceleratorV 4.6.1904.23336  (released 24th April)

Resolves:

  • Folder matches involving program files resolving to an incorrect x86/x64 path.
  • Issues with quotes in paths when calling CreateFileW.
  • HookMe.dll trying to load HookMe.clv from the executable path rather than the DLL path.
  • The enumeration of subkeys in the registry continuing even though there are no more entries.

Auto Packager

New Features

Auto Packager 4.6.1904.23978 (released 4th April)

  • Packager captures App ID keys for DCOM virtualisation.

Auto Packager 4.6.1904.24077 (released 30th April)

  • 64-bit runtimes re-added to Auto Packager.

Fixes

Auto Packager 4.6.1904.23978 (released 4th April)

  • Services configured with 8.3 paths are captured and expanded.

Auto Packager 4.6.1904.24077 (released 30th April)

Resolves:

  • An issue where the Auto Packager (and Container Editor) would capture and redirect the main AppId key if it were created upon installing an app.
  • An issue whereby file icon paths are not changed correctly in the FileAssociations.xml.
  • An issue where windows context menus are not capitalised correctly.

Cloudhouse Containers

New Features

4.6.1904.1227  (released 4th April)

  • DCOM configuration using the AppId registry key can be deployed.
  • Details of DCOM servers are now logged along with the suggestion of adding them to your Windows Firewall exceptions.

Fixes

4.6.1904.1227 (released 4th April 2019)

Resolves:

  • An exception if the COM EXEs have been deleted from the Container folder and the user then attempts to uninstall the Container from that folder.
  • LocalServer32 configuration for COM using hashed paths is no longer deployed.

4.6.1904.1275 (released 30th April 2019)

Resolves:

  • An issue where File Args do not correctly launch the containerised application.
  • An uninstall failing because of CLSID key on Windows XP.

Container Editor

Fixes

4.6.1904.1006 (released 30th April)

Resolves:

  • An issue where the Container Editor (and Auto Packager)  would capture and redirect the main AppId key if it were created upon installing an app.

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 is built on an x86 machine, then the Container Editor must be run on an x86 computer 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