Trouble installing to UNC path and/or mapped network drive

Erik Soderquist
Mon Aug 22 16:48:00 GMT 2016

On Mon, Aug 22, 2016 at 5:57 AM, Andreas Wettergren wrote:
> The computer I’m using to launch the setup from is running Windows 7 Professsional (64 - bit).
> I’m using setup-x86.exe version 2.874.

Why 32 bit rather than 64 bit in a 64 bit environment?  (more curious
than anything else, I don't think this affects the outcome).

> Antivirus (Webroot SecureAnywhere) is disabled, but not completely unloaded, during setup.
> (I have permissions to disable Webroot via a control applet, but I don’t think I’m allowed to unload it completely)

Do you have the option of creating a couple virtual machines to test
with virgin Windows installs?  That could relatively quickly determine
if it is something in the exiting environment...

> First I tried using an UNC path, but this does not work at all,
> the setup program complains that the UNC path is not an absolute path.
> (Should this be considered a bug?  If so I will rerun the setup, get the exact error message and report it separately.)

I believe this is expected, but will leave the final determination to
others with greater knowledge than I.

> To work around this, I mapped a network “drive” in Windows Explorer.
> The drive is mapped so that my target directory is Z:\Cygwin.

Did you set the drive mapping to be remembered on future logins?  If
not, a new instance after privilege elevation may also not have the
drive mapping.  (Still might not, I've had UAC/network drive mapping
problems with other programs as well).  Is disabling UAC and running
entirely as local admin to test an option?  For that matter, is
installinng on the host the installation is local to an option?

> The symptoms begin with an error saying something like “Unable to extract /etc/ -- the file is in use.” plus a suspicion about a corrupt package.
> Skipping past this error gives an almost identical error but about “/etc/postinstall”,
> and skipping that gives another about “/etc/postinstall/”.

When was the most recent filesystems check on the host with the actual
files?  A corrupt directory tree can cause similar issues.

-- Erik

Problem reports:
Unsubscribe info:

More information about the Cygwin mailing list