2

I've ran 6 different malware cleaners. Reset proxy settings. Reset network settings. Statically set IP Addresses. I can ping and resolve hostnames.

However, opening up web browsers Chrome, Firefox, Edge, IE, all have issues opening websites like google.com but can open some websites. Other machines work fine so I know it is locally to this machine.

I run and manage the network. The error I am getting is not a 404 but can't find the server at xxx domain. It act's like there is a proxy but all the proxy settings are not set or disabled.

C:\WINDOWS\system32>nslookup google.com 
Non-authoritative answer:

Server:  Wireless_Broadband_Router.home
Address:  192.168.1.1

Name:    google.com
Addresses:  2607:f8b0:4008:80b::200e
      216.58.219.174

Edit:

Tried a new account. No success. Set both DNS fields to Google. The system is also fully up-to-date

IS there anything else I can try to fix this?

Jason
  • 4,076

2 Answers2

1

Users around the world are reporting that they are no longer able to connect to the internet after applying a Windows Update. They receive the error ‘Wi-Fi doesn’t have a valid IP configuration’. Several ISPs around the world report about the issue and they report Microsoft is aware of the issue too. Fortunately there is a simple solution available. The British provider Virgin Media writes on its support page, “Some Windows 10 users are experiencing difficulty connecting to the internet after installing the latest update. In most cases the IP address is now starting 169…”

Users around the world lose internet connection after Windows Update (with fix)

Have a look at reserved IP address RFC 5735 under special use IPv4:

169.254.0.0/16 - This is the "link local" block. As described in [RFC3927], it is allocated for communication between hosts on a single link. Hosts obtain these addresses by auto-configuration, such as when a DHCP server cannot be found.

Why is Windows' default IP address 169.xx.xx.xx?

In other words, the update in question, is causing people systems to be unable to connect to their DHCP server.

E.V.I.L.
  • 238
0

The issue was an ISP issue. After calling them it was determined to be a problem relating to them.

Jason
  • 4,076