From: "Kutty, Rejeesh" <Rejeesh.Kutty@analog.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: setup-x86_64.exe does not start in win10 20H2
Date: Fri, 10 Dec 2021 20:19:50 +0000 [thread overview]
Message-ID: <05271369832b451a9c7c9aec9e533bd7@analog.com> (raw)
In-Reply-To: <DM8PR09MB70957E60F9999E146024DCCDA5719@DM8PR09MB7095.namprd09.prod.outlook.com>
No it didn't, but it reported access violation after RPCRT4.dll.
(This is the RPC API, as per google).
-----Original Message-----
From: Lavrentiev, Anton (NIH/NLM/NCBI) [C] <lavr@ncbi.nlm.nih.gov>
Sent: Friday, December 10, 2021 3:17 PM
To: Kutty, Rejeesh <Rejeesh.Kutty@analog.com>; cygwin@cygwin.com
Subject: RE: setup-x86_64.exe does not start in win10 20H2
[External]
> Renamed that DLL -- same behavior, and same access violation in WinDbg.
> Killed all Beyond Trust Services/Tasks -- same behavior.
Does WinDBG still show the DLL loaded?
Anton Lavrentiev
Contractor NIH/NLM/NCBI
next prev parent reply other threads:[~2021-12-10 20:19 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 [this message]
2021-12-11 5:38 ` Brian Inglis
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=05271369832b451a9c7c9aec9e533bd7@analog.com \
--to=rejeesh.kutty@analog.com \
--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).