From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 101365 invoked by alias); 27 Feb 2019 06:55:35 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 100653 invoked by uid 89); 27 Feb 2019 06:55:34 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-1.1 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,KAM_NUMSUBJECT,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=pcs, corporate, disturbing, auditors X-HELO: smtp-out-so.shaw.ca Received: from smtp-out-so.shaw.ca (HELO smtp-out-so.shaw.ca) (64.59.136.137) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 27 Feb 2019 06:55:32 +0000 Received: from [192.168.1.114] ([24.64.172.44]) by shaw.ca with ESMTP id yt7pgnbYzoK5Kyt7qgmvei; Tue, 26 Feb 2019 23:55:30 -0700 Reply-To: Brian.Inglis@SystematicSw.ab.ca Subject: Re: Cygwin 3.0.1-1 Breaks ALL cygwin applications on Windows 7 x64 To: cygwin@cygwin.com References: <9e344bdc-758b-5711-b25a-1ed2e46952be@yahoo.com> <746a01c6-0faf-aff3-51e6-c0e129a56cc4@yahoo.com> <110b2dfb62fa274469d2d2fae586fb99@smtp-cloud7.xs4all.net> <66C04238-FC33-4926-952D-775BF5DEBE2C@solidrocksystems.com> <06d6e35d-b645-61c2-089b-8256194168ef@yahoo.com> <35062835-c3cd-799e-d13a-16f954db2a19@yahoo.com> From: Brian Inglis Openpgp: preference=signencrypt Message-ID: <02f492d9-b334-1dab-aedb-17a747ede36b@SystematicSw.ab.ca> Date: Wed, 27 Feb 2019 07:26:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1 MIME-Version: 1.0 In-Reply-To: <35062835-c3cd-799e-d13a-16f954db2a19@yahoo.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2019-02/txt/msg00473.txt.bz2 On 2019-02-26 16:00, Jerry Baker via cygwin wrote: > On 2/26/2019 2:48 PM, Doug Henderson wrote: >> Good. This tells us something important. Right after the path listing, >> cygcheck list "Output from C:\cygwin64\bin\id.exe". The id exe is a >> cygwin exe which uses cygwin1.dll, cygintl-8.dll, and cygiconv-2.dll. >> That narrow the problem. These three DLLs might have been corrupted, >> or something is interfering with their correct operation. >> See BLODA: See https://cygwin.com/acronyms/ >> Check the list of BLODAs to see if you are running one of those. > It's just cygwin1.dll for sure. I can replace that with 2.x version and > everything works fine. > I don't recognize most of the BLODAs and not running any of them that I know of. > Are there any software packages known to interfere with 3.0 and not 2.x? >From what you said elsewhere, it sounds like you run an Enterprise image, so your org may have omitted components, features, or products essential to running Cygwin, may have added components, features, products (like many poor "security" solutions), or set policies inimical to running Cygwin. Compatibility of any specific release of any software product with any given enterprise image configuration requires adequate testing to ensure required dependencies are included in the image configuration. In addition, PCs with recent AMD and Intel CPUs, chipsets, and motherboards, and other newer hardware, are only supported under Windows 10 Enterprise, with support for selected enterprise vendor systems with Skylake CPUs under Windows 7, and nothing newer. A minimal datapoint might be running "cygcheck cygcheck" under cmd, with whatever explicit path is required to get the executable to run, and posting the output. If that works, then if you could try running "cygcheck -hrsv > cygcheck.out" under cmd, with the same path, and attach the output file as a text/plain attachment, that would help diagnose the problem. As Cygwin is a rolling release system, if you are not running current releases, some CVE security issues may remain unpatched, and your system may not be compliant to your corporate security policies (you may want to check with your IT security and/or IT auditors). -- 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