From: Simon Rozman <simon@rozman.si>
To: Richard Reiner <rreiner3@yahoo.com>,
"wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: RE: Windows client "Unable to create Wintun device"
Date: Thu, 12 Dec 2019 09:28:00 +0000 [thread overview]
Message-ID: <99D61A626FDA8A4B90A270669121BE10D0597A0F@PLANJAVA.amebis.doma> (raw)
In-Reply-To: <2078146812.1909563.1573533502212@mail.yahoo.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1731 bytes --]
Hi Richard,
I apologise for the delay. (Becoming my standard letter introduction these days. ☹)
Your error is saying that NetCfgInstanceId value did not appear in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e972-e325-11ce-bfc1-08002be10318}\<id> registry key in 10 seconds. Can you check the registry key what's going on there, please?
Also, check the event log (System and Application and Service Logs\Microsoft\Windows\DeviceSetupManager) for any errors at the time you are attempting to activate the tunnel. Maybe there's some disabled service causing interface device creation to fail?
Maybe your Windows is attempting to access Windows Update for a newer version of Wintun driver first, triggering 10 second timeout in WireGuard?
Best regards,
Simon
From: WireGuard <wireguard-bounces@lists.zx2c4.com> On Behalf Of Richard Reiner
Sent: Tuesday, November 12, 2019 5:38 AM
To: wireguard@lists.zx2c4.com
Subject: Windows client "Unable to create Wintun device"
On one of my machines, the Wireguard Windows client 0.0.35 was previously working well, but as of today whenever attempting to activate any tunnel it generates errors with log messages like:
2019-11-11 17:32:48.033: [TUN] [tun22] Unable to create Wintun device: Unable to create Wintun interface: GetStringValueWait(NetCfgInstanceId) failed: Timeout waiting for registry value
An uninstall - reboot - reinstall has not corrected this/
The affected machine has received some Windows 10 updates recently as well as a VMware Player update.
But another machine with the same software installed works fine.
Any thoughts or suggestions?
[-- Attachment #1.1.2: Type: text/html, Size: 7434 bytes --]
[-- Attachment #1.2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 4919 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
prev parent reply other threads:[~2019-12-12 9:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2078146812.1909563.1573533502212.ref@mail.yahoo.com>
2019-11-12 4:38 ` Windows client "Unable to create Wintun device" Richard Reiner
2019-12-12 9:28 ` Simon Rozman [this message]
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=99D61A626FDA8A4B90A270669121BE10D0597A0F@PLANJAVA.amebis.doma \
--to=simon@rozman.si \
--cc=rreiner3@yahoo.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).