DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=ZNAnqRNZxeRtGFHj
	Vxol9SGXd5I4B8r5Hhf0iY8HSNtDz9MvzLfLUkx8PvCZlqbaY+vBmtoD7Aglqgga
	BP1TR2LwtR2e/ScTijqeLudh3vDnvxYFTUSNROjv3l2jRqxi4e93JLlZaL8dtu5g
	ikiWEAmAGOoEQLlnsYPcF1B01GU=
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
Subject: Re: headache on build repeatibility: octave vs BLODA ?
To: cygwin AT cygwin DOT com
References: <2904b4fa-6349-bd3e-c4ff-4b32a0bb3838 AT gmail DOT com> <87y2tvs278 DOT fsf AT Rainer DOT invalid> <87h80febmg DOT fsf AT Otto DOT invalid>
From: Marco Atzeri <marco DOT atzeri AT gmail DOT com>
Message-ID: <6143b338-38ca-6157-711d-fae6ef431297@gmail.com>
Date: Tue, 28 Jan 2020 21:04:10 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.4.2
MIME-Version: 1.0
In-Reply-To: <87h80febmg.fsf@Otto.invalid>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Am 28.01.2020 um 18:25 schrieb ASSI:
> Achim Gratz writes:
>> Same thing here…
> 
> Since some of the discussion revolved on Windows versions: that is on
> Win10 Pro 1909, fully patched.  I no longer have a system with 1809
> since the period where you could hold up the update has expired
> recently.  There is an ISO image for Windows Server 2016 LTS
> (essentially 1709 I think) that you can use for free for 90 days (you
> can install it into a VHD and then boot that).  To (offixcially) get other Windows
> versions for testing you'd either have to have the licenses or have some
> sort of subscription with MSDN.  If you do have older install media or
> ISO, then of course you can do the install into the VHD trick again.  A
> Win 10 Pro can boot the VHD in a Hyper-V instance.
> 
> 
> Regards,
> Achim.
> 

Ok Achim,
you destroyed my theory

I just found that my W10 Home is 1909 build 18363.592 so probably was 
updated as your around mid Jan

https://docs.microsoft.com/en-us/windows/release-information/

But Corporate versions have different time table and patch

the one I have is Version 1709 Build 16299.15
It seems Corporate IT is forgetting to update it at all.

May be Takashi one is also behind in update and currently free
from the new bug/behaviour.

What I found interesting is that
https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-1909

This release had caused problems to some AV, so may be is changing
the play in area that are causing problems also to us.

Regards
Marco

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