In a document published recently, Microsoft confirmed that the Windows 10 update issues caused by incorrect DNS settings have been fixed.
As a quick reminder, in mid-January, Windows 10 users encountered many errors while trying to update their Windows systems.
Windows consumers reported that while updating the OS , they ended up with an error. The error notified them that they were unable to connect to update server. Error was:
We couldn’t connect to the update service. We’ll try again later, or you can check now. If it still doesn’t work, make sure you’re connected to the Internet
Tech giant responded to the issue and said that it was investigating the error.
However, at that time, many claimed that this issue existed in subsequent updates as well. Other users suggested that this could be because of the botched Windows Defender.
Originally it was because of a bug in the DNS services of ISPs and this issue had hit ISPs throughout the world including BT in the UK, Comcast of the United States, and many other ISPs in Japan.
But now the issue has been fixed. Officials reported that the downstream DNS servers have been updated with the corrected DNS entries. They commented on the situation:
The Windows Update service was impacted by a data corruption issue in an external DNS service provider global outage on January 29, 2019. The issue was resolved on the same day and Windows Update is now operating normally, but a few customers have continued to report issues connecting to the Windows Update service. We expect these issues will go away as downstream DNS servers are updated with the corrected Windows Update DNS entries.
With the problem resolved, the tech giant now assures the update is available again for all the affected users.
Although Windows 10 update was broken for many users, some overcame the problem by switching to Google’s 184.108.40.206 DNS or Cloudflare’s 220.127.116.11 service.
So, if you previously failed to update Windows, you can probably do it now. Update it and let us know if you still encounter any issue while updating it.