X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=tYHOzmSDTfgvBWWiczVcJ2HI3GTnN9KZTkoUiz45ZnNzSXL5csj4L
	NuUiCUGYaInGsW2/UV0ichqnOoSwCUwu3jm9xVj3jp7ORCOMA/bMl0fLRgfQz/or
	nTIg7uSW0aFbaV1X8/YiwODF+q0rmWIGWjHFOSIZxeYq+cp7OyT6Wc=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=3Ecg6uwM+od5dHxS/vE7u8k5YLs=; b=rV34KV1YmGqX6pY5cFKPABtZQmvA
	OdmR30EJEZlfJnWrzrxnTQx7MilaKPZMEn0I09p0ncghERu6/TDPjdV0yvte8Kb7
	RbAB7NzYNcFqimHN+M8nsIQ//rFNzIN2HM1q4qQqgpGgoZ6gLw4nKIE7j3AHMF+O
	7TsR/ZfanRo459k=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-5.9 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.2
X-HELO:	calimero.vinschen.de
Date:	Tue, 22 Apr 2014 13:51:46 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: Mount / Access is Denied
Message-ID:	<20140422115146.GG2339@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<CAE2r_FTL8EVGp_TdidOsiqE3zkh0Vk239-7Q2k8okmjRALuDDw AT mail DOT gmail DOT com> <53532F13 DOT 9060905 AT gmail DOT com> <CAAeCd-NVYpshL-StL7zW0WN3m9Wt=DicbjYfL=5y85-xh5rQWQ AT mail DOT gmail DOT com>
MIME-Version:	1.0
In-Reply-To:	<CAAeCd-NVYpshL-StL7zW0WN3m9Wt=DicbjYfL=5y85-xh5rQWQ@mail.gmail.com>
User-Agent:	Mutt/1.5.21 (2010-09-15)

--sgneBHv3152wZ8jf
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Apr 20 12:25, Robert Pendell wrote:
> On Sat, Apr 19, 2014 at 10:21 PM, Zeranoe wrote:
> > On 3/8/2014 12:50 AM, Cicero Silva Luiz Junior wrote:
> >>
> >> My OS is Windows 8.1 x64. UAC is on, behavior set as Prompt for
> >> Credentials on Secure Desktop. Only elavate executables that are
> >> signed and only elevate apps in secure locations settings are both on.
> >> Any help is greatly appreciated.
> >
> >
> > I just ran into this issue too.
> >
> > Everything worked fine on Windows 7 SP1 64-bit, but the same command on
> > Windows 8.1 fails with the same error.
> >
> > I'm using --no-admin, and have write access to the root and local folde=
rs.
> >
> > This seems to be a Windows 8.1 (maybe 8 as well) issue.
> >
> > I would be happy to provide any further information about this, but
> > currently the command line method is useless on Windows 8.1 unless you =
have
> > admin privileges.
> >
> > Thanks,
> >   Kyle
> >
>=20
> I was able to reproduce this as well on a lab machine at work that we
> have Windows 8.1 x64 Update 1 loaded on.  It seems to throw the error
> as soon as it goes to switch to installing the files and as suggested
> only happens with --no-admin set.  There are no files unpacked as a
> result.  There is no BLODA on my test machine as it is a clean install
> save for updates in itself.  I'm going to test again on a VM later on
> when I get a few minutes to run the install though and verify.  The
> setup.log provided no appreciable information beyond what was provided
> by the OP however if there is a way to up the verbosity I am more than
> willing to re-run the install.

It's definitely a bug in setup.  Or rather, two bugs.  What happens is
that a registry key cannot be created in HKLM.  The fact that setup
tries to create the key in HKLM even if the current user has no admin
rights is the first bug.  The second one is that the inability to create
the registry key results in fatal error handling, exiting the application.

Maybe some default permission handling changed in later Windows versions
which trigger the problem but still, it's a bug in setup in the first
place.

I applied a patch to setup.  A new version will be available soon.


Corinna

--=20
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--sgneBHv3152wZ8jf
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJTVlfSAAoJEPU2Bp2uRE+gfEAP/0PnCAopgiIZU+HpqdijWeia
N2t6SnbvyQwhzgnij32NllqqDfJAYWqYF2cU5DrxcpqevObKPBXWt+ZoyaTDoQ4K
cMFUD0A1wMPPqmuoG9UUhcy6ipLdJUG/oT8XQNGWdg28DdnW/+8DVsYc2/6vZZTe
4uHPwz07XFekXmZ1jNFkEdgcvqM76RXHFF4raQ+uwtO/iyWZ+vFUSnaVYksOTcwY
2pHNHgb/KRgnRDaczV9nOacPakANjVRclGwBQBO72CfJy0+1lm/l3ZK7kcNTXYCF
Mm/il9tNvjmFilGAjSxPqdrGP0uga3JEAwLnFHeRrs4mmOB2XYvvwHKMJCvLkueD
0VmuYMPwjeT3bg2JZKbiDBPULpP4+Lz5EVqUEv3Qk0r/YMYRuQOuFEQMn1ht0RSe
xo+QUa/URCbuvJjaMuHEG7ZRPJ22cM0ABYq+eWuVsUrBR8JGOrnNZc2sNZH/0bnC
3t5Q6VcvRpIkZvCl37hpreyRb+CQ6yIHgGUv/6gVw5twnvSeveZkJiQL9jT/XQz+
sAf4SLe1ToVXxuXtSy97OG+W4B9KPDA1fw9tfQG7VLrAmXZqZRzK9iSSI9PHWGUK
GSpNSO68IBFJdszLJSUdzuR3vdXeqaCS++AlK8VMM76VN3h6YcqY15klxbo/dxt4
sghxFy3mV/tz2zkJWX1O
=tUn5
-----END PGP SIGNATURE-----

--sgneBHv3152wZ8jf--

- Raw text -