What's new in Cloudhouse release 1911

Save to PDF

Applies to: AppAcceleratorV, Packager, Container Editor

18/11/2020 Cliff Hobbs   ID: 496047

Cloudhouse Release 1911 is available. This article summarises the changes and new features in Cloudhouse Release 1911 (component version 4.6.1911.nnnn).

AppAcceleratorV

New Features

AppAcceleratorV 4.6.1911.24577 (released 19th November 2019)

  • Add /minimize flag to AAV command line to launch child process minimised.

AppAcceleratorV 4.6.1911.24631 (released 25th November 2019)

  • New LoadSystemResources compatibility Feature allowing 32-bit apps running on a 64-bit operating system to access the system32 folder.

AppAcceleratorV 4.6.1912.24789 (released 28th November 2019)

  • Added new debugger detection evasion mechanisms.
  • Improved AAV log files.
  • Added support for virtualising DCOM.

Fixes

AppAcceleratorV 4.6.1912.24789 (released 28th November 2019)

  • Fixed crash when closing Office 2016.
  • Fixed issue caused by a bug in PESection reading.
  • Fixed issue preventing hooking of the application by modifying import tables.

Auto Packager

New Features

Auto Packager 4.6.1911.25022  (released 19th November 2019) 

  • Generation of stub executables has been disabled.
  • KeyScanErrors.json file is created during the end capture to list any issues scanning registry keys.
  • Improved Packager registry scanning performance.

Fixes

Auto Packager 4.6.1911.25022  (released 19th November 2019) 

  • Fixed issue reading invalid unicode chars from registry keys.
  • Fixed issue caused by adding a file to package from runtime analysis files.
  • Stopped packager from packaging its own shortcuts.

Container Editor

New Features

Released 19th November 2019

  • Added new items to the editor exclusion list

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.

Source:
Was this article helpful?

Table of Contents

    Can't find what you're looking for?

    Contact Support