From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: 64 bit setup fails to run on WIndows 10
Date: Tue, 12 Mar 2019 00:43:00 -0000 [thread overview]
Message-ID: <70d433af-48ea-49d5-4943-6701f0a91805@SystematicSw.ab.ca> (raw)
In-Reply-To: <CAKcYCGLghyPYj72QtJ_kDgZz487R9khn4hUp00sxPF9KF-w7Sg@mail.gmail.com>
On 2019-03-11 15:39, Adrian Blakey wrote:
> Any ideas why the 64 bit setup program fails to run at all on my corporate
> Windows 10 laptop, whereas the 32 setup runs fine?
>
> The symptoms are whenever I run it either from the finder or from the
> command line it does not initialize or produce any output.
>
> The machine is modern Lenovo Thinkpad that's only a couple of years old.
> it's running:
>
> Windows 10 Enterprise V 1703 OS Build 15063.1631 64 bit.
>
> I believe I have admin rights however even if I try to run it with
> --no-admin it makes no difference - it simply does not execute. I have
> noticed the same behavior with a couple of other open source windows
> installers.
Remove the downloaded file's Alternate Data Stream Zone.Identifier or Unblock in
file properties, and make executable, then check for other impediments in
Cygwin's Big List Of Dodgy Apps
https://www.cygwin.com/acronyms/#BLODA
at
https://cygwin.com/faq/faq.html#faq.using.bloda
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2019-03-12 0:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-11 21:39 Adrian Blakey
2019-03-11 21:49 ` Achim Gratz
2019-03-12 0:43 ` Brian Inglis [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=70d433af-48ea-49d5-4943-6701f0a91805@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).