From: Alexey Ivanov <alexey.ivanes@gmail.com>
To: wireguard@lists.zx2c4.com
Subject: Fwd: Wireguard for Windows breaks Task Scheduler
Date: Wed, 20 Nov 2019 08:08:50 +0300 [thread overview]
Message-ID: <CAJcUPC6YHtYy6f66+GQqsmPKMKWtiuLCx4+4VNxX9rGFFAkpjQ@mail.gmail.com> (raw)
In-Reply-To: <CAJcUPC7nXZXO6aJYMsEF3TYkLneftvH3VRNUtfVaGjWJTtkvWw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 2542 bytes --]
Im not exactly sure what wireguard doing to create virtual network adapters
in windows, but it's more looks like it can't handle deletion of them
properly.
This issue easy to reproduce:
1. Create wireguard's tunnels.
2. Connect tunnel, disconnect and remove it.
3. Repeat it multiple times.
Windows registry will be full of wrong records of these non-existed network
connections.
And now try to open Task Scheduler and click on "Create task..." it will
crash with log:
в Microsoft.Windows.ManagementUI.CombinedControls.INetwork.GetName()
> в
> Microsoft.Windows.ManagementUI.CombinedControls.UINetwork.GetUINetwork(INetwork
> network)
> в
> Microsoft.Windows.ManagementUI.CombinedControls.NetworkListManager.GetNetworkList()
> в
> Microsoft.Windows.ManagementUI.CombinedControls.ControlTaskConditions.PopulateNetworkComboBox()
> в
> Microsoft.Windows.ManagementUI.CombinedControls.ControlTaskConditions.InitializeConditions()
> в
> Microsoft.Windows.ManagementUI.CombinedControls.EditTaskDialog.InitializeView()
> в
> Microsoft.Windows.ManagementUI.CombinedControls.EditTaskDialog.Initialize(UITaskFolder
> folder, String taskName, String title, UserChoice userAction,
> BaseResultsControl inOwnerView, String inXmlText)
> в
> Microsoft.Windows.ManagementUI.CombinedControls.BaseResultsControl.CreateTask(UITaskFolder
> folder, String initialTaskName, String taskXml)
> в System.Windows.Forms.MenuItem.OnClick(EventArgs e)
> в System.Windows.Forms.MenuItem.MenuItemData.Execute()
> в System.Windows.Forms.Command.Invoke()
> в System.Windows.Forms.Control.WmCommand(Message& m)
> в System.Windows.Forms.Control.WndProc(Message& m)
> в System.Windows.Forms.ListView.WndProc(Message& m)
> в System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
> IntPtr wparam, IntPtr lparam)
>
So ive googled solution
https://answers.microsoft.com/en-us/windows/forum/all/task-scheduler-crashed/5acab7c5-eb79-48c8-876d-ade321565953?auth=1
(Programatix message)
To resolve the problem,
> Run regedit
> Go to HKLM\Software\Microsoft\Windows NT\CurrentVersion\NetworkList
> Delete everything under the following path,
> Nla->Cache
> Nla->IntranetEnabled
> Nla->Wireless
> Profiles
> Signatures->Managed
> Signatures->Unmanaged
> Reboot
>
And it actually helps.
Can wireguard just properly handle this "issue" on his own and do not break
Task Scheduler application?
[-- Attachment #1.2: Type: text/html, Size: 3239 bytes --]
[-- Attachment #2: Type: text/plain, Size: 148 bytes --]
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next prev parent reply other threads:[~2019-11-27 9:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-16 22:24 Wireguard for Windows breaks Task Scheduler Alexey Ivanov
2019-11-20 5:08 ` Alexey Ivanov [this message]
2019-11-27 10:55 ` Simon Rozman
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=CAJcUPC6YHtYy6f66+GQqsmPKMKWtiuLCx4+4VNxX9rGFFAkpjQ@mail.gmail.com \
--to=alexey.ivanes@gmail.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).