public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Fork issue on W10 WOW
Date: Sat, 14 Jul 2018 22:41:00 -0000	[thread overview]
Message-ID: <87zhyt66o4.fsf@Rainer.invalid> (raw)
In-Reply-To: <c4fc080a-7b31-05d4-990c-668113477f86@gmail.com> (Marco Atzeri's	message of "Sat, 14 Jul 2018 17:41:03 +0200")

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

  reply	other threads:[~2018-07-14 17:58 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-30 17:33 Marco Atzeri
     [not found] ` <c1505248-8d03-c0b6-37ca-9c6eed2100e9@cornell.edu>
2018-07-01  8:51   ` Marco Atzeri
2018-07-08 16:03   ` Marco Atzeri
2018-07-09  9:03     ` Corinna Vinschen
2018-07-09 11:37       ` Marco Atzeri
2018-07-09 12:37         ` Corinna Vinschen
2018-07-10  5:33           ` Marco Atzeri
2018-07-12 12:34             ` marco atzeri
2018-07-14 12:46               ` Corinna Vinschen
2018-07-14 14:31                 ` Marco Atzeri
2018-07-14 17:58                   ` Achim Gratz
2018-07-14 19:03                     ` Marco Atzeri
2018-07-14 22:41                       ` Achim Gratz [this message]
2018-07-15  2:12                         ` Brian Inglis
2018-07-15  9:18                           ` Marco Atzeri
2018-07-15 13:25                             ` Achim Gratz
2018-07-15 19:33                             ` Brian Inglis
2018-07-15 23:01                             ` David Stacey
2018-07-16 18:58                               ` Marco Atzeri
2018-07-16  1:06                             ` Andrey Repin
2018-07-17 18:34                             ` Marco Atzeri

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zhyt66o4.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).