X-Recipient: archive-cygwin AT delorie DOT com X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 953DF3858D39 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=Shaw.ca Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=shaw.ca DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=shaw.ca; s=s20180605; t=1639201126; bh=H51thVRO5A+twCEwJ9yORkGt8NqAsq6WrH7BMJnSloQ=; h=Date:Reply-To:Subject:To:References:From:In-Reply-To; b=OEwm3gnW7veIG6et0bPIxC1F2Nw35kDKyCBnkUl4LW++5CPclOZwxKZVxzZYiN2Ec zRmxsfBh1C5vOZnDcwrmRmYhllNXCDxwjird79Tq14Txbqu/5Hv/x3fFM15WFFWBPa pB5mHJ6EiD7lBoyCLoPrc2XTAwDXiW3oMfmq9tR9E2VIwNdx53cP5xjoMhdK/EvWJ2 wNCxk+vz1O0/DtBuryO157N07bDHOq4OotRZnZ1jJ02X2iaC9xvjFsTLRPW+RPSLPv A6xuu7cxOt0xFuHV/MMp7RMi/fCmXyiGp9/ZpNvEBarafjf0cAcpSjGsDwwGNe//l/ ElTMze+mEluxQ== X-Authority-Analysis: v=2.4 cv=FrgWQknq c=1 sm=1 tr=0 ts=61b43966 a=T+ovY1NZ+FAi/xYICV7Bgg==:117 a=T+ovY1NZ+FAi/xYICV7Bgg==:17 a=IkcTkHD0fZMA:10 a=w_pzkKWiAAAA:8 a=aPmGuZd-kSG-VUfIlncA:9 a=QEXdDO2ut3YA:10 a=9c8rtzwoRDUA:10 a=nWb9qXfGVYYA:10 a=sjVPaHIGsnYA:10 a=sRI3_1zDfAgwuvI8zelB:22 Message-ID: <61da59e2-19d1-95bc-ad91-2011d4fa52e8@Shaw.ca> Date: Fri, 10 Dec 2021 22:38:45 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.3.2 Subject: Re: setup-x86_64.exe does not start in win10 20H2 Content-Language: en-CA To: cygwin AT cygwin DOT com References: <4abe6a0550a842a78a991b9fd9f0a730 AT analog DOT com> <12db1d2b25d34c38b10889f66c6c674d AT analog DOT com> <5812b09e-4e95-0b12-d5f8-f90b7a910494 AT cornell DOT edu> <509d6dd350d140618d53d93081742abb AT analog DOT com> <05271369832b451a9c7c9aec9e533bd7 AT analog DOT com> From: Brian Inglis Organization: Inglis In-Reply-To: <05271369832b451a9c7c9aec9e533bd7@analog.com> X-CMAE-Envelope: MS4xfB8Be5sCKnQTL9FcO12uXNyy54dQwENcEq9lsicTAt4OBPKL+0KZk/DhODmtRtGn+jFd38YssBJuvrgfJezswbwbwk10goVgNhgQa2fDY2t01aCCJh6Z z4sb1NziBb9A9Hxagm42UXCxDAYRqUlk9fWA6B3BIpMLeq4Ve3dyK7V6YvlR/bCpmdU2CSvbWXh0Tw== X-Spam-Status: No, score=0.3 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, KAM_NUMSUBJECT, NICE_REPLY_A, RCVD_IN_BARRACUDACENTRAL, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H4, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Brian DOT Inglis AT Shaw DOT ca Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" 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.] -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation: https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple