X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 246AB3858C2D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1707788816; bh=w11oOfA0H7gem9EzUOlCLA0J+DYt8tbA15eEyzcYDeU=; h=To:Subject:Date:Cc:In-Reply-To:References:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=VJjCOBycTM19Q0dNn3cIpIxGvi2UmHuUSgqAa6QEHfyV2fVaPgjb8EKqucUyxHgs6 a1uakq+WdxOCKIeVgEb3bEA7Rr5nbneJSTRkpb/WBR5KipQQxt6H5fSNvCQMKtwXHk 64h3gz/70L9kFdtz2mH0ym/ReZATq7rpvC2pFpEw= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 8E6683858D20 ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 8E6683858D20 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1707788796; cv=none; b=Idt3dv3DfCuw9PXKXqcf7TkcSUC3rq1oareiEpkK4TA9dhtILRf6S2E1nOJOxjoCiuOVFJVVj9so9oqCWLvOV5fi3gaJedST0b9f9O9M3b8GBkzeYkLMfk9chiNS6UrqT8tfOZbnJY/xwYWDCogntSybVnLycyJwpS4M/oUZWVw= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1707788796; c=relaxed/simple; bh=ctjCOk9PxCk+PQYvqTeR9JEMOPpGw0SOd2kJ/PDqzts=; h=To:Subject:MIME-Version:Date:From:Message-ID; b=lchjaEKa/TRr5pShvmI5pWcwF9sLOPkH7P2F9bJktWBMAZBPrUzgsNy8tqFVAs+cmNhoajxZCkMIvw2jfDije+RN2IQu07hZvXDUTvPo/pMXApa69+cDPye1zJDFeIaryrnZ2ucnoF7d8C/NbZuRqWWtmNKDnzOJJvOzZ9PW+6Q= ARC-Authentication-Results: i=1; server2.sourceware.org To: "matthew patton" , "Jon Turney" Subject: Re: Running setup-x86_64.exe from cmd does nothing but works from cygwin itself MIME-Version: 1.0 Date: Tue, 13 Feb 2024 01:46:32 +0000 X-Mailer: RainLoop/1.12.1 Message-ID: <3e65cdcf1473b8da41694be7bcc3bebc@wsnyder.org> Cc: cygwin AT cygwin DOT com In-Reply-To: <928526454.844616.1707773847101@mail.yahoo.com> References: <928526454 DOT 844616 DOT 1707773847101 AT mail DOT yahoo DOT com> <6075b5bacd6adcdcaa71b9f50991ee15 AT wsnyder DOT org> <65097791-0312-42d3-8972-ffe942ecd1ef AT dronecode DOT org DOT uk> X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00, HTML_MESSAGE, KAM_DMARC_STATUS, SPF_HELO_PASS, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-Content-Filtered-By: Mailman/MimeDel 2.1.30 X-BeenThere: cygwin AT cygwin DOT com X-Mailman-Version: 2.1.30 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: wsnyder--- via Cygwin Reply-To: wsnyder AT wsnyder DOT org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces+archive-cygwin=delorie DOT com AT cygwin DOT com Sender: "Cygwin" Downloading and running as administrator the uncompressed version from https://cygwin.com/setup/ (https://cygwin.com/setup/) solved the setup-x86_64.exe "doing nothing". Thanks for your help. February 12, 2024 4:37 PM, "matthew patton" )> wrote: > If you really suspect some AV problems, it may help to try the > uncompressed setup executable, available from [1] Huh, when did this start? Nobody pays by BW anymore so what was the rationale behind a "self altering" executable? No wonder it would experience havoc in an A/V environment since the extracted temp file may well be located on a non-executable location and or EXEC would have been shimmed by AV and it doesn't correctly return control from an ephemeral location. On Monday, February 12, 2024 at 02:44:16 PM EST, Jon Turney via Cygwin wrote: On 12/02/2024 01:05, wsnyder--- via Cygwin wrote: > I have a Windows Version 10.0.19044 Build 19044 system with Cygwin > installed a while ago. > > Opening the cygwin terminal (which works fine), I see it is running: > > CYGWIN_NT-10.0-19044 version 3.3.6-341.x86_64 (corinna AT calimero) (gcc > version 11.2.0 20210728 (Fedora Cygwin 11.2.0-2) (GCC) ) 2022-09-05 > 11:15 UTC > > I needed to install some packages so downloaded setup-x86_64.exe onto > my desktop. When I run it from the desktop I get the "busy" cursor > for a fraction of a second and nothing happens. When I open the > native Windows cmd prompt as administrator, and run > "setup-x86_64.exe" or "setup-x86_64.exe -v" or "setup-x86_64.exe > --asdjasdjaskdhj", I just get the prompt back. > > If, however I startup the cygwin terminal (vs cmd window) and run > setup-x86_64.exe, it starts correctly. However I'm afraid to run it > this way as if it crashes I'll presumably never be able to run setup > again. This seems highly speculative. > This is a work machine so while I have admin, it's completely > possible they've added some broken virus checker rule that is now > preventing it from running. But, I get no alert, which I normally > would doing something unusual, and that it works under cygwin itself > seems odd. This is very odd behaviour. If you really suspect some AV problems, it may help to try the uncompressed setup executable, available from [1] [1] https://cygwin.com/setup/ (https://cygwin.com/setup/) -- Problem reports: https://cygwin.com/problems.html (https://cygwin.com/problems.html) FAQ: https://cygwin.com/faq/ (https://cygwin.com/faq/) Documentation: https://cygwin.com/docs.html (https://cygwin.com/docs.html) Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple (https://cygwin.com/ml/#unsubscribe-simple) -- 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