This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(201.6, 63%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
I am baffled by this kirks with my Windows 10 machines.
On boot up, my Windows 10 machines (1909) almost always fails to setup IPv6 addresses from my home and office SLAAC IPv6 networks. Toggling wifi off/on with the lower right wifi icon did nothing. But manually disabling the wifi adapter in Control Panel/Network and Internet will get the adapter to successfully setup IPv6 addresses from SLAAC router adverts.
This is happening on multiple machines including but not limited to HP Spectre x360 13(2018), Surface Go, Surface Pro 7, and Surface Go 2. But non windows machines (linux, androids, and IOS devices) have no such issues.
How I can fix this?
Ran wireshark to troubleshoot and it is even more baffling.
On the computer that switches to a different AP (for example from a mobile hotspot to a wireless network), seems that the wireless adapter does not properly send icmpv6 messages out at all. On wireshark on the switching network, I can see it sending out icmpv6 router solicitation messages and getting no responses whatsoever.
On another computer that is attached to the same network, I cannot see any messages from the roaming computer, but I can router advertisement messages from the router.
So pretty obvious when the roaming computer switches network, there is something not working with the ipv6 connection on the wireless adapter as the router solicitation messages are not going out on to the network successfully.
The routers advertisement is working correctly for all android and linux devices but Windows 10 machines seems to have a real problem with it, until manually disable/enable the network adapter.
Even ipconfig /renew6 will not fix it.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Intel NIC?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(92.8, 23%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESS%3C/text%3E%3C/svg%3E)
"netsh int ipv6 reset" may help, require a reboot.
You may install Install Wireshark and check the issue.
Do I have to do netsh int ipv6 reset on EVERY BOOT? That's a work around but not a fix.
Will do wireshark when I get a chance.
Actually did the netsh int ipv6 reset and the windows 10 machines still would not automatically configure an ipv6 address based on my SLAAC.
I further noticed that this is happening and reproducible when the machines switch wireless networks (switching APs for instance, or switching from a mobile hotspot to home network). The wireless interfaces will not setup an SLAAC ipv6 address until I manually disable and re-enable the network adapters.