X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=jp9f7JTZZ3gcgJ7Difb1TSDmBQBCj9ZY5wNf7oOiaIT
	fK9vRX2L5xieOEhUZ/3g1pQvW3EY3m51btS4yez17vZSSnD+dIlk8j2vglPr/xi6
	9QS0SQQjLgLKMCHDvMOQnbt7T8hfRCf+8zWnbi2tO5fVOdP46CaBCFI4jE1wN+sw
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=zKJdsA29hyXf+z/Ari0wwiLzhVA=; b=tvqZx3lh0Xk4F/lR2
	yAKvIYQ5Wlc0oif3HmKjTnSNTCJUQY11l4eOUnNK51A0c5lNl0EOB+czbywfg2ye
	uoETYb1ScHkDv4cLiEaN9HXpH+KjPWUKBmATuO+tTfY3GK1aA4TT0l6/GYdEUE6d
	nxxWFY/ZHQwe6iuxlyLKoWIGxE=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM,SPF_PASS autolearn=no version=3.3.2 spammy=wishes, H*RU:sk:omr-a01, Hx-spam-relays-external:sk:omr-a01, H*f:sk:f8327d4
X-HELO: omr-a014e.mx.aol.com
Message-ID: <581A7F49.5040902@verizon.net>
Date: Wed, 02 Nov 2016 20:05:29 -0400
From: Gerry Reno <greno AT verizon DOT net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: Windows 10 updates causes fork retry no child processes
References: <581A0AA5 DOT 5030107 AT verizon DOT net> <f8327d4c-37cd-9afb-824c-1a5ce96bfc89 AT yandex DOT ru>
In-Reply-To: <f8327d4c-37cd-9afb-824c-1a5ce96bfc89@yandex.ru>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
x-aol-global-disposition: G
x-aol-sid: 3039ac1adecd581a7f4a511a
X-AOL-IP: 47.196.166.20
X-IsSubscribed: yes

On 11/02/2016 01:31 PM, Evgeny Grin wrote:
> On 02.11.2016 18:47, Gerry Reno wrote:
>> Is there some automated way I can stop Windows 10 updates from continuously causing these fork retry no child process
>> issues after every damn update?
>> We use an application based on Cygwin (2.6.0) on our clients that gets wrecked everytime a Windows 10 update occurs.
>> The users have no idea about Cygwin because it's hidden from them so I cannot ask them to do anything with regard to Cygwin.
>> .
>> Any ideas for an automated way to stop these errors would be appreciated.
> Seems that you have two options:
> * Ask Microsoft to stop breaking Windows in Preview builds (according to
> my personal research - Windows unloads wrong .DLL instead of requested .DLL)
> * Ask your clients not to use Insider Preview because of "beta nature"
> of those builds.
>
> --
> Best Wishes,
> Evgeny Grin
Thanks for trying to help.
Nobody is using Preview builds.



--
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