Alchemy July 2026
The following topic describes each component available to upgrade within this release of Cloudhouse Alchemy. For the most recent component versions of Alchemy, see Alchemy Current Component Versions.
AppAcceleratorV (AAV)
The following table outlines each version of AppAcceleratorV (AAV) that has been released this month, alongside the release date.
Note: The table is ordered in reverse chronological order, with the most recent release at the top.
| Release Date | Version Number |
|---|---|
| 24th July 2026 | V4.7.2607.26937 |
| 22nd July 2026 | V4.7.2607.26934 |
New Features
There are no new features included within this month's releases of AAV.
Other Enhancements
There are no additional enhancements included within this month's releases of AAV.
Fixed Issues
The following issues have been fixed within this month's releases of AAV.
| Release Date | Version Number |
|---|---|
| 24th July 2026 | V4.7.2607.26937 |
PPD-5579 – Crash in CoCreateInstanceEx on Windows 11 24H2 and 25H2 When Invalid Arguments Are Passed |
|
|---|---|
| Affects Versions: V4.7.2605.26923 | Fix Version: V4.7.2607.26937 |
| Problem: | On Windows 11 24H2 and 25H2, applications running under AAV could crash when they called the API function CoCreateInstanceEx with invalid arguments. |
| Cause: | When CoCreateInstanceEx is called with a NULL results array and a requested interface count of one or more, the operating system on Windows 11 24H2 and 25H2 raises an access violation instead of returning an error as earlier versions of Windows do. AAV's hook forwarded these calls to the operating system, so the hooked application crashed. The ForceOfficeVisibility code path also used the results array without first checking that it was valid. |
| Solution: | AAV now checks the results array before forwarding the call. If the array is NULL when interfaces have been requested, AAV returns E_INVALIDARG to the application, which is the result earlier versions of Windows return. The ForceOfficeVisibility code path now also checks for a NULL results array. Applications that make well-formed calls are not affected. |
| Release Date | Version Number |
|---|---|
| 22nd July 2026 | V4.7.2607.26934 |
PPD-5575 – Stack Overflow Crash in 32-bit Applications Using the RedirectX64PackagedRegistry Compatibility Feature |
|
|---|---|
| Affects Versions: V4.7.2605.26923 | Fix Version: V4.7.2607.26934 |
| Problem: | When the RedirectX64PackagedRegistry Compatibility Feature was enabled, 32-bit processes could crash on launch with a stack overflow. This was seen with an AutoCAD Architecture 2027 package, where a 32-bit COM component failed to start and the features that depend on it were unusable. |
| Cause: | To resolve a registry path for a 32-bit process, AAV opens a registry key itself. That internal call passed back through AAV's own registry hook, which started resolving the path again. This repeated without limit until the stack overflowed and the process terminated. The stack trace could be misleading, as it pointed at an unrelated signature-verification call rather than the registry hook. |
| Solution: | AAV now detects when registry path resolution is already in progress and resolves the nested open against the real registry instead of re-entering the hook. Affected 32-bit COM components now start correctly. PackageIsolation behaviour is unchanged. Note: For more information on this Compatibility Feature, see RedirectX64PackagedRegistry Compatibility Feature. |
Auto Packager
The following table outlines each version of Auto Packager that has been released this month, alongside the release date.
Note: The table is ordered in reverse chronological order, with the most recent release at the top.
| Release Dates | Current Version Number | AAV Version Number |
|---|---|---|
| 28th July 2026 | V4.7.2607.20 | V4.7.2607.26937 |
| 23rd July 2026 | V4.7.2607.18 | V4.7.2607.26934 |
| 23rd July 2026 | V4.7.2607.16 | V4.7.2605.26923 |
| 17th July 2026 | V4.7.2607.9 | V4.7.2605.26923 |
New Features
There are no new features included within this month's releases of Auto Packager.
Other Enhancements
The following additional enhancements are included within this month's releases of Auto Packager.
Internal Build and Release Improvements
Auto Packager 4.7.2607.9 and 4.7.2607.16 contain internal build and release-pipeline improvements only, with no change to functionality.
Updated Component Versions
The following component versions have been updated:
- Auto Packager 4.7.2607.18: Updated AAV component version to 4.7.2607.26934. This includes the fix for stack overflow crashes in 32-bit applications that use the
RedirectX64PackagedRegistryCompatibility Feature. - Auto Packager 4.7.2607.20: Updated AAV component version to 4.7.2607.26937. This includes the fix for crashes in
CoCreateInstanceExon Windows 11 24H2 and 25H2. - Auto Packager 4.7.2607.20: Updated Package Runtimes component version to 4.7.2607.4335. This includes support for sharing environment variables between linked packages.
Fixed Issues
No issues have been fixed within this month's releases of Auto Packager. For the fixes delivered through updated AAV versions, see the AppAcceleratorV (AAV) section.
Package Runtimes
The following table outlines each version of Package Runtimes that has been released this month, alongside the release date.
| Release Date | Version Number |
|---|---|
| 28th July 2026 | V4.7.2607.4335 |
New Features
The following new feature is included within this month's release of Package Runtimes.
Shared Environment Variables Across Linked Packages
Linked packages now share environment variables. Previously, when a package was launched, Package Runtimes applied only the environment variables defined in that package's own EnvironmentVariables.xml file. It now also applies the environment variables of the packages linked to it, including values that append to PATH.
The following rules apply:
- The environment variables of the package being launched are applied first, followed by those of each linked package in the order the links are declared.
- If the launching package and a linked package define the same variable, and the variable is not an append variable, the launching package's value is used.
- Values from a linked package are expanded against that linked package's own deployed folder.
- If a linked package's environment variables file is missing or cannot be read, it is recorded in the log and skipped, and the launch continues.
- Variables from linked packages apply only to the packaged application and are not added to the host machine.
Note: Applications that pass their own explicit environment block to a child process do not receive the merged variables for that child process.
Note: For more information, see Sharing Environment Variables Between Linked Packages.
Other Enhancements
There are no additional enhancements included within this month's release of Package Runtimes.
Fixed Issues
No issues have been fixed within this month's release of Package Runtimes.