Citrix Fixes – App Layering

A list containing the majority of Citrix App Layering support articles collated to make this page a one stop place for you to search for and find information regarding any issues you have with the product and its related dependencies.

The page is updated daily with new support articles and information. Articles will change from time and if information here is outdated or incorrect please let me know using the comments. Links may also expire or change so if you find broken links, please again let me know. For each issue, known product versions affected are recorded however that does not mean products versions that aren’t listed are not affected.

There is a search box that you can use if looking for a specific fault. For example if you have an error code or error message, use that to perform a search. You can also use your browsers search feature which will perform a search against the whole page based on the words you enter.

App Layering:

wdt_ID Brief Description of Issue Brief Description of Fix Applicable Product Versions Affected (if known) Link to supplemental Support Article(s)
18 Published image (Unidesk Desktop) or Packaging Machine blue-screens with STOP code 0x75640007. This STOP error comes from the App Layering Filter driver. It specifically means not all of the required layers were mounted within 10 minutes. As the layers should appear instantly when Windows boots up, Citrix assumes there is a problem and blue-screens the machine so that the process can be retried. The most common cause for layer mounting failures are policies/software blocking access to removable drives.
19 When installing the App Layering Agent on a PVS server that has a French Windows OS installed, you receive the following failure message: "An error occured when executing netsh". The agent still installs, however you must manually perform the steps that have failed. Assign and SSL Certificate to port 8016 and manually run NETSH as an administrator.
20 Whilst logged on to the App Layering Management Console, you get unexpected errors and disconnects. From the console you may also see "Connectivity Failure" or "No connection to Layering Service". Reboot the Enterprise Layer Manager appliance. This allows the internal services to reconnect to each other and is the most likely solution. Citrix App Layering 4.x.
21 Windows 10 major upgrade may result in new Recovery Volume partition. Make sure to remove the volume using diskpart before finalising the OS Layer. Failure to do so could result in desktops failing to boot correctly. This also applies to booting Virtual Machines via PVS.
22 "SYSTEM_THREAD_EXCEPTION_NOT_HANDLED CVhdMP.sys" message when booting images created by App Layering via Citrix Provisioning Services. Check that there are no ghost network adapters in the image.
Check the NIC slot number if using VMware ESX.
Make sure the Target Devices hardware is not too different from the Packaging Machine.
Check the publishing Platform Layer Hypervisor version is set correctly for the Hypervisor you are using.
Make sure E1000 NICs are not being used.
24 When publishing an image to PVS, you receive the following error: "A failure occurred while publishing the image to PVS server servername (servername.fqdn). Error: The operation being requested was not performed because the user has not logged on to the network. The specified service does not exist. (Exception from HRESULT: 0x800704DD)". Uninstall then install the App Layering agent again. Try running the install media locally instead of over the network.
25 You receive various App-V related issues including publishing issues. Upgrade to App Layering 4.4+ Citrix App Layering 4.2 and 4.3.
26 Unable to import Windows 10 gold image into App Layering. During the import job, you receive the following error: "The CachePoint Appliance could not import the gold image VM to create the Operating System Layer. Error is: Failed to copy folders recursively". The import fails if the gold image has Windows Updates from Feburary 2017 and newer installed. From the gold image, delete file "Microsoft.MicrosoftOfficeHub".
27 When trying to create or edit a connector, you receive a "Authentication Failed (401)" error. This is a problem caused by long-running Active Directory queries inside the ELM appliance create a database lock that causes the rest of the connector transaction to timeout. Upgrade to App Layering 4.3+. This version introduces some improvements however some issues still remain.
28 When clicking the search box within Outlook 2016/2013 in an Elastic Layered image, a prompt for credentials is displayed and an installer launches and hangs. Install the Windows Search Service in a new OS Layer version.

Leave a Reply