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
	:content-type:content-transfer-encoding; q=dns; s=default; b=CAR
	JT8ltLHpncwd0o5yhMiofSU8esbHAu3VQ3p83MRT/IpBtKVLNsyyQwhD7R/+rkKL
	GOTQ7R1JmwkTLmazbVGSTNKEDA/AbHNEaZ/IvZ4v17VjHkFA7CqxkMn/+fpswsqB
	wgo370tSpJmjiiWHUNsnkSDfDCEO7hl/bXLZ1T6U=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <581A0AA5.5030107@verizon.net>
Date: Wed, 02 Nov 2016 11:47:49 -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: Windows 10 updates causes fork retry no child processes
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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.

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