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:from:to:subject:references:date:in-reply-to
	:message-id:mime-version:content-type:content-transfer-encoding;
	q=dns; s=default; b=TDc38qCIM9V1foL5CWMYD1WJ6YWkG45Pabrrzs2esCG
	+UBnuvErozBAJZlWLj9wSWtBwwWTokVC9bkCkiV4IeMf2/hbz2CwsG5U2AwhEUg0
	gxTe3O7ouMdYlolbrmzyzgDPnQofhySKeVvkvdYmBrVejSz3LoBxPGi5NDPYayUs
	=
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:from:to:subject:references:date:in-reply-to
	:message-id:mime-version:content-type:content-transfer-encoding;
	s=default; bh=WPQPX8f3DXyYP1VvL0ctIaDwUNI=; b=baLZ0xy/wsD+8D41e
	YqwmiY/v9d92yznWKHf7aO/doR1RdPRgS2H1UaFgUmjiHHw6A6nFTph6KvILC2Q0
	aVPovKXF3p0bvkS9nMsbJgmQRI1qljtmIuul8cFNwMJQzrpZ2aI6LOsy/8YPkSoi
	9Ui6L0oawQFXvUoOeseNOxAsIc=
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-Spam-SWARE-Status:	No, score=3.0 required=5.0 tests=AWL,BAYES_00,FOREIGN_BODY,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=no version=3.3.2 spammy=E-Mail, EMail, magazine, wurde
X-HELO:	vsmx011.vodafonemail.xion.oxcs.net
From:	Achim Gratz <Stromeko AT nexgo DOT de>
To:	cygwin AT cygwin DOT com
Subject:	Re: Fork issue on W10 WOW
References:	<7ad0e0d4-438b-33ad-a711-e0b1996fa6f6 AT gmail DOT com> <c1505248-8d03-c0b6-37ca-9c6eed2100e9 AT cornell DOT edu> <c618e65c-ab40-287d-39fb-d9daa9ef858a AT gmail DOT com> <20180709090332 DOT GC3111 AT calimero DOT vinschen DOT de> <87e94b8c-13d0-928e-957d-c32b15b8a962 AT gmail DOT com> <20180709123739 DOT GB27673 AT calimero DOT vinschen DOT de> <fd7e7ce2-84fd-aef3-b54a-0ff76ef8900c AT gmail DOT com> <CAB8Xom_DX=u0q17ewfRokh_mTcBYMppPZdDLS3UUdaPm5GMV4w AT mail DOT gmail DOT com> <20180712133847 DOT GT27673 AT calimero DOT vinschen DOT de> <c1aa10ad-e685-f232-6719-5c653f747f83 AT gmail DOT com> <874lh17txr DOT fsf AT Rainer DOT invalid> <c4fc080a-7b31-05d4-990c-668113477f86 AT gmail DOT com>
Date:	Sat, 14 Jul 2018 19:58:19 +0200
In-Reply-To:	<c4fc080a-7b31-05d4-990c-668113477f86@gmail.com> (Marco Atzeri's message of "Sat, 14 Jul 2018 17:41:03 +0200")
Message-ID:	<87zhyt66o4.fsf@Rainer.invalid>
User-Agent:	Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)
MIME-Version:	1.0
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id w6EHwcJg004161

Marco Atzeri writes:
> Nothing fancy, just vanilla fresh new
> W10 64bit Home preinstalled on HP Notebook
> German Language
> Version 1709
> Build system 16299.547

Hmmm.  That should update itself to 1803 almost the same second you let
it anywhere near a network.

Anyway, the only time I've seen similar behaviour was when some other
library was occupying the address space the systems libraries should
have occupied, and the they get some extremely random address assigned
until the next reboot.  To do this the other library must however be
loaded pretty early in the boot process.  If you wrote the mail on said
laptop, this

> Diese E-Mail wurde von AVG auf Viren geprüft.

might be an explanation for the whole thing.  AVG is well known for
intercepting things already during boot and loading a bunch of their
libraries early.  Some of it is still done even if you switch it off
completely and some changes to the registry might even survive a
deinstallation.

It sounds like you've already spent way more time with that problem than
you thought you would, but my suggestion is to try a clean boot of a
stock Windows installation.  You can install one into a VHD and
(multi-)boot into it without affecting your existing installation beyond
the space taken up by the VHD file (german magazine c't has described
both a manual way of doing that and developed a script that prepares the
VHD so that it just needs to complete the installation when first
booted).  If that works OK without your current problems, you can then
decide whether to keep a separate boot environment, trying to fix your
existing install or wiping the pre-installed Windows and doing a fresh
install on bare iron.



Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables

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

- Raw text -