App Layering

Fixed issues

The following issues are fixed in recent releases.

Fixed in App Layering 2011

  • Windows 10, 2004 login times. An issue where Windows 10 2004 sometimes took 2–4 minutes to start, and occasionally included black-screens for 30-45 seconds has been fixed. (UNI-80656)
  • kmssetup script not added to the startup scripts folder. An issue that had prevented the kmssetup.cmd script from being added to the startup scripts folder when unzipped has been fixed. (ALHELP-1279, UNI-80410)
  • HP UPD driver not available as a printer driver. When you include an HP UPD driver in an app layer that becomes part of a published image, the driver is now available as a printer driver. The issue that prevented the driver from being listed has been fixed. (ALHELP-1278, UNI-80426)
  • Sessions hangs for minutes. An issue that had caused sessions to hang for minutes has been fixed. This issue had appeared after upgrading to App Layering 2005. (ALHELP-1263, UNI-80262)
  • User cannot reconnect to their desktop in App Layering 2009. An issue that caused random occasional blue screens when users tried to reconnect to their desktops has been fixed. (ALHELP-1317, UNI-81156)

Fixed in App Layering 2008

  • VM in vSphere with elastic layers enabled no longer fails after being deployed to a Citrix Provisioning server. An issue that had caused a VM in vSphere with elastic layers enabled to fail after being deployed to a Citrix Provisioning server was fixed. (ALHELP-1202, UNI-76300)
  • An issue that had caused the AutoDesk 2020 installer to fail in an app layer has been fixed. (ALHELP-476)
  • Users can now synchronize their OneDrive files without issues when On Demand syncing and Elastic layers are enabled (ALHELP-468)
  • Chrome extensions no longer cause the error message, “FAILED_TO_COPY_EXTENSION_FILE_TO_TEMP_DIRECTORY,” when elastic layers are enabled and an app layer is assigned. (ALHELP-419)

Fixed in App Layering 2005

  • When using offload compositing with VMware vSphere, you can use layer names that start with brackets [], as long as you follow the closing bracket with a space. For example, the name [OS] Windows 10 works, but the name [OS]Windows 10 hangs in vSphere studio and times out after about 40 minutes. (UNI-78452)

Fixed in App Layering 2003

  • The Guest Layering service (ULayer) has been modified to not depend upon the Server service running on the end users’ virtual machines. (UNI-77242)
  • When delivered as an elastic layer, the Artiva application no longer fails when users attempt to log in. (UNI-76487)
  • An issue that had caused the StartCCMEXEC.cmd script to continually grow the log file, StartCCMExec.txt, even when CCMExec was not installed, has been fixed. To apply the fix, download the new OS Machine Tools folder for 20.3, and replace the StartCCMEXEC.cmd file with the new version. (UNI-77471)
  • When users install fonts on a user layer or elastic layer, the fonts persist the next time they log in. (UNI-63839)
  • When using a connector with Offload compositing enabled to publish an image, 8.3 file names are no longer incorrectly modified. (UNI-76961)
  • When adding a version to an app layer, you no longer receive the error “The Operation Failed due to a missing File. VMDK was not found.” (UNI-77702)
  • The issue with expiring JSON Web Tokens (JWT) when using the Offload Compositing feature in the connector configuration has been fixed. (UNI-76859)
  • The Hyper-V connector now reports the disk file size rather than its logical size, which was quickly filling up the cache. (UNI-76692)
  • Compatibility with Citrix Studio GPO policies when using images with user layers has been improved. (UNI-76918)

Fixed in App Layering 2001

  • In our App Layering appliance (ELM) deployment script for Azure, we have extended the expiration dates of signed Azure URLs pointing to standard repository disks. Make sure that you update your Azure deployment scripts from this release accordingly.
  • VDA installations no longer fail on a packaging machine. The issue where users saw repeated failures has been fixed. (UNI-76299)
  • When restarted, a layered image with a user layer no longer drops scheduler tasks. (UNI-77084)

Fixed in App Layering 1911

  • An error when finalizing OS layers with MBR partitions after a major Windows 10 upgrade has been fixed. (UNI-76210)
  • Compatibility with the Microsoft System Center Configuration Manager (SCCM) has been improved. (UNI-76198, UNI-76126, UNI-76129)
  • Users no longer lose their connection to a session host where FSLogix is running and elastic layering is enabled. (UNI-73793)
  • Rapid Reader 8.3 now starts as expected after being installed on a packaging machine. (UNI-76316)
  • IntelliJ IDEA Ultimate no longer freezes the desktop when the app is started. (UNI-76075)
  • Users no longer get a blue screen when they open SQL Management Studio and attempt to save a Query to OneDrive or a SharePoint folder. (UNI-76427)

Fixed in App Layering 1910

  • A PVS Support article that called for removal of the CDF Driver Registry entry has been updated to fix issues troubleshooting Profile Management. (UNI-75720)
  • The issue where Defender didn’t update correctly has been fixed. (UNI-74918)
  • Windows Search Service starts as expected on a packaging machine when using a caching connector. (UNI-75915)
  • Windows Defender now starts successfully on an app layer created from a Windows 1809 OS layer. (UNI-74997)
  • Users can now sync their OneDrive files when On Demand syncing and elastic layers are enabled. (UNI-74618)
  • OneDrive’s on-demand feature now streams files correctly when elastic layering is enabled. (UNI-73121)
  • User layer repairs now complete successfully when the minimum recommended permissions are set on the Users\ path. (UNI-75552)
  • When installing a Chrome extension with user layers enabled and an app layer assigned as an elastic layer, you no longer receive the error Can not install package: FAILED_TO_COPY_EXTENSION_FILE_TO_TEMP_DIRECTORY (UNI-75568)
  • Windows Search index performance has been improved when using full user layers. (UNI-73049)
  • This release adds validation and warnings about what disk size you can use. The guidance is based on your configuration and the app layers selected. (UNI-54390)

Fixed in App Layering 1908

  • Hyper-V connector PowerShell sessions no longer expire when a file copy takes longer than 30 minutes. (UNI-74283, UNI-74292)

  • The issue where System and Display properties did not open correctly when user layers were enabled has been fixed. (UNI-74547)

  • Removing store apps from a Windows 10 OS layer no longer causes features, like Settings and Display Properties, to malfunction. (UNI-74852)

  • The Windows Defender update KB4052623, now successfully installs and works for user layer-enabled users. (UNI-74942)

Fixed in App Layering 1907

  • Improved OneDrive compatibility. (UNI-73722, UNI-73900, UNI-73121)

  • Improved stability to decrease the likelihood that a desktop hangs. (UNI-74062)

  • Improved stability to avoid deadlocks that can happen during a volume rescan. (UNI-71573)

  • After a major OS version upgrade on the OS Layer, there was a problem with the user layer cleanup when users logged in. The cleanup now completes and the issue has been fixed. (UNI-73680, UNI-74002)

Fixed in App Layering 1905

  • Increased stability of packaging machines. They now avoid a stack overflow condition that had been observed after installing ESET antivirus software. (UNI-73224, UNI-73793)

  • Fixed high CPU utilization which resulted in slow elastic layering performance when Windows personalization is used. (UNI-73710)

  • Corrected page file settings used in Platform Layer packaging machines which were overriding the path specified in the OS Layer. (UNI-73470)

  • Improved App-V compatibility for failures encountered during application launches. (UNI-73074)

  • When publishing an image, you are less likely to get a disk integrity warning because of one or more folders that contain many files. (UNI-69703)

  • Fixed Start menu issues observed when using the Citrix Profile Management and Elastic Layering features together. (UNI-72858)

  • Corrected a file collision condition that happened after a program downloaded a temporary file and attempted to rename it to its permanent file name. (UNI-72824)

  • Fixed a hang condition happening while installing Oracle Database Client software on a packaging machine. (UNI-71726)

  • Improved the creation of OS Layer versions. The tile cache for the Windows Start menu no longer results in missing tiles. (UNI-69914)

  • Replaced inaccurate text displayed in the Image Preparation utility’s installer wizard. (UNI-73370)

  • When using caching in connectors, Windows Store apps, such as Calculator and Sticky Notes, now run correctly. (UNI-72854)

  • To shorten login times when using App-V and the Elastic Layering feature, we have optimized file access. (UNI-71083)

  • Reduced file open durations when using Dragon software which avoids lags when opening up the app and pressing the record button. (UNI-70331)

  • The Office prep script now uses the latest changes to the configuration. (UNI-72814)

  • Introduced performance tuning for file operations when Elastic Layering is enabled. (UNI-72125)

  • Improved synchronization in Citrix Machine Creation for Nutanix connector so that snapshots cannot be taken prematurely before the VM power-up/shutdown cycle is completed. (UNI-71858)

  • Upgraded CentOS packages on the appliance, rectifying issues seen with Scale-Out File Server compatibility. (UNI-72257)

  • In the Firewall ports topic Internal connections table, the ports for the agent on the Hyper-V server have changed:

App Layering source Destination Activity Protocol Ports
Agent on Hyper-V server Appliance Disk download TCP 3012 (HTTP), 3512 (HTTPS)
Agent on Hyper-V server Appliance Disk upload TCP 3015 (HTTP), 3515 (HTTPS)

The correct ports are now listed for disk downloads (3012 and 3512). The ports for disk uploads are new in this release.

Fixed in App Layering 1903

No issues were fixed in this release.

Fixed in App Layering 1902

  • Print jobs disappear: The issue with print jobs has been fixed, and they no longer disappear. (UNI-72037)
  • Office activation fails if Windows isn’t genuine: The issue where Office activation failed has been fixed. (UNI-72186, UNI-71109)

Fixed in App Layering 1901

  • App layer creation issues with Trend Officescan are fixed: When creating an app layer for Trend OfficeScan for Server 2016, the driver and blue screen issues no longer occur. (UNI-71823)
  • When creating an Adobe Acrobat app layer, you no longer receive and error message: The following error no longer occurs when installing Acrobat in an app layer: “Adobe Acrobat Reader DC – Error 1321. The Installer has insufficient privileges to modify the file C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\AIR\nppdf32.dll.” (UNI-71082)
  • Error updating Autodesk Revit 2018 app layer has been fixed: (UNI-71084)
  • You can now configure SAS 9.4 after installing it on an app layer: After installing SAS 9.4, you can now configure the app without getting a blue screen.

Fixed in App Layering 1812

  • When importing an OS using vSphere connector, you get a more helpful message if DNS lookup fails: The new message states, “Failed to resolve host name in DNS. (UNI-69913)

Fixed in App Layering 4.15

  • Faster ALMC AD login times - You can speed up ALMC AD logins by using an LDAP attribute-based implementation. (UNI-67637)
  • Layer priorities preserved in exported and imported layers - The Import and Export features now preserve each layer’s priority. (UNI-68269, UNI-69477)
  • Destination folder added to Export layer audit log - The audit log for the Export layers feature now includes the destination folder where the layers were exported. (UNI-61661)

Fixed in 4.14

  • Networking issue when publishing images with Office 365 Session User layers: When publishing images with Office 365 Session User layers enabled, early registry virtualization no longer causes layered images to lose their network connections. (UNI-69309)
  • Importing layers no longer requires Write permissions on the source file share: (UNI-69211)
  • The type command issued in a Command window now displays the correct file contents: (UNI-68786)
  • More detailed error messages are returned when a connector configuration page cannot communicate with the Citrix App Layering agent: The error messages now include more detailed information for unreachable or invalid hosts and timeouts. (UNI-67677)
  • The image template Audit history now includes the Elastic Layering mode when the User layer is set to Office 365 Session: This information was missing in the previous audit history. (UNI-68739)
  • User layer custom notification messages now take precedence over the default messages: (UNI-69087)
  • Full User layers on Windows 10 and Windows 7: Changes to Windows indexing options now persist when you enable Full User layers on Windows 10 and Windows 7 desktops. (UNI-56064, UNI-56213)

Fixed in 4.13

  • Increased stability when upgrading Windows versions with User layers: End users assigned user layers can no longer mistakenly run out-of-date files from the previous version of Windows. Out-of-date files are now cleaned up after each Windows version upgrade. (UNI-68820)
  • MMC snap-ins work correctly with vSphere connector caching: When using vSphere connector caching for an App layer, MMC snap-ins no longer fail to launch. (UNI-68565)
  • Improved App-V compatibility: Multiple fixes are included in this release to improve App-V compatibility with App Layering. (UNI-68277, UNI-68753)
  • Azure connector added retries when importing an OS image into an OS layer: Due to throttling on Azure, some OS layer import operations were failing with the error, “server is busy.” The connector now uses fewer threads and retries the import several times. (UNI-67030)
  • vSphere connector can edit layers when datastore name has international characters: International characters are now allowed when editing layers that use a vSphere connector. (UNI-66983)

Fixed in 4.12

  • DHCP service does not start on published image: Windows registry permissions are now transferred correctly when publishing images where the target registry key exists already. (UNI-67359)
  • Connector configuration page displays stale information: With the latest versions of Internet Explorer on Windows 10, the connector configurations are now displayed correctly. (UNI-67341)
  • Saving PowerPoint files in a Dropbox folder caused errors: When the file size of a PowerPoint presentation gets smaller before saving it, users no longer receive an error if the destination is a Dropbox folder. (UNI-66923)

Fixed in 4.11

  • Windows 10 Store apps: Windows Store apps now work as expected.

  • Skype layer assigned as Elastic layer: Users no longer receive the following alert when starting an elastically assigned Skype layer for the first time: “The Installer has insufficient privileges to modify this file: URL”. If the user clicks Ignore, Skype opens as expected. (UNI-52164)

Fixed in 4.10

  • Network adapter icon: A red “X” network adapter icon indicates that there’s an issue even when the network is functional. You can ignore the red ‘X.’ (UNI-53443).