public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin@cygwin.com
Subject: Re: setup-x86_64.exe does not start in win10 20H2
Date: Fri, 10 Dec 2021 22:38:45 -0700	[thread overview]
Message-ID: <61da59e2-19d1-95bc-ad91-2011d4fa52e8@Shaw.ca> (raw)
In-Reply-To: <05271369832b451a9c7c9aec9e533bd7@analog.com>

On 2021-12-10 13:19, Kutty, Rejeesh wrote:
>>> Renamed that DLL -- same behavior, and same  access violation in WinDbg.
>>> Killed all Beyond Trust Services/Tasks -- same behavior.

You will probably need to restart Windows after any changes in order to 
unload or reload DLLs and associated data.

>> Does WinDBG still show the DLL loaded?

 > No it didn't, but it reported access violation after RPCRT4.dll.
 > (This is the RPC API, as per google).

Many of these apps have difficulty handling dynamic modification, 
cleanly removing themselves from the call or message chains they insert 
themselves into, transparently passing along arbitrary calls, data, 
events, or messages, especially when application code is multithreaded 
and reentrant using mutexes and waits.

Beyond Trust is on the Cygwin Big List of Dodgy Apps: poorly written 
(often so-called "anti-malware", "anti-virus", or "security") software 
that monitors, logs, blocks, and/or interferes with normal operation of 
many applications, with effects sometimes indistinguishable from 
malware, and known to prevent Cygwin working properly; see:

	https://cygwin.com/faq/faq.html#faq.using.bloda

Beyond Trust has caused problems because its certs became outdated 
unless you kept the product and its certs updated. Try updating the 
product and check its certs are up to date in the cert store.
If that fails you may need to raise a case with the product vendor 
regarding Cygwin 64; especially useful to mention:

	https://www.cygwin.com/faq.html#faq.api.fork

-- 
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.
[Data in binary units and prefixes, physical quantities in SI.]

  reply	other threads:[~2021-12-11  5:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-10 14:39 Kutty, Rejeesh
2021-12-10 14:55 ` Marco Atzeri
2021-12-10 16:45 ` Ken Brown
2021-12-10 17:12   ` Kutty, Rejeesh
2021-12-10 18:28     ` Ken Brown
2021-12-10 18:38       ` Kutty, Rejeesh
2021-12-10 20:17         ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2021-12-10 20:19           ` Kutty, Rejeesh
2021-12-11  5:38             ` Brian Inglis [this message]
2021-12-13 23:26               ` Kutty, Rejeesh
2021-12-14  6:17                 ` Brian Inglis
2021-12-14  6:31                   ` Marco Atzeri
2021-12-14  8:09                     ` Brian Inglis
2021-12-10 15:19 Kutty, Rejeesh
2021-12-10 15:30 ` Marco Atzeri
2021-12-10 15:39   ` Kutty, Rejeesh

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=61da59e2-19d1-95bc-ad91-2011d4fa52e8@Shaw.ca \
    --to=brian.inglis@shaw.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).