Heya folks, Ned here again. A few customers have reported this known issue on Windows 11 machines & you may see this event at boot up and perhaps occasionally afterwards. In the Event Log, in the Sys...
Updated Nov 07, 2022
Version 4.0
Blog Post
Hi! The first time this problem occurred on my machine (ASUS TUF Gaming F15 FX506GM) was three weeks ago. It appeared just before the network adapter (Intel(R) Wi-Fi 6 AX201 160MHz) reported code 43 error and internet connection was shut down. At that time I had Windows 10. Since then I've tried all solutions recommended by Microsoft and Intel on their sites and pretty much every other found elsewhere. I've even upgraded to Win 11 (desperation on my side). So far nothing seems to work in the long run. My short time solution is to run MyAsus diagnosis tool after this problem appears and then restart the laptop. After the restart these errors don't reappear.
Unfortunately they always come back the next day.
Today I've noticed 85 events just before the network adapter shut down (code 43). First event (5002, netword adapter not working properly) happened at 13:58:54 and last (2505, The server could not bind to the transport \Device\NetBT_Tcpip__{4E6EBED0-E84E-421B-94A2-FFDA1D782614 because another computer on the network has the same name. The server could not start.) was at 14:00:11.
Most events were connected to netwtw10 source, which is Intel wifi driver. I've got 22.140.0.3 version installed, but the same problems were happening with previous versions as well.