Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Oliver Freyermuth <freyermuth@physik.uni-bonn.de>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Windows stuck in boot after WireGuard update (switch to WireGuardNT?)
Date: Fri, 24 Sep 2021 00:14:25 -0600	[thread overview]
Message-ID: <CAHmME9o_490d9W85=A6xUFktvKuvCAsmqb2T80BNsVY8BRfd0w@mail.gmail.com> (raw)
In-Reply-To: <e0d4dcbb-b0c8-1214-ff0c-c856d168d67f@physik.uni-bonn.de>

Hi Oliver,

These came out on Tuesday, which might correspond with your timeline:
https://support.microsoft.com/en-us/topic/september-21-2021-kb5005624-os-build-18363-1830-preview-b2a3af81-696b-4d59-8d7b-a05389407bb8
https://support.microsoft.com/en-us/topic/september-21-2021-kb5005625-os-build-17763-2210-preview-5ae2f63d-a9ce-49dd-a5e6-e05b90dc1cd8

Is it possible that you installed either of these immediately before
the problem began? Post hoc ergo propter hoc, of course, but if you,
Joshua, and a third private reporter of this bug all have the same
correlation, that's interesting...

Thanks,
Jason

  parent reply	other threads:[~2021-09-24  6:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-22 10:09 Oliver Freyermuth
     [not found] ` <CAHmME9pgz6PiXdFqcRw90EafHK-Jq9RfcgLUZaJ1ARrtdnjG0w@mail.gmail.com>
2021-09-22 14:02   ` Oliver Freyermuth
2021-09-22 18:57     ` Jason A. Donenfeld
2021-09-22 19:36       ` Joshua Sjoding
2021-09-24  0:21     ` Jason A. Donenfeld
2021-09-24  7:24       ` Oliver Freyermuth
2021-09-24  6:14 ` Jason A. Donenfeld [this message]
2021-09-24 17:48 ` Jason A. Donenfeld
2021-09-24 17:53   ` Joshua Sjoding
2021-09-24 17:57     ` Oliver Freyermuth
2021-09-24 19:59   ` Jason A. Donenfeld
2021-09-24 20:15     ` Arlo Clauser
2021-09-24 20:17       ` John-Paul Andreini
2021-10-14  5:56     ` Jason A. Donenfeld

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='CAHmME9o_490d9W85=A6xUFktvKuvCAsmqb2T80BNsVY8BRfd0w@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=freyermuth@physik.uni-bonn.de \
    --cc=wireguard@lists.zx2c4.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 NNTP newsgroup(s).