The Microsoft App-V Team Blog

The official blog for Microsoft Application Virtualization

Fix: Error xxxxxxx-xxxxxx0A-0000E01E launching Cygwin for Windows when sequenced using Microsoft App-V

Fix: Error xxxxxxx-xxxxxx0A-0000E01E launching Cygwin for Windows when sequenced using Microsoft App-V

  • Comments 1
  • Likes

Toolbox3You may run into an unusual issue when running a virtualized sequence of Cygwin under Microsoft Application Virtualization (App-V).  The application will sequence correctly and launch both during the Monitoring phase and the Launch phase, however when you attempt to launch the application in any deployment context you will get the following error:

The Application Virtualization Client could not launch Cygwin Bash Shell 1.0.

An unexpected error occurred. Report the following error code to your System Administrator.

Error code: 46027C5-16D1190A-0000E01E

Cause

While this error indicates that the sequenced application package might be corrupt, simply re-sequencing the package alone will not resolve the issue. The issue is tied to the fact the environment’s working directory must be initiated under a modifiable file system context.

In the case of the Cygwin Bash Shell, it will create a directory under <MNT>\Cygwin\Home\ for the username (which will then get redirected to the PKG file once sequenced properly.)

Resolution

There are two ways to successfully sequence Cygwin:

Prior to Sequencing, create an exclusion for the Sequencing Drive and the Cygwin home directory. If you are sequencing to Q:, you would add in the following path:

Q:\cygwin.001\cygwin\home

(This assumes you are sequencing to Cygwin.001 as the mount and the install directory is Q:\c ygwin.001\cygwin)

If you want to modify the package, you will need to Edit the package and under files, change the attributes for the Q:\<MNT>\Cygwin\home path to de=select override and change the type to “User Data.”

Hope this helps,

Steve Thomas | Senior Support Escalation Engineer

The App-V Team blog: http://blogs.technet.com/appv/
The WSUS Support Team blog: http://blogs.technet.com/sus/
The SCMDM Support Team blog: http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
The OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/
The SCVMM Team blog: http://blogs.technet.com/scvmm/
The MED-V Team blog: http://blogs.technet.com/medv/
The DPM Team blog: http://blogs.technet.com/dpm/
The OOB Support Team blog: http://blogs.technet.com/oob/
The Opalis Team blog: http://blogs.technet.com/opalis

clip_image001 clip_image002

Comments
  • I have performed both of these steps in several different scenarios and still have not been able to get pass this error message. Any other possible issues?

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment