From: Joshua Sjoding <joshua.sjoding@scjalliance.com>
To: wireguard@lists.zx2c4.com
Subject: WireGuard for Windows failed to start after update to v0.2.1
Date: Tue, 17 Nov 2020 09:46:35 -0800 [thread overview]
Message-ID: <CALaUSuvDgxsr99R2qiOrXM20btnvnaiyAx7197jfcTauOt5CTA@mail.gmail.com> (raw)
I attempted to update my WireGuard for Windows installation from 0.1.1
to 0.2.1 today. Unfortunately the service failed to restart after the
install and left me without a functional WireGuard tunnel. I'm on a
laptop running Windows 10 2004 (OS Build 19041.630).
From the Windows event logs it looks like it couldn't remove the old
wintun driver. I believe I saw some patches on the list from Marc
Becker recently that may or may not be related.
These events are from the Windows Application event log on my
computer, in order of occurrence:
----
Error, Event 1013, MsiInstaller, 11/17/2020 8:41:49 AM
Product: WireGuard -- Wintun error: Unable to remove existing driver:
The system cannot find the file specified. (Code 0x00000002)
----
Error, Event 1013, MsiInstaller, 11/17/2020 8:41:49 AM
Product: WireGuard -- Wintun error: Failed to uninstall driver: The
operation completed successfully. (Code 0x00000000)
----
Info, Event 11708, MsiInstaller, 11/17/2020 8:41:49 AM
Product: WireGuard -- Installation failed.
----
Info, Event 1033, MsiInstaller, 11/17/2020 8:41:49 AM
Windows Installer installed the product. Product Name: WireGuard.
Product Version: 0.2.1. Product Language: 1033. Manufacturer:
WireGuard LLC. Installation success or error status: 1603.
----
Joshua Sjoding
SCJ Alliance
IT Specialist
www.scjalliance.com
next reply other threads:[~2020-11-17 20:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 17:46 Joshua Sjoding [this message]
2020-11-17 20:59 ` Jason A. Donenfeld
2020-11-17 21:19 ` Joshua Sjoding
2020-11-17 21:56 ` Jason A. Donenfeld
2020-11-17 22:03 ` Jason A. Donenfeld
2020-11-17 22:05 ` Jason A. Donenfeld
2020-11-17 22:46 ` Joshua Sjoding
2020-11-18 0:05 ` Jason A. Donenfeld
2020-11-18 0:42 ` Jason A. Donenfeld
2020-11-18 13:41 ` Jason A. Donenfeld
2020-11-19 19:39 ` Joshua Sjoding
2020-11-19 20:00 ` 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=CALaUSuvDgxsr99R2qiOrXM20btnvnaiyAx7197jfcTauOt5CTA@mail.gmail.com \
--to=joshua.sjoding@scjalliance.com \
--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).