I haven't been using App-V for very long so I'm sorry if some of my nomenclature is incorrect here.

I'm trying to sequence Cygwin 1.79 on a Windows 7x64 box with a Q: asset folder. I set the sequence folder to Q:\Cygwin1.79 to avoid some of the potential 8.3 issues I've read about and to keep available for future upgrades.

When I do the actual Cygwin install, I've been trying to install to the same folder of Q:\Cygwin1.79. When I do this, I get an error of:

The Application Virtualization Client could not launch Cygwin Bash Shell 1.0
Error code: 4617581-16D1160A-0000E01E.

I've looked up the error and everywhere I could find. Most subjects refer to setting exceptions to Q:\<MNT>\Cygwin\Home and setting the home directory to user data / no override.

I've done that to no avail.

I've installed to Q:\Cygwin1.79, Q:\Cygwin1.79\Cygwin... no variation works unless I just let the install go directly to the C:\Cygwin as is default. I'm hesitant to do this as it is not best practice but I do not know what else to do. Any ideas of what could be going wrong?

I've also made sure that UAC is turned off among with a couple other tweaks to the registry (for 8.3 and a setting that escapes me right now about the UAC virtualization setting in the local system security of the sequencing box).

Anything anyone can offer as a thought would be greatly appreciated.
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Hi superhumanben,

may the Client did not allow the 8.3 file and folder name creation. See this post on www.kirkx.org for more details.

Happy sequencing!
Answered 07/31/2011 by: vkleiner
Orange Senior Belt

Please log in to comment
I've done this. Changing the registry, changing the name of the sequenced path to just Q:\Cygwin... nothing works. Here are the two other main articles I've referenced and tried numerous ways.


Answered 08/01/2011 by: superhumanben
Yellow Belt

Please log in to comment
If you can't get it working with a Mount Point (MNT), then it is prefectly acceptable to install to Virtual File System (VFS).
That functionilty is there for a reason.

It was advised against as the redirection of a VFS to the correct locations can cause launch delays - but in reality it should be barely noticable, if at all, to your end-users.

Hope that helps,

Answered 08/01/2011 by: dunnpy
Red Belt

Please log in to comment