Earlier this month, several Windows 10 users reported issues with downloading updates from Windows Update. Microsoft had confirmed that the issue was caused by an external DNS service provider's global outage, which was fixed after a day of disruption. However, multiple user reports indicated that the problem persisted.
In a fresh update, Microsoft has today clarified that the issues have finally been resolved for all users and the problem has been "fully mitigated because the majority of local Internet Service Providers (ISP) have refreshed their DNS servers."
The company has advised users to contact their local ISP if they continue to experience any problems. Here is the complete statement:
Windows Update customers were recently affected by a network infrastructure event caused by an external DNS service provider’s global outage. A software update to the external provider’s DNS servers resulted in the distribution of corrupted DNS records that affected connectivity to the Windows Update service. The DNS records were restored by January 30, 2019 (00:10 UTC), but downstream effects continued. We believe the issue to be fully mitigated because the majority of local Internet Service Providers (ISP) have refreshed their DNS servers and customer services have been restored. If you are still encountering download failures, please contact your local ISP.
The company said that although the issue wasn't due to Microsoft services, it takes any service disruption for its customers seriously. "We will work with partners to better understand this so we can provide higher quality service in the future even across diverse global network providers," Microsoft added.
The Windows maker has been getting negative feedback for the past several months due to broken updates. This latest issue just added to the fire even though it wasn't caused by Microsoft. The company is currently working on the upcoming Windows 10 version 1903 (19H1) while the last version 1809 is still waiting to be installed on millions of machines as it had to be pulled back due to data loss issues.