From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 59994 invoked by alias); 3 Nov 2016 13:46:20 -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 59469 invoked by uid 89); 3 Nov 2016 13:46:19 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.5 required=5.0 tests=BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RP_MATCHES_RCVD autolearn=ham version=3.3.2 spammy=moss, Moss, HX-HELO:sk:mailsrv, H*r:sk:mailsrv X-HELO: mailsrv.cs.umass.edu Received: from mailsrv.cs.umass.edu (HELO mailsrv.cs.umass.edu) (128.119.240.136) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 03 Nov 2016 13:46:15 +0000 Received: from [10.154.243.44] (ip-80-113-15-100.ip.prioritytelecom.net [80.113.15.100]) by mailsrv.cs.umass.edu (Postfix) with ESMTPSA id AA7614387360; Thu, 3 Nov 2016 09:46:13 -0400 (EDT) Reply-To: moss@cs.umass.edu Subject: Re: Windows 10 updates causes fork retry no child processes References: <581A0AA5.5030107@verizon.net> <0d98a082-e270-659f-5b48-b9dfd01fc85f@SystematicSw.ab.ca> <581AD3D3.2020908@verizon.net> <9619f42f-e8c8-c48c-fd6d-48e8bf33789d@SystematicSw.ab.ca> <581B3ECE.1030000@verizon.net> To: cygwin@cygwin.com From: Eliot Moss Message-ID: <26dcb6b4-f4fb-18ff-d259-d18383b0e967@cs.umass.edu> Date: Thu, 03 Nov 2016 13:46:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <581B3ECE.1030000@verizon.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2016-11/txt/msg00023.txt.bz2 On 11/3/2016 9:42 AM, Gerry Reno wrote: > We are only seeing this on the newer W10 machines. > W8 machines don't exhibit this problem. > And both have the exact same set of software installed on them. > So there must be something different about W10. Windows 10 is definitely aggressive about forcing reboots after updates. I've not yet found an effective way to turn it off so that I can do it at a more convenient future time. This changed some (harder to turn off auto-restart) with W 10 Anniversary Edition. Regards - Eliot Moss -- 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