Newest update messed up IPv6?
I hope people will understand what I’m talking about and maybe help fix it. On my Windows 7 desktop connected by Ethernet I noticed that under connections it says “IPv6 connectivity: No internet access”, and under details IPv6 DNS Server is blank. I have connectivity to IPv4 though. In case anyone is wondering what I’m talking about,you right click the Ethernet symbol in taskbar and click open network and sharing center, and then near connections you click on Local Area Connection (or Wireless Network connection if using WiFi) and under IPv6 it says No internet connectivity. I have come to conclude it’s due to the latest NIS update, which is 220.127.116.11, I believe. I checked another desktop connected by WiFi running Windows 8.1 that uses this NIS license and before I updated it IPv6 said Internet, and then when I updated it and had to restart to apply the patch, IPv6 also said “No internet access” after updating NIS and restarting. I also have a Windows 10 desktop connected to WiFi that doesn’t have NIS and just uses Microsoft’s security, and IPv6 says it has Internet on there under Network and Sharing Center, and the IPv6 DNS server isn’t blank. I even restarted it and IPv6 still says internet. Also have a Windows 8.1 laptop I don’t really use that has the third license for this NIS account, although I haven’t updated NIS on it in a year or two, and IPv6 said connected on there. I might try updating it to the latest version later just to confirm on that too, but after checking it just seems too convenient this NIS did something to IPv6 on the two desktops I updated to the latest version of. Is there a way to go back to the last version of NIS to see if it fixes it? Does IPv6 saying “no internet access” mess up anything on my computer, like the security or anything? Is it going to mess up the internet? This has been bugging me the last few days... And yes, under adapter settings IPv6 is checked. Can anyone else confirm this happened to them, too? Or is there a way to fix it or revert NIS back to an earlier version to see if it fixes it?