All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Sjoding <joshua.sjoding@scjalliance.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Oliver Freyermuth <freyermuth@physik.uni-bonn.de>,
	 WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Windows stuck in boot after WireGuard update (switch to WireGuardNT?)
Date: Wed, 22 Sep 2021 12:36:52 -0700	[thread overview]
Message-ID: <CALaUSutA42xfnnpLcNsYvE2-XH0qGA7zUPbYKJJFQE2yq1snYA@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9rP1a5XPtHp10_M5=w_ozGysOPYAk-PJ5hhZUCRXCJmQg@mail.gmail.com>

We've seen these symptoms (infinitely spinning dots during bootup) at
least twice in the past week, but hadn't thought to link the behavior
to WireGuard. We had a third case this morning, and I can confirm that
the steps outlined by Oliver got the machine back to a bootable
condition. Thank you Oliver!

Before disabling the devices in Device Manager, we tried disabling the
WireGuard Tunnel service instead, but it still failed to boot.

The laptop that failed today is a Lenovo ThinkBook 15 G2 ITL
(20VE006UUS) laptop running Windows 10 Pro 20H2.
The laptops that failed previously are Lenovo ThinkBook 14s Yoga
2-in-1 (20WE001DUS) laptops.

We collected the WireGuard logs today while still in Safe Mode via
wireguard.exe /dumplog. I'll send those directly to the WireGuard team
off-list. We'll grab the setupapi logs as well when we get a chance
later today.

While this might be an issue with WireGuard for Windows, it's also
possible that the fault lies elsewhere, like a recent Windows update
or some other driver update. Like Oliver, we have BitLocker enabled on
these devices.

Joshua Sjoding
SCJ Alliance
IT Specialist

On Wed, Sep 22, 2021 at 12:00 PM Jason A. Donenfeld <Jason@zx2c4.com> wrote:
>
> Hi Oliver,
>
> Could you send the wireguard application log, as well as any other
> logs you find? Also \windows\inf\setupapi.*.log would help.
>
> Jason

  reply	other threads:[~2021-09-22 19:39 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 [this message]
2021-09-24  0:21     ` Jason A. Donenfeld
2021-09-24  7:24       ` Oliver Freyermuth
2021-09-24  6:14 ` Jason A. Donenfeld
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=CALaUSutA42xfnnpLcNsYvE2-XH0qGA7zUPbYKJJFQE2yq1snYA@mail.gmail.com \
    --to=joshua.sjoding@scjalliance.com \
    --cc=Jason@zx2c4.com \
    --cc=freyermuth@physik.uni-bonn.de \
    --cc=wireguard@lists.zx2c4.com \
    --subject='Re: Windows stuck in boot after WireGuard update (switch to WireGuardNT?)' \
    /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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.