netbird could not connect after windows 11 updates

[Slava-Gll]

Describe the problem

netbird could not connect after windows 11 updates

CPU: snapdragon X elite (ARM64, running via windows translation) OS: Windows 11 24H2 latest

before the update, netbird has worked like a charm. Also netbird works fine on my other non-ARM machines(though i don't know if they are latest)

To Reproduce

1. have an ARM laptop with WIN11
2. install windows updates(KB5048162, or older, i did not update for a week or two)
3. reboot
4. try to open some webUI on my remote network(it does not work)
5. open netbird UI, try to connect(nothing happens)
6. try to open some webui on my remote subnet(it does not work)

Expected behavior

i expect netbird to connect succesefully

Are you using NetBird Cloud?

No i run a self-hosted NetBird's control plane.

NetBird version

0.33.0

NetBird status -dA output:

command hangs

Do you face any (non-mobile) client issues?

Please provide the file created by netbird debug for 1m -AS. command also hangs

Screenshots

Additional context

my relevant programs: wireguard(at most times turned off) OpenVPN Connect (at most times turned off) V2RayN (off while writing this and capturing logs)

i don't know if it has anything to do with my problem, but recently i had installed java jre8 and supermicro IPMIView20

found the log file at C:\ProgramData\Netbird client.log part(i removed sensitive information):

2024-11-30T01:20:26+03:00 INFO client/internal/connect.go:242: connecting to the Relay service(s): rels://netbird.example.com:443
2024-11-30T01:20:26+03:00 INFO relay/client/picker.go:66: try to connecting to relay server: rels://netbird.example.com:443
2024-11-30T01:20:26+03:00 INFO [relay: rels://netbird.example.com:443] relay/client/client.go:165: create new relay connection: local peerID: *****************************************, local peer hashedID: ******************************************
2024-11-30T01:20:26+03:00 INFO [relay: rels://netbird.example.com:443] relay/client/client.go:171: connecting to relay server
2024-11-30T01:20:26+03:00 INFO [relay: rels://netbird.example.com:443] relay/client/client.go:188: relay connection established
2024-11-30T01:20:26+03:00 INFO relay/client/picker.go:84: connected to Relay server: rels://netbird.example.com:443
2024-11-30T01:20:26+03:00 INFO relay/client/picker.go:58: chosen home Relay server: rels://netbird.example.com:443
2024-11-30T01:20:26+03:00 INFO client/iface/wgproxy/factory_usp.go:15: WireGuard Proxy Factory will produce bind proxy
2024-11-30T01:20:26+03:00 INFO client/internal/routemanager/manager.go:144: Routing setup complete
2024-11-30T01:20:26+03:00 INFO client/iface/device/device_windows.go:59: create tun interface
2024-11-30T01:20:41+03:00 ERRO client/internal/engine.go:365: failed creating tunnel interface wt0: [error creating tun device: Error creating interface: The device is not ready for use.]
2024-11-30T01:20:41+03:00 INFO client/iface/iface.go:220: interface wt0 has been removed
2024-11-30T01:20:41+03:00 ERRO client/internal/connect.go:266: error while starting Netbird Connection Engine: create wg interface: error creating tun device: Error creating interface: The device is not ready for use.
2024-11-30T01:20:41+03:00 INFO [relay: rels://netbird.example.com:443] relay/client/client.go:536: closing all peer connections
2024-11-30T01:20:41+03:00 INFO [relay: rels://netbird.example.com:443] relay/client/client.go:345: start to Relay read loop exit
2024-11-30T01:20:41+03:00 INFO [relay: rels://netbird.example.com:443] relay/client/client.go:544: waiting for read loop to close
2024-11-30T01:20:41+03:00 INFO [relay: rels://netbird.example.com:443] relay/client/client.go:546: relay connection closed
2024-11-30T01:20:41+03:00 WARN [relay: rels://netbird.example.com:443] relay/client/client.go:531: relay connection was already marked as not running
2024-11-30T01:20:51+03:00 INFO client/internal/connect.go:242: connecting to the Relay service(s): rels://netbird.example.com:443
2024-11-30T01:20:51+03:00 INFO relay/client/picker.go:66: try to connecting to relay server: rels://netbird.example.com:443
2024-11-30T01:20:51+03:00 INFO [relay: rels://netbird.example.com:443] relay/client/client.go:165: create new relay connection: local peerID: *******************************, local peer hashedID: ****************************
2024-11-30T01:20:51+03:00 INFO [relay: rels://netbird.example.com:443] relay/client/client.go:171: connecting to relay server
2024-11-30T01:20:51+03:00 INFO [relay: rels://netbird.example.com:443] relay/client/client.go:188: relay connection established
2024-11-30T01:20:51+03:00 INFO relay/client/picker.go:84: connected to Relay server: rels://netbird.example.com:443
2024-11-30T01:20:51+03:00 INFO relay/client/picker.go:58: chosen home Relay server: rels://netbird.example.com:443
2024-11-30T01:20:51+03:00 INFO client/iface/wgproxy/factory_usp.go:15: WireGuard Proxy Factory will produce bind proxy
2024-11-30T01:20:51+03:00 INFO client/internal/routemanager/manager.go:144: Routing setup complete
2024-11-30T01:20:51+03:00 INFO client/iface/device/device_windows.go:59: create tun interface

i think the most important part is 2024-11-30T01:20:41+03:00 ERRO client/internal/engine.go:365: failed creating tunnel interface wt0: [error creating tun device: Error creating interface: The device is not ready for use.]

i also bump this #2624, i think that Windows ARM64 build could resolve the issue.

feel free to ask any additional information