This part of your log: 2020-11-17 08:19:14.469253: [MGR] Migrated configuration from ‘C:\WINDOWS\system32\config\systemprofile\AppData\Local\WireGuard\Configurations\SCJ.conf.dpapi’ to ‘C:\Program Files\WireGuard\Data\Configurations\SCJ.conf.dpapi’ 2020-11-17 08:19:14.480225: [MGR] Migrated service command line arguments for ‘WireGuardTunnel$SCJ’ 2020-11-17 08:19:14.485210: [MGR] Starting UI process for user ‘[REDACTED_PERSON_A]@SCJ’ for session 1 2020-11-17 08:19:14.509146: [TUN] Unable to load configuration from path: open C:\WINDOWS\system32\config\systemprofile\AppData\Local\WireGuard\Configurations\SCJ.conf.dpapi: The system cannot find the path specified. 2020-11-17 08:19:14.509146: [TUN] Shutting down
Seems like it's do to a race in the migration, which this commit should fix: https://git.zx2c4.com/wireguard-windows/commit/?id=6e4e535e0c1108bbd5a3f15e273e13868f4ece20 But this part of your log: 2020-11-17 08:19:29.582424: [TUN] [SCJ] Enabling firewall rules 2020-11-17 08:19:29.746988: [TUN] [SCJ] Unable to enable firewall rules: Firewall error at golang.zx2c4.com/wireguard/windows/tunnel/firewall/helpers.go:100: The specified group does not exist. 2020-11-17 08:19:29.767930: [TUN] [SCJ] Shutting down Is extremely puzzling. I'm wondering what led to this and how you eventually appeared to fix it. Did it go away on its own without user intervention? Did you have to manually start/stop the tunnel a few times? Jason
