This is a rather fustrating problem I've been dealing with as of the last few weeks. I somewhat have a solution, but it is not one I can continue to do for several days at a time. I've had windows10 for quite a while, and I know many people had this problem when they first got win10, but none of the solutions I've found on the internet have fixed my problem. Below are the most key points to my current experience with this error.
It is a great time to be or become a network administrator! Because in many networks, you will find both IPv4 and IPv6 working together. After the hard work of learning to subnet an IPv4 network, you may find that subnetting an IPv6 network is much easier. A Packet Tracer at the end of this module will give you the opportunity to subnet an IPv6 network.
IP addresses enable resources in your VPC to communicate with each other, and with resources over the internet. Private IPv4 addresses are not reachable over the internet. To connect to your instance over the internet, or to enable communication between your instances and other AWS services that have public endpoints, you can assign a globally-unique public IPv4 address to your instance.