A6100-10000S Windows 10 v1607 IPv6 Issue

James,

Thank you for your interest.

No, unfortunately I do not own another wireless PC running Windows 10 Anniversary, 'though wouldn't that have been helpful to us both!

I still have the problem with the system properly recognizing a working internet network connection or the network that it is connected to.  I have made some headway in the last days and now believe that it is not only isolated to the IPv6 protocol.  I cannot, however, isolate the problem as originating with Windows 10 Anniversary or with the A6100 driver: I disabled the IPv6 radio and primary from my router and achieved internet connection through IPv4 only and obtained the same non-recognition of the connection.  Before doing so, I specified Private IPv6 addresses (fd00 etc.) which were not recognized as private.  My IPv4 address begins 192.168, is private, but the system thinks it is public.

I have used the Task Manager to investigate the effect of enabling those Services which are "network connection related" but which are not running on the system.  I disabled Norton Security Suite (NSS), Windows Firewall (which is under NSS control), and the firewall in my ARRIS SBG6700-AC cable modem/wireless router.  I scanned for malware and adware and found nothing.  I've run SFC and DISM, reset IP, DNS, and Winsock.  I have run all the relevant Trouble Shooters.  The Homegroup reports my issue is with the Network.  The Network Troubleshooter finds nothing actual but offers to reset my network devices (because I have disabled my on-board wireless for lack of a driver -- that's why I bought the A6100 in the first place); I did reset without resolving the issue.  I even tried to load drivers for the A6200 (more recent driver dates) series into the A6100 but they do not load.  Please note that the Win 10 1.0.0.32 drivers are identical in byte size and date as the Win 8 drivers; how can this be correct if a new driver was touted as being created for use in Win 10?  

I have noted something else unusual with Win10Anniv: there are developer features that I want to enable in the effort to fix my issues such as Device Discovery.  This separate issue has sent me down a rabbit hole of bad correction efforts.  These require the loading of a package which the system finds but cannot install.  Further, it is not listed as an app to add.  

Since it has been more that 10 days, I cannot restore Win 10 v1511, but I want to because nearly everything worked properly.  I can't update v1607 since October 8th: MS requires that the system be connected to a network to update.  MS doesn't have a download site that users can access in the alternative.  

While I cannot say for certain that the issue is with the Netgear A6100 Driver, it deserves in-house testing on the basis of this user's anecdotal experience.